Fix cmip6 indicators bbox validation #512
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes a small modification to the CMIP6 Indicators route such that it fetches the spatial bounds from rasdaman and constructs a bounding box to validate the lat-lon of the request.
This should enable locations to have both their CMIP6 data and CMIP6 indicators queried.
To test this PR, make sure you are pointing at datacubes and then try routes like this:
You should get data here:
http://localhost:5000/indicators/cmip6/point/50.5/-147
But not here:
http://localhost:5000/indicators/cmip6/point/49.5/-147
For the latter, the map isn't great but IMO that is OK for now. Also, the bounding box reported on this page is accurate due to the weirdness of the re-grid. However, any requests for latitude 90.1 or something will get caught by this block:
Closes #493