[OSM-dev] API threw unexpected NoMethodError exception

[Martin Schafran]

On Saturday 06 April 2013 23:55:19 Peter K wrote:
> Martin,
> 
> > routing is not enough
> 
> Why not? I don't see your problem. Do you have an example?
> 
i need a different routing namely:
give me the next traffic signals in my driving  direction and a radius of 2 km. 
this is already implemented.
its not give me the route from A to B.


> > how can i import data partially and consistent?
> 
> Regarding routing: IMO this is possible when you just import the ways in
> your current boundary (and all of the involved nodes).

i deleted all relations and it works

> > one junction = one relation, this is already proposed since many years and
> 
> You can generate the data you like out of OSM like all routing software
> is doing these days ...

i need to know when the car leaves the junction area: 
to fire the next request
and to determine the driving directions.
traffic signals can have different timings for diff. directions. i need to know 
them for showing and synchronizing GLOSA for all directions.

small crossings work fine and i can generate all data automatically.
its not working on bigger junction unless the junction nodes are in a 
relation.

martin