Changeset When Comment
191817764

If you read our Santa Cruz County wiki, you'll see that I have spent over 15 years cleaning up a massive (and badly botched) import Zoning -> landuse import. I did not and do not control the keys imported (at the first two versions) but I do now (and over the last 15 years).

These (zoning-related) keys have a complex history, improve over time (albeit slowly) and will benefit from an improved process after this (v19) update, where the next update published by the county government GIS department will be "diffed" (a Unix command line tool to determine row-by-row differences), making version-to-version updates much easier.

Really, such nitpicking about relatively minor data clutter (which is fully explained in our wiki) isn't helpful, especially when you might not realize that Santa Cruz County has won a "Gold Star Award" (from bestofosm.org) for having "nearly perfect landuse."

After the v20 update in 2027, this county might actually be a model of landuse data in OSM. See what Joseph Eisenberg (a primary author / contributor to the Carto rendering engine) has to say about our county in our wiki, please. We're doing just fine here.

I accept your apology. It is complicated around here and it's easy to skip what's up (in our wiki), but now you know.

Onward to a better map!

191817764

Fixed.

191500985

See: osm.wiki/Santa_Cruz_County,_California#Additional_landuse_tags

191499384

Sorry, these four polygons were a minor mistake I have since corrected; these are now correctly tagged and properly-roled members of their host multipolygon.

191342619

It does clarify, and I do my best to preserve OSM relation histories (and way and even node histories). But sometimes, especially early in the construction of complex OSM data (like multiple, semantically-related / tied-together relations), the net result of all the editing to make it much better results in the loss of some history. We're in early days (of these trains, and even of their rail construction) and it's not a great loss. (And, all the history of all the edits in OSM are in the "guts" of OSM anyway).

I've had people totally blow away some of my old ways and relations and while I was saddened at what seemed like a loss (it isn't really, it's more like good practice to "polish" the old stuff into "better new" stuff), the fact that what replaced (my) old stuff is BETTER, well, that's good for the map. Even if some older rough sketch (usually incorrect and incomplete anyway) gets replaced with rough spray paint, then some watercolor, then some chisled-in representation of something more permanent, then "goes final" and everybody (in OSM) agrees that it is a valid representation of what is in the real world.

We're better on our way to getting there for BW, so thanks for your efforts. OSM is a team project and we're on the same team, even if your sketch is now a light dusting of "better paint."

Improvements (on BW and its relations and their elements) will continue well into the future — onward!

191342619

There are now TWO route=train relations associated with the route=railway: LV to SoCal and vice versa. Both of their relation numbers are in the route=railway relation. Also, the colour=* tag was removed from the infrastructure elements and added to the route=train relation where it belongs.

See, incrementally better and better tagging (and relation memberships) as we grow these into the future!

191342619

The "history of the train route" has barely begun, in fact, it hasn't even yet really begun in the real world, it has only begun in OSM's methodology of saying "what is" (in the real world): a proposed route=railway relation (with only track infrastructure) and a proposed route=train (a prototype of stations, stop_positions, etc.).

"The way you categorized them" is now superseded by "the way OSM categorizes them" (more properly, as they are now categorized...about exactly the same as Minh and I and others have built CAHSR relations).

We don't use route=tracks relations in the USA (and most of the world), period.

I'm not sure what we are disagreeing about, if anything. The way BW is now two relations (similar to how CAHSR is two relations) is now much more correct than it was. Will it evolve to become different in the future? Of course, these are very long-term projects (decades-long).

If you wish for the relations to have different tagging (such as proposed: prefixes) which differ than they do now, let's discuss that. But I don't know what you mean (or meant) by "the history of the train route" on such a baby route.

We do follow guidelines here (like not trying to delete routes and preserving histories), but we are in the early stages of "organizing" BW in OSM, and the way these two relations are right now is much (MUCH) more correct than the way they were — after all, they were modelled after a quite similar project (the largest public works project in the USA): CAHSR.

191342619

So, someday in the future closer to when BW offers revenue service (in the 2030s, at least), these two relations will merge into a PTv1 route=train relation (with BOTH rail=railway, AFTER it goes from construction to "real" AND the stations).

191342619

Different jurisdictions because of different funding(s) and because this is a largely (or mostly or even completely) privately-funded but may be partially public-funded (City of Las Vegas might be funding some of this), all kinds of possibilities arise. We're trying to do the right OSM thing here, but it's still very early in both CAHSR and BW projects (in the real world and in OSM tagging), so of course, this tagging is plastic and will continue to evolve. It is MORE correct now in both CAHSR and BW by breaking out the train-oriented stuff into a route=train relation and keeping this route=railway with "tracks only."

Your earlier efforts were "on the right track" (heh) but I think the tags and two relations are now much more correct.

See our United States/Railroads wiki to read about differences between tracks and railway relations. "Tracks" is used in Germany and there, route=railway means something slightly different, but in conjunction with route=tracks. It's subtle, but hopefully the wiki explains it. In all countries besides Germany, route=tracks relations largely don't exist and route=railway relations describe "rail aggregations particular to how that country / region organizes rail." More or less.

191342619

It's not for OSM to wonder what is suspicious, but to map what is accurately proposed, under construction and actually on-the-ground.

Accordingly, and because CAHSR has had its stations "broken out" of the route=railway relation (Sierra Subdivision, the IOS / CVS) — thanks Minh — this relation has had the same treatment, and its "new" route=train relation is created: relation/21860078.

191342619

