-
Notifications
You must be signed in to change notification settings - Fork 5
Clarify/fix proj:epsg
requirement
#15
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
Conversation
… with template
Dev call: Don't require proj:epsg at all (but say that having EPSG would be great), see #7 for more discussions. Thus, the schema in this PR needs an update. |
# Conflicts: # CHANGELOG.md # README.md
As discussed in a STAC meeting last year, we are removing the proj:epsg requirement. Updated this PR to reflect that, I'd appreciate a new round of reviews. |
# Conflicts: # examples/assets.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fine with me.
Co-authored-by: Pete Gadomski <[email protected]>
* Add more examples, clarify/fix `proj:epsg` requirement stac-extensions#7, align repo with template * Don't require proj:epsg as discussed in the STAC meeting * Clarification * Recommendation around thumbnails * Update README.md Co-authored-by: Pete Gadomski <[email protected]> --------- Co-authored-by: Pete Gadomski <[email protected]>
* Add more examples, clarify/fix `proj:epsg` requirement stac-extensions#7, align repo with template * Don't require proj:epsg as discussed in the STAC meeting * Clarification * Recommendation around thumbnails * Update README.md Co-authored-by: Pete Gadomski <[email protected]> --------- Co-authored-by: Pete Gadomski <[email protected]>
Fixes #7 + #16
This requires
proj:epsg
in the scope whereproj
fields are used.This might be an issue for cases where currently proj:epsg is in Item properties and the individual assets use proj:shape/proj:transform only. I think I've seen that in implementations...