aerostitch / testnavit

0 stars 0 forks source link

add public transport features #195

Open aerostitch opened 11 years ago

aerostitch commented 11 years ago

Issue migrated from trac ticket # 1150

component: mapdrivers/OSM | priority: minor | keywords: publictransport, networks, map,items

2013-07-14 07:02:36: spielraum@web.de created the issue


I would like to generate an xml layout which is similiar to the public transport layout for openstreetmap:

http://www.öpnvkarte.de/?lat=50.9542&lon=13.9201&zoom=13

or a similar style here:

https://wiki.openstreetmap.org/wiki/User:TEL0000/Kosmos

to be able to do so I would need the following osm to navit.xml tag conversions to be added to as far as I have figured out at least:

  722     "w railway=abandoned rail_abandoned\n"
  723     "w railway=disused rail_disused\n"
  724     "w railway=light_rail rail_light\n"
  725     "w railway=monorail rail_mono\n"
  726   "w railway=narrow_gauge rail_narrow_gauge\n"
  727     "w railway=preserved rail_preserved\n"
  728     "w railway=rail rail\n"
  729     "w railway=subway rail_subway\n"
  730     "w railway=tram rail_tram\n"
  731     "w route=ferry ferry\n"

eg by replacing

  724     "w railway=light_rail rail_light\n"

  729     "w railway=subway rail_subway\n"
  730     "w railway=tram rail_tram\n"

with

  724     "w route=light_rail rail_light\n"

  729     "w route=subway rail_subway\n"
  730     "w route=tram rail_tram\n"

to avoid double rendering of elements and in addition to add bus routes

  +++     "w route=bus route_bus\n"

(see https://wiki.openstreetmap.org/wiki/User:TEL0000/Kosmos#Routes)

best regards

robin

aerostitch commented 11 years ago

2013-07-14 07:28:38: usul changed priority from major to minor

aerostitch commented 11 years ago

2013-07-14 07:28:38: usul changed component from core to mapdrivers/OSM

aerostitch commented 11 years ago

2013-07-14 07:28:38: usul edited the issue description

aerostitch commented 11 years ago

2013-07-14 07:28:38: usul changed owner from KaZeR to cp15

aerostitch commented 11 years ago

2013-07-14 07:28:38: usul commented


Hi Robin, thanks for your request :)

But how do you like to do realize the network relation transformation to navit? AFAIK we have no mechanism to do so, but it would be really useful even for other networks (bicycle, hiking...).

So IMHO this is not only about introducing new keys, but (maybe) also to introduce new kinds of elements or a additional step in maptool, which creates then double ways for networks who share this ways (e.g. roads) with old school elemts.

aerostitch commented 11 years ago

2013-07-14 07:28:38: usul

aerostitch commented 11 years ago

2013-07-14 07:30:08: usul edited the issue description

aerostitch commented 11 years ago

2013-07-15 01:51:23: spielraum@web.de commented


Maybe in a first step

+++ "w route=bus route_bus\n"

could be added, so public transport networks can visualised. it would not have the route names, which is a nice to have but not necessary.

maybe one solution to the general problem of having segments with two types can be solved in the following way:

you have a base layer type, with all standard elements (streets, wood, bus stops) and top layer types such as routes, speed limits, and so on which you can just toggle.

it becomes a bit more complicated when you want to mix information of both during routing eg adding a weight penalty to cobblestone streets for bicycle routing as in #1122.

br

robin

aerostitch commented 11 years ago

2013-07-28 05:53:22: usul

aerostitch commented 11 years ago

2013-07-28 05:53:22: usul changed title from add route= to add public transport features

aerostitch commented 11 years ago

2013-07-28 05:53:22: usul commented


I guess this will become more complex, so I put our maintainer in CC and schedule it for the next major release.

aerostitch commented 11 years ago

2013-07-30 22:02:31: spielraum@web.de commented


it will certainly need a lot of thinking, on how one wants to deal with multiple information per edge.

adding

+++ "w route=bus route_bus\n"

though should not interfere with this and you'd have a nice "static" view of bus routes possible as well.

br

robin