Sonds promising but a short question:
what happens to the way IDs, if the map data is upgraded on the
server but not on the client which uses the route?
As I understand, the data in Openstreetmap is quite dynamic...
Regards
Andreas
Am 19.11.2007 um 21:18 schrieb OJW:
On Monday 19 November 2007 20:03:26 Nic Roets wrote:
I'm to make a cgi-bin version of gosmore that does this. So if we
can agree
on an interface now, it will hopefully not be too long before gosmore
catches up.
Sounds good.
6. Y for fastest route, N for shortest
It might be easier to just consider this to be part of the "mode"
field
so "vehicle type" might become
* "car, fastest route"
* "car, shortest route"
* "car, non-motorway"
* "car, quiet roads"
7. Y to output way names, N to output way IDs
Not having the option for way names could potentially make
implementations a
lot simpler (e.g. allows fixed-width output, routing servers not
required to
store road names) and clients can go to OSMXAPI with the list of
way numbers
if they want more info.
The only other option I could think of for the interface is
"format" (binary,
text, json, or xml)
4. Bearing to travel
5. Length of leg
Note that 4 and 5 are actually redundant.
Agree about those being redundant - probably easier for the client to
calculate that if they want it.
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/routing
Andreas Leupin
Kretzgasse 2
CH-5416-Kirchdorf
Tel. P [+41](0)56 282 07 40
G [+41](0)56 310 39 32
[EMAIL PROTECTED]
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/routing
