Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

two many locn:geometry #249

Open
jze opened this issue Jun 1, 2023 · 0 comments
Open

two many locn:geometry #249

jze opened this issue Jun 1, 2023 · 0 comments

Comments

@jze
Copy link
Contributor

jze commented Jun 1, 2023

For DCAT-AP the extension generates too many locn:geometry values.

DCAT-AP specifies the cardinality of locn:geometry for the class dct:Location as [0..1].

Currently the export looks like this

<dct:spatial>
  <dct:Location rdf:nodeID="N1c28db5fb3c64004809faa27ab9f2c18">
    <locn:geometry rdf:datatype="https://www.iana.org/assignments/media-types/application/vnd.geo+json">{"type":"Polygon","coordinates":[[[8.63647,54.30695],[8.63629,54.30572],[8.63691,54.30567],[8.63697,54.30688],[8.63647,54.30695]]]}</locn:geometry>
    <locn:geometry rdf:datatype="http://www.opengis.net/ont/geosparql#wktLiteral">POLYGON ((8.6365 54.3070, 8.6363 54.3057, 8.6369 54.3057, 8.6370 54.3069, 8.6365 54.3070))</locn:geometry>
  </dct:Location>
</dct:spatial>

I suggest to remove the GeoJSON entry. Then the export would be:

<dct:spatial>
  <dct:Location rdf:nodeID="N1c28db5fb3c64004809faa27ab9f2c18">
    <locn:geometry rdf:datatype="http://www.opengis.net/ont/geosparql#wktLiteral">POLYGON ((8.6365 54.3070, 8.6363 54.3057, 8.6369 54.3057, 8.6370 54.3069, 8.6365 54.3070))</locn:geometry>
  </dct:Location>
</dct:spatial>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant