-
Notifications
You must be signed in to change notification settings - Fork 12
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
GDAL GTI #528
Comments
The missing field is the import geopandas as gpd
df = gpd.read_parquet("items.parquet")
df['location'] = df.assets.apply(lambda x : x['blue']['href'])
df.to_parquet("items_with_location.parquet")
ds = xarray.open_dataset("GTI:/home/rave/dask_on_ray_poc/items_with_location.parquet", engine = "rasterio")
ds.values Dimensions: (band: 1, x: 12036, y: 9924)
Coordinates:
* band (band) int64 8B 1
* x (x) float64 96kB -112.1 -112.1 -112.1 ... -110.9 -110.9 -110.9
* y (y) float64 79kB 35.24 35.24 35.24 35.24 ... 34.25 34.25 34.25
spatial_ref int64 8B ...
Data variables:
band_data (band, y, x) float32 478MB ...> So I think the issue is two fold.
I'll raise an issue in gdal about 2. |
Is this in a spec anywhere? Is it something we should add to the stac-geoparquet spec to help with interoperability? |
I don't think so I've only found it in the GTI docs. I'm learning that GTI at this point only supports single band assets and doesn't handle the complexity of multi CRS or multi resolution assets, so it doesn't support multi band assets at all. I think Even is working on supporting this though by making use of the existing spec's assets field, but possibly introducing the use of a |
Would this solve the problem for you? It seems hard to generalize a single |
I think it would be neat to be able to load the result of a stacrs query as a lazy xarray.DataSet via rioxarray. The new GDAL Raster Tile Index (GTI) enables this
when chunks are accessed from the xarray dataset, reprojection happens behind the scenes for the user
example from https://gist.github.com/mdsumner/724f1db0bd0d211de6e3775486cd3df0
I tried out GTI on a stac-geoparquet query result but I think there's a difference in how stacrs formats the result and what GTI expects.
Query setup, search, save to stac-geoparquet
Trying to open as a GTI backed xarray.Dataset.
the error is below, I think the uris to the assets are expected in a different column name and possible a different structure
I'm looking into why this field issue is occurring and curious if once this is diagnosed we could get this working in
stacrs
?The text was updated successfully, but these errors were encountered: