bravesilvernest comments on Why does CoMaps seem to not understand addresses?

Why does CoMaps seem to not understand addresses? (lemmy.zip)

submitted 1 month ago by Debs@lemmy.zip to c/CoMaps@sopuli.xyz

31 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] flamingo_pinyata@sopuli.xyz 29 points 1 month ago* (5 children)

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/

permalink

fedilink

source

hideshow 5 child comments

[–] bravesilvernest@lemmy.ml 6 points 1 month ago

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.