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

Clarify the meaning of multiple values of spatial coverage #107

Open
jakubklimek opened this issue Mar 8, 2024 · 2 comments
Open

Clarify the meaning of multiple values of spatial coverage #107

jakubklimek opened this issue Mar 8, 2024 · 2 comments
Labels
release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft type:improvement Improvement of current handling of a problem webinar:2024-04-23 To be discussed in the 2024-04-23 webinar

Comments

@jakubklimek
Copy link
Contributor

Problem statement
With multiple values for spatial coverage allowed e.g. for a dataset, it may not be clear enough, what the interpretation of those multiple values should be based on the current usage note:

This property refers to a geographic region that is covered by the Dataset.

This is also an issue in DCAT-AP in general.

Example 1 - here we have a collection of possible spatial expressions that migh fit:

<ds> dct:spatial _:Belgium .
<ds> dct:spatial _:Brussels .
<ds> dct:spatial _:Antwerp .

Example 2 - using in addition, different ways of representation of spatial coverage:

<ds> dct:spatial _:Belgium .
<ds> dct:spatial [ dct:identifier _:Brussels ] .
<ds> dct:spatial [ skos:prefLabel "Antwerp"@en ] .
<ds> dct:spatial [ dcat:bbox """{ "type": "Polygon", "coordinates": [[
      [ 2.345693352852237, 51.705922095507674 ],
      [ 2.345693352852237, 49.478466262366766 ],
      [ 6.50311285587884, 49.478466262366766 ],
      [ 6.50311285587884, 51.705922095507674 ],
      [ 2.345693352852237, 51.705922095507674 ]
]]}"""^^<http://www.opengis.net/ont/geosparql#geoJSONLiteral>
   ]

Proposal
Explicitly say in a usage note that when multiple values are used for spatial coverage, this may be interpreted as a spatial union, or as alternative representations of spatial coverage that might fit, with no explicit spatial relation, to give guidance to implementers as to how to treat the multiple values of spatial coverage.

@jakubklimek jakubklimek added type:improvement Improvement of current handling of a problem release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 webinar:2024-04-23 To be discussed in the 2024-04-23 webinar labels Mar 8, 2024
@jakubklimek jakubklimek added the next-webinar To be discussed in the next webinar label Mar 21, 2024
@jakubklimek jakubklimek removed the next-webinar To be discussed in the next webinar label Apr 25, 2024
@jakubklimek
Copy link
Contributor Author

Proposal accepted during webinar.

@jakubklimek jakubklimek added the status:resolution-provided Resolution statement present, not yet applied in draft label Apr 25, 2024
@jakubklimek jakubklimek added status:fixed Resolution applied in draft and removed status:resolution-provided Resolution statement present, not yet applied in draft labels May 8, 2024
@uvoges
Copy link

uvoges commented Jun 26, 2024

spatial union, is fine with me.- +1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft type:improvement Improvement of current handling of a problem webinar:2024-04-23 To be discussed in the 2024-04-23 webinar
Projects
None yet
Development

No branches or pull requests

2 participants