OpenStreetMap

Users' diaries

  • Rss

Recent diary entries

Mapeamento na UFES

Posted by clestonforechi on 15 May 2018 in Brazilian Portuguese (Português do Brasil)

Mapeamento de teste dentro da UFES para aula de Cartografia Escolar, utilizando o GPS Essentials. Foram marcados pontos de interesse dentro do campus, com destaque para áreas de risco (locais com pouca iluminação ou pouca circulação de pessoas).

Location: -20,275, -40,304

ICs

Posted by Yago Oliveira on 15 May 2018 in Brazilian Portuguese (Português do Brasil)

Foi utilizado para marcar a trilha o celular, pelo software GPS essentials, no qual foi possível marcar um pequeno caminho marcado pelos ICs, passando pela entrada do IC2, logo após passou pela cantina do honofre, no qual muitas pessoas vão para poder lanchar e interagir um com o outro. Logo após passou pela xerox, subindo a passarela até que chegasse no IC2 novamente.

Location: -20,275, -40,304

Mapeamento em aula

Posted by Borini on 15 May 2018 in Portuguese (Português)

Hoje, na disciplina de Cartografia Escolar, iniciamos um mapeamento por áreas da Universidade Federal do Espírito Santo. Marcamos pontos, tiramos fotos georreferenciadas e fizemos trilhas, utilizando esta plataforma e o GPS Essentials, via celular.

Location: -20.275, -40.304

Panoramica ciclabili Milano con umap

Posted by Cascafico on 15 May 2018 in Italian (Italiano)

Il comune di Milano ha pubblicato un dataset delle piste ciclabili. Facciamo una umap per capire la situazione rispetto ad osm.

  • facciamo il login con le credenziali OSM
  • selezioniamo "creare una mappa"
  • importiamo il dataset (nel nostro caso geojson) con il bottone e dx "importa dati"; se il nostro file non ha una estensione esplicita, dobbiamo informare umap di cosa si tratta con "scegli il formato dati"; se va tutto bene ci troviamo il layer delle ciclabili nel colore di default (blu).
  • otteniamo i dati al volo tramite overpass-turbo: questa è la query per Milano che estrae le ciclabili da OSM, per altri comuni basta sostituire la geocodeArea in alto.
  • su overpass-turbo salviamo da qualche parte la stringa che genera i dati della query: export>query, clicchiamo sul "compact" e copiamo il link
  • per importare i dati della query in umap è necessario creare un nuovo layer ed aprire il form a destra su "dati remoti"; qui incolleremo la stringa appena copiata; scegliamo il formato dati "osm"; mettiamo in ON le opzioni "dinamico" e "richiesta proxy"
  • salviamo la mappa e dopo alcuni secondi (dipende da traffico su overpass-turbo) dovremmo vedere anche il layer dei dati estratti da OSM.

Questa è la procedura di base, dopicichè si tratta di aggiustare lo sfondo (ho scelto il monocromatico), i colori dei layer e le eventuali etichette che appaiono passando il mouse sopra ed al click.

Just Mapping

Posted by Valerie143 on 14 May 2018 in English (English)

It's been a while i mapped. I'm glad the network is better now. Currently working on #4525 - 2018 Ebola #8, Mbandaka (E Av. Revolution), DRC

... and so it begins

Posted by Thomas_Hervey on 14 May 2018 in English (English)

Week 1

Today is the first programming day for GSoC 2018. If you haven't read about the student projects, go take a look! For this week, I will be firming my understanding of the iD services implementations (paying particular attention to mapillary and openstreetcam). Notes will end up being a toggleable service much like these two. Thus far, I've already experimented with many parameterized curl calls to the Notes API, and have delved deep into D3 (since iD relies heavily on it). This week, I am also going to explore how JOSM handles notes (to see if it is different from openstreetmap.org).

If you're curious about other improvements to notes, please share your ideas here and take a look at an ongoing discussion about categorizing notes.

Below you can see iD currently without notes and openstreetmap.org with notes enabled. I'll be using my home campus, UCSB, as a test area for this work. So if you check the area out, you may see a lot of notes popping up! UCSB no notes UCSB notes

Cheers!

When OpenStreetMap met Mapbox-GL : 🍚IDLY-GL

Posted by kepta on 14 May 2018 in English (English)

Today I am super excited to announce Idly-Gl! It is an opensource Mapbox GL plugin which renders OpenStreetMap data.

idly-gl

What is Idly-Gl?

Idly-Gl is a small plugin which reads data from Openstreetmap's API and renders it on any Mapbox GL map. Click here for a demo.

What is IDLY 🍚?

Idly is an Indian rice cake 🍚. I picked this name as it can be the little brother of iD editor.

Why did you create it?

I work with a lot of Mapbox-gl maps and I am very impressed with their speed and portability. I have also worked with iD editor and it has impressed me with the way it handles OSM data. The only problem is that these two don't talk to each other well. To bridge the gap, we would have a button to open it in iD. This works well when you have to make an edit, but if a user just wants to inspect/visualize OSM data the only option is to open the OSM website.

What does it do?

  • 😎 It renders live osm data on a mapbox-gl map, which makes it blazingly fast.

image

  • 👯‍♀️ It tries to mimic iD editor's familiar styling.

idly_id_style

  • 🕵 Dig deep into OSM entities, by interacting with them.

screen

  • 💪 Add to any existing Mapbox-gl map to give it OSM superpowers.

add_anytime

What is next?

  • Idly-gl already does an impressive 3d buildings. I plan on adding some advanced 3d visualization of OSM data, provided Mapbox-gl supports it.
  • The Openstreetmap 's entity inspector provides a nice way to inspect an entity. I imagine Idly-gl doing the same thing. There are certain features like viewing the history or the changeset which are not yet there in Idly-gl, but I have plans to add them.
  • If all goes fine, I think being able to search would be great. I imagine putting a query like highway=* and Idly-gl only shows all the highways on the map.
  • I also wanna try to add some sort of linting into Idly-gl. There are already some great rules at osmlint, which I feel can be used to highlight entities which violate any selected linting rule.
  • Currently it just visualizes Turn restrictions. I plan on adding more Restriction visualization, but the tricky part is how to best visualize restrictions without the map being too cluttered.

What is the goal Idly-gl?

The goal of Idly-gl is to be a highly customizable developer tool which helps the developers add powerful OSM data inspection/visualization into their apps.

How do I add it to my website?

I am glad that you want to give it a try, head over to the Github repository Idly-gl!

Where can I play with it?

Idly-gl Demo

(Tip: If you want to see the 3d buildings, make sure you switch on 3d extrusion layer)

Final thoughts

Idly-gl is currently very new and I am super excited to talk about it. I would really appreciate if you could try it out and give me feedback or ideas on how to further improve this tool and help OSM community build amazing things on top of it.

Vespucci 11.0 BETA

Posted by SimonPoole on 14 May 2018 in English (English)

Work has proceeded nicely on the next major release of Vespucci and while there are still some rough edges and not quite everything has been added that I intended to, it definitely makes sense to test this version. THe beta APK is available from googles play store and our github repository.

Layer control

The most obvious visual difference in version 11 is the layer control on the main map view.

Currently it is not possible to change the ordering or add more than one layer of a specific type, supported functionality:

  • Hide/Show button turns drawing of the layer off/on. Hiding a layer doesn't free any resources associated with the layer.
  • Zoom to extent. Zooms and pans the screen so that the whole extent of the layer is displayed, if the extent cannot be determined this will zoom out to the full web-mercator coverage. Note: on the data layer this may not be particularly useful if you have downloaded areas that are far apart.
  • Menu button.
    • Tile based layers:
      • Select imagery. Same contents as on the prefernce screen, if multiple layers have been used, a most-recently-used list will be displayed above this menu entry, allowing quick layer switching. Selecting the "None" entry from the list will disable the layer, and requires re-enabling it via the "+" button on the layer dialog.
      • Flush tile cache. Moved here from main menu.
      • Background properties. Set contrast of layer, moved here from main menu.
    • GeoJSON layer.
      • Change style. Show the layer styling dialog.
      • Discard. Delete the layer including any saved state.
    • GPX layer. The GPX layer is currently mainly controlled via the entries in the GPS menu.
      • Change style. Show the layer styling dialog.
    • Photo, Grid and Task layers.
      • Disable. Turn this layer off, needs to be re-anbled via proferences. For the tasks and photo layers this will free resources if the app is exited and re-started.
  • "+" button:
    • Load GeoJSON layer. Loads a GeoJSON layer from a file, any existing one will be replaced.
    • Map background. Shown if the background layer has been disabled, allows the same selection as from the preferences screen.
    • Map overlay. Shown if the overlay layer has been disabled, allows the same selection as from the preferences screen.

Support for GeoJSON layers

A single (currently) GeoJSON based layer can be displayed on the map, individual elements are selectable. On loading the GeoJSON data from a file colour, stroke width and a tag for displaying a label can be selected.

A typical use case would be to verify third party data in GeoJSON format on the ground and similar mapping activities.

Re-arranged Preferences

The two preferences screens have been re-arranged with just the most important settings on the first screen and the "Advanced preference" screen split up in to multiple sub-screens.

The Authors and Licence screen has been move to the main menu, just as the Debug screen has.

Undo/redo of individual checkpoints

Previously selecting an undo or redo checkpoint from the undo menu (long press on the undo icon), always undid/redid all checkpoints back to that point in time. In Vespucci 11 a dialog is shown that allows you to select the previous behaviour or to undo/redo just the single selected checkpoint.

While selecting just one checkpoint will result in consistent data, it may have unintended consequences as all elements changed in the checkpoint will be reinstated to the stored state when the checkpoint was created, except if elements are referenced, for example way nodes or relation members, that have been deleted in later edits. References to deleted objects will not be re-created, including relation memberships in later deleted relations.

Example: as the first operation you split a way, as the second step you delete one of the two halves of the way. Undoing the first operation will only add way nodes back that were not removed in the second step.

Simple tag changes in a checkpoint can in general be undone without negative consequences.

Review changes before upload

Entries on the list of the created, changed and deleted elements can now be selected and the actual changes inspected. Elements that have failed the validator tests will have a red icon displayed.

Auto-Presets from taginfo

The results in the preset search are now complemented by results from querying Jochen Tops taginfo service, currently this requires network connectivity to work and will only return results for tags that have at least one wiki page. In general so generated presets should not be taken as gospel and the tagging will typically need some manual work.

Selected search results from taginfo are added to a special preset file that is stored on device in the public Vespucci directory, this can be used as a starting point for creating a proper preset for the object in question.

This feature can be turned off in the Advanced preferences "Data and Editing settings".

Miscellaneous

  • Support for icons in preset combos and multi-selects.
  • The info display for selected elements will now show the original state of the element side by side with the current state if the element has been modified.

The full change log is available here

Known problems

Upgrading from previous versions

Mapping of services for persons with disabilities

Posted by stefan_lorenzkowski on 13 May 2018 in English (English)

#What am I writing about I support on of our projects in a mapping exercise that looks at access to services important for persons with disabilties in Rwanda. For now we have a bulk of information on 256 services, notably looking at the aspects: *Adresses of the services (inc. GPS) *General description of teh service *Target group *Accessibility levels *Levels of inclusion

I would appreciate, if you could have a read through the article Geography and Inclusion

Location: 52.485, 13.423

New Wiki Page on Ashgabat

Posted by apm-wa on 13 May 2018 in English (English)

I've started a new wiki page on the city of Ashgabat. Suggestions on what more to include are solicited and welcome.

Location: 37.934, 58.393

Calles agregadas en Barrio Los Tilos. Las Higueras. Córdoba. Argentina

