On Tue, Mar 17, 2009 at 11:00:09AM +0000, Mark Burton wrote:
When entering an address, the road names are searchable incrementally but the city names are not. Interestingly, if you enter a city name or the prefix of a city name it will scroll the list of city names to the appropriate position - weird.
The Garmin Edge 705 won't. It just says something like "no match" (I'm using it in Finnish). So, the only option is to scroll the list of city names.
As reported by a tester, if you select a city, it doesn't limit the roads in the list to only the roads in that city, you still get presented with a list of all the roads in the known universe.
That's true for the list of street names. However, if you select a city, it will limit the matches on the main "find a street" screen. I tested by searching for "Ratatie" before and after selecting "Ahjo, FIN" (a suburb of the town Kerava).
I have good reason to believe that these two issues will only be solved by supplying further index information (MDR file perhaps?)
So, it may be that the current functionality is the best we can hope for until the MDR is cracked.
A buggy street name database is better than no street name search. I'm looking forward to the commit.
-# Set highway names to include the reference if there is one -highway=* {name '${name} (${ref})' | '${ref}' | '${name}' } +# If highway has a name, use it, or if it has a ref, use that as the name +highway=* {name '${name}' | '${ref}' }
Why is this change needed? Street ref signs are much easier to spot than name signs. Is there a way to see the ref on the map (or the map cursor tooltip) even when the street does carry a name? I can live with this; I'm just wondering. One thing that I'd like to see fixed soon is that multiple matches are being returned for the same road when a section of the road is a bridge, tunnel or cycleway. Marko