There is a frustrating issue with the CoMaps work flow. If I copy an address from Google maps into the CoMaps search bar, the application cannot find it.
For example, if I copy the address listed for the Portland Art Museum into CoMaps search:
1219 SW Park Ave, Portland, OR 97205
The search result varies. Sometimes it is:
Southwest 18th Avenue, 1219
Sometimes it is for the entire road:
Southwest Park Avenue
Is there a syntax issue here? You would think this would be a very easy find.
Interpreting addresses is a hard problem. For example what Google does is absolutely amazing.
Unfortunately CoMaps doesn’t seem to be able to reach anything even similar. I don’t know if it’s about lack of resources, or lack of expertise … well it all comes back to money anyway.
https://www.mjt.me.uk/posts/falsehoods-programmers-believe-about-addresses/
Then give me the option for a form with “number, Street, City, State/province” as an option.
Comaps is great when you know your lat/lon. The search is terrible to the point of broken though.
Problem is not everywhere in the world they use that style of addresses. Japan famously doesn’t use street names for the most part, for example.
No shit - but you don’t use one form for all locales. You can localize it. The parsing it does now is broken to the point that I lookup places in Google Maps and copy coordinates to Comaps because even when it has the address it only works like 80% of the time.
Noone stops you from writing an issue or even implement what you say in code.
Addresses were the bane of my existence a few years back. I tried to migrate from google to another provider, and figured I would just take the lat-lngs, do math to determine apprx distance, and validate that way. Turns out sometimes the new provider was off by the mailbox while google used the building, and sometimes google just guesstimated while the new provider was spot on.
Jfc, reading this convinced me that getting wiped out by an asteroid is a mercy we collectively don’t deserve.