Please stop rounding the ramps of, that is in no way representative of the shape of the ramp.

please stop mapping turn:lane tagging as geometry.

this was already mapped correctly because we shouldn't map turn:lane tagging as geometry.

next time please don't name things with a description since names aren't descriptions, for more info see osm.wiki/Names#Names_are_not_for_descriptions .

also entrances don't go in the middle of a road, they describe places you can enter a building, so usually they are at the spot a footway meets a building.

Happy mapping,
Udar.

if you have access=private on a road or gate it is implied that the other uses are also private, as in if you have access=private you don't need motor_vehicle=private. you only need to specify a value for motor vehicles, bicycles or any other mode of transportation of it is different than the default or is only usable by certain modes like a bicycle and foot path.

also names aren't descriptions.

Happy mapping,
Udar.

so then logically we should also remove footway=* tags. that's the pattern here, you have a tag telling you what the feature is and then then a tag that starts with what it is from the previous tag telling you what type of what it is it is.
for example sidewalks, highway=footway tells you they are a footway but since sidewalks a re more specific than the nebulous "footway" you specify the type of footway with footway=sidewalk. the same logic applies for crossings. highway=footway tells you they are pedestrian navigation features, footway=crossings tells you that the feature is for crossings roads but that isn't all the information that matters about a crossings, you also have to know whether or not its signalized since that is what distinguishes crossings, not how they are marked so you need a crossings=*.
As I clearly laid out in the above post (see it for more detail) this makes crossings:signals=* the imposter here and thus it should be deprecated.

just because the tag crossings=* has in the passed been inconsistently interpreted in the passed doesn't mean it has to now. the change is rather simple in fact, all we have to do is deprecate all crossings=* values other than uncontrolled and traffic_signals (as laid out above); and although that change would make it abundantly clear what the meaning of crossings=* is we specify in the wiki that it is purely for whether or not it is signalized. that is anyways basically the state of things now. again all we have to do is deprecate all 910 other tags apparently.

again, as to keep the tagging internally consistent either we deprecate crossing:signals or both crossings=* and footway=*. pick your poison apparently.

Happy mapping,
Udar.

If we deprecate crossing we would be going against all the conventions that have already been established elsewhere in the tagging, for example we don't describe sidewalks as a set of properties added to ways with the tag highway=footway, we add footway=sidewalk to describe that something is a sidewalk. by the same logic we shouldn't describe different types of crossings with different tagging, we should just say the type of crossing through a crossing tag. in the same way as footway=* tells you the type of footway crossing=* tells you the type of crossing.
∴ if we deprecate crossing=* we should also by the same logic deprecate footway=* since they both serve the same purpose in specifying the type that they are.

I'll add a note here that there are really ony two types of crossings, uncotrolled and controlled(traffic_signals), I agree that the tagging still needs some work, I just think that we should deprecate crossing=unmarked as we did with crossing=marked since crossing=unmarked and crossings:markings=no encode the same information and since they are duplicate information one should be removed. Due to the fact that crossing=uncotroled and traffic_signals (what I'm calling controlled) do not encode the type of marking present at a crossing, crossing:markings=* is neccessary for cases were crossinga:markings is not "no" and ∴ crossings=unamrked should be deprecated. this does not apply to crossing:signals=* since if crossing=unmarked is deprecated then the two values of crossing=* would already encode the same infomation as crossings:signals=* and since crossings=* already exists we dont need a new tag and ∴ crossings:signals=* should be depredcated. essentially we either deprecate crossing:markings or crossings:signals and since it is significantly harder (it takes exponetially more tags) to encode crossings:markings fully into crossings=* it should be the one thats kept since all it takes to encode the same information as crossing:signals into crossing=* is two tags that we already have.

Happy mapping,
Udar.

please in the future do not add the crossing:signals=* because it is implied the by the crossings=* value; this is because crossings=uncontrolled and crossing=unmarked both imply that the crossings isn't signalized (aka crossing:signals=no)(literally the definition of uncontrolled in this context) and crossings=traffic_signals implies crossing:signals=yes because that means that the crossings has signals.

Happy mapping,
Udar.

as a note, the refs are at least somewhat incorrect, I don't know how to check what they should be, I just traced based on newest imagery.

next time please don't remove footway=sidewalk from ways along the side of a road (even if it is a service roads) that are tagged as sidewalks.

the bicycle=designated foot= designated means that this is bicycle and foot path specifically marking those as private stops that, also these aren't for cars so the general access=private doesn't really apply to the bicycle and foot paths.

what the source for this because on the Bing aerial imagery Okeechobee Frontage Road connects between the two carriageways of Northwest 138th Street Extension.

sorry miss read the changeset comment, my brain registered "colour = White -> roof:colour = white" instead of what you write, my bad. I'll be more careful next time.

were these checked with aerial imagery before uploading, I ask because some of these may be the color of the walls of the building not the roof.

as mentioned previously we (OSM) don't have the right to use Waze data as a source and since that is the source for this commit I have reverted it, for more info see osm.wiki/Waze .

changeset/158067086

I saw a world spanning commit so I translated the changeset comment to see if it properly described what was in the commit and it wasn't so I left the comment about that and because from my experience when there are geographically large commits made by new contributors there's a high chance of the commits being vandalism so I translated some of the name changes to check. the changed names came out sus so I left a comment pointing out that there's possibly an issue here so that someone with more experience and knows the language can check them and see if they are vandalism. I just didn't call it vandalism from the get go since from other commits you seems to be mostly well intentioned so I left it implied. I was just tying to be nice about it, I always like to give others the benefit of the doubt on these things unless it is really clear what it is. it isn't ignorance to point out possible vandalism, the whole point of me pointing out that I don't know the language was to point out that there might be vandalism in this commit and other who know the language can fix any issues; ignorance would be me calling it vandalism without pointing out that I don't know the language.
I was just flagging this commit so that others may look at it and check its contents who actuality know you language. also I didn't just use duck duck go, I used other translation services and they all spat out nonsense, if multiple translation services spit out nonsense then theirs a high chance of issues.

please respond

it seams like the changes made to the names of these countries translate to completely nonsensical things

next time can you please leave a better changeset comment, for m ore info see osm.wiki/Good_changeset_comments .
also after translating some of the names you added with the default duck duck go translator (I searched "translate to english") it seams like the names add are likely incorrect since I doubt that "West Harbour" is a good translation for "Atlantic Ocean". I may be missing something since I don't know the language but it seams based on the translation that at least some of these translations are incorrect.