MLH-Fellowship/RapiD

Figure out which OSM node tagging / information needs to be attached to each mapillary object.

Closed this issue · 0 comments

OSM entities (ways, nodes, releations, etc) can have 'tags' associated with them- tags are non-geometric information that describe an object- the surface of a road, the height of a building, the address associated with a point, etc.

This means that we need to ensure that the proper 'tags' are attached to each entity that we display in the rapid-mapillary layer. To this effect, we need to know how to convert the 4 types of objects to OSM points.

We need two pieces of information to do this:

  1. The tag that uniquely identifies the point / styles it with the correct icon on the map.
  2. A way to record the original mapillary ID as part of the node, so we can do conflation later.

For 1):
A google search for 'osm fire hydrant' brings you to the OSM wiki page about hydrants: https://wiki.openstreetmap.org/wiki/Tag:emergency%3Dfire_hydrant

So, each hydrant in mapillary will need to be an OSM Node with the tag emergency=fire_hydrant. You'll need to do a little searching to figure out what the tagging schema will look like for the other three features!

For conflation, let's also use two tags:

a) mapillary:map_feature=${MAPILLARY_ID}. (more here: https://taginfo.openstreetmap.org/keys/mapillary%3Amap_feature)This will let us figure out what we need to display later on, after we start adding features to the map.
b) mapillary:image=${IMAGE_ID} to save the image that generated the prediction (more here: https://taginfo.openstreetmap.org/keys/mapillary%3Aimage)

Finally, keep in mind that all this tagging information should show up in the rapid feature inspector when each feature gets hovered over!