Closed sjordan29 closed 5 months ago
Is this done to some degree in the Coverages provider?
e.g. https://github.com/geopython/pygeoapi/blob/master/pygeoapi/provider/rasterio_.py#L202 ??
Would the pattern there be something to follow in the xarray provider?
As per RFC4, this Issue has been inactive for 90 days. In order to manage maintenance burden, it will be automatically closed in 7 days.
As per RFC4, this Issue has been closed due to there being no activity for more than 90 days.
Is your feature request related to a problem? Please describe. I am working with @dblodgett-usgs to configure the pygeoapi EDR provider to work with zarr files with projected coordinate systems. The current implementation appears to require lat/lon coordinates. You can kind of work around this limitation by defining
x_field
andy_field
as the projected coordinates in the config file instead. You can then query the data with projected coordinates. However, this does not seem user-friendly or in line with the OGC API EDR standard.An example dataset to serve with EDR provider and projected coordinates:
This dataset has
lat
&lon
values, but the xarray.sel()
method only works onx
andy
coordinates.Describe the solution you'd like For data with projected coordinate systems, I would like users to query with coords in WGS84 and have the EDR provider transform the coordinates in that query to the appropriate CRS. I anticipate this could leverage some of the work done in PR #1174 for feature providers, with
storageCRS
in the configuration file, or work done for coverages (e.g., rasterio_ provider).