output the highway tag in instructions

[rodo]

Hi,

This is a feature request, is it possible to add in route_instructions the highway tag ? It will be useful to show total time by highway type, in web services we can show something like "3 hours on road, and 4 hours on ferry".

Thanks

[DennisOSRM]

Would the ferry duration tag and the direction tag/relation work for you?

Am 31.05.2012 um 23:24 schrieb Rodolphe Quiédeville reply@reply.github.com:

Hi,

This is a feature request, is it possible to add in route_instructions the highway tag ? It will be useful to show total time by highway type, in web services we can show something like "3 hours on road, and 4 hours on ferry".

Thanks

---

Reply to this email directly or view it on GitHub:
#282

[rodo]

It's enough to split on earth/on sea, but it could be better to split primary equivalent/track for bicycle too.

[jordanderson]

I'm the developer of the ridethecity.com bike routing website and we've been looking at osrm as a possible alternative to pgRouting, which is what we use now.

This issue highlights an important feature for us because it allows us to represent some OSM way tags as icons in the route instructions -- and also to change the color of the route line based on the OSM tag. See for example, http://ridethecity.com/?wide=1#2495133

One approach would be to allow users to specify a list of relevant tags in the configuration and then support an additional API parameter e.g. include_tags=true that would provide the key/value for each way in the route instructions.

This is complicated by the fact that way tags might change when the street name and street directions don't. The link above shows an example of this starting at step 4 in which 2nd Avenue begins as a separated bike path, becomes a bike lane for 0.4 miles, and then turns into a separated path again. We break that into 3 separate steps in our instructions because the bicycle facility has changed even though the street name and direction remains the same.

Just so you understand some of the ways this might be used, our icons include: bike path, bike lane, bike route, rough surface (e.g. cobblestones, gravel), ferry, walk your bike, caution (for high-speed streets), and stairs -- all features useful to cyclists that we extract from OSM way tags. To make things a bit more complex, we also extract information from some OSM relations, too (mostly regional bike route info).

[emiltin]

hi, i'm the project manager for the city of copenhagen's upcoming bike planner. (alfa at http://www.ibikecph.dk) it's interesting to hear your thoughts on ridethecity. we're working with the osrm team to provide even better support for bike routing in osrm.

dennis will be able to answer your question better, but i think one challenge with outputting tags is how it would affect performance. currently when the osm data is parsed, a simplified version is saved to disk, which doesn't include any tags. so it's not straightforward to output tags as part of the route instructions.

but i agree that having (a filtered number of) tags available in the route instructions would be nice. also it would be nice when performing the contaction (preprocessing) of data. for example, turn penalties could depend on the type of way you turn from/to.

[jordanderson]

Hello!

Yes, I agree that this requirement would need to be balanced with its impact on performance. I'm not sure it's even a widespread enough requirement to warrant adding to the core of osrm.

[jordanderson]

If it's useful, the way that pgRouting deals with this is by mapping osm tags to integer codes via a configuration file like this one: https://github.com/pgRouting/osm2pgrouting/blob/master/mapconfig.xml

That helps condense the additional data required and also allows the application to condense redundant tags as necessary e.g. you might consider highway=cycleway and cycleway=yes as equivalent and have them resolve to the same tag id.

[DennisOSRM]

Will think about that.

[emiltin]

somthing like this is already used for storing strings, like street names

[daniel-j-h]

Here's an update as of v5.5:

don't encode arbitrary strings into the way's name, ref, pronunciation or other similar properties. Doing so will completely screw the internal guidance heuristics and will probably lead to unusable / far too noisy announcements (think: multiple continues after each other).

Here's the recommended way of doing this: use the annotations=true parameter:
https://github.com/Project-OSRM/osrm-backend/blob/master/docs/http.md

this adds OSM Node IDs to the route response. Then either do the lookup

OSM Node ID -> arbitrary metadata

yourself or use https://github.com/mapbox/route-annotator which was built exactly for this use-case.

[MoKob]

related: #4203: we might be able to solve this, when we use the user-classes @TheMarex is working on to represent highway tags.

[daniel-j-h]

5.9 has the road class in the intersection object:

https://github.com/Project-OSRM/osrm-backend/blob/5.9/docs/http.md#intersection-object

the default car profile sets toll, ferry, restricted, motorway road classes:

https://github.com/Project-OSRM/osrm-backend/blob/5.9/profiles/lib/handlers.lua#L280-L310

and you can change that in your own profile.

Closing this as resolved.