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

Rewrite Principle #17 (geospatial relations -> geospatial elements) #44

Closed
jyutzler opened this issue Oct 15, 2020 · 1 comment
Closed

Comments

@jyutzler
Copy link

Principle #17 – Follow OGC Guidelines regarding geospatial elements

  • Provide SRSs with all coordinates.
  • Where possible, explicitly name coordinates instead of relying on coordinate order. When this is not possible, follow the OGC Axis Order Policy.
  • When needed, use WKT2 to describe SRSs. (from #37)
  • Use explicit geospatial relations. (as in the existing Principle 17)
@fterpstra
Copy link
Contributor

discussed in web api guidelinse telecon 22-01-2021. The principle makes spatial relations explicit while the pull requests adds information on implicit relations that can be extracted from coordinates. Therefor this information on SRSs etc should not be added to principle 17. Maybe we should be more clear on the use of relations and not limit it to geospatial relations. It should apply to all relations. perhaps we should change the title and take the word geospatial out.
Discussed on 5-2-2021: The more specific guidelines are the less valuable they become. We would argue to not refine the guidelines in the way suggested here.

@cmheazel cmheazel closed this as completed Feb 5, 2021
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

Successfully merging a pull request may close this issue.

3 participants