mapbox / osm-navigation-map

A map to explore navigation data in OpenStreetMap

OpenStreetMap Navigation Map

The OpenStreetMap Navigation map is a web application which uses Mapillary vector layer to highlight the traffic signages detected in Mapillary images. The application is helpful to add/verify/modify turn-restrictions on OpenStreetMap.

Develop

• git clone
• npm install && npm start

Tilesets

The map uses various custom Mapbox tilesets maintained by @planemad that has OSM navigation data extracted via overpass/shaktimaan. The tilesets are updated infrequently, please request an update if required.

• Project cities boundaries - maning.worldcities
• OSM turn restrictions type=restriction - planemad.osmturnrestrictions
• OSM turn lanes turn:lanes turn:lanes:forward turn:lanes:backward - planemad.osmturnlanes
• OSM traffic signals highway=traffic_signals - planemad.osmtrafficsignals
• OSM speed limits maxspeed=* - planemad.osmmaxspeed
• OSM access restrictions access=* - planemad.osmaccess

Interface

OpenStreetMap Navigation Map consists of 3 layers which helps you to navigate between OpenStreetMap data and Mapillary data.

• Tile Boundaries : Tile boundaries is a overlay layer which divides the map into tiles which is visible after zoom10. This layer helps to divides the working area/city into blocks and make sure that mappers don't work on the same area.

Image showing tile boundaries along with tile numbers

• Oneways : The Oneway layer highlights the roads with oneway tag in OpenStreetMap which helps the mapper to analyse the turn-restriction and the road data before adding it.

Image showing oneways highlighted in map style

• Mapillary Street Photos : Mapillary Street Photos enables the Mapillary vector layer on the map which highlights the detected images with signages in it. The arrow on the GPS traces indicate the direction of the Mapillary sequence.

Image showing Mapillary traces in map style

Map Styles

OpenStreetMap Navigation map highlights different features present in OpenStreetMap and Mapillary detected signs in different colours. Below is the description on colours used in the map style:

• Mapillary detected Turn-restriction : The turn-restrictions detected on Mapillary vector layer are shown in the form on respective detected icons. The turn-restriction signages differ from country to country. Below are few examples:

• Turn-Restriction present on OpenStreetMap : The map shows the turn-restrictions present on OpenStreetMap for the mapper to get the overview of the detection and go forward.

  • No-turns : No turn-restriction like no-left-turn, no-right-turn, no-u-turn and no-straight-on are styled with

    • from as yellow line.
    • via as red circle/dashed-line.(orange in case of no-u-turn)
    • to as red dashed-line.
      

  • Only-turns : Only turn-restriction like only-left-turn, only-right-turn and only-straight-on are styled with

    • from as yellow line.
    • via as blue dot/line.
    • to as in blue dashed-line.

Workflow

Step 1

Login to OpenStreetMap : Logging-in to your OpenStreetMap account helps to know who reviewed the detected turn-restriction.

Step 2

Detecting turn-restriction images : The position of the detected signage will be a probable location of the turn-restriction.

1. When clicked on the specific detected signage, you get to edit add/edit the label for the turn-restriction.
2. The respective images location of detected signage is highlighted as big green arrow. The highlighted green arrow have the signage in it and lets you to play the sequence of the images to get an overview of where the turn-restriction is applicable when you click on it.
3. The detected image Mapillary sequence can be played to see the images and get the identify better image with signage.
4. laying the sequence all the photos present in that sequence are shown as smaller green arrows. We can also open image in a new tab to get a wider picture of the turn restriction by clicking on the image.

Note : Sometimes the popup might hide the detected image location. Close the popup to find green-arrows with image location

Step 3

Add/Verify/Modify turn-restriction : While navigating in the navigation map using image sequence, we can find out where and to which junction the turn-restriction applies to.

• Click on Edit Map to edit using iD editor - Follow instructions here on how to add turn-restriction in iD editor.
• When clicked on detected signage, the map view bounding box will be downloaded as layer in JOSM (if JOSM is open) - Follow instruction here on how to add turn-restriction in JOSM editor.

Step 4

Label reviewed turn-restriction : Once done, update the status of the restriction on the OSM navigation map:

• Valid - The detected restriction is valid and is either already present on OpenStreetMap or added to OpenStreetMap base dont his workflow.
• Redundant - The detected restriction is correct but is not necessary to be added to OpenStreetMap since it is redundant for routing. eg. A no left turn against a oneway road.
• Invalid - The detected restriction on Mapillary is incorrect. Do not add to the map
• Note - An OpenStreetMap note can be added if you want any local mapper to verify the turn-restriction before it is added to OpenStreetMap.

Note : For junctions where same signage is detected multiple times, review one of them and leave the rest unattended and do not label them with any of the above.

