[Talk-us] Extremely long Amtrak route relations

[Rory McCann]

On Sat, 21 Nov 2020, at 18:06, Clay Smalley wrote:
> Many long-distance Amtrak trains have route relations with 1000+ 
> members. If I split one way that happens to be a member of one of these 
> routes, I end up with a changeset with a gigantic bounding box, and 
> often get edit conflicts due to someone doing a similar change hundreds 
> of miles away along the same line.

While mapping lots of little admin bounadaries in Ireland, I encountered this problem too, with splitting the "Ireland" admin boundary on the coast. It's a PITA, but if you upload & download/update as often as possible (even as soon as you make a change/split the way), then yous can alleviate as much as of the problem as possible. Essentiall "edit live"

On Sat, 21 Nov 2020, at 21:58, Brian M. Sperlongano wrote:
> Personally, I think if the world is complicated, the model should be 
> complicated.  If the thing we're modeling is large in the world, it 
> should be large in the map.  It seems that we are increasingly doing 
> things to simplify the model because certain tooling can't handle the 
> real level of complexity that exists in the real world.  I'm in favor 
> of fixing the tooling rather than neutering the data.

I 100% agree. Let's fix the tooling. Let's not map for database backend.