That was me converting "maxweight = 33 Tons" into standard metric tons because I didn't know how to properly tag US short tons.
maxweight = 33 st would be more appropriate.

Yes, the original value was formatted incorrectly and at the time I think was under the impression that all measurements on OSM should be in metric units. I've reverted it back to the proper value.

I removed some crossings in this area where there are no lowered curbs or pavement markings indicating that they are places where pedestrians should cross the street

Understood. Thanks for letting me know.

Apologies, thanks for the heads up.

Thanks for the heads up. I'll keep that in mind

Checking back, the data was already present on the island areas, so all I did was remove the redundancies.

I didn’t delete the keys, I just took the data that was stored in the imported NGIS points and applied it to the area representing the entire island, then removed the redundant points afterwards.

Hi, Just a heads up that you seem to be adding the same objects in multiple changesets, creating situations where multiple copies of the same fire hydrant, bench, etc. are stacked on top of each other.

Do "USCGC Hudson" etc. represent the locations of individual ships? If so, I don't think those should be mapped since they can move from their moorings at any time.

Oh, I see! Thanks for the tip.

Yes, I did that with a lot of school zones in the area. The condition is "when the lights on the sign are flashing" but I don't know how to tag that.

Oh, I see. Reverting it now.

Signage at the junction with Crosswater Parkway identifies the Nocatee Parkway as CR 120, FL 120 was an error on my part

Why did you feel the need to add untagged lines separating the individual parking spaces here? They don't add any information to the map.

Hello, When making drain pipes could you please use waterway=drain + tunnel = culvert instead of man_made=pipeline + substance = drain? I don't feel that culverts and storm drains fall under the generally accepted usage of man_made=pipeline.

I tried fixing it myself just now, but feel free to revert anything you think needs reverting

Acknowledged. I've been working to improve my practices as a mapper over the course of the year, and I'll admit that the quality in some of my older changesets might be lacking

I understand, but OSM data is used for many different purposes, so it is in everyone's best interest if its as accurate as possible. Tagging features incorrectly for the sake of convenience is bad practice.

Hello,
Why have you mapped features such as rough, etc. as water hazards?