<<<
I don't think this should be part of the OSM data model,
but something I was thinking about was to run a standard
OSM file through a pre-processor which would add a
"routing=yes" attribute to the nd elements of a way to
indicate which nodes are shared with other ways. Obviously
it would have to be configurable so you could say which tags
indicate that a way should be considered routable. It's not a
big change but it might make some operations slightly
easier--avoid having to do reference counts on each node
as you're processing a way.
>>>
adding a "routing=yes" attribute to the nd elements of a way to
indicate which nodes are shared with other ways is not enough.
You need to refer to a routing node id. then from refered routing node id we can find the link
to other routing nodes outside the current way.
Regards,
--- On Mon, 3/17/08, Karl Newman <[EMAIL PROTECTED]> wrote:
From: Karl Newman <[EMAIL PROTECTED]>
Subject: Re: [Routing] propose a new data structure for routing
To: [email protected]
Cc: [EMAIL PROTECTED]
Date: Monday, March 17, 2008, 4:44 PM
I don't think this should be part of the OSM data model, but something I was thinking about was to run a standard OSM file through a pre-processor which would add a "routing=yes" attribute to the nd elements of a way to indicate which nodes are shared with other ways. Obviously it would have to be configurable so you could say which tags indicate that a way should be considered routable. It's not a big change but it might make some operations slightly easier--avoid having to do reference counts on each node as you're processing a way. Karl
On Mon, Mar 17, 2008 at 9:07 AM, Marcus Wolschon < [EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Digitalmobilemap Digitalmobilemap schrieb:
| Hi All,
|
| In order to do routing with OSM data, we need to have routing nodes
and graph
| data in osm database.
| I study OSM data structure version 0.5 but I could not find any proper
data
| structure to store routing information.
|
| I would like to propose a new data structure for capturing and/or
calculating
| routing information.
| The proposal uses xml tags similar to node,way,relation.
|
| I name the new data structure as <rtnode /> to distinguish with the
current node
| <node /> (node in osm is not
| a node, it is just a point only)
Hello,
what is the purpose of these new nodes you propose?
What is your reason for violating the first
normal-form of database-design?
How do you suppose to generate them?
If you want to have a simplified data-set for
your and other's routing-applications, you are
free to render it
regularly and provide access
to it for everyone who may find it usefull.
They should not, however be a part of OSM.
| <rtnode id="757312" lat="51.3450785" lon="-0.4606170"
| timestamp="2006-04-17T08:57:53Z">
| <rtnode ref="251490798" distance="2km" traveltime="10minutes"
| maxspeed="60kmh" />
We already have maxspeed and similar in the ways.
Travel-Times depend heavily on the type of vehicle you are
using and external factors and need to by calculated by the
routing-application.
Also the selection of osm-ways that are relevant for
routing depends on your vehicle. Bicycles and motor-
scooters cannot use motorways. Heavy trucks cannot
use certain bridges...
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH3pc/f1hPnk3Z0cQRAnbJAJwKqKyEjk5we3GzlOB2QuEjsp1g5ACfWKbC
vTsRWG/0iUsZVa5ZVtGkdaI=
=Q3Gv
-----END PGP SIGNATURE-----
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/routing
|
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
_______________________________________________
Routing mailing list
[email protected]
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/routing
