Skip to content

Mapping turn-restrictions for navigation in 30 cities in USΒ #187

Closed

Description

@srividyacb

Aim:

To map turn-restrictions in 39 US cities using Mapillary as the source.

Task Workflow

  • Here is the workflow to follow to add turn-restrictions to OpenStreetMap.
  • Here is the spreadsheet where we will be tracking the progress.

image

Team : @mapbox/team-data

Features to map : Turn-restrictions by using mapillary as the main source and Bing/Mapbox Satellite imagery.

Process:

  • Two team members can pick one city together and update the spreadsheet with their name.
  • Before starting the mapping run the below overpass query by changing the city name in the query and update the spreadsheet with number of turn-restriction present before mapping.
  • Overpass Query: http://overpass-turbo.eu/s/gqr
  • Divide the city into half based on a road/landmark and work at different parts of the city.

JOSM Setup

Plugins:

Paint Styles

  • Traffic Signs : JOSM Preferences -> Map Settings -> traffic signs

Changeset Comment: Updating turn restrictions in CITYNAME using Mapillary imagery https://github.com/mapbox/mapping/issues/187

Source: Bing/Mapillary

Activity

  1. changed the title [-]Mapping tur-restrictions for navigation in 30 cities in US[/-] [+]Mapping turn-restrictions for navigation in 30 cities in US[/+] on May 24, 2016
  2. geochetan commented on May 26, 2016

    @geochetan

    I came across few Mapillary images in Los Angeles where the turn-restriction was written on a turn-lane boards (white background and black signs).

    screen shot 2016-05-25 at 3 48 33 pm

    screen shot 2016-05-25 at 5 52 58 pm

    In such situations make sure to add no_u_turn turn restrictions.

    More information: Refer Department of Transportation (DoT), California document here.

  3. jinalfoflia commented on May 28, 2016

    @jinalfoflia

    @mapbox/team-data have been working on adding turn-restrictions in 30 US Cities to improve the navigation data.
    ​

    Process we are following
    • Dividing a city to 2 or 3 people based on Mapillary coverage in that city.
    • Update the number of turn-restriction already present in OpenStreetMap.
    • Use Mapillary traffic sign detection to identify the turn-restriction present in the junction.
    • Click on the detected turn-sign to open in JOSM and follow the workflow to add data to OpenStreetMap.
    • Once done with the city add βœ”οΈ to the city in the table below and run the Overpass query to update the number of turn-restrictions added.
      ​

    Below is the overpass query to run for all the users who are working on turn-restriction. (Need to change the timestamp as required)
    http://overpass-turbo.eu/s/gxe

    The number of turn restrictions already present in the cities listed below can be found here. Below is the list of cities where we are adding turn-restrictions:

    Serial No. City Team No. of Restrictions Added Status
    1 Detroit @ramyaragupathy 0 βœ”οΈ
    2 Los Angeles @ramyaragupathy @nikhilprabhakar @chtnha 71 βœ”οΈ
    3 Minneapolis and St Paul @maning @krishnanammala 68 βœ”οΈ
    4 New York City @oini @jothirnadh 168 βœ”οΈ
    5 Phoenix @planemad @poornibadrinath 39 βœ”οΈ
    6 Boston @srividyacb @pratikyadav 40 βœ”οΈ
    7 Chicago @andygo @RichRico 152 βœ”οΈ
    8 Seattle @srividyacb @krishnanammala 30 βœ”οΈ
    9 Portland @jothirnadh @samely @RichRico 7 βœ”οΈ
    10 El Paso @pratikyadav 0 No mapilary coverage
    11 Austin @poornibadrinath @nikhilprabhakar @jothirnadh 25 βœ”οΈ
    12 Huston @nikhilprabhakar 3 βœ”οΈ
    13 Columbus @karitotp @krishnanammala 10 βœ”οΈ
    14 Atlanta @karitotp @samely @RichRico 4 βœ”οΈ
    15 Washington D C @jinalfoflia @abhisheksaikia @chtnha @pratikyadav 162 βœ”οΈ
    16 Indianapolis @RichRico 24 βœ”οΈ
    17 Baltimore @poornibadrinath @jothirnadh @nikhilprabhakar 82 βœ”οΈ
    18 Las Vegas @srividyacb @RichRico 24 βœ”οΈ
    19 Atlantic City @samely 1 βœ”οΈ
    20 Buffalo @samely 2 βœ”οΈ
    21 Columbus @krishnanammala @karitotp 10 βœ”οΈ
    22 Denver @karitotp @RichRico 11 βœ”οΈ
    23 San Antonia @karitotp @abhisheksaikia 2 βœ”οΈ
    24 Jacksonville @samely 0 βœ”οΈ
    25 Miami @Andygol @RichRico 127 βœ”οΈ
    26 Portland @samely @RichRico @jothirnadh 7 βœ”οΈ
    27 Nashville @karitotp @RichRico @chtnha 1 βœ”οΈ
    28 Kansas City @karitotp 35 βœ”οΈ
    29 Mikwaukee @karitotp @abhisheksaikia 25 βœ”οΈ
    30 Orlando @RichRico 27 βœ”οΈ
    31 Philedelphia @abhisheksaikia 4 βœ”οΈ
    32 Dallas and Forthworth @jothirnadh 13 βœ”οΈ
    Total added 1133

    /cc @planemad @maning

  4. Andygol commented on May 31, 2016

    @Andygol
    Contributor

    Chicago is Done 🎯
    /cc @planemad

  5. planemad commented on May 31, 2016

    @planemad
    Contributor

    We have updates to the experimental OSM navigation map to help review and add turn restrictions from Mapillary quickly.

    untitled2

    http://mapbox.github.io/osm-navigation-map/

    Features

    • Inspect existing turn restrictions
    • Inspect Mapillary photos with detected turn restriction signages
    • Open location in JOSM via remote control on click
    • Add a reviewed marker with the status of the detected restriction:
      • Valid Restriction is correct and has been mapped
      • Redundant The restriction is correct but is not useful to add to the map. eg. No turn against a oneway.
      • Invalid The restriction was wrongly detected, is temporary or in the wrong location. Do not map.

    Please submit feedback and file issues at https://github.com/planemad/osm-navigation-map/issues

    cc @mapbox/team-data

  6. planemad commented on Jun 1, 2016

    @planemad
    Contributor

    Reminder to @mapbox/team-data to take care of conditional restrictions like this:

    screenshot 2016-06-01 17 52 07

    The correct tagging is restriction:conditional=no_left_turn @ (Mo-Fr 06:00-09:00,16:00-18:00). This is already documented in the workflow.

    Also be careful with conditional restrictions since JOSM will not recognize restriction:conditional and will not display the type in the relation list. Here duplicate restrictions were added to the same roads.
    untitled2

  7. poornibadrinath commented on Jun 2, 2016

    @poornibadrinath
    Contributor

    While marking turn restrictions near one ways as redundant, it would be great to check instances like this with u turns.
    image
    image
    While left and right turn restrictions near one ways are redundant, u turns on one ways can be valid.

    /cc: @mapbox/team-data

  8. Andygol commented on Jun 2, 2016

    @Andygol
    Contributor

    @mapbox/team-data I want to attract your attention to this case of turn restriction https://www.openstreetmap.org/relation/2573759.

    Here is no_left_turn restriction with 3 via members!

    image

    This restriction makes sense because of the markings before the crossroads. Here is solid marking so drivers not allowed to change their lanes from the node where motorway_link join to the primary road down to the intersection. Drivers traveling from the motorway may move only by the most right lane to right. On the other hand, drivers moving along primary not allowed to make right turn, that described by this turn restriction - https://www.openstreetmap.org/relation/2573760

    Please be careful when you are editing

  9. abhisheksaikia commented on Jun 3, 2016

    @abhisheksaikia

    The Mapillary layer in the navigation map is showing a series of possible turn restriction images.

    screen shot 2016-06-03 at 3 37 20 pm

    A series of mapillary images with possible turn restrictions in Georgia Avenue

    But when I am opening the at same area in JOSM, the mapillary plugin is not displaying the series of images that are displayed in a line around "Georgia Avenue".

    screen shot 2016-06-03 at 3 40 18 pm

    No mapillary images displayed in JOSM

    The plugin has been updated and I have tried deleting and loading the mapillary layer again multiple times. The problem still persists.

    Is this because the mapillary layer has not been updated?

    cc @gyllen @planemad @jinalfoflia

  10. samely commented on Jun 3, 2016

    @samely

    @planemad
    While working on turn restrictions, I found some stuff that I think could be improved.

    • Could you change the style of points? In the tool, you easily see the red and the bright green ones, but we need to fix just the green ones. So, if you could change the color and size of the points that aren't already done, would be great.
      image
    • When you work in a certain city, we just see WIP, but we don't know what part is already done. So I think in the spreadsheet we could add a column to add the covered area i.e. Done the north part of Ventura fway in NorthWest Los Angeles
  11. jinalfoflia commented on Jun 4, 2016

    @jinalfoflia

    Week [ 30th May 2016 - 3rd June 2016]

    The team has completed adding 425 turn restrictions in a total of 14 cities since 25th May 2016. This week the team completed 9 cities and added 216 turn restrictions in the following cities:

    • Austin
    • Baltimore
    • Boston
    • Columbus
    • Houston
    • Indianapolis
    • New York
    • Pheonix
    • Portland
    • Seattle
    • DC
    • Chicago

    Please refer to the above table to get more details about the cities completed and the cities that we are currently working on.

    /cc @planemad @maning

  12. planemad commented on Jun 4, 2016

    @planemad
    Contributor

    @samely looks like there was some confusion in the style. have updated it:

    • Blue markers are the areas that have been reviewed
    • Green circles are detected Mapillary signage (visible only after z14)

    openstreetmap_navigation_data_map

  13. jinalfoflia commented on Jun 11, 2016

    @jinalfoflia

    Great work team πŸ‘
    A team of 14 members worked on 32 US cities adding 1178 turn restrictions in 13 days. The time spent on each of the cities varies based on the Mapillary coverage and number of turn restrictions detected. The city-wise stats can be found here.πŸ’₯

    Next Action[s]

    • The team will work on a work-flow to validate the added turn-restrictions.
    • The team will work on re-reviewing all the cities based on the workflow, to ensure that all the detected turn-restrictions are mapped correctly.

    /cc @mapbox/team-data

  14. jinalfoflia commented on Jun 20, 2016

    @jinalfoflia

    The team will work on a work-flow to validate the added turn-restrictions.

    This is the trial run on the proposed work-flow to be followed to validate the turn restrictions added by the team in the 30 US cities.

    Team: @abhisheksaikia @jinalfoflia @oini

    • Use Overpass to extract the turn restrictions added by the team from 25th May to 11 June
    • Create the .osm per city and share it with the team
    • The team will validate the turn restrictions added in these cities.

    Changeset comment to be used: Validating turn restrictions in the US cities using Mapillary imagery https://github.com/mapbox/mapping/issues/187

    /cc @planemad @abhisheksaikia @oini

  15. jinalfoflia commented on Jul 7, 2016

    @jinalfoflia

    @mapbox/team-data team has completed the validation of close to 900 turn restrictions mapped in the 30 US cities using the above work-flow. The team will next jump into validating 300 odd conditional turn-restrictions in these cities.

  16. jinalfoflia commented on Jul 21, 2016

    @jinalfoflia

    @mapbox/team-data completed validating the conditional turn restrictions in the 30 US cities.πŸ’₯ No further actions here. Closing it.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions