monav does not find a street in Finland

[GoogleCodeExporter]

What steps will reproduce the problem?

sudo apt-get install monav
mkdir ~/.monav
cd ~/.monav
wget iki.fi/lindi/monav/Finland.zip
unzip Finland.zip
monav
select ~/.monav as the data directory
click finland
click load
click the red circle on the left
click "Address"

try to find the street named "Avaintie" which is in Vantaa, Finland. The 
openstreetmap web interface shows it

http://www.openstreetmap.org/?mlat=60.27009&mlon=24.82631&zoom=17&layers=M

so it should be in the database.

I've tried Helsinki, Vantaa and Vapaala as a city but can't find the street.

Would it be possible to add support for searching a street when you don't know 
the city (or the city is apparently marked wrongly in the database)?

What is the expected output? What do you see instead?

The user can find the street "Avaintie".

What version of the product are you using? On what operating system?

monav 0.3-4 on amd64 from debian unstable.

Original issue reported on code.google.com by timo.lin...@gmail.com on 21 Jul 2011 at 1:31

[GoogleCodeExporter]

I will have a look at it later on.

The problem is that we cannot use the Karlsruhe Address Schema, since its not 
widely spread in usage yet. Therefore we heuristically assign each street to a 
city, which can go wrong.

One solution might be to assign the street to every candidate city. Or to allow 
for a global search.

Original comment by veaac.fd...@gmail.com on 21 Jul 2011 at 4:04

• Changed state: Accepted

[GoogleCodeExporter]

I would very much like a global search feature :-) Sometimes users would like 
to see which cities have a street with given name.

Original comment by timo.lin...@gmail.com on 21 Jul 2011 at 9:14

[GoogleCodeExporter]

I iterated over all the place names that are stored in the trie and monav finds 
Avaintie only from Kajaani. I guess Vantaa's Avaintie is lost already in the 
preprocessing step?

Original comment by timo.lin...@gmail.com on 26 Aug 2011 at 12:31

[GoogleCodeExporter]

Oh and it seems it thinks "Konemiehentie" is in Helsinki while technically it 
is in Espoo (by several kilometers).

Original comment by timo.lin...@gmail.com on 26 Aug 2011 at 12:33

[GoogleCodeExporter]

I'm seeing the same issue in Sydney, Australia. Streets in many suburbs cannot 
be found, and this makes address search there largely unusable. How does the 
heuristic work for assigning streets to cities? I assume this is done in the 
pre-processor? Is there a straightforward way for me to examine the data for 
specific examples to try to debug this?

In the case of Sydney I think a good heuristic would be to assign streets from 
any Sydney suburb (might be difficult to calculate - anything in the area?) to 
the city of Sydney as well. This way if the street can't be found you can 
search within the metropolitan area of Sydney to find it instead.

I'm going to do some further reading on the Karlsruhe Address Schema, but it 
seems like implementing that is going to be a concentrated distributed effort.

Original comment by m...@hethos.org on 6 Sep 2011 at 10:12

[GoogleCodeExporter]

MoNav doesn't find Avaintie, because it's too far away from any City or Town. I 
increased those values in OSMImporter::computeInCityFlags and then Avaintie 
could be found from Kauniainen. (Outlines don't work?)

Original comment by jekkukal...@gmail.com on 20 Sep 2011 at 9:47