New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USA – Detroit – Lanes #5

manuelab-telenav opened this Issue Apr 10, 2017 · 6 comments


6 participants

manuelab-telenav commented Apr 10, 2017


This project is designed to improve the quality of OSM by adding and updating lanes and turn lanes on motorways, motorway_links, trunks and trunk_links, in Detroit, Michigan.

How to map

For editing lanes and turn lanes we will use JOSM, the TurnLanes-tagging Editor plugin and the Lane and road attributes map paint style.
We will use the ‘lanes=*’ tag to add the number of lanes on every way as it is described here.
For the direction in which a lane will lead we will use the ‘turn:lanes=*’ tag as it is described here.


  • Aerial Imagery: Bing, Mapbox, NAIP, Digital Globe
  • Street level imagery: OSC, Mapillary

Who will be involved

Telenav mapping team

See also


This comment has been minimized.

markscalf commented Apr 11, 2017

Mapbox did a significant amount of turn lane editing in Detroit last summer which requires clean-up; specifically along Michigan Ave in Dearborn/Detroit. Here is an example where their edits were incorrect:

Lane count is wrong and the turn lanes are not fully mapped.
Lanes:foward = 3
Lanes:backwards = 4
turn:lanes:backward = left|through|through|right

Recommend that this not be added from Bing imagery alone as there has been a significant amount of local construction. OpenStreetCam and/or Mapillary imagery should be required.


This comment has been minimized.


andreis-telenav commented Apr 13, 2017

Hello @markscalf ,
Thank you for your advice. For now, we are focused only on motorways, motorway_links, trunks and trunk_links. We used also Mapillary and OSC in our edits, but from now on we'll pay more attention to them.
If you have any other suggestions or if you'll find any mistakes in our edits please let us know.


This comment has been minimized.


manuelab-telenav commented Apr 21, 2017

We started editing lanes in Detroit area and we’ve encountered some cases where we are not sure how to add lane number.
In the examples below, how many lanes do we have between the red lines? Where should we split the road when adding lane numbers? Is it ok to split them where the red lines indicate?

1. Location: 42.6025814, -83.023706


2. Location: 42.553038, -82.872834



This comment has been minimized.


manuelab-telenav commented May 4, 2017

This is how we map lanes (42.474427, -83.155894):


  • Move motorway_junction to postion 2 (usually where continuous line begins)
  • Split way between 1 and 2; add lanes=5 on motorway
  • Split way between 2 and 3; add lanes=4 on motorway and lanes=1 on motorway_link
  • After 3, add on motorway lanes=4

If you have any suggestions or comments, we are happy to learn from them.


This comment has been minimized.


manuelab-telenav commented Jul 20, 2017

We worked on this issue for 2 months and succeeded to review a large part of motorway, trunk, primary and secondary roads from Detroit area, in order to add or update lane info.

During this project, we managed to review 3100 miles and edit 1730 miles of roads.



Here’s how the number of miles of roads with lane information has increased during the project:

The edits we made cover a large area of the Wayne, Macomb and Oakland counties. In the GIF below you can see an evolution (difference between March and July) of our lane info edits in Open Street Map .

1 lanes_diff

Some edits in Detroit downtown, from April until July:

2 lanes_wayne


This comment has been minimized.


hoream-telenav commented Aug 22, 2018

This issue was moved to TelenavMapping/US_mapping_projects#20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment