<div dir="ltr">Hi SteveA,<div><br></div><div>I see that you have summarized the a lot of the same information from your email on the United States Railways wiki page:</div><div><br></div><div><a href="http://wiki.openstreetmap.org/wiki/WikiProject_United_States_railways" target="_blank">http://wiki.openstreetmap.org/wiki/WikiProject_United_States_railways</a><br></div><div><br></div><div>Looking through Paul's comments and yours, I don't see any specific information about exactly how one would go about identifying specific railways in Oregon so that they could be added to relations.</div><div><br></div><div>For the railways, Paul may be objecting to the content of the name and ref tag on the Way objects themselves for the railway. However, it is not clear how to find out what the name actually should be. The wiki page does indicate that the name tag on the Way objects should match the name tag on the Relation object with type=route and route=railway tags. For many rails around Portland, these Relations (type=route, route=railway) have not yet been created.</div><div><br></div><div>You mention 2 specific examples (type=route; route=railway): Brooklyn Subdivision (<a href="http://www.osm.org/relation/2203588" target="_blank">http://www.osm.org/relation/<u></u>2203588</a>) and Fallbridge Subdivision (<a href="http://www.osm.org/relation/1443651" target="_blank">http://www.osm.org/relation/<u></u>1443651</a>). Some of the Way objects in Fallbridge Subdivision are also contained in <a href="http://www.osm.org/relation/4734792" target="_blank">http://www.osm.org/relation/4734792</a>. Both of the relations for Fallbridge Subdivision have FIXME tags expressing uncertainty about exactly where the route Relation should begin and end. How would one determine the exact end of the Relation for the Fallbridge Subdivision?</div><div><br></div><div>Also, looking through the history of the above relations, I can't really find anything in the changeset tags regarding the source of the data about the railroads. Where do the names Brooklyn Subdivision and Fallbridge Subdivision come from?</div><div><br></div><div>Paul mentions that we should be using the name "Banfield Mainline" but where does that name come from and what exactly does it refer to?</div><div><br></div><div>Are there signs on the ground with these things?</div><div><br></div><div>Peter</div><div><br></div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 25, 2015 at 5:18 AM, stevea <span dir="ltr"><<a href="mailto:steveaOSM@softworkers.com" target="_blank">steveaOSM@softworkers.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hello Peter:<br>
<br>
The California/Rail wiki page you describe documents a couple of different ways we tag rail. OpenRailwayMap (ORM) documents a three tier (route=tracks, route=railway, route=train) method used in parts of Germany. As that page (as well as the USA Rail WikiProject) explain(s), because of the way TIGER entered rail in the USA, (and the way we structure and name rail) we often use just two of these, skipping route=tracks relations and "jumping" right to putting "named rail" into relations of route=railway: rail "infrastructure." You might say that two ORM/German-style "lower and middle level" relations have been merged into a single "middle level" relation here in the USA. There are also ("higher level," and the whole OSM world agrees) passenger rail relations: route=train (or route=light_rail, route=subway, route=tram...effectively at the same logical "level" as route=train). That's OSM rail "structure" in a nutshell.<br>
<br>
In Oregon, there are the Brooklyn Subdivision (<a href="http://www.osm.org/relation/2203588" target="_blank">http://www.osm.org/relation/<u></u>2203588</a>), the Fallbridge Subdivision (<a href="http://www.osm.org/relation/1443651)." target="_blank">http://www.osm.org/relation/<u></u>1443651).</a>.. these are (correctly) the middle-level infrastructure relations tagged route=railway. There are also (predictably, also, the higher-level) route=train passenger rail relations like Amtrak Cascades (<a href="http://www.osm.org/relation/71428" target="_blank">http://www.osm.org/relation/<u></u>71428</a>) which are often made up of a group of Subdivisions (route=railway relations) like Brooklyn and parts of Fallbridge.<br>
<br>
THIS is what Paul was typing about in those Notes. Specifically, a (higher-level/passenger) route=train relation should not have as its name=* tag the name of the system (like MAX, BART, Metro or Amtrak), it should be the name of the passenger line (Green Line, Downtown to University...). And, the "underlying" (lower-level infrastructure) route=railway relation should be correctly "named" as the rail company (or public works department, transit district...) names it: often something like XYZ Subdivision or ABC Industrial Line.<br>
<br>
OSM's Transport Layer is handy to display (rather raw) railway=* and (at closer zoom levels) route=bus.<br>
ORM is handy to display rail infrastructure (with Infrastructure radio button selected), especially usage=* tags.<br>
OpenPublicTransportMap (<a href="http://openptmap.org" target="_blank">http://openptmap.org</a>) is handy to display passenger rail relations.<br>
<br>
The USA is largely under construction for all of these, but we've come a long way.<br>
<br>
It's all in those wikis. Makes sense?<br>
<br>
Regards,<br>
SteveA<br>
California<br>
</blockquote></div><br></div></div>