comaps uses openstreetmap data. you can help improve that data, including by filling in missing addresses. check this to start: https://wiki.openstreetmap.org/wiki/Addresses
post
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.
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.
When i put just "1219 SW Park Ave, Portland" it immediately finds the museum. Municipal code formats vary everywhere in the world and my best guess is that it gets confused by the extra numbers at the end. In general my experience with osm applications is that less verbosity is better for the search.

As I was repeating the above example, every once in a while it would find the museum correctly. It is just very inconsistent. It misinterprets what it thinks I am looking for.
You would think that a well formatted address copied from Google maps would be a slam dunk.
I’ve had the same issue and not being able to search and pull up a simple address is a big turn off
This is going to surprise you but I work in logistics software and can assert it's true
There's no correct way to parse an address, and no assumption that can generally be applied about it
You basically need some form of AI to parse an address with acceptable quality in an application designed for international audiences
If the search feature is for one province or area you might be able to get away with some hard coded format or heuristic but in the international space, even between countries that speak the same language, or within one country, there is no one technique for parsing an address
I think CoMaps only finds addresses that are within the coverage area of the downloaded maps. Quite annoying, but in my experience it works quite well within that area.
I have this map downloaded. It's my hometown.
If you're putting in street numbers and only getting back streets, chances are that street number does not exist in openstreetmap yet and you'll need to add it
There is something more going on here. As I was running the above example, the results would vary. Every once in a while it would even find the museum correctly. So open street maps does have it in their database. It just was misinterpreting what it thought I was looking for.
Its why I don't use it. When I can put an address in it and I can actually navigate to that address, I will switch.
It does work if you have the GPS coordinates by the way. But unfortunately I can't recommend it until that issue is resolved. I think the main issue is its source data. Yes I'm aware I can add addresses, but that doesn't help me with actually using the app.
Try just "1219 sw park ave" or "1219 southwest park avenue"
City, state, zip, is rarely tagged (correctly) in OSM.

all 32 comments