Corrigenda

Apply Clear

Toggle_check # Status Subject Corrigendum INSPIRE document/system Discussion (link)
2649NewComplete table of http URIs for the default CRS (Issue 3)Check if there is any operative http URI for the ISA CRS (currently there is no http URI provided in EPSG). Consider to request EPSG to include it in the registry.================ Data specifications ====================, TG RS [Data specification on Coordinate reference systems]Revision of the TG document by a member of the cluster.
2648NewComplete table of http URIs for the default CRS (Issue 2)Http URI provided in the table for LAT CRS is already operative and shall be put in black text (is currently in red).================ Data specifications ====================, TG RS [Data specification on Coordinate reference systems]Revision of the TG document by a member of the cluster.
2647NewProvide an ElevationGridCoverage encoding exampleReplace the GMLCOV example currently provided in Section 9.4.1.2 – “Default encoding(s) for application schema ElevationGridCoverage (coverage data)” of TG on EL, with the following example prepared in collaboration of Thematic Cluster #3: -- See attached file -- Edit the full description of the example, replacing the text: “EXAMPLE The following is a complete RectifiedGridCoverage instance (taken from [OGC 09-146r2]), using the base type RectifiedGridCoverage defined in the OGC GML Application Schema – Coverages available from http://schemas.opengis.net/gmlcov/1.0/.” With the following text proposal: “EXAMPLE The following is a complete RectifiedGridCoverage instance showing an ElevationGridCoverage using GML multipart representation.” Note that this example shall be placed at the same level of Section 9.4.1.2 or at the level of the new subsection on “GML multipart representation” (newly proposed here - https://ies-svn.jrc.ec.europa.eu/issues/2534).TG EL [Data specification on Elevation]https://themes.jrc.ec.europa.eu/discussion/view/42326/need-more-guidance-for-elevation-encoding-and-correct-example-for-elevationgridcoverage-on-the-basis-of-gmlcov-schema
2646NewCorrection of inconsistencies/errors found in Annex E “Encoding rules for TIFF and JPEG 2000 file formats (Issue 4) - INSPIRE TG on OIPage 146: Clarification of the structure for providing XML within JPEG 2000. • In the ‘XML box’ row in table 13 “Mapping between boxes in JP2 format and GML elements”, replace the text "The place to provide GML within JPEG 2000 (see OGC standard for more details)" (placed in the final column of the row) with the text "N/A" - meaning that thix box is not to be used. • Add the following extra row at the end of table 13 “Mapping between boxes in JP2 format and GML elements” - meaning that this box is the one to be used: ASOC Box | 'asoc' | "outer" association Box for XML formatted information to a JP2 file. | Optional | The place to provide GML within JPEG 2000 (see OGC standard 05-047r3 paragraph 8.2).TG OI [Data specification on Ortho-imagery]https://themes.jrc.ec.europa.eu/discussion/view/32920/inconsistencieserrors-found-in-the-inspire-tgs-on-orthoimagery
2645NewCorrection of inconsistencies/errors found in Annex E “Encoding rules for TIFF and JPEG 2000 file formats (Issue 3) - INSPIRE TG on OIPage 144: Error when writing binary number 37 - in table 13 “Mapping between boxes in JP2 format and GML elements”. • 'bpc' ('bpcc' type - bits per component) must have the following Condition/Value: 'x000 0000 to x0100101 Component sample bit depth = value + 1. x=0 (unsigned values) x=1 (signed values)' TG OI [Data specification on Ortho-imagery]https://themes.jrc.ec.europa.eu/discussion/view/32920/inconsistencieserrors-found-in-the-inspire-tgs-on-orthoimagery
2644NewCorrection of inconsistencies/errors found in Annex E “Encoding rules for TIFF and JPEG 2000 file formats (Issue 2) - INSPIRE TG on OIPage 142: Errors in the transformation from offsets to sizes - in Table 12 "mapping between markers in JPEG2000 codestream and GML elements". • 'Xsiz' marker in JPEG2000 codestream, maps to 'doimainSet.limits.high[0] + 1' (was written ‘doimainSet.limits.high[0]’ by error). • 'Ysiz' marker in JPEG2000 codestream, maps to 'doimainSet.limits.high[1] + 1' (was written ‘doimainSet.limits.high[1]’ by error). • 'Ssiz' marker in JPEG2000 codestream, must have the following Value: 'x000 0000 to x0100101 Component sample bit depth = value + 1. x=0 (unsigned values) x=1 (signed values)' TG OI [Data specification on Ortho-imagery]https://themes.jrc.ec.europa.eu/discussion/view/32920/inconsistencieserrors-found-in-the-inspire-tgs-on-orthoimagery
2643NewRenumber Annex E “Encoding rules for TIFF and JPEG 2000 file formats - INSPIRE TG on OIPage 128: Annex E “Encoding rules for TIFF and JPEG 2000 file formats” must be renumbered to Annex F, because there is a previous Annex E in the TG on OI (“Data structure examples”). TG OI [Data specification on Ortho-imagery]https://themes.jrc.ec.europa.eu/discussion/view/32920/inconsistencieserrors-found-in-the-inspire-tgs-on-orthoimagery
2642NewRemove missing reference in TG GGRemove the sentence with the reference bookmark error in Section 5.3 "Modelling of grids" (page 15): It has a reference to an 'Appendix 1' existing in previous versions of the document. This Appendix 1 was deleted in the current version of the TG, because it was meaningless. It is proposed to remove the full sentence: "Error! Reference source not found. contains template application schema for Discrete Surface Grid Coverage (from [ISO 19129])".TG GG [Data specification on Geographical grid systems]Revision of the TG document by a member of the cluster.
2641NewCorrection of typo in TG GGCorrect the typo in Section 5.2.2.1 of the TG (page 10): where we read "all the themes with similar needs makes use of the same geographical grid" we shall read "all the themes with similar needs make use of the same geographical grid".TG GG [Data specification on Geographical grid systems]Revision of the TG document by a member of the cluster.
2602NewProvide guidelines for identifying the Vertical CRS1) Add the following guideline at the end of Section 5.5.1.2.4 – “Attribute ElevationGridCoverage::rangeType”: • Quantity::referenceFrame attribute Identification of the vertical CRS used for referring the elevation values, which shall be always specified. 2) In Section 6.2.1.4.1 of TG on EL: • Add the following NOTE at the end of the text under heading “Vertical CRS linkage to Elevation 2.5D vector data and TIN models”: "NOTE: The Coordinate Reference System association (‘CRS’ role) is implemented in GML by the 'srsName' property from geometric objects types - From OGC 07-036 GML, D.2.3.2 Geometry root (page 277): “'GM_Object' is represented by the 'AbstractGeometry' object element, the 'CRS' role is represented by the 'srsName' property.”" • Add the following NOTE at the end of the text under heading “Vertical CRS linkage to Elevation 2D vector data with the elevation property attribute”: "NOTE: The Coordinate Reference System association (‘CRS’ role) is implemented in GML by the 'srsName' property from the coordinate list - From OGC 07-036 GML, D.2.3.4 Coordinate geometry (page 283): “'DirectPosition' is represented in GML as a type with simple content where the 'coordinate' attribute is mapped to a list of doubles. The 'coordinateReferenceSystem' role is represented by a 'srsName' attribute property and 'dimension' is represented by an optional attribute property of the same name (type is positiveInteger).”" • Add the following NOTE at the end of the text under heading “Vertical CRS linkage to Elevation grid coverages”: "According Requirement 13 of OGC 09-146r2 GML Application Schema Coverages (GMLCOV), “A coverage of type ‘RectifiedGridCoverage’ shall have a domain that is a ‘gml:RectifiedGrid’ geometry”, and this geometry is restricted to 2 dimensions in this specification. Hence, the Coordinate Reference System association (‘CRS’ role) is implemented in GML / GMLCOV by: • For specifying the horizontal CRS: the 'srsName' property from ‘gml:RectifiedGrid’. • For specifying the vertical CRS to which the elevation values in the ‘rangeSet’ of the coverage are referenced: the ‘referenceFrame’ property from the ‘swe:Quantity’ element (defined in OGC 08-094r1 SWE Common Data Model), as part of the 'rangeType' component of the coverage - as already stated in Section 5.5.1.2.4 of this specification." TG EL [Data specification on Elevation]https://themes.jrc.ec.europa.eu/discussion/view/42326/need-more-guidance-for-elevation-encoding-and-correct-example-for-elevationgridcoverage-on-the-basis-of-gmlcov-schema
2600NewTHEME Minerals: proposed changes to codelistsSummary of proposed changes, classification-method-used (ClassificationMethodUsedValue) One term modification commodity (CommodityCodeValue) Major modification – new code list has been created, evaluated and adopted by CCI/GWTG and Minerals4EU project Three hierarchy changed 30.10.2015 GTWG decision - 1. Scandium to metal 2. Europium from LREE to HREE 3. Gadolinium from LREE to HREE end-use-potential (EndusePotentialValue) Major modification – new code list has been created, evaluated and adopted by CCI/GWTG and Minerals4EU project exploration-activity (ExplorationActivityTypeValue) Major modification – new code list has been created, evaluated and adopted by CCI/GWTG and Minerals4EU project exploration-result (ExplorationResultValue) Major modification – new code list has been created, evaluated and adopted by CCI/GWTG and Minerals4EU project mineral-deposit-group (MineralDepositGroupValue) Major modification – new code list has been created, evaluated and adopted by CCI/GWTG and Minerals4EU project mineral-deposit-type (MineralDepositTypeValue) New code list has been created and proposal to MR TG, evaluated at Minerals4EU project mineral-occurrence (MineralOccurrenceTypeValue) Some modification – new code list has been created, evaluated and adopted by CCI/GWTG and Minerals4EU project mining-activity (MiningActivityTypeValue) Major modification – new code list has been created, evaluated and adopted by CCI/GWTG and Minerals4EU project processing-activity (ProcessingActivityType) Major modification – new code list has been created, evaluated and adopted by CCI/GWTG and Minerals4EU project reserve-assessment-category (ReserveCategoryValue) One term modification resource-assessment-category (ResourceCategoryValue ) One term modification earth-resource-expression(EarthResourceExpressionValue) New code list for Mineral Resource TG Value earth-resource-form (EarthResourceFormValue) New code list for Mineral Resource TG Value earth-resource-material-role (EarthResourceMaterialRoleValue) earth-resource-shape (EarthResourceShapeValue) New code list for Mineral Resource TG Value environmental-impact (EnvironmentalImpactValue) New code list for Mineral Resource TG Value raw-material-role (RawMaterialRoleValue) New code list for Mineral Resource TG Value UNFC (UNFCValue) New code list for Mineral Resource TG Value waste-storage (WasteStorageTypeValue) New code list for Mineral Resource TG Value Detail of proposed changes: Please see the uploaded document (INSPIRE_MIG_proposal_Minerals4EU.docx) for details of the proposed changes. Within chapter 5 a detailed comparison of the code list values of INSPIRE Mineral Resources and CGI vocabulary is presented. The first paragraph of the each detailed section (in chapter 5) have an official proposal from Minerals4EU project to INSPIRE MIG modify INSPIRE code lists as implemented in “Minerals Intelligence Network for Europe – Minerals4EU”. The column “Mapping advice” gives information about the submission procedure within INSPIRE. Additionally agreed terms will be provided for the use to all users of the INSPIRE infrastructure by proposing them to be included in the INSPIRE Registry. If accepted by the INSPIRE MIG, the proposed values will be marked according to the ISO 19135, e.g. retired, superseded or submitted as described in Chapter 1. RegistryProject website: https://vyvi-some2.vy-verkko.fi/gtk/Minerals4EU Document location: Folder: Minerals4EU/Work Package 5/All documents
2597NewHarmonise extensibility of code listsAn harmonisation of the extensibility used in the codelists is needed, given the misalignments present among Technical Guidelines, Implementing Rules, UML models, Registry. This issue has been reported for the INSPIRE Environmental Monitoring Facilities but it could be present in other themes. In case of EMF, the extensibility should be defined as "none", as described in the UML model and the values be included in the INSPIRE Registry. IR ISDSS [Implementing Rules for Interoperability of Spatial Data Sets and Services], TG EF [Data specification on Environmental monitoring facilities]https://themes.jrc.ec.europa.eu/discussion/view/34147/extensibility-of-code-lists-in-inspire-ef
2596NewHow to manage the transition from a Sites of Community Importance (SCI) designation type to a Special Areas of Conservation (SACs) designation type
2595NewDesignationSchemaValue: need to aware of exisiting validation processes
2594NewHow to handle geometries with multiple designations
2593NewWrong value type of Geometry attribute in StatisticalGridCell [SU]Change value type for Geometry of StatisticalGridCell from GM_Polygon to GM_Surface. (note: in the implementing rules the type is correct - GM_Surface, so only the TG need a correction)TG SU [Data specification on Statistical units]https://themes.jrc.ec.europa.eu/pages/view/52526/wrong-value-type-of-geometry-attribute-in-statisticalgridcell-su
2592NewEndorsing ELF extensions within INSPIREhttp://elfproject.eu/documentation/specification/elf-data-specifications
2591NewNew featureType for StatisticalValue in Population Distribution [PD]Introducing another featureType in the PD model for StatisticalValue that would acquire geometry from aStatisticalUnit would solve the problem with feature access and usability of GML files.IR ISDSS [Implementing Rules for Interoperability of Spatial Data Sets and Services], TG PD [Data specification on Population distribution – demography]https://themes.jrc.ec.europa.eu/pages/view/52478/new-featuretype-for-statisticalvalue-in-population-distribution-pd
2590NewGN - Revise code list for attribute "type" of feature type NamedPlacehttps://themes.jrc.ec.europa.eu/file/view/53698/list-of-change-proposals-for-technical-guidelines-for-topographic-and-cadastral-reference-data
2589New9.2 Encoding
2588NewPortrayal - Align definition of style description unitshttps://themes.jrc.ec.europa.eu/discussion/view/17602/points-or-pixel-align-definition-of-style-description-units
2587NewTN Road - Description of attribute direction to be correctedhttps://themes.jrc.ec.europa.eu/discussion/view/39225/editorial-error
2586NewTN Rail - Remove duplicate attribute "fictitious" in TN-Rail xml schemahttps://themes.jrc.ec.europa.eu/discussion/view/26968/remove-duplicate-attribute-fictitious-in-tn-rail-xml-schema
2585NewTN Road - Introduce additional attribute for harmonised functional road classhttps://themes.jrc.ec.europa.eu/discussion/view/12866/harmonization-of-functional-road-class-at-eu-level
2584NewUpdate the INSPIRE Networkhttps://themes.jrc.ec.europa.eu/discussion/view/13413/update-of-the-inspire-network-model

1 2 3 4 (1-25/81) Per page: 25, 50, 100

Also available in: Atom CSV PDF