geopython / pycsw

pycsw is an OGC CSW server implementation written in Python. pycsw fully implements the OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web]. Initial development started in 2010 (more formally announced in 2011). The project is certified OGC Compliant, and is an OGC Reference Implementation. pycsw allows for the publishing and discovery of geospatial metadata via numerous APIs (CSW 2/CSW 3, OpenSearch, OAI-PMH, SRU). Existing repositories of geospatial metadata can also be exposed, providing a standards-based metadata and catalogue component of spatial data infrastructures. pycsw is Open Source, released under an MIT license, and runs on all major platforms (Windows, Linux, Mac OS X). Please read the docs at https://pycsw.org/docs for more information.
https://pycsw.org
MIT License
211 stars 155 forks source link

how do ogc-api link-types map to pycsw link types? #962

Open pvgenuchten opened 9 months ago

pvgenuchten commented 9 months ago

Current behaviour of pycsw for rel="xxx" of ogcapi item links is: if a link contains rel, then this link is taken

https://github.com/geopython/pycsw/blob/3fefd4e7ac53346e21a259f437316ea97c3004c8/pycsw/ogc/api/records.py#L1236-L1241C11

Not sure how the value is populated (but that is a follow-up of this thread)

Recommendation 9 in https://docs.ogc.org/DRAFTS/20-004.html recommends to use a rel from https://www.iana.org/assignments/link-relations/link-relations.xhtml

Is some mapping required between link types used in for example iso19139/dublin core to these ogc-api types?

tomkralidis commented 4 months ago

How does ISO 19115 deal with link relations? Or does it still deal with gmd:protocol per se?

We have to verify this behaviour in -3, at which point we can decide on our plan in pycsw (via update to geolinks.