Users' diaries

  • Rss

Recent diary entries

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".


  • 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 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 (日本語)






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




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


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

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



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

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


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


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

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








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 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 (日本語)


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




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


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



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







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

二条城 京都の二条城 on








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

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


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





もちろん! 行先を確認するときなどに を使っています。


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

あと、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 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

As always, we welcome any bug reports at

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.


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.


The Turkmenistan page in OSM's Wiki

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

I am working on the Turkmenistan page in the OSM Wiki, seeking to add information I've acquired during my tour of duty here in Ashgabat. If you have suggestions for information that should go on this page for purposes of preserving institutional memory, please sing out! If I don't possess the information I'll try to find it during the time left on my tour of duty.

Location: Nomadic village, Ahal Region, Turkmenistan

Revamping M5 motorway in Brisbane, Australia.

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

This entry is for my reference and for anyone who is interested in cleaning their motorways.

I have decided to do some clean ups and fixes along a motorway (mostly linking roads) here in Australia. I think this is important for GPS usage, or otherwise clarity sake whilst viewing. I want to list the things I did to cleanup and otherwise improve.

Adjust to GPX and imagery

This one should come as no surprise, but I'm still seeing these off by a few meters. It is important to use a good imagery source and offset by GPX. Keep in mind that people driving will be in different lanes, so align the road to be in the centre of this

Use of destination tags on linking roads and junctions (e.g. offramps and onramps)

This one is important for GPS navigation. Here are the tags that I'm going with:

destination= This tag is for whatever the sign says, I reserve this one mostly for a Suburb or City name. Use a semicolon to separate multiple names: City 1;City 2. Mapillary and OpenStreetCam help here.

destination:street= The name of the road that is at the end of the linking road.

destination:ref= The reference number of the road that is at the end of the linking road.

destination:network= I think this one is unofficial, but I use this if the destination has a network.

Improving junctions

Someone has already done a good job at adding most. However where I am, motorway junctions are only used when the exit has a ref number (e.g. Exit 32). This isn't good for exits which don't have numbers. So to areas which didn't have any. I've added them and used the destination tag on them instead.

I have also added destinations tags to existing ones where needed. These were placed as per the wiki's instruction.

Making transition roads at junction

Although the placement=transition tag isn't official, I like to use it on the slight bit of road that connects the motorway to the motorway_link road.

An example image from the wiki

Another big clean-up here involved, putting the junctions at the last legal turn off, many old edits from decades are still present. Many lanes are marked as individual roads, this make clarity hard to see.

Slight Proposal

I'm not too sure if this is really useful. But it does make me think: do we really need to put the motorway junction ON the fork between the motorway and offramp? I understand that the highway=motorway_junction is meant to signify the beginning of the exit, but couldn't the placement=transition tag perhaps take care of this?

Location: Jindalee, The Hills, Queensland, 4074, Australia

Turkey Run State Park

Posted by h4ck3r9 on 10 May 2018 in English (English)

Turkey Run was certainly worth the trip. The trails are awesome! Trail #3 isn't very dog friendly though, just so you know. You can spend hours and even days just hiking around the trails and doing fun things. There is horseback riding, canoeing, rafting, and tons of other things. We'll definitely have to come back to this place later.

Location: Cincinnati, Parke County, Indiana, 47832, United States of America

Kaisertal Pfad wieder von mir gelöscht

Posted by chrsmsk on 10 May 2018 in German (Deutsch)

Nach langem Hin- und Herüberlegen hab ich mich entschlossen den von mir eingetragenen Weg wieder rauszunehmen, Grund ist einzig allein das abgerutschte Stück, das nur noch recht gefahrvoll zu begehen ist. Was noch hinzu kommt: Dieses Stück ist wohl auch ständigen Veränderungen durch Ausspülung bei Starkregen unterworfen. Ich will dafür nicht die Verantwortung übernehmen. Natürlich könnte ich die Verantwortung auf die auf OSM basierenden Endprodukte (die Renderer) abschieben, denn wenn der Pfad /das kritische Stück überall korrekt wiedergegeben würde, könnte ich wohl damit leben. Ist aber nicht so. Für die meisten Apps/ auf OSM basierenden Karten ist es einfach ein stinknormaler Weg wie jeder andere. Das Kaisertal ist eine Tourismusregion und ich weiss um das Freizeitverhalten mancher Gäste, die einfach ihrem Smartphone nachgehen.

Und sagen wir mal so Besucher hat es geschafft sich bis zu diesem Stück vorzuarbeiten, kommt dann aber nicht weiter, muss er wieder Stunden zurückgehen oder weglos durch Steilgelände einen Abstieg versuchen. Bei anderen Wegen sind die Schwierigkeiten klar ersichtlich von Anfang an. Hier nicht so, obwohl auch schon im ersten Teil anspruchsvolle Passagen kommen.

Ich habe die Linie stehen gelassen, sollte der Pfad also ausgebessert werden kann man sie wieder verwenden.

Wer den Pfad trotzdem wieder einzeichnen will, bitteschön, aber nicht unter meinem Namen/Kürzel.

Полное редактирование города Торжка.

Posted by Sergey_sheglov on 10 May 2018 in Russian (Русский)

Цель задания - восстановление объектов "на свои места". Исправление ошибок необозначенных зданий, Удаление несуществующих зданий, проведение исследования при помощи GPS трекера для вырисовки дорог невидимых с космоса.

Location: Лазутино, Торжок, городской округ Торжок, Тверская область, Центральный федеральный округ, 172035, РФ


Posted by Esmat Enan on 10 May 2018 in English (English)

Trying to extract Z value from OSM using TCX

Map internationalization launched everywhere, AND embedded maps now live on 276 Wikipedias

Posted by naveenpf on 10 May 2018 in English (English)

As of today, interactive (Kartographer) maps no longer display in the language of the territory mapped; instead, you’ll read them in the content language of the wiki where they appear—or in the language their authors specify (subject to availability of multilingual data). In addition, mapframe, the feature that automatically embeds dynamic maps right on a wiki page, is now live on most Wikipedias that lacked the feature. (Not included in the mapframe launch are nine Wikipedias [1] that use the stricter version of Flagged Revisions).

If you you’re new to mapframe, this Kartographer help page [2] shows how to get started putting dynamic maps on your pages. If you’d like to read more about map internationalization: this Special Update [3] explains the feature and its limiations; this post [4] and this one [5] describe the uses of the new parameter, lang=”xx”, which lets you specify a map’s language. And here are some example maps [6] to illustrate the new capabilities.

These features could not have been created without the generous programming contributions and advice of our many map-loving volunteers, including Yurik, Framawiki, Naveenpf, TheDJ, Milu92, Astirlin, Evad37, Pigsonthewing, Mike Peel, Eran Roz, Gareth and Abbe98. My apologies to anyone I’ve missed.

The Map Improvements 2018 [7] project wraps up at the end of June, so please give internationalized maps and mapframe a try soon and give us your feedback on the project talk page [8]. We’re listening.

[1] [2] [3],_2018,_Special_Update_on_Map_Internationalization [4],_2018,_You_can_now_try_out_internationalization_(on_testwiki) [5],_2018:_OSM_name_data_quirks_and_the_uses_of_lang=%E2%80%9Clocal%E2%80%9D [6] [7] [8]

Email from Joe Matazzoni Product Manager, Collaboration Wikimedia Foundation, San Francisco