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

Allow point as granule spatial representation #110

Open
lisakaser opened this issue Dec 5, 2024 · 2 comments
Open

Allow point as granule spatial representation #110

lisakaser opened this issue Dec 5, 2024 · 2 comments
Labels
question Further information is requested
Milestone

Comments

@lisakaser
Copy link

Handle "Point" granule level spatial representation (info is in CMR)

Sample data set: needed (likely a CSV/ASCII)

points might need to be re projected if not in 4326

Open question: Clarify if Point is single location or could be file with multiple point locations (Amy)

Acceptance criteria:
UMM-G should show correct geometry with one point or array of points

@lisakaser lisakaser added this to the Dec-Jan-Feb milestone Dec 5, 2024
@lisakaser lisakaser added the question Further information is requested label Dec 5, 2024
@lisakaser
Copy link
Author

@afitzgerrell the specific question here for you is if a file/granule has to match to one point or if there could be a file that has multiple point locations inside that all should be handed off to UMM-G.

@afitzgerrell
Copy link
Contributor

Technically (from a CMR perspective) a granule is allowed to be represented by multiple point locations. Functionally, however, current-SIPSmetgen expects a point granule's spatial representation to comprise a single lon/lat coordinate pair, thus this is the immediate case that MetGenC should handle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants