This changeset has been reverted.

This changeset has been reverted.

Helina, please respond ASAP to this changeset discussion or we will need to revert this and changset 30581704.

> signifying that track segment is part of a high speed line.

There's no evidence of that from what I read.

> To show my continuing good faith and hopefully to assuage the situation somewhat

Why don't you just do what everyone can agree is correct, and tag the route, rather than the individual ways? The route is absolutely high speed, but when you say the tracks are, that's where there's a disagreement.

To me, a track that's labeled high speed is like a road that's labeled max_speed.

Saying the route is high speed makes sense, but these individual tracks... I can't get behind that.

Steve, if you want a route to have a specific tag, that's fine, use a relation and apply the tag to that route as a whole.

By tagging each way, you are saying "This track is high speed capable", which isn't true for some of these ways. I don't know which tracks are high speed capable and which aren't, other than by my observation having taken this route that the train seems to slow down during certain times, and speed up during others (all while the train being on schedule). I also know that the news reports that Amtrak wants to upgrade tracks alone this route to make them high speed capable.

If you can find out which tracks are high speed capable and which aren't, then that would be wonderful, but until we have that, please stop tagging individual ways with these tags saying that they're capable of high speed travel.

Russ, the issue is that individual tracks are tagged as high speed, not a single route. That indicates to me that the tracks must therefore be high speed capable, and many are not.

What are you changing in these cities?

kartalakopang, Please respond to these changeset discussion posts. I believe this is an import, and I will delete it and other similar changesets if I don't hear from you.

Steve,

I'd request that you please stick to the discussion at hand, which is the issue of the track data.

I'd also ask that you please keep a civil tone and not use condescending language, such as telling someone to "relax".

To the substance of your email, as you say, the tag is for objects, not routes, and you're tagging the tracks as high speed. Unless you know if a tag is high speed, then it shouldn't be tagged as such. The issue regarding the rendering of that tag is separate, and goes to OSM's general policy of not tagging to the renderer (osm.wiki/Tagging_for_the_renderer).

Will you please correct your tagging on these objects to reflect which track segments are high speed and which aren't?

In addition to Amtrak, you're also saying that some Metro-North rails are high speed. Please tell me where you can tell which rails are being replaced with high speed capable rails, because I haven't heard that they've completed that renovation universally. In other words. So what is your source?

Steve, you sent me an email, but I want to keep all conversations public. Please specify the source for where you say that these track ways are high speed compatible. Based on my experience, some are and some aren't.

This is another changeset with a source that doesn't really make sense to me. Where is the source for these changesets? Is there a URL or other public source?

Hi bboy15,

Welcome to OpenStreetMap

You should be aware that we only use name tags for the actual name of the objects, such as might appear on a sign. This is different than a description tag.

I find it hard to believe that the primary language of these objects is Spanish, and not English.

What is the source of this data?

While this information is true (most of the NE corridor tracks) allow for speeds about 120mph, not all do. I know because I was just on Acella a few days ago on this very route and sometimes we were going >100mph, and then in the middle of the journey, we dropped to ~30mph, around bends and populated areas. Other travelers said this was normal for this route.

You say Amtrak is the source. Where does Amtrak specify which tracks do and don't have highspeed access?

Can you say more about this changeset and the others like it? What is lpis? Does it correspond with this? osm.wiki/LPIS

If so, I believe this page describes an import that does not conform to the OSM Import Guidelines (osm.wiki/Import/Guidelines) due to a number of issues (import list discussions, separate accounts), etc.

It also appears based on the rapidity of these imports that they were done very quickly, possibly too quickly to have been reviewed manually.

Can you please address some of these concerns?

I found it on the list. It'd be good to link to the wiki page on this import in the changesets.

Is this import following the Import Guidelines?

osm.wiki/Import/Guidelines

I don't recall seeing it discussed on the import list. Can you point me to it?

If not, it needs to stop and be reverted.

Sadly Google Street View data isn't something we're allowed to use to populate OSM, so please only use things that you verify by being there (or on Mapillary)

What is the mistake? The tagging or the thing you're fixing?

I'm concerned this is an import, which would require that I revert this changeset. Please reply so we can resolve this.