<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>It seems that OSM has a an architectural problem with over-large
relations?</p>
<p>Is modifying the relations in potentially arbitrary ways a good
solution?</p>
<p>Seeking something that may work now, can any "size-based"
relation splits be done in a way that they can be automatically
removed at some futute point? Is there a meta-relation structure
that can relate relations, or is that just a relation?</p>
<p>I do not know enough about how OSM is implemented to make real
suggestions, but changing the data for this seems like a bad
smell.<br>
</p>
<p>cheers - ray<br>
</p>
<div class="moz-cite-prefix">On 11/21/20 9:06 AM, Clay Smalley
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHR3E+omaGwNW7AVt800XnTmPHCsQbycd-VLvyXOVqMzrVruLw@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>I posted this on the Slack but I figured I should put this
on the mailing list to make sure it reaches everybody:<br>
</div>
<div><br>
</div>
<div>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. I really would like to split up these relations
into smaller chunks to make them more manageable.</div>
<div><br>
</div>
<div>One way of doing that would be to split them up by state
(as US and Interstate highways are) but that seems odd for a
train relation, since they'd start and end at places that
aren't train stations (except maybe Texarkana). My other
thought would be to split them up at "station stops", where
trains dwell for 10+ minutes to facilitate crew changes and
allow passengers to step off the train and get some fresh air.
These are roughly every 4 hours apart schedule-wise (typically
200-300 miles apart). The annoying part is that station stops
are not well-advertised and you pretty much need to ride the
train to figure out where they are.</div>
<div><br>
</div>
<div>Other suggestions on the Slack include splitting them up by
the underlying railway infrastructure lines (aka
subdivisions). I'm not convinced this is an intuitive way to
approach splitting long routes into sub-relations.<br>
</div>
<div><br>
</div>
<div>Anybody have opinions one way or the other?</div>
<div><br>
</div>
<div>-Clay<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-us mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-us">https://lists.openstreetmap.org/listinfo/talk-us</a>
</pre>
</blockquote>
</body>
</html>