Posted by Pablogerard on 13 May 2018 in Spanish (Español)

Buen dia gente de openstreet: Oportunamente agregué unas calle en mi barrio, pero no las veo reflejadas en mi App maps.me. Queria saber que es lo que sucede y cuando me aparecería, los cambios en mi App?. Atte Pablo

Location: -39,301, -61,611

Курск

Posted by vitaliy_casper on 13 May 2018 in Russian (Русский)

Привет всем. Я облагораживаю центр города Курска, в основном мелкие детали и обновляю данные об объектах, т.к. жизнь не стоит на месте...

Location: 51,721, 36,172

今月のマッパー: Tomoya Muramoto (日本)

Posted by escada on 12 May 2018 in Japanese (日本語)

自己紹介をお願いします。

村本といいます。マッパーの方々はITに詳しいというイメージがあるのですが、私はITには詳しくなく、化学工学が専門です。日本の横浜でマッピング活動を行っています。

いつ、どのようにしてOpenStreetMapを知りましたか?

私はかつてジオキャッシャーでした。ジオキャッシングの地図がOSMに切り替わったときに、初めてOSMを知りました。周囲のジオキャッシャーからは不満の声が多く上がりましたが、一方で私は、OSMが「自由な地図」であることを知り、「終わらない遊び」であると感じて活動を始めました。

何をマッピングしますか?

いくつかのテーマがあります。 ・小さな島のリモートマッピング ・神社境内のマイクロマッピング ・ハイキングコースのマッピング ・災害地区の復興マッピング テーマにおおまかに共通するところは、商用地図がカバーできていないところをマッピングしようと思っているところでしょうか。

マッピングの方法は?現地調査派ですか?リモートマッピング派ですか?ツールはどのようなものを使っていますか?

現地調査重視です。GoMap!!は現地調査時にさっと編集できるので愛用しています。

現地調査の方法は?

旅行やハイキングに出かけたさいに、写真を撮り地物を記録します。なるべく360写真て記録するようにしています。 道路構造が複雑な場合はGoMapを使って現地でマッピングしてしまいますが、主には写真をもとに帰宅後にJOSMで編集しています。

最も大きなマッピングの成果は何でしょうか?

個人的には、青ヶ島と利島を現地調査に基づいてマッピングをほぼ完成できたことが最も大きな成果であると考えています。 青ヶ島は、日本で最もアクセス困難な場所のひとつであり、米国のNGOは死ぬまでに行くべき場所としてピックアップしました。 http://www.onegreenplanet.org/animalsandnature/amazing-natural-wonders-photos/ 青ヶ島の魅力はここで語る必要もないので省略。Mapillaryでバーチャルツアーを楽しむこともできますが、二重カルデラや崖を這うような道は、ぜひ現地に行って肌で感じてください。

3D Aogashima island Map: Mapillary, OpenStreetMap contributors. Elevation data: Kokudochiriin. Renderer: Kashmir.

しかしコミュニティの観点からは、WeeklyOSMの翻訳活動が最も大きな成果かもしれません。

あなたがマッピングする理由は何でしょうか?

地図は歴史です。歴史を残すために地図を作りたいと考えています。これが最も大きなモチベーションです。 日本で2011年3月11日に起こった大震災により、多くの人命やコミュニティが失われました。被害を受けたコミュニティの一部は仮設商店街を作り、それは復興のシンボルとなりました。私はいくつかの復興商店街をまわり、OSMとMapillaryでその状況を記録しました。震災から時間がたち、復興の進展にともなって、いくつかの復興商店街はその役目を終えて閉鎖されました。OSMのデータも削除されましたが、記録は残っています。Overpass turboなどのツールを活用すれば、なくなった商店街もその姿を取り戻すことができるのです。多層的な街の歴史を地図に残していけるのはOSMの大きな利点ではないでしょうか。 http://d.hatena.ne.jp/muramototomoya/20171221/1513860787

virtual revival of demolished shopping mall Map: OpenStreetMap contributors. Data mining: Overpass API.

