OpenStreetMap logo OpenStreetMap

Changeset When Comment
166830118

you know that you can just drag a node to a better position instead of deleting the old node and adding a new one. In fact it is generally advised to do so that the history of the node is better kept. For more info see osm.wiki/Keep_the_history

166830178

you know that you can just drag a node to a better position instead of deleting the old node and adding a new one. In fact it is generally advised to do so that the history of the node is better kept. For more info see osm.wiki/Keep_the_history

166830251

you know that you can just drag a node to a better position instead of deleting the old node and adding a new one. In fact it is generally advised to do so that the history of the node is better kept. For more info see osm.wiki/Keep_the_history

166829985

you know that you can just drag a node to a better position instead of deleting the old node and adding a new one. In fact it is generally advised to do so that the history of the node is better kept. For more info see osm.wiki/Keep_the_history

166829813

you know that you can just drag a node to a better position instead of deleting the old node and adding a new one. In fact it is generally advised to do so that the history of the node is better kept. For more info see osm.wiki/Keep_the_history

166829705

you know that you can just drag a node to a better position instead of deleting the old node and adding a new one. In fact it is generally advised to do so that the history of the node is better kept. For more info see osm.wiki/Keep_the_history

166829328

you know that you can just drag a node to a better position instead of deleting the old node and adding a new one. In fact it is generally advised to do so that the history of the node is better kept. For more info see osm.wiki/Keep_the_history

166367934

typo, port Miami.

166330548

the Bing aerial imagery, which in this part of Miami dade county is more up to date, does not show those jersey barriers and thus they are not there unless you have access to some streetside imagery you have not listed in the sources or mentioned.

166232368

are you sure that this website using has its contents licensed in an OSM compliant way and therefore can be used as a source.

166233626

are you sure that this website using has its contents licensed in an OSM compliant way and therefore can be used as a source.

166237496

are you sure that this website using has its contents licensed in an OSM compliant way and therefore can be used as a source.

166131024

we are not allowed to use google maps as sources as their license is not compliant with ours

166231851

small note, the only angle in this section of the building is 90 degrees but I couldn't get it to square them properly so there are some places were there are issues.

166131024

whats your source for this?

166131083

whats your source for this?

166107938

the Consulate General of Israel seems to still be there and this still leaves multiple tags that point to the Consulate General of Israel still there; this also duplicates the existing Consulate General of Germany, why did you do this.

166044983

Bing street side in the area is multiple years out of date while Esri and Miami dade county latest area significantly more up to date. This is due to construction in the area, for more info see https://www.youtube.com/watch?v=_p__df2Kvuk , https://www.fdotmiamidade.com/okeechobee and https://okeechobeeprojectmap.com/ . As a final note passed the intersection with HEFT the work the Lyft team has done in the area is more accurate then the imagery, once the Miami dade county latest updates (likely in August with imagery from December) I will do another pass through the area cleaning up what every needs it to be best of my ability).

165915883

names are not supposed to be used as descriptions, for more info see:
osm.wiki/Names#Names_are_not_for_descriptions

165863367

Crossings should only be mapped as separate geometry when there is a distinguishable difference across the section of way being considered to be split into a separate crossing way. In this case, as the sidewalk is completely straight across the section and there is no other (in pattern, surface, or other) significant difference across the section of sidewalk so it should not be split. Normal crossings get split as they differ greatly from the sidewalk sections they connect to. In this case, it is very clear that this is a sidewalk that a road happens to cross, where the road is brought to the same level as the sidewalk. Also, this is a spot where vehicles cross a pedestrian traffic way which, essentially the opposite of normal crossings where pedestrians cross vehicle ways; we don't have a proper way to map that currently.
As I previously pointed out, the sidewalk is very obviously continuous across the whole area, both on aerial and (most importantly) on the latest (in the area) street side imagery, this means that it is a sidewalk that the road intersects, not a separate crossing way. The road does technically cross there, so there is a highway=crossing tag on the vertex where the sidewalk and road meet, and nothing else, as there isn't a tag (something like crossings=vehicle) that clarifies that this is a spot where vehicles cross pedestrians compared to the normal pedestrian crossings vehicles. Again, that sidewalk is very clearly one continuous object along the center line of the sidewalk, so no splits should be done.