開放街圖標誌 OpenStreetMap 開放街圖

Elevations mass editing

於 2018年三月13日 由 CascaficoItalian (Italiano)發表。 上一次更新在 2018年三月14日。

Update: comments pointed out that such edits are against the code of conduct, even if not automated. I leave this post just as personal hint on queries and regexp’s.


It happens there’s a lot of OSM tags “ele”=” m" that can't be processed by useful queries like [find volcanoes between 1000 and 2500 meters high](http://overpass-turbo.eu/s/wXw)

How I remove unit of measure:

  • download faulty data with this generic overpass-turbo query
  • from export menu, “download/copy as raw OSM data”

  • load resulting .osm file in Notepad++ (or whatever regexp editor)
  • find&replace (CTRL+h) twice with the following fields:
    find: k=”ele” v=”(\d+(.\d+)) m” will find for example “450.5 m”
    replace: k=”ele” v=”$1” will replace “450.5”
    find: k=”ele” v=”(\d+) m” will find for example “450 m”
    replace: k=”ele” v=”$1” will replace “450”
  • load in JOSM modified .osm file
  • select all (CTRL+a) and add a fake tag (ie: pippo=pluto) to every node and remove it (just a shortcut to add “modify” tag to elements, otherwise you won’t be able to upload anything

Remember to add proper changeset comment.

電子郵件圖示 藍天圖示 Facebook 圖示 LinkedIn 圖示 乳齒象圖示 Telegram 圖示 X 圖示

討論

mmd2018年03月13日 17時39分 發表的評論

It’s really not necessary to remove the trailing „m“ in Osm data for overpass turbo to work. Instead you should convert the relevant ele tags to a number. Roland wrote a blog post about this topic which explains all the details!

http://dev.overpass-api.de/blog/numbers.html

Cascafico2018年03月13日 19時31分 發表的評論

Thanks a lot! I will read carefully those queries (I didn’t know there were a blog about overpass-turbo).

FeRDNYC2018年03月14日 08時08分 發表的評論

And it seems that when someone tried to mass-edit elevations to remove “ m” suffixes last year, those edits were reverted with a link to the Automated Edits code of conduct.

See e.g. the history for the elevation example in that blog post, the Sickersberg.

Cascafico2018年03月14日 09時45分 發表的評論

Thanks for this info! Actually I didn’t think my mass edits falled in “automated” category mentioned by the code of conduct you quoted.

I hope somebody will document the precious overpass.turbo syntax that “overpass” :-) mixed value notations.

mmd2018年03月14日 12時53分 發表的評論

Actually I didn’t think my mass edits falled in “automated” category mentioned by the code of conduct you quoted.

If you take a look at the scope of said Automated Edits code of conduct, you’ll notice that your blog post exactly matches point 4 in the scope section:

“use of find-and-replace functionality using a standard editor such as JOSM or finding using services such as Overpass API and changing without reviewing cases individually”

Cascafico2018年03月16日 10時14分 發表的評論

If you take a look at the scope of said Automated Edits code of conduct, you’ll notice that your blog post exactly matches point 4 in the scope section

Yes, after your hint I red the whole article; what I ment is that title “Automated edits code of conduct” was misleading. I had a different idea of “automated”.

登入 來留下評論