osm-navigation-map's Issues

Using mapillary-js

From #1, @kepta lets figure out how to integrate mapillary-js for providing more context of photos to mappers.

The objective is to help a user establish the correct position and orientation of a photograph on the map.

Use restriction sprites instead of circles

From #36

• https://www.mapillary.com/sprites/sprites.png
• https://www.mapillary.com/sprites/[email protected]
• https://www.mapillary.com/sprites/sprites.json and
• https://www.mapillary.com/sprites/[email protected]

Functionality to expand the Mapillary image inside the navigation map itself.

@planemad - It would be great if we could expand a Mapillary imagery in the navigation map itself by double clicking on the small image shown in the tool. This would mean that we don't have to open the image separately in a new tab.

Current output:

We only have a small image on the left bottom corner which is not interactive. It is difficult to determine a turn restriction as the image is small.

Expected output:

When we double click on the mapillary image it should expand the image to full-screen size inside the navigation map tool itself so that we don't have to open the image in a new tab or JOSM.

Highlight selected restriction

cc @maanyaumashaanker

Mapillary objects not located on the trace

Possibly related to #51

http://mapbox.github.io/osm-navigation-map/#17.72/49.25876/-123.02055

Many detected signages don't appear to coincide with the coverage layer traces. This particular object does not seem available through either iD or JOSM.

cc @srividyacb @oini @gyllen

Allow updating previous review

Due to #4 and other human errors, it is useful to be able to update the state of a previous review.

cc @ramyaragupathy

Add a geocoder to the map

Geocoder will easily help us to jump to a map location, instead of just panning through the map.

Reviewer information for each TR

There should be a way to add mapper details to each TR. Also if the TR has already been reviewed, along with the review status, reviewer name should be highlighted as well.

cc @planemad

Autoupdate the map on the client-side

When more than one person is editing the same location, it will help to have a sense of changes being made by other users. One approach to this now could be to auto-refresh the browser each 5 minutes or so and get the updated dataset. We should also give an indication on the UI for long along the map was updated.

cc: @planemad @geohacker @amishas157

OSM login

Usernames have to be entered manually. Adding OSM login will make this easier.

cc: @planemad @geohacker @amishas157

Automate updating the tilesets

Currently, the tilesets used by osm-navigation-map need to be updated manually. There are two approaches we can take to automate this:

• Have an EC2 instance than runs a scheduled process that uses shaktimaan to update the tilesets.
• Have a more generic tool that listens to a dynamosm stream for incoming features, filters it based on a set of tags and updates a tileset or dataset API.

cc: @planemad @geohacker @amishas157

Forgetting the reviewer name

The navigation-map is not remembering the reviewer's name here. http://planemad.github.io/osm-navigation-map/?review=valid&reviewer=Chetan_Gowda#19.51/38.90555/-77.07452

• Browser: Google Chrome: Version 50.0 (64-bit)

@planemad

Allow deleting reviews

Dataset API is quickly getting overloaded due to multiple reviews for the same restriction. We need to be able to delete unnecessary reviews to reduce the payload.

Expand Mapillary restriction filter for European cities

The map currently only highlights turn restrictions in US and Canada based on this signage list.

This list needs to be expanded to highlight restriction in Europe and the rest of the world. Need to do some digging on what are the expected values of turn restrictions in the Mapillary layer for the other geographies.

@gyllen what the best place to get full list of possible Mapillary objects, is it https://github.com/mapillary/traffico/tree/master/mapillary-mappings ?

Image location not matching with imagery and OpenStreetMap Data

Image location mismatch

http://mapbox.github.io/osm-navigation-map/#18.33/49.23247/-123.01175

Here the location of the image showing in Mapillary layer is not matching with the OSM data present around. Seeing the same difference in both iD and JOSM editors.

@gyllen It would be great if you have a look at this and see what is making this difference of location.

cc @planemad

Allow zooming into Mapillary image

Expected behavior: Clicking on Mapillary thumbnail should display full size image in the same view.

cc @nikhilprabhakar

Highlight Canadian restrictions in Mapillary layer

Save mapillary id, country name and timestamp for each review

Adding this information will help with stats and providing feedback to the mapillary team.

cc @planemad @geohacker @amishas157

Visual changes in representing detected Mapillary signage

@planemad Currently, the road signage that are detected in the Navigation map are represented in small sized green colour dots. These are only visible beyond zoom level 14.

Problems:

• The dots are too small to spot on green colour mapillary path background. After zoom level 14 we spend a lot more time in panning over the map in search of the ones which are not reviewed

Proposed changes:

• A colour change in the signage detected dots and bigger size of the circle that represents it
• Allowing them to be visible in higher zoom levels such as 10 or 12

cc @poornibadrinath

