-
Dear colleagues,
your CSW interface (https://inspire-geoportal.ec.europa.eu/srv/ger/csw?REQUEST=GetCapabilities&VERSION=2.0.2&SERVICE=CSW) don't work as expected. Can you check your geonetwork conf…
-
PT appears to have consensus that scope of 19115-2 is broader than 'imagery'. Now is the time to resolve this.
-
Is '2013' a valid value for the 'gco:DateTime' element? When I transformed an old ISO file to the new 19115-1 standard and validated it with the new schema, I got an error stating that this is not a v…
-
Add a GEMINI sub-element equivalent to LI_Lineage.source, in order to provide a better way for a dataset that is derived from other datasets to acknowledge its sources.
This may require redefining th…
-
Suggested at OGC API - Records code sprint in September 2022.
The OGC API - Records developers suggest standardising a JSON encoding of at least a subset of ISO 19115.
Some felt the encoding sho…
-
Justification: It has been brought forward by XMG that the xsd files as they associate to part 3, all four of the XSD files have miss-ordered elements, some worse than others
Proposal: Discussion…
-
## User Story
In order to understand what information harvester 2.0 is responsible for processing, datagov wants to define the supported spatial metadata standards of harvester 2.0
## Acceptance Cri…
-
I recently translated and reviewed 19111 and found a few errors. I'm being cautious since the Amd2 DIS vote is over, but I'm posting them here.
Min, bluesky61
===
1. throughout the document
-…
-
Geographic information -- Imagery sensor models for geopositioning -- Part 1: Fundamentals
Proposal4.33 geographic information - Change the reference to ISO 19101-1:2014.
4.59 metadata - The defi…
-
Issue as forwarded by Standards Australia to Secretariat, shared with PMG, WG6 convenor, posted here for future work.
[SA_SNZ_TS_ISO_19163.2 MA.xls](https://github.com/ISO-TC211/StandardsTracker/f…