-
Justification Amend ISO 19115-1:2014 (Amd 1:2018) as per presentation
Proposal Amend ISO 19115-1:2014 (Amd 1:2018)
Decouple the specification of the Date type from ISO 19103:2015 and define (e.g.)…
-
Je ne sais pas si c'est une feature qu'on a enlevé, qu'on doit activer dans les paramètres ou si c'est un bug, mais les liens entre les fiches de service n'apparaissent plus en valid (test non plus)
…
-
Support for 19115-1:2014/AMD 1:2018.
Related Issues:
mdJSON Schemas: https://github.com/adiwg/mdJson-schemas/issues/242
- [x] contact>identifier
- [ ] spatialRepresentation>scope
- [ ] cove…
dwalt updated
8 months ago
-
## User Story
In order to identify changes between documents, datagov wants to harvest an ISO19115 document and its transformed counterpart (DCATUS) on catalog-dev.
identify changes in content bet…
-
Justification: GCO and GCX - Responsibility for the management of XML schemas for the GCO and GCX namespaces will be transferred from ISO 19115 to ISO 19103
Propo…
-
The constraint in **MD_MaintenanceInformation** (Fig. 10 of ISO 19115-1, and Table B.6) says at least one of _maintenanceAndUpdateFrequency_ or _userDefinedMaintenanceFrequency_ must be present: `{cou…
-
**Is your feature request related to a problem? Please describe.**
Currently GeoNode only supports ISO 19115:2003 from the ISO metadata standards which has been withdrawn and revised by ISO 19115-1:2…
-
In the AHG on e-Government recommendations were made for the future revision of ISO standards and new standard projects:
-ISO/TC 211 should continue to derive RDF/OWL from the harmonised UML models i…
-
Add support for embedding ISO 19110 into contentInfo section of ISO 19115-1
-
When I do request for "ISO 19115-1" identifier, first match will be "ISO 19115-1:2014 ED1(en,fr)", but as document identifier it returns "ISO 19115-1":
```
3.1.1 :002 > bibitem = RelatonIso::IsoBibl…
mico updated
9 months ago