Open aazaff opened 7 years ago
do you want me to make the table for you and you just add it in?
Columns can cross multiples states/provinces, countries, or not exist in any of the above as is the case with the Deep Sea columns. Additionally, in the future the geometry of columns could change on a regular basis, requiring us to maintain this attribute.
While it would be convenient, I feel that because we offer the data in spatial formats this functionality is not necessary. Thoughts?
I don't mind returning the states/provinces as an array.
Why not just make it automated that when you change a column geometry it recalculates its intersection with state/provinces and geoplate?
This is an app-side problem.
I would like to reopen this issue. I just had a request from a user for the ability to refine location by state. It's true that a user could do this on their own with GIS, but not every user is GIS savvy. Please advise.
We have decided that a better solution would be to make the search queryable by spatial criteria, but not return that as a field.
I changed the name of this issue, because I think what we're really asking for would be the ability to POST a geom and find the intersection columns.
Have the intersecting state/province of each column returned as a field of the column's route.