search

SEMICeu / GeoDCAT-AP

Repository of the geospatial extension to DCAT-AP (GeoDCAT-AP)
https://joinup.ec.europa.eu/solution/geodcat-application-profile-data-portals-europe
Creative Commons Attribution 4.0 International
19 stars 6 forks source link

Specifying spatial coverage with a bbox #1

Closed andrea-perego closed 3 years ago

andrea-perego commented 6 years ago

For this purpose, GeoDCAT-AP v1.0 uses property locn:geometry, because none of the reference vocabularies were supporting a more specific approach.

The situation has not changed, so the question is whether it is worth addressing this issue by defining appropriate classes and/or properties, and, in such a case, whether this should be done in the framework of GeoDCAT-AP or of the Core Location Vocabulary.

A proposal is outlined in https://github.com/SEMICeu/Core-Location-Vocabulary/issues/2

andrea-perego commented 5 years ago

The new version of DCAT does use locn:geometry, and defines additional properties:

They could be added in GeoDCAT-AP - taking into account backward compatibility.

andrea-perego commented 4 years ago

The new version of DCAT does use locn:geometry, and defines additional properties:

They could be added in GeoDCAT-AP - taking into account backward compatibility.

These new properties have been adopted in DCAT-AP 2 (see https://github.com/SEMICeu/DCAT-AP/issues/85), so they should be inherited by GeoDCAT-AP, possibly taking into account backward interoperability.

andrea-perego commented 3 years ago

This revision has been implemented in the first working draft for GeoDCAT-AP 2.0.0:

https://semiceu.github.io/GeoDCAT-AP/drafts/2.0.0-draft-0.1/