Country-wise datasets

This would help with

• Separating stats for different countries #46
• Loading data only specific to the country being mapped
• Not overloading a single dataset with all restrictions data

cc: @planemad @geohacker @amishas157

Review field always populated as `valid` for a feature

While marking a reviewed turn restriction as redundant, feature seems to be picking valid status instead of redundant. Same is the case with invalid option too.

Status field for a feature, should be populated with the chosen option.

@planemad

Add edit in iD link

cc @maning

No change in marker position when there are group of Mapillary photos

Here the Mapillary layer is detecting two turn-restriction in the images.

When opened in JOSM/iD the Mapillary image sequence (Next/Previous picture) shows multiple photos of the road ahead but the image marker won't move forward or backward and the images continues to appear (upto 10-15 and more). With this group of images, its hard to find the image where the sign was detected.

Seeing the same in Mapillary website too where the marker is not moving but image sequence keeps changing.

@gyllen Is this the GPS problem or anything else?

cc @oini @manoharuss @planemad

Stats by country

@planemad Thanks for the live stats counter.
Continuing from #34, it would be awesome to have live stats counter per country as well in the OSM navigation map.

cc: @poornibadrinath

Points marked as done are not showing up on the map when browsed in Chrome.

The points marked as done are not showing up on the map when in Chrome browser. It shows this error message:
XMLHttpRequest cannot load https://api.mapbox.com/datasets/v1/planemad/ciotrgzko002ew8m29jh4lvhf/featu…aXlsbnd5dCJ9.7Ui7o2K3U6flUzDGvYNZJw&start=1060ece262ab71c00aacc1310349c72b. The 'Access-Control-Allow-Origin' header has a value 'http://127.0.0.1:4000' that is not equal to the supplied origin. Origin 'http://planemad.github.io' is therefore not allowed access.
map.js:906 Error: Input data is not a valid GeoJSON object.

This happens only with Chrome.

When in other browsers, eg. safari, the clusters that are previously worked are seen clearly

Create new dataset for Canada restrictions

Show image location on clicking Mapillary restriction object

From #51 #53 #54 #56 the Mapillary detected restriction location has changed from the location of image capture, to predicited signage location.

This is confusing for the reviewer as it is difficult to understand from which location the photo was taken and to which road the restriction applies.

As per the API documentation #48 (comment) we should be able to use the Image Layer tiles to find the display the photo location on the map.

Ideal interaction would be:

1. Click on detected object marker
2. Highlight image locations that correspond to that restriction
3. If more than one image for the restriction, hovering/clicking over image locations should load the corresponding Mapillary image

Reference: Mapillary Vector tiles docs #48 (comment)

cc @amishas157 @ajithranka @oini @srividyacb

Reviewed restrictions stuck at 5 on map load

From #36

Looks like some issue requesting the reviewed restriction data from the Mapbox Dataset API. Reloading after a few times seems to fix this. Initial count of 5 needs to be checked.

Feed for Mapillary Objects

Lets start thinking about how we can get a feed going with the latest detected objects from Mapillary. The database lookup would be quite expensive. So maybe we can cache something every hour and send back through an API.

We are rewriting our v3 API to use netflix falcor. Is that something you would be able to consider using for getting data from the feed. We will have an easier API REST API as a part of v3. But falcor will give you more abilities to tweak your requests.

Create updated readme for mapping workflow

Having the TMS layer for the blocks in the navigation map

It will be great to have the blocks we are working on for SF turn restrictions in the navigation map instead of the tms layer in JOSM. Will help us get a better idea of where we are rather than verifying the roads and the borders.

The layer is tms[99]:https://api.mapbox.com/v4/pratikyadav.3a2c11f9/{zoom}/{x}/{y}.png?access_token=pk.eyJ1IjoicHJhdGlreWFkYXYiLCJhIjoiMTA2YWUxNjRkNmFmZGQ4YzAxZWFiNDk0NDM1YjE1YjAifQ.4P6N5dNmA_WQXd3BsJvu5w

cc @planemad

Min/Max zoom for Mapillary sources

Upgrade mapillaryTrafficSigns to have min/max zoom to 14 this layer will contain all information. Quering lower zoom levels will just make unecessary tile requests.

Upgrade mapillaryCoverage to have maxzoom 14 (its the last tile you ever need)

Show bearing for mapillary images

Similar to iD, we can show the location of the image, the camera angle and a sprite for the traffic signs.

Related issue: Use restriction sprites instead of circles

cc: @planemad @geohacker @amishas157

Location of detected sign does not match with iD and JOSM

Here the location of the detected signage (on the right) does not correspond to iD and JOSM. Both iD and JOSM locates the same image where the left dot is (on the left). Also, the left dot is no longer clickable.

cc @planemad @amishas157

User feedback

The map has been highly useful to quickly add missing turn restrictions from Mapillary. There is significant time saved by avoiding the use of JOSM. Requests:

• A method to add a marker to the map indicating the location has been reviewed - added, redundant, false positive
• Navigation controls to reorient the map if rotated
• Integration of mapillary-js for interactive photo browsing

Dataset API limited to 100 results

Need to implement pagination to fetch more than 100 results. Reference: https://github.com/osm-in/flood-map/blob/gh-pages/js/chennai.js#L148-L178

Mapillary object tiles not loading

Sometimes the detected restrictions from Mapillary fail to load, there are these errors in the console:

cc: @planemad

Multiple entries created for the same TR

There should be a way to show the current review status of a turn-restriction. At present, this is not detected, instead we have multiple entries created for the same point.

@planemad

Mapillary Vector Layer showing up signage location and not image location

Ref #53 and #54

Mapillary seems to have updated it's traffic-sign vector layer with the probable location of the object (traffic sign) rather than the location from where the image was taken. This is great except that without the knowledge as to which side the sign is facing, it is quite difficult to gauge which two roads the restriction is applying to. Also, many a times, this detection is not accurate. Thus, it would be of extreme help if we could see both the location of the object as well as the location from where the image containing that object was taken in the osm-navigation map itself. This would simplify and fasten up our process of adding turn restrictions manifold.

• Example of an Incorrect Detection: http://mapbox.github.io/osm-navigation-map/#17.72/49.25876/-123.02055

• Example of a Correct Detection: http://mapbox.github.io/osm-navigation-map/#19.14/45.41285/-75.71271

In both the above cases, we had to look around in iD and JOSM to get the location of the same image containing the traffic sign to try and add it to OSM.

cc @planemad @gyllen @maning @geohacker @srividyacb @abhisheksaikia

Update Canada city boundaries

Issues with hiding the mapped turn restrictions

The click button for hiding the existing turn restrictions is not working for nodes. It only hides the line features and leaves the nodes. It would be great if we can hide and unhide both point and line features as well.

cc/ @planemad

Style OSM turn restrictions better

Showing existing OSM turn restrictions on the map help to easily compare with Mapillary restrictions and add/update the data onto the map.

_Current styling of OSM turn restriction `from` `via` and `to` members in red_

@rasagy can you review the issues with this styling from a reviewer perspective and post your notes on how it should ideally look?

cc @andreasviglakis

Zoom-in button in the map is not working

@planemad - The zoom in button in the right top corner of the OSM navigation map is not working. As as a resuIt, I am unable to zoom-in inside the map using the button.

Can you please fix this issue?

Add reviewer name to each review

Simple text box for the reviewer to add their name when submitting/updating a review. This will help in stats collections.

Marker clusters for reviewed TR

It'd be great to have a cluster layer with numbers for reviewed TRs. This would make it possible to just look at an area and get an approximate number of reviewed features.

@planemad

Pulling out filtered stats

@planemad It would be great if there is a straight way to pull out stats straight from the Navigation Map from set time to time. This would allow us to have day to day stats(Valid,Redundant,Invalid) for that city during Canada mapping sprint.

Even better. From the data team usernames on this page it would be awesome if we can pull out stats only for our data team and total reviews seperately. So we can have a clear idea of how much community participation was involved and how much data team activity is involved.

cc @poornibadrinath

Mapillary object tiles at lower zoom levels

A recurring pain point while adding turn restrictions is not being able to have a high level overview of detected restrictions in a city, since the Mapillary vector tiles start at z14.

Would be great to have detected turn restrictions available at lower zoom levels from z10, and other objects available at higher zoom levels.

cc @gyllen @geohacker @ajithranka

Missing mapillary images when loaded in JOSM

Mapillary images shown in the osm-navigation-map are not being loaded in JOSM. I came across this issue quite a few times, so thought of ticketing this.

Mapillary image detected in osm-navigation-map

No mapilary image in loaded on JOSM

Imagery location:

• http://mapbox.github.io/osm-navigation-map/#17.88/45.45784/-73.82010
• http://mapbox.github.io/osm-navigation-map/#18.58/45.42085/-73.97119

This issue is already mentioned in our previous mapping task aswell

cc:/ @planemad @geohacker

Splitting area into blocks

Adding a new layer that shows blocks like in tasking manager inside the city boundaries that can help map in a more organized way when more than 2 mappers are involved. A lock and release function would be a bonus.

cc @planemad @geohacker @ajithranka @amishas157

Different colours for identifying Valid, Redundant and Invalid Restrictions

It would be great if we could have different colours to identify or differentiate between valid, invalid and redundant TR nodes or points, so that it becomes easier while adding, checking and validating.