This early, yes. There IS NO route=train relation. So what we do (same in CAHSR) for proposed railway (this is one) is to tag elements which are actually under construction (like a parking lot south of Las Vegas airport) with construction tags, everything else is proposed. As elements go from proposed to construction (actual shovels-in-ground, heavy equipment and material getting staged and used...) they can be tagged construction. In fact many landuse=construction polygons exist for CAHSR (for roadway / bridge work...) and these are kept up-to-date in OSM with details of road and rail construction.

In this single-relation model (which CAHSR's Sierra Subdivision, MUCH further along than BW, also uses), the route=railway (only) relation contains "route=train - oriented" elements (like stations) which are to be migrated in future to a PTv1 then PTv2 route=train relation. But for BW, not until the 2030s, at least. It's way, way too early for BW to be asserting that OSM should contain a route=train relation, we shouldn't.

187355868

They are (as indicated to me) actually a LIDAR smear, approximated. These data may represent an old trail or roadbed, it's hard to say. A path, desired, maybe. Could be useful in an emergency evac, maybe.

187258476

I had a chat with user:agrifolia about these, as he originally entered these data. They have been changed to desire paths. No need to follow-up; happy mapping!

187315188

P.S. Railways, especially passenger services that "sit on top of" (logically / semantically speaking) rail infrastructure (sometimes shared with freight rail, sometimes not) is a fairly "advanced" topic in OSM. It literally took me several years of practice, talking to others, reading (and writing!) wiki, seeing how things are done in Europe, (especially Germany, QUITE different from the rest of the world, but still in a working "3 relation" framework whereas most of the rest of the world uses a "2 relation" framework), how things are done in China, how rail kind of "drifts apart" from technical specifications from one country / region and another (though, technically, it's "all still rail on Earth") and on and on.

Even with good knowledge of computational linguistics, cartography and a good historical knowledge of rail, I STILL find it a challenge to keep it all straight!

The "trick" is to eat things one bite at a time, climb higher with your knowledge and your view gets better and better with "more altitude" (as you climb). Happy Mapping!

187315188

That's great; I'm glad to hear things make sense. I am constantly amazed at how OSM teaches me things, and when I do them "as we all agree" (and that can sometimes be difficult as we hammer out the details), things "just work."

We're (all of us!) always able to learn something new; good on us when we do.

187315188

In short, in OSM, you simply can't have a route=train without its underlying infrastructure. In the USA (North America, really) in OSM, we use two relations, #1, the route=railway (physical infrastructure expressing trackage, organized into logical wholes which follow certain rules) relation, and #2, the route=train (passenger services) relation.

In a relational database like OSM, this is simply "if you wish to (properly, so everybody understands) express a passenger train route, here's how." And we even have PTv1 and PTv2 flavors. These are version 1 and 2 of the Public Transport schemes that have evolved.

It's a "whole thing," my friend. And it can be read about in our wikis.

That's why.

187258476

I'm happy to help, but I'd rather get things correct, than wholesale delete (which is what a revert of the changeset would do).

The idea in OSM is to "draw into the map" what you see (or know) using easily-discovered tagging schemes.

So, let's do that together. I can fix what appears to be wrong easily, rather than deleting the entire edit session. Is the "north of the Open Air Stage" line-squiggle (such a line segment in OSM is called a "way") a footpath? Paved? Dirt? Is it wide enough to drive a vehicle down, even if only dirt or gravel?

And so on.

The nice thing about OSM is you can make it "rather vague" (to quote Brian Eno) or you can "do like Deutschland" (German mappers in OSM are notoriously detail-oriented down to the very benches and drinking fountains in every park).

I like the rough sketches in Deer Creek, they look great and can act as "just enough" for locals. There's a sweet spot just waiting to happen.

187315188

This is simply a "syntax=semantics" equation. OSM has, and does, partly by evolving for its data structures to represent the semantics of "passenger rail routes" as a certain kind of route=relation. These are predicated upon route=railway relations. They simply "are" this way in OSM. In Germany (and I believe in other parts of Europe), there are THREE relations needed to properly express the semantics of how passenger rail (at the "top" of the 3-relation hierarchy) use the "middle" route=railway AND the "lowest" route=tracks relations.

In North America we eliminate the route=tracks relations (it works to express our familiar "subdivisions," as USA railroads do, with route=railway relations and eliminate route=tracks relations).

This is simply "how we do it." It has evolved over decades of OSM and world wide rail tagging, and I've been there, around the world.

Just get the syntax the way everybody else uses it and everybody else will use the data smoothly.

Your characterization of "a linestring of freight rail elements" has some overlap with what I'm talking about, but that is exactly why we use such "intermediate" (route) relations in OSM (which is a relational database, and has quite exact syntax that means quite exact semantics).

We've tuned up landuse=railway and railway=station and a bunch of stuff about railways in general in OSM in our wikis. Read up on it, they're marvelous for us all to not only see how things are done, but to see how others do things, including making changes to how we map.

187258476

Hi DoubleBear, welcome to OSM! Can you explain the hundreds of meters long amenity bench here? I can (sorta) see a large amphitheater here, too, but is this a walkway or a path, rather than a bench? Thanks in advance.

187315188

I appreciate your attempt at using the proposed:route=train tagging, but that is 100% superfluous. In OSM, train routes (passenger AND freight) are "born first" as railways. If you wish to build a (fantasy) route=train, use another relation, and put the proposed stations into that, and use the route=railway elements properly. Please remove your tag and (optionally) build a proper (start with PTv1) route=train, if you wish to do that. There are correct ways to achieve the semantics you seem to mean, so, use the right syntax to do that.