Presentation is loading. Please wait.

Presentation is loading. Please wait.

Discovery Metadata. Currently Discovery Metadata is in two locations Clause 12 Appendix Contains similar information.

Similar presentations


Presentation on theme: "Discovery Metadata. Currently Discovery Metadata is in two locations Clause 12 Appendix Contains similar information."— Presentation transcript:

1 Discovery Metadata

2 Currently Discovery Metadata is in two locations Clause 12 Appendix Contains similar information

3 Discovery Metadata At the S-101 Stakeholders forum in March, it was proposed that the following should also be considered for discovery metadata: A way to digitally check for the correct Feature Catalogue and Portrayal Catalogue version The ability to insert a corrected through field that would inform the mariner and port state control which notice to mariner the ENC was corrected to.

4 Proposed Discovery Metadata NameCardinalityValueTypeRemarks dataSetDiscoveryMetadata--- metadataFileIdentifier1CharacterString metadataPointOfContact1CI_ResponsibleParty metadataDateStamp1Date metadataLanguage1 EnglishCharacterStringAll data sets conforming to S-101 PS must use English language fileName1CharacterStringDataset file name filePath CharacterString Full path from the exchange set root directory abstract1CharacterStringShort description of the area covered by the dataset. For example, harbor or port name, or area between two named locations.

5 Proposed Discovery Metadata purpose1 {1} to {4}CharacterString1. New, 2. New Edition, 3. Update, 4. Cancellation specificUsage1 {1} to {3}CharacterStringNavigation purpose for cataloging. 1. Ocean Passage, 2. Coastal, 3. Port Entry editionNumber1CharacterStringWhen a data set is initially created, the edition number 1 is assigned to it. The edition number is increased by 1 at each new edition. updateNumber1CharacterStringUpdate number 0 is assigned to a new data set. updateApplicationDate0..1Date issueDate1Date productSpecificationEditi onNumber 1 S-101 product Specification edition number editionNumberS-1001Edition of S-100 that the product specification is based on producingAgency1CI_ResponsibleParty dataProtection1{1} to {2}CharacterString1. Encrypted 2. Unprotected

6 Proposed Discovery Metadata displayScale1 {1} to {13} doubleDisplay scale must be one of the 13 predefined in clause 3 – Spatial Resolution. horizontalGeodeticDat um 1CharacterString verticalDatum1CharacterString soundingDatum 1 CharacterString boundingBox1EX_GeographicBounding Box boundingPolygon1EX_BoundingPolygon comment0..1CharacterString cyclicRedundancyChec k 1NonNegativeInteger layerId1..*DoubleIdentifies the relationship to other layers that are required to view the complete data set.

7 Proposed Additional Fields NameCardinalityValueTypeRemarks featureCatalogueVersion1CharacterStringVersion of the S-101 Feature Catalog that is in use with this product specification. potrayalCatalogueVersion1CharacterStringVersion of the S-101 Portrayal Catalog that is in use with this product specification updateCorrection1CharacterStringNotice to Mariner that the update corrects the ENC through. This would be used for port state control to verify if the ENC is up-to-date to notice to mariner items. compressionFlag1{1} to {2}CharacterString1.Yes 2.No algoritymMethod1CharacterStringZIP, RAR, etc. sourceMedia1 replacedData1If a data file is cancelled is it replaced by another data file dataReplacementCell name

8 Decisions for Consideration Combine the content of both tables and place in Clause 12 – metadata. This will make maintenance easier Review the proposed combined table to ensure that what is currently documented is correct. Review and approve the proposed additions to the discovery metadata. Propose additional fields for other types of metadata.

9

10 Discussion questions Should TSMAD/DIPWG use the language in the IEC VDR specification in regards to support file formats or should S-101 specify file types. The IMO VDR states the following: The software should be compatible with an operating system available with commercial-off-the-shelf laptop computers and where nonstandard or proprietary formats are used for storing the data in the VDR, the software should convert the stored data into open industry standard formats.

11 Discussion questions If file types are specified, what formats should be supported to make S-101 future proof? Text HTML Audio Video What are the appropriate Audio and Video Formats?

12 Discussion Questions In regards to support file management, should S-101 specify the implementation or just specify that redundant files are deleted?

13 Discussion Questions What information regarding support files needs to go into the S-101 Discovery Metadata and S-101 Catalogue file?

14

15 Background At CSMWG 18 it was suggested that simplified symbology has very little acceptance by the mariner at the following options should be explored: Option a) delete simplified symbols Option b) delete simplified symbols and redefine traditional symbols as coloured Option c) declare simplified symbols as a voluntary option It was also suggested that Colour Palattes be investigated also

16 Background Additionally, NOAA also asked a question regarding the display of M_QUAL and CATZOC

17 Background Approximately every year NOAA conducts a user survey that reaches the following groups: AMERICAN PILOTS ASSOCIATION1,200 MEMBERS LOCAL PORT AUTHORITIES40 LOCATIONS MASTER AND MATES UNION3,000 MEMBERS US POWER SQUADRON6,000 NAMED CHART USERS US COAST GUARD AUXILIARY 3,000 NAMED CHART USERS US COAST GUARD1,400 NAMED CHART USERS US NAVY300 US SHIPS AMERICAN WATERWAYS ORGANIZATIONNAMED OPERATORS TUG AND BARGE COMPANIES5,000 TUG BOATS WORKBOAT COMPANIES100 COMPANIES LAKE CARRIERS ASSOCIATION12 COMPANIES

18 Q.19 IF HYDROGRAPHIC SURVEY QUALITY AREAS COULD BE PORTRAYED WITH THE STARRED SYMBOL OR THE YEAR OF THE SURVEY AND THE ZONE OF CONFIDENCE (CATZOC). WHICH OF THESE DO YOU PREFER?

19

20 Q.20 THERE ARE TWO TYPES OF ECDIS BUOY SYMBOLOGY – TRADITIONAL AND SIMPLIFIED. WHICH OF THESE DO YOU PREFER?

21

22 Q.20B) HOW OFTEN DO YOU NAVIGATE AT NIGHT?

23 Q.20A) WHICH ECDIS COLOR PALETTE DO YOU PREFER TO USE TO NAVIGATE AT NIGHT?

24

25 Questions Should Simplified Symbols be retained for S-101? What is the benefit that S-101 will gain from reducing the number of palattes?

26

27 Discussion Questions How are the SI and SD datasets related? How does one ensure that an SI feature doesnt exist in an SD dataset or vice versa?

28 Discussion Questions How will portrayal work? Portrayal of SI and SD data together Portrayal of one area that has SI and SD data adjacent to an area that does not

29 Discussion Questions How will distribution work?

30 Discussion Questions How will updates work? Sometimes an update will affect both SI and SD data – are they packaged together and released simultaneously. What happens if the end user only gets updates to the SI data and not the SD data?

31 Discussion Questions Would TSMAD consider multiple SI cells by different themes? Eg. An SI cell that contains only TSS information and a SI cell that contains Aids to Navigation. These would have to be related in some way. Can the same association cover two different datasets?

32 Discussion Questions Can the perceived benefits be achieved in another way?

33

34 Consistency ISSUEIn S-101Comment Compilation Scale versus Display Scale YesThis is now set as spatial resolution and is aligned with the standard RADAR ranges. Need to consider changing CSCL to DSCL (Display Scale) in the 8211

35 Consistency ISSUEIn S-101Comment Guidance on the use of M_CSCL NoDoes TSMAD need to mandate this

36 Consistency ISSUEIn S-101Comment USAGE Band Assignment NoUsage bands are to be utilized for catalogue purposes only and will not have a display scale attached Need to be harmonized in the discovery metadata.

37 Consistency ISSUEIn S-101Comment SCAMINYesSCAMIN that is now in S-65 will be incorporated into S-101. Recommendation for which section?

38 Consistency ISSUEIn S-101Comment Data Inconsistencies across usage bands NoHow does TSMAD prevent this?

39 Consistency ISSUEIn S-101Comment Contour IntervalsNoMandate that contour intervals align with S-4 * *the United States(NOAA) objects

40 Consistency ISSUEIn S-101Comment Inconsistent Depiction and misalignment of data at cell boundaries NoCan S-101 fix this or is this encoding guidance?

41 Consistency ISSUEIn S-101Comment Inconsistent Depiction of Data within a cell NoCan S-101 fix this or is this encoding guidance?

42 Consistency ISSUEIn S-101Comment Holes in Data coverage YesThis should be resolved by the new display scales.

43 Consistency ISSUEIn S-101Comment Use of CATZOC in M_QUAL NoPossibly remove unassessed as an allowable enumeration

44 Consistency ISSUEIn S-101Comment Data Gaps and overlaps NoNeed to establish rules for the handling of gaps and overlaps.

45 Consistency ISSUEIn S-101Comment Strengthening Encoding Rules in the UOC YesIntention is to Mandate

46 Even more outstanding issue/questions that need to be answered….

47 Aggregated Feature Types S-101 Section S-101 Section Header S-101 Text and/or IssueS-101 Questions 4.3.4Aggregated Feature Types Features with a use type of aggregated can have multiple associations to other feature types. They also are defined in the Feature Catalogue. All association or aggregation relationships using collection features are assumed to be peer to peer. The Relationship Indicator [RIND] subfield of these collection feature records must be {3} = peer. The use of these named aggregations is described in the Data Capture and Classification Guide. At TSMAD 19 – It was pointed out that the highlighted portion is not correct. What is correct for this section?

48 ENC Data Set S-101 Section S-101 Section Header S-101 Text and/or IssueS-101 Questions 4.6ENC Data SetAn data set is a collection of geo-referenced cells containing geographic features that are used to fully describe the physical marine environment for the safe passage of vessels. Is this clause needed? As S-101 is more specific in clause Datasets?

49 Cells S-101 Section S-101 Section Header S-101 Text and/or Issue S-101 Questions 4.7CellsFeatures with the geometric properties of point or line coincident with the border of two cells within the same layer and with the same display scale must be part of only one cell. What is the intent of the phrase within the same layer? Can this be removed?

50 Geometry S-101 Section S-101 Section HeaderS-101 Text and/or IssueS-101 Questions 4.9GeometryThe following is currently stated in S-101: The underlying geometry of an will be constrained to S-100 level 3a which supports 0, 1 and 2 dimensional objects (points, curves and surfaces). The third dimension is expressed as an attribute of a feature. Is this also valid for soundings? If so, TSMAD needs to explicitly state this.

51 Geometry S-101 Section S-101 Section HeaderS-101 Text and/or IssueS-101 Questions 4.9GeometryDespite the saving in data volume offered by the use of arcs/curves, the disadvantages are such (e.g. during updating, generating warnings/alarms) that they must not be used for ENC. How does this fit in with the use of GM_Curve in the Figure and curves in the previous issue above? S-101 Work Item Leader recommendation: Remove this paragraph as S-101 is only to state what is allowed, but need to explain the use of GM_Curve.

52 Units of Measure S-101 Section S-101 Section Header S-101 Text and/or IssueS-101 Questions 5.4Units of MeasureUnits to be used in an ENC: Position: latitude and longitude in decimal degrees (converted into integer values). Depth: metres. Height: metres. Positional accuracy: metres. Distance: nautical miles or metres. Time: seconds. Bearings: decimal degrees. Is this correct? What about angular measure?

53 Positions S-101 Section S-101 Section Header S-101 Text and/or IssueS-101 Questions 5.4.1PositionsPositions are in WGS84 and coordinates are held in the Data Set Structure Information field under coordinate multiplication factor for X, Y and Z coordinate. Coordinates must be held in production systems at a resolution of (10 -7 ) and the coordinate multiplication factor value should be set to (10 7 ) for all cells. This is what is currently in S-101. COMF has been divided into three fields for X,Y and Z. The question is where does S-101 specify the resolution: a.In the main body of the product spec b.In the 8211 In addition, is the spatial resolution the same for X,Y, and Z?

54 Depths S-101 Section S-101 Section Header S-101 Text and/or IssueS-101 Questions 5.4.2DepthsDepths are converted from decimal meters to integers by means of the 3- D (Sounding) Multiplication Factor. Soundings are never encoded with a resolution greater than one decimetre, so the value of sounding multiplication factor must be 10. For update cells, Coordinate Multiplication Factor [X], [Y] and the 3-D (Sounding) Multiplication Factor [Z] will not be present. In this case, the values from the original base cell should be used. How do we state this for Depths as the second paragraph is no longer a valid statement. COMF has been split into CMFX, CMFY, and CMFZ.

55 Data Maintenance S-101 Section S-101 Section HeaderS-101 Text and/or IssueS-101 Questions 8Data MaintenanceIs what is in this section enough, does TSMAD need to add more. How do S-58 validation checks fit into S-101?

56 Implementation S-101 Section S-101 Section HeaderS-101 Text and/or IssueS-101 Questions 11.1ImplementationThe binary implementation of S 101 must be used for ENC. Therefore, the Implementation [IMPL] subfield of the Catalogue Directory [CATD] field must be set to BIN for the data set files. Where is this actually set? Is this still needed? If so, is it needed in the 8211 or in the main part of the PS.

57 ENC Cell Naming S-101 Section S-101 Section HeaderS-101 Text and/or IssueS-101 Questions ENC cell namingWhat needs to go into the cell name? Does TSMAD need to limit it to 8 characters? At the S-101 Stakeholders meeting there was thought to including the display scale in the name for cataloguing purposes?

58 S-101 Section S-101 Section Header S-101 Text and/or IssueS-101 Questions New Editions and Updates This section describes how the standard encoding defines updating methodologies for cells. In order to ensure that feature type updates are incorporated into an ECDIS in the correct sequence without any omission, the file extension and a number of other parameters encoded in the data are used in the following way: file extension every new data set or new edition must have a.000 extension as per the translation from EDTN to the file extension. For update cell files the extension is the value of the UPDN field, ranging from.001 to.999. These numbers must be used sequentially, without omission. Number.001 is the first update after a new data set or a new edition. edition number when a data set is initially created, the edition number 1 is assigned to it. The edition number is increased by 1 at each new edition. update number update number 0 is assigned to a new data set. The first update cell file associated with this new data set must have update number 1. The update number must be increased by one for each consecutive update, until a new edition is released. The new edition must have update number 0. In the case of an update cell file the file extension is the same as the update number. update comment comment for describing the change introduced by an update. issue date date up to which the data producer has incorporated all applicable changes. In order to cancel a data set, an update cell file is created for which the edition number must be set to 0. This message is only used to cancel a base cell file. Where a cell is cancelled and its name is re used at a later date, the issue date must be greater than the issue date of the cancelled cell. Maintenance of support files is described in S-100. In this section, a small workgroup added the update comment field that describes the change added by the update. There are also outstanding issues on how to update support files that need to be discussed.


Download ppt "Discovery Metadata. Currently Discovery Metadata is in two locations Clause 12 Appendix Contains similar information."

Similar presentations


Ads by Google