[OSM-dev] API threw unexpected NoMethodError exception

[Martin Schafran]

On Sunday 07 April 2013 14:05:44 Peter K wrote:

> IMO your step by step approach is not sufficient to work properly.
> You'll need a the driver's final destination and full path.

this app is not routing. 
this app "just" provides speed and timing info of the next traffic signals even 
if no path is available.

as no path is known it assumes 2 things:
1. next signal is distance based
2. you go straight on

I don't want to force drivers to provide a path. 
if a path is available its even better. but this is not the problem.



> 
> Also here in my city (Germany) several junctions have a separate lane
> for turning right.
> And this lane has no traffic light, but the junction has one!

you got it. 
and i can't solve it without a defined junction.
the solution is:
first define a "via" member of a relation (lane or direction). this "via" member 
is a junction, that consists of multiple nodes on bigger junctions.

after that you can define driving directions like "from"->"via"->"to" and 
distinguish between lanes.
to each lane a timing info can be assigned (see glosa tag in german forum).
 
please define at least a junction. this wouldn't hurt anybody.


and if you want glosa, define also additional glosa tags.
there are enough pretimed signals out there even in germany and the parameters 
don't change often.
the result would be as on my videos.


martin