Results for "TC-MIG-2016.4"
The INSPIRE Community Forum is now part of the INSPIRE helpdesk system, based on GitHub (https://github.com/INSPIRE-MIF), so please start there any new discussions.
The current platform will remain available in read only mode in its current form and URL address until 31/01/2021, then its content will be archived and then published in a different URL which will be announced when it becomes available.
Tags
ETRS89-TMzn and raster data for OI and EL in the group Elevation, Ortho & Grids
I have some doubts regarding use of valid INSPIRE coordinate reference system (CRS) especially for providing raster data for orthoimagery (OI) and elevation (EL) themes. According to Regulation No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament a...Tags: TC-RS, Map-projections, Transverse-mercator, TC-Data-provision-distribution, TC-Data-interoperability, TC-MIG-2016.4, TC-Question, TC-On-going, TC-Data-transformation, RS-transformation, TC-TG, TC-Data-specifications, TC-IR
Last updated
Clarification of the Transverse Mercator projections allowed in INSPIRE in the group Elevation, Ortho & Grids
Description Question raised by Poland about the conformance to the Coordinate reference systems mandated in the INSPIRE Implementing Rules and associated Technical Guidelines, if the country stick to its national projected coordinate reference system (national CRS PUWG 1992 (EPSG:218...Tags: TC-RS, Map-projections, Transverse-mercator, TC-Data-provision-distribution, TC-Data-interoperability, TC-MIG-2016.4, TC-On-going, TC-Dedicated-page
Last updated
Need more guidance for Elevation encoding and correct example (for ElevationGridCoverage) on the basis of GMLCOV schema in the group Elevation, Ortho & Grids
As strongly involved in IGN imagery and gridded data standardisation activity, I tried to evaluate the present INSPIRE EL DS specification, and discovered that guidance is too limited for ensuring correct implementation. I went down to 9.4.1.2. Default encoding(s) for application schema Elevation.........
Last updated
Proposals for modifications in the Technical Guidelines [SU, PD, HH] in the group Statistics & Health
The aim of this page is to gather all proposals for modifications in the Technical Guidelines that may be forwarded to the INSPIRE MIG-T MIWP-14 for endorsement and potential implementation: New featureType for StatisticalValue in Population Distribution [PD] Wrong value type of Geometry at...Tags: TC-SU, TC-PD, TC-MIG-2016.4
Last updated
Preliminary proposals for modifications of the Technical Guidelines on Land Cover and Land Use in the group Land Cover & Use
The aim of this page is to gather preliminary proposals for modifications of the Technical Guidelines on Land Cover and Land Use that may be forwarded to the INSPIRE MIG-T MIWP-14 for endorsement and potential implementation. Find below direct links to the preliminary chan...Tags: TC-LC, TC-LU, TC-Change-request, TC-MIG-2016.4, TC-MIG, TC-TG, TC-IR, TC-Dedicated-page
Last updated
Collecting proposals for change the Technical Guidelines on EL, OI, RS & GG (1st Round) in the group Elevation, Ortho & Grids
The INSPIRE Thematic Clusters facilitators have been asked to collect and evaluate the existing proposals for change the Technical Guidelines (TGs) from our thematic community, in order to propose and discuss them during the next MIG-T meeting to be celebrated in Rome, on 30th November &ndas...Tags: TC-EL, TC-OI, TC-RS, TC-GG, TC-MIG-2016.4, TC-Change-request, TC-TG, TC-Data-specifications, TC-IR
Last updated
Move guidelines on recommended MD elements "Process step" and "Data source" to common section about "Lineage" (EL & OI TGs) in the group Elevation, Ortho & Grids
Description The recommended theme-specific metadata elements "Process step" (stated in section 8.3.5) and "Data source" (stated in section 8.3.6) proposed in both TGs, Elevation and Orthoimagery, provide guidelines on how to populate such elements (useful information items ...Tags: Lineage, cross-cluster, TC-EL, TC-OI, TC-TG, TC-Data-specifications, TC-Metadata, TC-Data-quality, TC-Issue, TC-Editorial-issue, TC-MIG-2016.4, TC-Change-request, TC-On-going, TC-Dedicated-page
Last updated
Provide an ElevationGridCoverage encoding example and guidelines for identifying the Vertical CRS in the group Elevation, Ortho & Grids
Description Handling of Vertical CRS is specified at an abstract level in Section 6.2.1.4.1 - “General mechanism for the identification of the vertical CRS” of TG on EL, more concretely under “Vertical CRS linkage to Elevation grid coverages” heading and Figure 23 ...Tags: TC-EL, Elevation-grid-coverage, TC-Encoding-rule, TC-Coverage, TC-Raster, GMLCOV, CIS, TC-RS, Vertical-CRS, TC-Implementation-example, TC-MIG-2016.4, TC-Change-request, TC-On-going, TC-Data-interoperability, TC-Data-provision-distribution, TC-TG, TC-Data-specifications, TC-Dedicated-page
Last updated
Why ps:legalFoundationDate is DateTime instead of beeing Date ? in the group Biodiversity & Area Management
Hello everybody, In the ProtectedSites.XSD schemas (both version 3.0 and 4.0) the legalFoundationDate element is declared as beeing dateTime even if the element legalFoundationDate and its definition states that this is a date, as it can be seen below: <element name=&...Tags: dateTime, ps:legalFoundationDate, TC-PS, TC-MIG-2016.4, TC-Biodiversity_Area_Management, TC-Change-request
Last updated
Issues related to PS application schema in the group Biodiversity & Area Management
The aim of this page is to have a clear list of the reported issues and suggestions for the next update of the PS application schema / Technical Guidelines. Find below direct links to topic-relevant posts: legalFoundationDate (changing data type from DateTime to Date&n...Tags: TC-Data-interoperability, TC-Encoding, TC-PS, TC-Schema, TC-TG, TC-Issue, TC-Change-request, TC-MIG-2016.4
Last updated