-
Notifications
You must be signed in to change notification settings - Fork 109
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
Handle Spatial Data crossing meridian appropriately #5002
Comments
here's a relevant tool: https://github.com/gadomski/antimeridian not suggesting using it. just something to potentially help with the problem. |
so CKAN spatial acknowledges the issue, but then basically ignored it? |
Kind of. When you have 4 points on a sphere, technically you can go either direction. We just have to be explicit. The schema is specific, but we aren't specific when translating to CKAN's spatial extension. |
This reminds me ckan/ckanext-spatial#90. I doubt splitting the box into two is a solution. |
If that's not a viable solution, we should demonstrate it. It is what is recommended in the CKAN spatial docs: https://docs.ckan.org/projects/ckanext-spatial/en/latest/spatial-search/ |
Also, it's amazing you have had this issue open since 2014, @FuhuXia ! |
The issue opened in 2014 is dealing with sending spatial query across 180° longitude line. The current ticket is related but different. it is dealing with serving spatial query results that is across 180° longitude line. |
Example dataset here: https://catalog.data.gov/dataset/species-of-greatest-conservation-need-national-database
The geospatial extent should go from just below the equator to 70 deg north, and from a little east of japan to just east of Maine. However, if you search anywhere in the northern hemisphere west of japan and east of the US, this dataset will show up. That is because it's treating the bounding box as wrapping all the way around the united states. If you search inside the united states, it won't show up. See example within the US and in Europe
How to reproduce
Expected behavior
Spatial search works as expected.
Actual behavior
Spatial search doesn't work as expected.
Sketch
This is actually called out in the ckanext-spatial extension here (search for
antimeridian
). We need to handle this use case by building the appropriate geojson object. This will require testing.The text was updated successfully, but these errors were encountered: