Reverted

Reverted

Reverted

Reverted

I have reverted this change as it contravenes OSM's on-the-ground rule, and the OSMF's Disputed Territories policy. Please respect how OSM does things: the status quo ante also represented the consensus views of many people including members of the Argentinian mapping community.

As I said there is no real boundary to the ski resort which can be meaningfully surveyed. There are multiple areas which different people might consider to correspond to Parsenn as a ski area, but these are mostly subjective and possibly based on marketing by the skilift companies under the Davos-Klosters banner. There are alternative methods such as a site relation encompassing the relevant pistes and lifts which I think is much more appropriate for European ski areas. This type of mapping really only makes sense in North American resorts which have a notion of in-bounds and out-of-bounds skiing. Note that in general the wiki is not always a reliable source of information.

We are not like Wikipedia who arbitrarily delete information which does not meet guidelines, but on OSM we general expect people to be mapping things which they know about. I would expect someone mapping ski resorts in this fashion to have at least skied there enough to be familiar with them. It is up to you to provide good quality information not for others to be expected to refine it.

My attention has been drawn to the landuse=winter_sports area you have drawn here. I don't think that this is a) accurate; b) useful; c) reflect real landuse. The actual landuses in the area are farming: hay meadows, pasturage on alpine and valley meadows, some gravel extraction etc; d) remotely reflect which areas are actually used by skiiers; e) accurately reflects the area known as Parsenn (either as a true toponym) or the ski area promoted by the lift company; f) includes areas serviced by the Klosters lift company usually under the name Gotschna. The long Parsenn runs to Saas, Conters, Kublis etc are very rarely in condition (perhaps a few days each season), require good local knowledge for navigation. Nowhere E of the railway is used for the kind of winter sports you are thinking about: in practice I think there are at most 3 descents from below the skilifts towards Wolfgang and Laret. The Gotschnawang area should be excluded (almost the same could be made for Drostobel, it's a very demanding run & not clearly marked last time I was there). There is no skiing beyond the S-side of Dorftaelli (and indeed with avalanche risk not close to the ridge either).
So I rather wonder what you are wishing to achieve with this object.

I've done as much as I can using Vespucci. Working out which buildings have been demolished to accommodate the new A&E requires a bigger screen. So will return to this shortly. In meantime yes I know there are crossing buildings.

You changed the intended meaning of the tags on at least one object. name_1 is largely a deprecated tag largely created in handling TIGER data. However it's meaning is clear: it an alternate name CONCURRENT with the base name tag. The disused1:name etc use ordinals after the disused to distinguish & group different historical aspects of the object. This is a common problem of global edits fixing things: sometimes you ignore what the original mapper(s) intended.

But you changed a number of nodes which were mapped as shop=mobile_phone & therefore there were inconsistencies requiring on the ground resolution. Unless you know the original mappers intention, remote automated updates can often degrade data in ways which are difficult to predict.

I hope you discussed this changeset beforehand. It very much looks like an automated edit as I doubt that you have visited or have personal knowledge of the various places in this changeset. We have a policy about Automated Edits which should be followed.

Did you intend to delete object across such a large area? A comment in Spanish for an edit in Northern Ireland looks rather odd.

On post boxes

I think this has been pointed out before: Freefone & local call numbers: 0385, 0845 are not reachable through international dialing. Therefore adding the international prefix is actually wrong: there are no such numbers. This is a typical problem when contributors make large scale search & replace type changes: lack of detailed consideration of edge cases.

Hi, It looks as if something went wrong with some of these changes. The road labelled Sripali has ended up in the middle of the sea off Africa: way/653330968#map=3/-0.02/0.31.

If you let me know what was intended I can help you fix it.

SK53

Should the traffic lights named "The Commodore" have some kind of junction tag. At the moment it renders remarkably early as it is (perhaps a bug in Carto-CSS)

Hi EoghanM,

Would you like me to return Blackpool to its original node with all current tags?

Jerry

On the other hand it provides a more consistent format of machine readable text to be readily handled. Most OSM users will be using the data in some way mediated by apps & not as stored natively in the database. On my phone numbers entered in international format always work; in national format only when I'm in country.

Just wondered if Chestal really joins the new road in the middle. This picture http://www.dursleyglos.org.uk/html/dursley/news/aug_2018/long_street_10aug2018.htm suggests it still goes along by The Priory

and this suggests (as I thought) that Chestal is now in wrong place