congratulations for making such a big changeset area, you took half the world. Please save your changes more frequently so as not to ruin the spirit of osm
---

Published using OSMCha: https://osmcha.org/changesets/168576603

⚠️ It looks like this changeset re-used several existing relations all over the world to transform them into relations for roads in Colorado.

Take this one, which was a multipolygon in London (UK) up to version #5: relation/332/history

Or this one was a river in Iraq up to version #11: relation/147/history

Very strange, I hope it is not necessary to contact the Data Working Group

Not sure how this happened, but he used relations with increasing id's 1, 2, 3 etc. I mean...how often do you touch the first relation ever created :)

Might be a wrong-sign error as the api expects temporary negative id's for new objects.

Anyways this needs a full revert.

I reverted the changeset here: changeset/168579807

All the relations elsewhere in the world were restored to their previous state.

@Flap Slimy Outward: your work to create road relations in your area was preserved too, in most cases through new relations.

The comment by @limes11 is correct.

To create new objects in OSM, you should give them *negative* numbers and the API will create them for you. On the contrary, if you use *positive* numbers, you will ask the API to re-use an existing object having that number. That created the mess here, because your upload requested to edit several relations that were already in use and move them to Colorado.

I apologize severely. I used Overpass Turbo and JOSM to edit them. I used a Python script to find all highways in a bounding box (in this case, Weld County) to create new road route relations. As I only had data from that box, I had no idea that I was adding these routes to different relations, so I deeply apologize; I did not mean to break half the world. I will fix the script to make the relation IDs negative so they don't mess up any existing relations. Once again, I'm very sorry, and I hope you understand. Thank you.

@limes11 It was a wrong sign error, as I completely forgot that new IDs should be saved with negative numbers.

Thank you for providing the details on what caused the issue! :) We all make mistakes, and that's okay.
Happy mapping!