Opened 10 years ago

Last modified 10 years ago

#1150 new enhancement/feature request

add public transport features

Reported by: ah be Owned by: cp15
Priority: minor Milestone: version 0.6.0
Component: mapdrivers/OSM Version: git master
Severity: Keywords: publictransport, networks, map, items
Cc: cp15

Description (last modified by usul)

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


or a similar style here:

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"


  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"


best regards


Change History (5)

comment:1 Changed 10 years ago by usul

  • Component changed from core to mapdrivers/OSM
  • Description modified (diff)
  • Keywords publictransport networks map added
  • Owner changed from KaZeR to cp15
  • Priority changed from major to minor

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.

Last edited 10 years ago by usul (previous) (diff)

comment:2 Changed 10 years ago by usul

  • Description modified (diff)

comment:3 Changed 10 years ago by ah be

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.



comment:4 Changed 10 years ago by usul

  • Cc cp15 added
  • Keywords items added
  • Milestone set to version 0.6.0
  • Summary changed from add route= to add public transport features

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

comment:5 Changed 10 years ago by ah be

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


+++ "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.



Note: See TracTickets for help on using tickets.