マッピングで難しいところは?

メンテナンスです。 地物があることを確認するのは簡単ですが、マップされた地物が「ない」ことを確認するのは非常に大変です。また、複雑に詳細にマッピングされたオブジェクトは修正が大変です。バランスが重要だと思います。

今後のマッピング計画を教えてください。

横浜駅を対象にして、バリアフリーマップを事例をつくりたいと考えています。 これまでに、駅ビル内の歩道をマッピングしました。 次のステップとしては、駅構内の写真を活用するなど、マッピングされたバリアフリー情報をどのように表現したらよいのか考えたいと思っています。 http://d.hatena.ne.jp/muramototomoya/20171128/1511872639

wheelchair route search result by QGIS Map: OpenStreetMap contributors. App: QGIS

他のマッパーと連絡することはありますか?

日本ではTwitterのハッシュタグ#osmjpでコミュニケーションが行われています。質問が投げかけられたときは可能な限り回答を返すようにしています。

自分ではOSMを使っていますか?

多くのハイキングコースはGoogleマップに載っていないので、OSMを使います。Maps.meを使うことが多いです。海外旅行のときにも、オフラインマップとしてMaps.meを使っています。しかし、日常ではGoogleマップを使う機会のほうが多いです。

マッピング以外でOSM関連の活動は何か行っていますか?

上述したように、WeeklyOSMの編集チームの一員で、翻訳活動を行っています。日本人は(私自身を含めて)英語が苦手な人が多いので、日本語の情報を増やすことが必要であると考えています。

最後に一言どうぞ。

OSMは国際的な協働活動です。カルチャーやコミュニティが違えば、マッピングやタグ付けスタイルも変わる可能性があります。そのギャップを埋めるため、コミュニケーションを拡げ、他の文化やコミュニティを尊重し、 活動をosm wikiにドキュメント化していきましょう。

Las cachimbas marroquís

Posted by ermondejere on 12 May 2018 in Spanish (Español)

Cada vez es más común ver cachimbas en nuestro pais. Obviamente, las cachimbas no son una creación española, si no marroquí. Cada vez es más habitual ver en lugares de ocio fumando shisha de sabores. Las hay con nicotina y sin nicotina. Obtuve esta información en cachimbas baratas

The Hand-Cut Pass Through Solid Rock in Turkmenbashy, Turkmenistan

Posted by apm-wa on 12 May 2018 in English (English)

Do a virtual drive via these Mapillary images I took last week of the pass cut by hand by Japanese prisoners of war after World War II. The pass was carved out of solid rock using hand tools.

There is a small memorial to Japanese POWs at the top of the hill.

So far about 5,000 of the over 30,000 images I collected on this trip have been uploaded. I copied them from my smartphone to my desktop computer and am using the desktop interface with Mapillary.com to upload them. Due to the slow internet speeds of the Turkmen internet, it will be a while before all images are uploaded.

Location: 40.041, 52.972

OSM Needs Gateopeners too

Posted by bgirardot on 11 May 2018 in English (English)

Zverik's diary post contained the word "Gatekeeprs" and I have also used that term, as well as "self appointed Sheriff's of OSM" and "grumpy people" :)

OSM contributor Dzertanoj made the comment that "Gatekeeper" was a very negative term in Russian, that it even implied "dumb". In American English it is a negative term, but mildly so. In fact, to most folks it even implies the longest contributing, most experienced folks in an open source project.

Gatekeeping is a critical role to a large open project like OSM.

The problem is, that over time, years of experience supporting and contributing to the project, the gatekeepers are in the best place to see what is needed to keep the project at a very high level of quality, which OSM is at, a very high level of quality, infrastructure, data, code base, ecosystem, etc, it is in large part due to the gatekeepers.

But I think what happens is that after several years, over 10+ years in some cases, of seeing all sorts of folks and ideas and efforts come to the "commons" that is an open source project, the gatekeepers get a little focused on keeping the gate closed. They have cleaned up after this, heard this, seen this, tried this, whatever it may be and they know all the parts that cause issues on the commons. So they rightly keep the gate closed or try to.

