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

update text for geoshape box, and CRS/SRS #104

Merged
merged 12 commits into from
Jan 28, 2021
Merged
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,4 @@
# python virtual environment
env
*.xpr

25 changes: 25 additions & 0 deletions decisions/101-spatialExtent.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Title - Clarify Spatial Extent encoding.

GeoShape box format unclear #

Discussion: https://github.com/ESIPFed/science-on-schema.org/issues/101
https://github.com/ESIPFed/science-on-schema.org/pull/104

## Status ##
Proposed

## Decision ##
per PR #104:
In full.jsonld Example:
- Fix Duplicate person problem in the JSON.
- update the spatialCoverage content

in guides/Dataset.md
- edits in the Spatial section, introduction, point location discussion,
- edits in geoshape location section, add additional discussion of problems and approaches: bounding box coordinate specification (coordinate order), how to deal with extents that include the poles,

## Context ##
Questions about coordinate ordering and syntax for describing bounding boxes, and how to describe spatiale extents. Try to clarify behavior of Google Dataset search with spatial extent.

## Consequences ##
Metadata harvesters should be able to systematically index geolocation specified in schema:spatialCoverage.
Loading