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
{{ message }}
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
Currently we respond with ClimateDataCell lat/lon in our Indicator, climate data and City endpoints. We should consistently respond with geojson point features in EPSG4326. That's currently not the case, because our lat lon values are pass through from the internal netcdf value where lon is [0 - 360). We can still provide the original netcdf lat lon values as geojson properties if desired.
This would be a breaking change for users depending on this data.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently we respond with ClimateDataCell lat/lon in our Indicator, climate data and City endpoints. We should consistently respond with geojson point features in EPSG4326. That's currently not the case, because our lat lon values are pass through from the internal netcdf value where lon is [0 - 360). We can still provide the original netcdf lat lon values as geojson properties if desired.
This would be a breaking change for users depending on this data.
The text was updated successfully, but these errors were encountered: