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

Geometry encoding as GeoJSON #11

Open
dr-shorthair opened this issue Jun 3, 2020 · 3 comments
Open

Geometry encoding as GeoJSON #11

dr-shorthair opened this issue Jun 3, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@dr-shorthair
Copy link
Collaborator

Add asGeoJSON (datatype property) and geoJSONLiteral (datatype) to support popular geometry encoding

@dr-shorthair dr-shorthair added the enhancement New feature or request label Jun 3, 2020
@dr-shorthair
Copy link
Collaborator Author

Note: this is already on the agenda for OGC GeoSPARQL revision, so we can test it more rapidly here.

@dr-shorthair
Copy link
Collaborator Author

It turns out that there is a rdf:JSON datatype introduced in the JSON-LD 1.1 revision. So I think we will only need to add asGeoJSON, which is essentially just a modified clone of asWKT etc.

However, rdf:JSON would not disambiguate between GeoJSON and Schema.org (which is usually serialized as JSON).

@mathib
Copy link

mathib commented Jun 5, 2020

FYI, the FOG ontology has a lot of geometry format specific properties, including:

Since the GeoJSON-LD is essentially RDF, the property is an owl:ObjectProperty, thus the property should link to the top node of the GeoJSON-LD file. In the two other cases, the properties are owl:DatatypeProperty and should link to a string in an RDF literal containing the entire JSON.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants