the problem is that these are bicycle and foot paths so removing the foot=* and bicycle=* removes that fact, especially removing the foot=* since this is for those (likely employees) with access to this private land, thus just leaving the highway=cycleway alone makes it seem as if this is only for cycling and not for foot and that is wrong, that is why I put the foot=* there in the first place.

how, I don't see how, access=private tells you who is allowed on a way while *=designated tells you the type of transportation allowed on a way not who is allowed on a way, removing bicycle=designated and foot=designated would remove important information in this case. access=private tells you only certain people can access this way while bicycle=designated + foot=designated tells you that only bikes and pedestrians on foot are allowed to use these ways. the *=designated tags don't say that anyone can use the way they imply no such thing, they just tell you the type of transportation allowed on the way and in that way doesn't override the access=private.

next time can you please leave a better change set comment, for more info see osm.wiki/Good_changeset_comments and split your commit up geographically so that the geographic size of the commit is smaller, for more info see
osm.wiki/Changeset#Geographical_size_of_changesets

please respond

next time can you please leave a better change set comment, for more info see:
osm.wiki/Good_changeset_comments
Also I was wondering why you are removing sections from the timezone relation.

Thank you so much for the help with the roundabout.

So can you please either add the new building or move the POI so that it’s in a building.

first of all, on OSM we don't map for data consumers, if an app is using the OSM data incorrectly its on them to fix their implementation. I have mapped enough pedestrian and foot paths in Miami that look the exact same to be 99% certain that this is a pedestrian and foot path along with driving by many a time as I used to live somewhat near by. again designated does not necessarily mean public access, it just means that the specific type of traffic (in this case bicycle and foot) are allowed to use the path, again the access=private is what marks it as private.
again as previously explained desginated only tells you which transportation modes are allowed to use a specific way, private, permit, etc. tell you what the permissions on the way are, aka. if you need permission to access a way.
again access=private already tells you that, while changing bicycle=designated to bicycle=private actively lowers the amount of information encoded as we are no longer specifying that this way is specifically for pedestrians and bikes. again let me make it abundantly clear that these ways are tagged as private due to the access=private tag.
also don't pretend I don't know what the underline is as I have made several fixes to its alignment after the second phase of construction finished up last year.

It is designated because from what I can tell it is a pedestrian and foot path and thus the tags used are highway=cycleway + foot=designated + bicycle=designated, those are just the community decided on tags for pedestrian and foot paths, that is why there is the general access=private because unless something specifically overrides the general access=* tag it applies to all uses, and the designated value doesn’t override the access=private because designated tells you whether a specific mode of transportation is allowed on a way and if so how, it does not tell you what the access requirements are (what private tells you). In essence the access private tells you that bicycle access is private and foot=designated + bicycle=designated tells you that only bikes and pedestrians are allowed to use the path which because of access=private means that only private pedestrians and bikes are allowed to use the path. I have already explained this in comments left on your commits previously.

please respond

thank you so much for the clarification, looking at the imagery it does seem a bit unclear as to weather or not there is a road connection between the two ends of Dickson Drive divided by the pedestrian features and I think its safest to leave it as pedestrian until better aerial or street side imagery makes that clear.

while I have y'all's attention, I hope it wouldn't be to much of a bother if y'all can check weather or not the roundabout at node/384024486 is complete and if so fix the geometry as there is nothing there on the latest imagery and I am basically certain that they are placing a roundabout at that location. if its to much of a hassle please ignore, y'all just have significantly better imagery then I have so can check the state of that construction.

since there isn't any good up to date imagery in the area I was wondering if you could provide screen shots of the "Lyft-owned aerial imagery " so that those of without access can check. I ask as a contributor, who from what I can tell goes to UM seemed pretty sure that it was only pedestrian in the area, from what I could tell; I am just trying to clarify things on my end here, since this commit leaves me unsure on what exactly is what since we are unlikely to get new OSM compliant aerial imagery sources in this area until at least July, likely August.
If you cant I understand.

the positioning of this seems off in the aerial and street side imagery available in OSM, so I was wondering what your source for this commit is.

changeset/162800792 seemingly didn't fully upload to OSM so trying again.

changeset/162837745

changeset/162800792 seemingly didn't fully upload to OSM so trying again

changeset/162807379

accidentally reverted the wrong commit, got the tabs mixed up, the accidentally reverted one was my own so not effecting anyone here, will be more careful next time.

changeset/162800792

my bad accidentally reverted my own commit, got the tabs open mistaken

these are bike and foot paths and thus necessarily have tags of "bicycle=designated" + "foot=designated" + "highway=cycleway", they already have a tag of access=private, that is enough to mark these as private.

changeset/162800365

these are bike and foot paths and thus necessarily have tags of "bicycle=designated" + "foot=designated" + "highway=cycleway", they already have a tag of access=private, that is enough to mark these as private.

changeset/162800351

as I have previously mentioned, these are bike and foot paths, that means that they have tags of "bicycle=designated" + "foot=designated" + "highway=cycleway", so stop changing the bicycle=* value. there is ageneral access=private, that already tells you that it is private, disgnated tells you that this path si specifically for use by bike and foot with the general access=private telling you its private bikes and pedestrians, please stop changing this.

Happy mapping,
Udar.