Hi, just to let you know, you deleted several parts of a relation (8319625), which ended up breaking it. It's going to be tricky to fix so I may have to revert your changeset entirely.

You made several changesets all of which mass deleted large portions of the relation seemingly for no reason, was this all unintentional? You really shouldn't be using iD when modifying large relations.

Hi, just to let you know, you deleted several parts of a relation (8319625), which ended up breaking it. It's going to be tricky to fix so I may have to revert your changeset entirely.

Hi, just to let you know, you deleted several parts of a relation (8319625), which ended up breaking it. It's going to be tricky to fix so I may have to revert your changeset entirely.

Please split up your changesets, thanks.

Hey, could you be more descriptive with your changeset comments? I also noticed you broke several things by carelessly box selecting and deleting nodes for things that still exist.

Sorry if this sounds pretty blunt but personally, I think you should be user blocked until you start using more descriptive changeset comments and splitting up your edits. It's very difficult to validate your mass deletion edits when they're done like this.

You've been called out about this several times before, yet you never changed.

Please split changesets. Thanks.

Friendly reminder to keep edits local. Read more here: osm.wiki/Changeset#Geographical_size_of_changesets

As this may have been an accident, make sure to double check what you're editing in OsmAnd stays within the same general area.

Correction in title: PTv2

Could you go back and fix your last few changeset? It seems like what your imports have the wrong address of addr:state=FL

This is only one section of many, and with most of the U-turn sections being done incorrectly as a separate way instead of following standardized mapping practices with the use of turn lanes it may take a while to correct.

When splitting a road into a dual carriageway please check ALL the tags especially :forward and :backward tags, as you left the turn lanes unmodified in the change. The adjacent junction was also incorrectly set up missing one-way segments and messed up turn restrictions.

Must have accidentally copied it over there or something I have no idea. Yeah it should be safe to remove.

I see you have marked your changeset with review_requested. What needs to be reviewed?

Could you be more descriptive with your changeset comments?

Thanks for letting me know, I've gone ahead and updated those aliases.

osm.org/changeset/102591366

I agree.

This is quite the achievement.

Simply the reason for this change is to reduce tag fragmentation and improves data compatibility with applications that only use the far more common prefixed social media. Additionally, as no one else has seemed to tackle it yet, I may write up a proposal to formally deprecate the use of the non-prefixed social media keys along with a discussion for systematically updating the keys. Until then, the cleanup of the fragmented keys is halted.

The tags of the non-prefixed <site>=* has not yet been deprecated, however the very low tag usage and consensus with other members on the Discord, we decided to help with reducing the defragmentation by updating them to reflect the current documentation on the wiki.

I helped organize this indoor mapping project with some other fellow mappers. If you are in the OSM Discord you can see that message here. https://discord.com/channels/413070382636072960/641926452950073344/807089369848348704

Someone posted something about this area, as it is highly detailed. After we saw that the mall had no indoor data we decided to fix that.