What is needed, what I have personally tried to do, and what HOT (disclosure: I am a HOT member and past board member) tries to do is be "Gateopeners"

We know the rules as the community and gatekeepers in particular have created, they are things like the import guidelines and draft of the directed edition policy are two great examples.

We open the gate and say "Welcome, glad you are here. Sure you can do that, let us show you around the place a bit. Here are the guidelines for doing X, we can go over them with you, help you with them, show you where the wiki templates are, but you have to just follow them. You will get great feedback from the community on issues and they are very helpful with suggestions. Your project to do X will go much better following their advice. They have also done this many times and may have examples of how they did it in the past they will share with you."

But it takes time and folks to do that and unfortunately gatekeepers are usually also doing another job or two around OSM, like making significant contributions and/or running a business around OSM.

So we need gatekeepers, but we need gateopeners too. Gateopeners just want to work with and along side the gatekeepers. Let us help you by fulfilling that role so you can keep to other important matters.

I should also note what I hope is obvious: There are gatekeepers and gateopeners in other areas besides tech. They exist for fundraising and diversity as well and I am sure other areas that I am not thinking of at the moment.

I have seen great examples of gateopening over the past few years across all of these areas and I hope to have been an effective one myself. Thank you for performing an equally critical and often unrecognized role.

This whole post is meant in the most genuine appreciation for gatekeepers, self appointed Sheriffs, and grumpy experienced folks who have helped make OSM the success it is now and the success it will enjoy in the future. I won't "name names" but I hope you know who you are and know that your contributions and role in OSM mean the world to folks. I look forward to working with you all more in the future!

As Heather Leson likes to say: "Let's go be awesome together."

Respectfully, blake

Location: 42.288, -83.740

今月のマッパー:山下康成(日本)

Posted by escada on 11 May 2018 in Japanese (日本語)

自己紹介をどうぞ

私は東京に住んでいて、 地図とは全く関係のない会社で仕事をしています。

山下康成さん

あなたはいつオープンストリートマップに出会いましたか?

2009年9月に友人に紹介されました。

小石川植物園でのマッピングパーティ Mapping party @ 小石川植物園

何をマッピングしてますか?

以前は道路さえ描かれていなかったので、道路が中心でした。 最近は、神社仏閣や庭園を中心にマッピングしています。

護国寺でのマッピングパーティ

どのようにマッピングしていますか?

毎月マッピングパーティを開催しています。 サーベイ時には、フィールドペーパーを使い、またたくさんの写真やビデオを撮ります。

どのツールを使っていますか?

編集にはJOSMを使っています。

何処をマッピングしていますか?

東京都内の神社仏閣、庭園を主にマッピングしています。

浜離宮恩賜庭園でのマッピングパーティ

マッパーとしての最大の成果は何ですか?

一昨年まで私は京都に住んでいました。 京都では金閣寺や清水寺といった17ヶ所の世界遺産をすべてマッピングしました。 その成果は昨年日本で開催されたSOTMでも発表しました。 その時のスライドはこちらです。 speakerdeck

二条城 京都の二条城 on historic.place

なぜあなたはマッピングするのですか?

楽しいからです!

マッピングで一番難しいことは何でしょう?

初心者の教育です。

日本の住所体系は大きく異なると聞きました。何か問題になりますか?

私は、地理の専門家ではないので、よくわかりません。

日本には大きく2つの住所体系があります。

一つは道路の両側に同じ住所が付く場合。 これはマッピングが難しいと思います。

もう一つは区画に同じ住所が付く場合。 これはマッピングしやすいと思います。

道路の区分も違うと聞きました。何かコメントできますか?

はい。違うと思います。 文化が違えば道路の区分も違うのは普通でしょう。 そこで、日本独自の定義をしています。それはこちらで見られます。 the wiki

あなたは他のマッパーと連絡を取り合っていますか?

はい。基本的には毎月のマッピングパーティにて。

小石川後楽園でのマッピングパーティ

あなたはオープンストリートマップを使っていますか?

もちろん! 行先を確認するときなどに http://openstreetmap.org を使っています。

マッピング以外に何かオープンストリートマップに貢献していますか?

編集時のコメントを都道府県ごとにツイートするボットを運営しています。 例えば 東京都は https://twitter.com/osmjp_tokyo 京都は https://twitter.com/osmjp_kyoto です。

あと、Mapillary にも参加しています。

最後に何か一言どうぞ

Happy Mapping!!

OpenStreetMap Carto release v4.11.0

Posted by kocio on 11 May 2018 in English (English)

Dear all,

Today, v4.11.0 of the OpenStreetMap Carto stylesheet (the default stylesheet on the OSM website) has been released. Once changes are deployed on the openstreetmap.org it will take couple of days before all tiles show the new rendering.

Changes include

  • Fixed office/amenity conflict
  • Brightened built-up areas on z12
  • Refurbished natural=spring icon
  • Added rendering for amenity=police and amenity=fire_station areas
  • Added rendering of amenity=nursing_home
  • Added rendering of amenity=childcare
  • Added rendering of amenity=driving_school
  • Added area rendering for amenity=bus_station
  • Added area rendering of amenity=taxi
  • Made highway=traffic_signals icon less obtrusive
  • Moved barriers to higher zoom level
  • Hiding railway=platform with location=underground, tunnels and covered=yes
  • Small documentation and code fixes

Thanks to all the contributors for this release.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.10.0...v4.11.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

OSM & Britain’s Most Upwardly-Mobile Village

Posted by alexkemp on 11 May 2018 in English (English)

You may have missed the reports in April about Willand, a pretty little village in Devon that is 2cm (0.7 inches) closer to god each year (from the heliocentric view, of course), yet no-one knows why:

Willand village in Devon

The connection to OSM is a little tortuous, but real.

The University of Nottingham has a Geography department, and it has spun off a commercial company called Geomatic Ventures Limited (GML). GML has created a United Kingdom Relative Deformation Map using results from the Sentinel-1 satellite. Here is the blurb from the mangomap site:

United Kingdom Relative Deformation Map

A relative deformation map of the United Kingdom, generated from ~ 2000 Sentinel-1 images acquired between October 2015 - October 2017. The data was processed using the Intermittent Small Baseline Subset (ISBAS) InSAR method. Each pixel represents the average vertical height change over the period of observations in millimetres per year.

There is an extensive history of coal-mining throughout Britain, almost all of which is now defunct. The seam that Gedling Pit, Nottinghamshire was following eastwards just before closure in 1991 runs under Nottingham itself; in fact, Dowson Street (just round the corner from me) is the very street above where they stopped underground. Most of those mines were continuously pumped to keep them free of water, and that stopped at closure. There are thus both blue areas on the GVL mangomap (rising ground) due to re-flooding and red areas (falling ground) due to collapsing seams within those former mining areas.

The point of Willand is:

  1. It has the fastest rise in Britain
  2. No-one has a clue as to why!

What has OSM got to do with this?

There is a flyout within the map that allows you to add a Base Map to the Deformation Map, and the first two choices are both OSM. Very nice.

2018-05-22: Added OSM / Wikipedia links for Willand, Gedling, Dowson Street & Nottingham.

Location: 50.891, -3.373

Census project on place names dedicated to king Vittorio Emanuele III in Campania (Southern Italy).

Posted by bubix on 11 May 2018 in English (English)

As part of the #cittasenzamemoria project, the verification of toponyms dedicated to Vittorio Emanuele III in Campania was updated.

Campania

The data comes from the map of OpenStreetMap aimed at creating a free content cartography of the world. The map information is freely accessible under license ODbL and updated every day. To facilitate the consultation, the toponyms are also available on the dedicated online map. A total of 50 names were identified below:

id name City

1 Via Vittorio Emanuele III Aversa
2 Piazza Vittorio Emanuele III Aversa
3 Piazza Vittorio Emanuele III Castel Volturno
4 Piazza Vittorio Emanuele III Cervino
5 Corso Vittorio Emanuele III Benevento
6 Corso Vittorio Emanuele III Castelvetere in Val Fortore
7 Corso Vittorio Emanuele III Fragneto l'Abate
8 Piazza Vittorio Emanuele III Montefalcone in Valfortore
9 Corso Vittorio Emanuele III Pontelandolfo
10 Viale Vittorio Emanuele III Sant'Agata de' Goti
11 Corso Vittorio Emanuele III Afragola
12 Via Vittorio Emanuele III Arzano
13 Via Vittorio Emanuele III Calvizzano
14 Via Vittorio Emanuele III Camposano
15 Via Vittorio Emanuele III Casalnuovo di Napoli
16 Corso Vittorio Emanuele III Frattamaggiore
17 Corso Vittorio Emanuele III Marigliano
18 Via Vittorio Emanuele III Napoli
19 Via Vittorio Emanuele III a Miano Napoli
20 Via Vittorio Emanuele III a Secondigliano Napoli
21 Via Vittorio Emanuele III Poggiomarino
22 Via Vittorio Emanuele III Pompei
23 Piazza Vittorio Emanuele III Somma Vesuviana
24 Corso Vittorio Emanuele III Torre Annunziata
25 Piazza Vittorio Emanuele III Tufino
26 Corso Vittorio Emanuele III Capri
27 Corso Vittorio Emanuele III Lettere
28 Viale Vittorio Emanuele III Bisaccia
29 Corso Vittorio Emanuele III Casalbore
30 Piazza Vittorio Emanuele III Cassano Irpino
31 Via Vittorio Emanuele III Lacedonia
32 Piazza Vittorio Emanuele III Lioni
33 Corso Vittorio Emanuele III Pietradefusi
34 Corso Vittorio Emanuele III Quadrelle
35 Corso Vittorio Emanuele III Villanova del Battista
36 Biblioteca Nazionale Vittorio Emanuele III Napoli
37 Rione Vittorio Emanuele III Napoli
38 Corso Vittorio Emanuele III Aquara
39 Via Vittorio Emanuele III Campagna
40 Piazza Vittorio Emanuele III Cava de' Tirreni
41 Via Vittorio Emanuele III Mercato San Severino
42 Corso Vittorio Emanuele III Montecorvino Rovella
43 Corso Vittorio Emanuele III Montesano sulla Marcellana
44 Piazza Vittorio Emanuele III Morigerati
45 Via Vittorio Emanuele III Morigerati
46 Via Vittorio Emanuele III Padula
47 Corso Vittorio Emanuele III Piaggine
48 Corso Vittorio Emanuele III Sala Consilina
49 Via Vittorio Emanuele III Stella Cilento
50 Corso Vittorio Emanuele III Valle dell'Angelo

In detail, individual odonyms are also viewable on the wiki page of the project #cittasenzamemoria related to Campania.

  • Work method

The working method consisted in verifying the data coming from ISTAT 2011 Census. If the route is present in the ISTAT database through ancillary sources, it has been determined that the plates are actually registered to Vittorio Emanuele III and does not have its two homonymous predecessors (Vittorio Emaneuele I and II). If the check is positive, the presence of the road on OpenStreetMap has been checked. The result produced was that almost all the 50 mames checked were mostly already present and therefore verified by the local community of OpenStreetmap users. The strong presence of anthroponyms dedicated to Vittorio Emanuele III in Campania is due to the fact that in the constitutional referendum of 2 June 1946 with 78.9% in Naples, 72.9% in Salerno and 69.9% in Benevento, the opponents won the elections to introduction of the Republic.

  • Final considerations

The work carried out on Campania shows that the map of OpenStreetMap can be considered a valid database reliable and certified by the same community of voluntary mappers that with their painstaking work, verify, check and update the data on the maps.

Bubix