
On Mon, 23 Mar 2009 15:10:16 +0100 Florian Lohoff <flo@rfc822.org> wrote:
On Mon, Mar 23, 2009 at 01:36:45PM +0000, Mark Burton wrote:
A little nitpick (Its always possible to optimize something :) )
Nitpicks are fine.
+ // given a list of roads sorted by name and city, build a new + // list that only contains one entry for each group of roads + // that have the same name and city and are directly connected
As it happens i live in a street which is intersected by a roundabout. As the roundabout does not have the street name on it this will produce multiple segments. So probably it should be directly connected or via a way with "junction=roundabout" ...
But this is just a little optimization probably for the next generation ;)
I am sure that some people would prefer that the two roads are not squashed together in that situation because it would "hide" one of the roads and so they may think that the one road that has been shown stops at the roundabout when, in reality, it carries on past the roundabout. So, given that it's a bunch of work to implement and I'm not convinced it would be universally popular, I will leave that for someone else to add.
The point is when you have a long road you'd like the navi to select the right segment based on the housenumber. So when you are out of luck you select the wrong segment and wont find that specific housenumber.
Sorry, I don't understand what you are saying there. Cheers, Mark