Arlindo Pereira <[email protected]> writes: > 1) creating a table listing each street on his road list to an array of OSM > Way IDs, and somehow indicating to the algorithm that those ways are > preferred. But this would require constant maintenance as people > edit/split/merge/erase ways. > > 2) considering the street names, and somehow making the routing algorithm > prefer those ways.
The basic issue is keeping two databases in somewhat sync. If there is KML, I would be inclined to have a combining step where the preferred roads are matched up with OSM data by geometry and then the OSM ways marked with the special tag (locally). Here, any of id, name, or shape/location could work. shape/location is probably pretty stable. > 3) mapping those characteristics that made he chose those particular > streets in first place (maxspeed=, incline=, lanes=, highway= itself, etc > etc) and tuning the routing algorithm to prefer those streets. But nothing > would garanteed that the router wouldn't pick a particular tertiary or even > highway=residential that is not "calm" in oppositon to a "calm road". This would be interesting in the long run, but seems very hard. Is this other dataset also under OdbL and the merged dataset being released under the same terms?
signature.asc
Description: PGP signature
_______________________________________________ dev mailing list [email protected] https://lists.openstreetmap.org/listinfo/dev
