You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle "Point" granule level spatial representation (info is in CMR)
Sample data set: SNEX23_SSA (for us to use SNEX23_SSADUCk) - CSV with point representation
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
The text was updated successfully, but these errors were encountered:
@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.
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.
Thanks Amy! As we discussed in one of our meetings last week lets tackle the one point per granule in this issue and write a second issue to deal with the multiple points per granule. Likely this second issue will only be worked if a use case need comes up.
Handle "Point" granule level spatial representation (info is in CMR)
Sample data set: SNEX23_SSA (for us to use SNEX23_SSADUCk) - CSV with point representation
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
The text was updated successfully, but these errors were encountered: