Joint Nordic Implementation test project
-
Upload
oscar-gordon -
Category
Documents
-
view
21 -
download
0
description
Transcript of Joint Nordic Implementation test project
![Page 1: Joint Nordic Implementation test project](https://reader035.fdocuments.net/reader035/viewer/2022072013/56812be6550346895d90631b/html5/thumbnails/1.jpg)
2001-03-07 Joint Nordic test, Lisbon, Kristina Essén
1
Joint Nordic Implementation test project
• Denmark
• Finland
• Iceland
• Norway
• Sweden
http://www.statkart.no/standard/jnip/
![Page 2: Joint Nordic Implementation test project](https://reader035.fdocuments.net/reader035/viewer/2022072013/56812be6550346895d90631b/html5/thumbnails/2.jpg)
2001-03-07 Joint Nordic test, Lisbon, Kristina Essén
2
Joint Nordic Implementation test project
Phase 2Transfer of data
ISO 19118
Phase 1 Application schema ISO 19100
![Page 3: Joint Nordic Implementation test project](https://reader035.fdocuments.net/reader035/viewer/2022072013/56812be6550346895d90631b/html5/thumbnails/3.jpg)
2001-03-07 Joint Nordic test, Lisbon, Kristina Essén
3
19108 Temporal schema
• 19109 states that 19108 shall be used for temporal attributes
• 19103 defines basic datatypes - e.g. Date, DateAndTime
Change in 19109 to allow use of basic datatypes from 19103
![Page 4: Joint Nordic Implementation test project](https://reader035.fdocuments.net/reader035/viewer/2022072013/56812be6550346895d90631b/html5/thumbnails/4.jpg)
2001-03-07 Joint Nordic test, Lisbon, Kristina Essén
4
19108 Temporal schema• The UML-model in 19108 requires an explicit
association between TM_Position and TM_ReferenceSystem
• In the text it is written that TM_Position & TM_Refsys only needed when other than Gregorian calendar and UTC
Improve writing in 19108 about TM_Position & TM_ReferenceSystem
![Page 5: Joint Nordic Implementation test project](https://reader035.fdocuments.net/reader035/viewer/2022072013/56812be6550346895d90631b/html5/thumbnails/5.jpg)
2001-03-07 Joint Nordic test, Lisbon, Kristina Essén
5
ISO 19115 Quality model
Can be shared by many DQ_
Meas ure-objects and be
standardiz ed."domainOfMeas ure" is d ivided into
type- and uni t-OfMeas ure
DQ_Com pleteness DQ_LogicalC onsistency DQ_Pos itionalAccurac y DQ_ThematicAcc uracy DQ_TemporalAc curacyDQ_Additional
additionalSubelement : DQ_Additional Information
DQ_Com pletenessO mission
DQ_Com pletenessC omiss ion
DQ_Com pletenessAddi tional
additionalSubelement : DQ_Additional Information
DQ_ConceptualConsistenc yDQ_Dom ainCons is tency
DQ_Topologic alConsistenc y
DQ_Abs oluteEx ternalPosi tionalConsistenc y
DQ_FormatC onsistency
DQ_Abs oluteEx ternalPosi tionalAccurac y
DQ_GriddedDataPosi tionalPosi tionalAc curac y
DQ_RelativeInternalPos itionalAcc uracy
DQ_Pos itionalAccurac yAddi tional
additionalSubelement : DQ_Additional InformationDQ_ThematicClas si fic ationC orrec tness
DQ_NonQuanti tativeAttributeAcc uracyDQ_Quanti tativeAttributeAcc uracy
DQ_ThematicAcc uracy Additional
additionalSubelement : DQ_Additional Information
DQ_Accurac yOfATim eMeas urement
DQ_TemporalCons istency
DQ_TemporalValid ity
DQ_TemporalAc curacy AdditionaladditionalSubelement : DQ_Additional Information
Subtyping c an be done in d ifferent ways, this is
eas y to im plem ent (no parametrizedClas ses).MD_Metadata
MD_Usage
LI_Lineage
DQ_DataQuali ty
sc ope : DQ_Scope
0..*0..*0..*
+us age0..*
0..1
DQ_Meas ureD ata
nameOfMeas ure[0..1] : CharacterStringvalueTy peOfMeas ure[0..1] : TypeName
valueUni tOfMeasure[0...1] : UnitOfMeas ure
desc ription[0..1] : CharacterStringevaluationProcedure[0..1] : CI_Ci tation
DQ_LogicalC onsistency Additional
additionalSubelement : DQ_Additional Information
dateTimes: alway s aDateTim e, can be a
range of tim es .
DQ_OverviewElem entinform ation : CharaterString
0..*
+overv iewElement
0..*
DQ_Additional Inform ation
name : CharacterString
desc ription : CharacterString
11 +additionalOverviewElem ent
0..1+lineage
DQ_Quanti tativeR esul t
va lueDom ain[0..1] : RecordType
res ul t[1..*] : Rec ord
DQ_ElementSubElement
dateTimes[1..*] : DateTimeconfResul[0..1] : DQ_Conformanc eResult
0..*0..*
*1 *1
1
+ quantResult
1
Additonal elementsCommon descriptors”
![Page 6: Joint Nordic Implementation test project](https://reader035.fdocuments.net/reader035/viewer/2022072013/56812be6550346895d90631b/html5/thumbnails/6.jpg)
2001-03-07 Joint Nordic test, Lisbon, Kristina Essén
6
ISO 19107 Spatil & 19106 Profile • A profile needed: instantiable, restricts, extends
Specify what is allowed in a profile
-- A PortEdge has no -- nodes associated -- with it, e.g., self.port == NULL-- A PortEdge can have zero lengthLength > = 0-- Can be used for connecting "ferry berths" where --NT_PortEdge is the "ferry service"
NT_Element
- gen : Generalize
NT_Network
NT_Overlaps
assocPoint : GM_Point = NULL0..* 10..* 1
comElements
0..*
1
+overLaps
0..*
1
1
+overLapsWith
1
NT_NodeNT_Edge
- Length : meter0..*2
+primitive
0..*
+boundary
2
NT_PortEdgeNT_Port
- RelativPos : GM_Position
0..1
0..*
+connectsTo
0..1
+port
0..*
0..*2
+primitive
0..*+boundary
2
specialises
![Page 7: Joint Nordic Implementation test project](https://reader035.fdocuments.net/reader035/viewer/2022072013/56812be6550346895d90631b/html5/thumbnails/7.jpg)
2001-03-07 Joint Nordic test, Lisbon, Kristina Essén
7
19109 Rules for appl. schema
• The role of GFM unclear • Model in UML and not following the ”main rules”
in 19109 - A RISK!
TP_Node
NT_NodeX: TM_Period
E.g.
![Page 8: Joint Nordic Implementation test project](https://reader035.fdocuments.net/reader035/viewer/2022072013/56812be6550346895d90631b/html5/thumbnails/8.jpg)
2001-03-07 Joint Nordic test, Lisbon, Kristina Essén
8
Some conclusions Joint Nordic implementation project - phase 1
• Useful
• Complex
• Harmonize ISO 19100
• Need more specific models