Hi Tobias,
Thanks for the reply! Yeah, I think I can simplify my question now, to
make more sense. I have looked at the OSM in JOSM.
So, I think my problem is basically, OSM route software seems to
report 'Ways' rather than 'Nodes' (sorry, OSM terminology is still new
to me!). And I can see that makes sense for GPS navigation software,
it usually says things like, follow the road for 2miles until
junction. Which is probably the length of the 'way'.
But, for my simulated vehicle to follow this route, I really need to
break it down into the nodes that make up that 'way' (and JOSM even
tells me the lat lon of them which is perfect!)
So, I think you're right, it looks to me like the gpx file only
contains sparse track points and end of ways, or intersections,
whereas what I really need is all Nodes along the route, so that my
simulated vehicle can just follow these points in order to follow the
road. Also, it doesn't matter too much to me if the vehicle doesnt
follow the road perfectly! A few metres is OK, but with the curved
road, it cuts out the entire road and goes through a building! :)
Hope that makes sense!
Thanks
Vin
Quoting Tobias Knerr <[email protected]>:
Hello Vin,
original projects like yours are something I always find interesting,
especially when they involve 3D models. So I hope we can solve your
routing problem.
On 02.09.2012 20:49, Vin Baines wrote:
I've looked at the travelling salesman code, which almost does what I
want - I can pass it a set of lat-longs and get the route, but its
returned as OSM nodes, or a gpx file. If I load gpx data and use that as
coordinates for the driver to move to, then any curves in t he road get
ignored. But, in the GUI the route follows the road exactly. Ideally,
I'd export this data in say 5m intervals, and the driver agent would use
that as a series of moveTo(X,Y) actions.
I'm not sure whether I understand the issue, but as I'm not familiar
with the output of Travelling Salesman, I may be missing something. Some
clarifications would be helpful.
You say you can get the result as a gpx file, but it doesn't include
curves. Does this mean that the gpx only contains track points at
junctions and nothing in between? Is that also the problem with the
nodes - that you don't get *all* nodes along the route, but just a few
of them?
Tobias
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/routing
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/routing
