Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-07-03 Thread Chuck Sanders
After a sidebar with a couple of other folks on the list a few minutes ago, I realized I hadn't clearly wrapped up my conclusions from this part of the discussion and what followed. In light of the online meeting tomorrow to discuss, I want to take a moment as suggested to clear this up, since it

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-15 Thread Chuck Sanders
Nathan, I've been working to "broaden my horizons" as an east coast guy, and I can see why it was probably confusing why I didn't understand your references to line segment numbering. I've been rooting around in BNSF and UP timetables, and they really are used prominently over there. Turns out

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-15 Thread Chuck Sanders
My thoughts exactly. I think part of the problem is that some map editors spend so much time as a map editor, they forget to both think as a map user, and to think broadly that there are a lot of types of map user that are interested in fundamentally different but compatible things from their

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-15 Thread Russell Nelson
On 6/14/20 6:34 PM, Chuck Sanders wrote: after watching the re-discussion of the abandoned railroad line "where do we draw the line" topic, from a somewhat-outside perspective, I've given up arguing. I treat deletion of abandoned railways as vandalism and just fix it. Not seeing something is

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-14 Thread Chuck Sanders via Talk-us
Agreed on all of that, honestly. It's funny, but the one handy thing about the state wikis is having such a good place to keep notes. I started adding info to the Virginia/Railroads page just under a week ago because it turns out to be a simpler way of keeping notes on what I have and haven't

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-13 Thread Chuck Sanders
Sorry to be a little slow today, the weather was gorgeous here today (probably the prettiest day we've had all spring so far!) and I got cabin fever at lunch. Now I'm in nap mode, and trying to get caught up on all the excellent discussion that happened when I was soaking up the sun this

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-13 Thread Natfoot
I guess I have been confused all this time. Nathan P email: natf...@gmail.com On Sat, Jun 13, 2020 at 12:49 PM Clay Smalley wrote: > If I'm not mistaken, the examples you've given are instances of > railway:track_ref=*, not ref=*. > > Throwing my two cents in here—that coincides with the way

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-13 Thread stevea
Russ Nelson writes: > Yeah, for me the map is much more important than the wiki. Except for > Wikipedia's stupid citation rules, all that information > belongs in > Wikipedia. Although if it drives more mappers, that's fine. Maybe we should > populate the wiki with the > old_railroad_operator

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-13 Thread Clay Smalley
If I'm not mistaken, the examples you've given are instances of railway:track_ref=*, not ref=*. Throwing my two cents in here—that coincides with the way I personally use railway:track_ref=*. My understanding is that this uniquely identifies tracks within a line, station or yard, and is not

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-13 Thread Natfoot
Chuck, I think you make some good points in your email. I would discourage the hang ups on the diffring railroad terminology as it is different by railroad and location. Coming to a decision on how we are going to tag is more important. I agree that line segments are useful and interested to

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-13 Thread Chuck Sanders
Nathan, thanks - I've been thinking over your email and use case since coffee this morning, and looking for the right questions to pick your brain too, so that we can get the documentation right in the NA tagging wiki, and all of us on the same page. I also started working up a a NA-specific and

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-13 Thread Russell Nelson
On 6/13/20 12:30 AM, Natfoot wrote: And I don't trust the FRA database to be accurate. No database is perfect. Not even OSM. Some databases can be useful. ___ Talk-us mailing list Talk-us@openstreetmap.org

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-13 Thread Russell Nelson
On 6/13/20 12:25 AM, stevea wrote: It is absolutely fascinating (to me, anyway) to watch this conversation! I thanked Russ Nelson on wiki for his comments at New York/Railroads. (And we still have a ways to go there). Yeah, for me the map is much more important than the wiki. Except for

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-12 Thread Natfoot
Sorry I saw your email in the ORM list and responded directly. I find line segment numbers on track charts and timetables. I mostly work with lines that have left BNSF or its predecessors so I have line segments that were assigned by those railroads. Here is a great list of line segments of the

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-12 Thread stevea
It is absolutely fascinating (to me, anyway) to watch this conversation! I thanked Russ Nelson on wiki for his comments at New York/Railroads. (And we still have a ways to go there). SteveA ___ Talk-us mailing list Talk-us@openstreetmap.org

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-12 Thread Chuck Sanders
I'd love any information you can send regarding any sort of route number in use here like you're discussing. I've worked around the US rail industry for several decades (federal bridge engineer), and have never heard of such a thing, so I'm very curious. You're not talking about the FRAARCID in

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-12 Thread Natfoot
Chuck, Thank You for your time fixing the reporting marks section. Railroad Line numbers do exist for railroads in the United States and Canada. Ref= is for the use of line numbers. I can send you links to line numbers. Line numbers were given to a line by the railroad when it was laid and

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-12 Thread Chuck Sanders
In the interim this week, I got the wiki page up for tag:reporting_marks, and started using the tag in my area as a bit of a test - we had the thought that if there proved to be a better tag to hold this info, since this is a "novel" tag, it'd be easy to query out places we'd used it and just

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-06 Thread stevea
I point out for those who might not know this: rail tagging, despite excellent efforts by the ORM folks (largely in Germany, I understand) to encourage OSM to follow global tagging conventions for ORM, have already quite seriously fractured (necessarily) into country-specific tagging

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-06 Thread stevea
Volker (hello!) discusses that the tag (used in the USA, but not extensively) of "reporting_marks" isn't (I paraphrase him a bit) "as international as OSM might like it," and proposes presumed-better tag "operator_identifier" (I correct a minor spelling error in his posted suggestion). Volker

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-05 Thread Chuck Sanders
Actually, that makes complete sense to me too. It would be very easy to use "operator_identifier", and simply clarify in the North America tagging wiki that the appropriate value is the primary reporting mark for Canada, US, and Mexico lines. I see no reason that wouldn't serve exactly the same

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-05 Thread Chuck Sanders
Volker, sorry for the double response, forgot to replay-all so this would go back to the list. Ways. The original use of Reporting Marks in NA is for rolling stock identification, yes. However, it's also the only common, reliable, and consistent short form abbreviation for operators. It's

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-05 Thread Volker Schmidt
Question on the term "reporting_mark" Wikipedia defines "reporting_mark " as "code used to identify owners or lessees of rolling stock and other equipment" and describes

Re: [Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-04 Thread stevea
My apologies (it was my error): the correct link to Chuck's post is https://wiki.osm.org/wiki/Talk:OpenRailwayMap/Tagging_in_North_America ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] Rail tagging in US (and North America): operator=* and reporting_marks=*

2020-06-04 Thread Chuck Sanders
For those who map rail in OSM in the US or in North America in general, https://wiki.osmap.org/wiki/Talk:OpenRailwayMap/Tagging_in_North_America contains some recent chatter about using the tag reporting_marks=* as well as the "full name" (not abbreviations) of operators in the operator=* tag.