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
The definition of the bbox spatial extents has non-obvious construction:
The first bounding box always describes the overall spatial extent of the data. All subsequent bounding boxes can be used to provide a more precise description of the extent and identify clusters of data.
i.e. [[extent]] or [[extent], [child], [child]...]
Should the schema try to catch people interpreting the spec as a simple list of bboxes by enforcing either a length of 1 or 3?
Or is that too restrictive and the catch should be passed down to validators like stac-check?
The text was updated successfully, but these errors were encountered:
The definition of the bbox spatial extents has non-obvious construction:
The first bounding box always describes the overall spatial extent of the data. All subsequent bounding boxes can be used to provide a more precise description of the extent and identify clusters of data.
i.e.
[[extent]]
or[[extent], [child], [child]...]
Should the schema try to catch people interpreting the spec as a simple list of bboxes by enforcing either a length of 1 or 3?
Or is that too restrictive and the catch should be passed down to validators like
stac-check
?The text was updated successfully, but these errors were encountered: