Am 03.09.12 18:58, schrieb Tobias Knerr:
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?
The result of routing on the command line (for use in scripts) are
pairs of wayID, start-nodeID, end-nodeID with lat+lon included to make
scripting easier.
More complex schemas are trivial to code in Java as TS is only a graphical
frontend to the osmRouting library wich uses the libOSM library and it's
plugin-framework.
All 3 are intended for prototyping algorithms and data storage structures
by having only to code whatever part of an end-user routing application
you are working in and getting all other aspects for free.
Tobias
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/routing
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/routing
