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.

Sign up for GitHub

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

Jump to bottom

Explicitly expect significant digits in numerical data #13

Open
lvdbrink opened this issue Oct 18, 2019 · 1 comment
Open

Explicitly expect significant digits in numerical data #13

lvdbrink opened this issue Oct 18, 2019 · 1 comment
Labels
change request discovery Used to discover what we need to do. May propose a way forward.
Milestone
GeoSPARQL 1.3

Comments

@lvdbrink
Copy link
Collaborator

Official change request: OGC CR 579

Numerical data published using GeoSPARQL often have an unrealistic amount of digits. At the same time, there is no standardized way to express spatial resolution yet. Both these problems can be addressed when numerical data, published using GeoSPARQL, are explicitly expected to have only significant digits.
@jabhay jabhay transferred this issue from opengeospatial/geosemantics-dwg Sep 21, 2020
@jabhay
Copy link
Collaborator

jabhay commented Sep 23, 2020

MoSCoW poll created

@nicholascar nicholascar added the discovery Used to discover what we need to do. May propose a way forward. label Dec 16, 2020
@nicholascar nicholascar added this to the GeoSPARQL 1.2 milestone Dec 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
change request discovery Used to discover what we need to do. May propose a way forward.
Projects
None yet
Milestone
GeoSPARQL 1.3
Development

No branches or pull requests
3 participants
@nicholascar @lvdbrink @jabhay