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

Geo predicates wiki #170

Closed
eliotjordan opened this issue Jul 19, 2016 · 8 comments
Closed

Geo predicates wiki #170

eliotjordan opened this issue Jul 19, 2016 · 8 comments
Assignees

Comments

@eliotjordan
Copy link
Contributor

eliotjordan commented Jul 19, 2016

Create wiki doc listing geo specific predicates that are used in GeoConcerns. Requested by @tpendragon and the Hydra URI Management Working Group.

@eliotjordan eliotjordan changed the title Geo Predicates Wiki Geo predicates wiki Jul 19, 2016
@eliotjordan
Copy link
Contributor Author

Let's take another look at projection​ predicate.

@johnhuck
Copy link
Collaborator

johnhuck commented Sep 1, 2016

DCMI Box encoding scheme also accommodates recording projection. Would that be a solution? http://dublincore.org/documents/dcmi-box/

@eliotjordan
Copy link
Contributor Author

eliotjordan commented Sep 1, 2016

@johnhuck What we want, I think, is just the projection bit. It seems to me that dcmi-box describes the projection of the bounding box not necessarily the projection of the underlying dataset. This is quite common. I suppose what I mean is, does there exist a predicate/vocabulary that describes projection that we can use out of the box. Or is it like it like geospatial file format, and we'll have to cobble something together ourselves.

@eliotjordan
Copy link
Contributor Author

eliotjordan commented Sep 1, 2016

@johnhuck I'm sure you've seen this, but EPSG is a comprehensive and industry standard list of coordinate reference systems. Is there a linked data vocab that already uses this list? If not, then perhaps we can build one. This one is easier than file format, because EPSG is exhaustive. Not entirely complete I'm sure, but pretty darn close.

http://spatialreference.org/ref/epsg/4326/

@johnhuck
Copy link
Collaborator

johnhuck commented Sep 1, 2016

Since EPSG assigns URNs to manage different projections, what they are maintaining is already a controlled vocabulary, so there wouldn't be a need to make a different one. As least as far as RDF is concerned, a URN is a URI and can be used anywhere a URI is required. But if we used bf:projection, whose range is rdfs:Literal, its URI status would be irrelevant, except as an unambiguous identifier, which could perhaps be repurposed later. Several online services like the one you mention seem to provide the value-added service of a URL for the terms. This one supplies the GML metadata for the projection, but I think it's a third-party offering: https://epsg.io/4326.gml

@johnhuck
Copy link
Collaborator

johnhuck commented Sep 2, 2016

Added a wiki page with a basic table. Needs more information.

@eliotjordan
Copy link
Contributor Author

We have the basic wiki. I think we can close this issue.

@johnhuck
Copy link
Collaborator

johnhuck commented Sep 9, 2016

Agreed.

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

2 participants