Replies: 2 comments 3 replies
-
I can respond to the reverse geocoding: it is already implemented in the new Stimulus map controller, so we're good there. Then it's down to parsing the string Google returns. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm curious how the reverse geocoding works. Can we generally get a county level name? How does it deal with parks and other less political locations? Is there somewhere I can play with what it does? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I think we agree that the these days, the first thing we should ask for are images. If images are provided then we should use those to determine date and lat/long if available (with the ability to edit the date, revise the lat/long, say to hide the lat/long). If multiple images are provided, the user should be able to select the data any of them.
I think that the named Locality should become optional. I'm not sure what sort of reverse geocoding we can do from lat/long these days. I know when I looked at it a number of years ago the options were kind of complex and not very intuitive. If we could determine something like county from lat/long that might make the most sense. There are definitely hidden complexities here since it needs to work internationally where there may not be a county concept, or you get places like Louisiana where they have parishes instead of counties and if I remember correctly each city is it's own parish. There are also case where the same city is in multiple counties (e.g., Portland, Oregon) and you have parks that cross state lines (e.g., The Great Smokies). It's not totally clear to me what of the existing mapping features for observations should stay as they are and which need to be revised.
Beta Was this translation helpful? Give feedback.
All reactions