S'abonner à flux
OpenStreetMap blog aggregator
Mis à jour : il y a 15 min 24 sec

OpenStreetMap Awards 2017

il y a 4 heures 44 min

Did you know that the community voting for the OpenStreetMap Awards is open right now? We have chosen many nominees that did a great job last year, 45 of them! Not as many as the total number of active community members, but still a lot. And nine will receive the award at the Stat of the Map in August.

All nominees will be features in the series of OSM Blog posts:

Help translate the website and project descriptions to your language:

The voting closes on 16th of August. Vote now — you can change your choice at any time. Nominees would be glad to hear they are supported by hundreds of voters, so we would need at least a thousand people to vote.

Promote the Awards in your local communities, and if you are nominated, do encourage your subscribers to vote for you :) That is okay, provided you don't pay for votes or anything like that.

FrOSCon OSGeo- and OpenStreetMap track

jeu 27 jui 2017 - 22:09

FrOSCon is coming up in three weeks from now, and the program is now online.

We’re going to have a full OSGeo & OSM track this year in our own dev room, and I’m going to have three different sessions there:

How I built a wind map with WebGL

jeu 27 jui 2017 - 18:53

Check out my WebGL-based wind power simulation demo! Let’s dive into how it works under the hood.

I have an unflattering confession to make: for the last few years working at Mapbox, I avoided direct OpenGL/WebGL programming like a plague. For one reason: the OpenGL API and terminology deeply terrified me. It always looked so complex, confusing, ugly, and verbose that I could never take the plunge and dive into it. I would get an uneasy feeling simply hearing terms like stencil masks, mipmap, depth culling, blend functions, and normal maps.

This year, I decided to finally confront my fears and build something non-trivial with WebGL on my own. 2D wind simulation looked like a perfect opportunity — it’s useful, visually stunning, and challenging, yet it still felt attainable in scope. I was surprised to discover that it was much less scary than it looked!

Wind visualization on the CPU

There are many examples of wind power visualization online, but the most popular and influential one is, a famous project by Cameron Beccario. It’s not open source itself, but it has an old open source version which most other implementations based their code on. One notable open source derivation is Esri Wind-JS. Popular weather services that use the technique include Windy and VentuSky.

Wind power simulation on

Typically, such a visualization in the browser relies on the Canvas 2D API and roughly works like this:

  1. Generate an array of random particle positions on screen and draw the particles.
  2. For each particle, query the wind data to get the particle speed in its current location, and move it accordingly.
  3. Reset a small portion of particles to a random position. This makes sure that areas the wind blows away from never become fully empty.
  4. Fade the current screen a bit and draw newly positioned particles on top.

This has subsequent performance limitations:

  • The number of wind particles should be kept low (e.g. Earth uses ~5k).
  • There’s a big delay every time you update the data or the view (e.g. ~2 seconds for Earth) because data processing is expensive and happens on the CPU side.

Moreover, to integrate it as a part of an interactive WebGL-based map like Mapbox is that you would have to upload the pixel contents of the Canvas element to the GPU on every frame, which would significantly reduce the performance further.

I was looking for a way to reimplement the full logic on the GPU side with WebGL, so that it would be fast, capable of drawing millions of particles, and possible to integrate into a Mapbox GL map without a big performance loss. Luckily, I stumbled upon a wonderful tutorial about particle physics in WebGL by Chris Wellons, and realized that the wind visualization can use the same approach.

OpenGL Basics

The confusing API and terminology makes OpenGL graphics programming very intimidating to learn, but under the surface, the concept is extremely simple. Here’s a practical definition:

OpenGL provides a 2D API for drawing triangles efficiently.

So basically all you do with GL is draw triangles. The difficulty, besides the scary API, comes from the various math and algorithms required to do this. It can also draw dots and basic lines (without smoothing or round joins/caps), but those are rarely used.

Illustration from Brief Introduction to Shaders Using GLSL

OpenGL provides a special C-like language — GLSL — to write programs that are directly executed by the GPU. Each program is divided into two parts, called shaders — the vertex shader and the fragment shader.

The vertex shader provides the code for converting coordinates. For example, multiplying triangle coordinates by 2 so that our triangle appears twice as big. It will run once for every coordinate we pass to OpenGL when drawing. A basic example:

attribute vec2 coord;
void main() {
gl_Position = vec4(2.0 * coord, 0, 1);

The fragment shader provides the code for determining the color of each drawn pixel. You can do a lot of cool math in it, but in the end it comes down to something like “draw the current pixel of the triangle as green”. Example:

void main() {
gl_FragColor = vec4(0, 1, 0, 1);

One of the cool things you can do in both vertex and fragment shaders is adding an image (called texture) as a parameter, and then looking up pixel colors in any spot of this image. We’ll rely on this heavily in the wind visualization.

The fragment shader code execution is massively parallel and heavily hardware-accelerated, so it’s usually many orders of magnitude faster than an equivalent computation on the CPU.

Getting the wind data

Every 6 hours, the US National Weather Service publishes weather data for the whole globe, known as GFS, in the form of a latitude/longitude grid with associated values (including wind velocities). It’s encoded in a special binary format called GRIB, which can be parsed into human-readable JSON with a special set of tools.

I wrote a few small scripts that download and convert the wind data into a simple PNG image with wind velocities encoded as RGB colors — horizontal velocity as red and vertical as green in each pixel. It looks like this:

GFS wind power data encoded as an image

There are higher resolution versions you can download (2x and 4x), but 360×180 grid is enough for a low-zoom visualization. PNG compression is quite a good fit for this kind of data, and the image above typically weights just about 80 KB.

Moving particles on the GPU

Existing wind visualizations stored particle state in JavaScript arrays. How do we store and manipulate this state on the GPU side? A new GL feature called compute shaders (in OpenGL ES 3.0 and equivalent WebGL 2.0 specifications) allows you to run shader code on arbitrary data (without any rendering). Unfortunately, support for the new specifications across browsers and mobile devices is marginal, and so we’re left with only one practical option: textures.

OpenGL allows you to draw not only to the screen, but also to a texture (through a concept called framebuffer). So we can encode particle positions as RGBA colors of an image, load it to the GPU, calculate new positions based on wind velocities in the fragment shader, encode them back into RGBA colors and draw it into a new image.

To store enough precision for both X and Y, we store each component in two bytes — RG and BA respectively, giving us a range of 65536 distinct values for each.

Illustration from A GPU Approach to Particle Physics

An example 500×500 image would then hold 250,000 particles, and we would move every particle with the fragment shader. The resulting image would look like this:

Illustration from A GPU Approach to Particle Physics

Here’s how the position is decoded and encoded from RGBA and back in the fragment shader:

// lookup particle pixel color
vec4 color = texture2D(u_particles, v_tex_pos);// decode particle position (x, y) from pixel RGBA color
vec2 pos = vec2(
color.r / 255.0 + color.b,
color.g / 255.0 + color.a);... // move the position// encode the position back into RGBA
gl_FragColor = vec4(
fract(pos * 255.0),
floor(pos * 255.0) / 255.0);

On the next frame, we can take this new image as the current state and draw the new state into the other image, etc., swapping the two every frame. So, with the help of two particle state textures, we can move all the wind simulation logic to the GPU.

This approach is extremely fast — instead of updating only 5,000 particles 60 times per second on the browser, we can suddenly handle one million.

One thing to keep in mind is that near the poles, the particles should move much faster along the X axis compared to the ones on the equator, because the same number of longitude degrees represents a much smaller distance. This can be taken into account with the following shader code:

float distortion = cos(radians(pos.y * 180.0 - 90.0));
// move the particle by (velocity.x / distortion, velocity.y)Drawing the particles

As I mentioned earlier, in addition to triangles, we can also draw basic points — rarely used, but perfect for 1-pixel particles like this.

To draw each particle, we’ll simply look up its pixel color on the particle state texture in the vertex shader to determine its position; then determine the particle color in the fragment shader by looking up its current velocity from the wind texture; and finally map it to a nice color gradient (I picked the colors from the trusty ColorBrewer2). At this point, it looks like this:

That’s something, if a little empty. But it’s hard to get a sense of wind direction from particle movement alone. We need to add particle trails.

Drawing particle trails

The first approach to drawing the trails I tried is using preserveDrawingBuffer WebGL option, which makes the screen state persist between frames, so that we can draw particles over and over on top of each other every frame as they move. However, this WebGL feature is a big performance hit, and many WebGL articles recommend against using it.

Instead, similar to how we do with particle state textures, we can draw the particles into a texture (which is in turn drawn onto a screen), then use this texture on the next frame as the background (slightly dimmed), and swap the input/target textures every frame. In addition to better performance, an advantage of this approach is that we can port it directly to native code (which has no preserveDrawingBuffer equivalent).

Interpolating wind lookupsIllustration from a Wikipedia article on Bilinear interpolation

The wind data has values for specific points on a latitude/longitude grid, e.g. (50,30),(51,30),(50,31),(51,31)geographical points. How do we get an arbitrary intermediate value, e.g. (50.123,30.744)?

OpenGL comes with free interpolation when you look up texture colors. However, it’s quite imprecise, which can lead to blocky, pixelated patterns. Here’s an example of these artifacts in the wind texture when scaled:

Native GL linear interpolation

Luckily, we can smooth out the artifacts by looking up 4 neighbor pixels in each wind probe, and doing manual bilinear interpolation math on them in the fragment shader. It’s more expensive, but fixes the artifacts and leads to a more fluid wind visualization. Here’s the same area with this technique:

Manual bilinear interpolation on the fragment shaderPseudo-random generator on the GPU

There’s one tricky logic left to implement on the GPU — randomly resetting particle locations. Without this, even a huge number of wind particles degenerates into just a few lines on the screen, because areas the wind blows away from become empty with time:

The problem is that shaders don’t have a random number generator. How do we randomly decide if a particle needs to be reset?

I found a solution on StackOverflow — a GLSL function for pseudo-random number generation that accepts a pair of numbers as input:

float rand(const vec2 co) {
float t = dot(vec2(12.9898, 78.233), co);
return fract(sin(t) * (4375.85453 + t));

This curious function depends on sin result varying a lot with big values. Then we can do something like this:

if (rand(some_numbers) > 0.99)

The challenge is picking an input for each particle that would be “random” enough so that the generated values are uniform across the screen and do not exhibit weird patterns.

Using current particle position as the seed is not perfect because the same particle positions will always generate the same random numbers, so some particles will disappear in the same area.

Using particle position in the state texture also doesn’t work because the same particles will always disappear.

What I ended up with eventually depends on both particle position and state position coupled with a random value that’s calculated on every frame and passed to the shader:

vec2 seed = (pos + v_tex_pos) * u_rand_seed;

But then we have another minor problem — areas where particles are very fast will look much more dense than areas where there’s not much wind. We can balance this out a bit by increasing the particle reset rate for faster particles:

float dropRate = u_drop_rate + speed_t * u_drop_rate_bump;

speed_t here is a relative speed value (from 0 to 1), and u_drop_rate and u_drop_rate_bump are parameters you can tweak in the final visualization. Here's an example of how it affects the result:

High drop rate (reminds me of a Van Gogh painting)What’s next

The result is a fully GPU-powered wind visualization that can render a million particles at 60fps. Try playing with the sliders in the demo, and check out the final code — it’s about 250 lines total, and I tried to make it as readable as possible.

The next step is integrating this into a live map you can explore. I’ve made some progress on this but not enough to share a live demo. Here’s a little sneak peek though (sorry for the poor quality capture):

Thank you for reading and stay tuned for more updates! And check out my previous article on spatial algorithms if you missed it.

Very special, warm-hearted thank you to my Mapbox team mates @kkaefer and @ansis, who patiently answered all my silly questions about graphics programming, gave tons of valuable tips and helped me learn so much. ❤️

P.S. Want to work on cool stuff like this? Check out our job openings.

How I built a wind map with WebGL was originally published in Points of interest on Medium, where people are continuing the conversation by highlighting and responding to this story.

weeklyOSM 366

jeu 27 jui 2017 - 18:01


SotM Africa in Kampala – read two reports 1 | © Harry Wood

  • Martijn van Exel writes on the Telenav blog a little bit about MapRoulette. He feels that the page with the most popular and newest challenges is not particularly easy to use. He asks for input to improve the way to find challenges of interest for contributors.
  • Pander proposed some improvements to the beautified JOSM presets for natural=tree in the tagging mailing list. See also discussion on the related Vespucci github issue..
  • Stuart Reynolds asks on Talk-gb mailing list whether “St” in names should be abbreviated or not.
  • Vivek Bansal, of Santa Clara Valley Transportation Authority, wants to set up a US Tasking Manager task for adding sidewalk=* tags across the entire Santa Clara County, California.
  • Mapillary invites participation in a mapathon to improve street-level photo coverage in Medellin. The mapathon runs until August 3rd.
  • Mapillary draws attention to the US Summer Bus Mapathon and publishes a tutorial on “How to Map Bus Routes and Infrastructure on OpenStreetMap”.
  • The ‘Mapper of the Month’ chosen by OpenStreetMap Belgium is Jamie Nadeau aka LogicalViolinist from Canada.
  • OpenStreetMap awards are back. It’s time for you to vote and support not just one but multiple nominees. This time’s procedure involves Approval Voting. Learn more about this in the blog post.
  • Mapmeld reasons and writes about translating OpenStreetMap into Divehi, the local language of the Maldives.
  • It looks like Robin Paulson has discovered an import of buildings with no documentation (Auckland, NZ).
  • Sam Libby works on a new feature for the iD editor to ease the import of “authoritative” (his wording) data from ArcGIS REST into OpenStreetMap without the need to use JOSM. Several OSM contributors have already commented on his issue.
OpenStreetMap Foundation
  • On July 18, an executive board meeting of the OSMF took place. Various topics were discussed, among others like “Microgrants”, and the corporate editing policy. OSM France was recognized as regional chapter (the contract is in the OSMF wiki). The log was still not online at the time.
  • The first SotM Africa was held between 8th and 10th July, you can read reports by Map Zambia and Janet Chapman sharing their experience at the conference.
Humanitarian OSM
  • An invitation on the Talk mailing list to a Community Webinar about the improvement of mapping residential areas initiates some criticism about the way that landuse=residential is used in some HOT mapping projects. Christoph Hormann explains why from his point of view you cannot use the same assumptions as used in Europe in regions where most people work in the primary sector (agriculture).
  • Wondering how to get an OSM-based map onto a Garmin device without external storage? This diary entry by robbieonsea contains detailed instructions.
  • OpenMapTiles developed a map which shows the names of places in different languages.
  • Mapbox presents “Whaam!” a map style inspired by the pop art movement, in particular, the work of Andy Warhol, James Rosenquist and Roy Lichtenstein. True eye candy!
Open Data
  • Dmitrij Kožuch is planning an open landuse map for Africa based on available data sources. The main source probably will be OSM.
  • The Guardian and GiGL have worked together to produce an open data set (currently only available through GiGL’s dropbox) of privately-owned public spaces (squares, plazas, parks etc) for Greater London.
  • The Overpass API instance of FOSSGIS e.V. ( had problems following a power outage. Metadata queries (out meta;) did not work. The problem is now fixed.
Programming Releases

Walter Nordmann published emergency map 2.8. Main new feature is clustering for fire hydrants and rescue points.

Software Version Release date Comment Jungle Bus 1.2.4 2017-07-20 No infos. Komoot Android * 9.3 2017-07-18 No infos. Magic Earth * 2017-07-19 Many changes, please read release info. Mapbox GL JS v0.39.0 2017-07-21 Many changes, please read release info. Android * 7.4 2017-07-20 Improved routing, recent map data. iOS * 7.4 2017-07-20 Improved routing, recent map data. OSRM Backend 5.9.0 2017-07-19 Many changes, please read release info. OSM Contributor 3.0.9 2017-07-20 Bugs fixed. QGIS 2.18.11 2017-07-21 No infos. Simple GIS Client * 9.2 2017-07-18 VMany changes, please read release info. VTM 0.8.0 2017-07-19 Many changes, please read release info.

Provided by the OSM Software Watchlist. Timestamp: 2017-07-22 21:29:55+02 UTC

(*) unfree software. See: freesoftware.

Did you know …
  • … there are coasters with OSM map print available on the Net? Including yellow cast for “vintage” look, however still without attribution.
  • Mike Bostocks command-line cartography – part 1 and part 2?
  • … the website where you can follow several OSM-related blogs?
  • … the open source project Plan4all? The umbrella organization offers open data for use in research, development, and innovation. OpenStreetMap plays an important role.
Other “geo” things Upcoming Events Where What When Country Seattle Complete The Map Challenge, Mapillary image mapping 2017-06-23-2017-07-31 Itami 【西国街道#08】オープンデータソンin伊丹「有岡城惣構」 2017-07-29 Tokyo 東京!街歩かない!マッピングバーティ2 2017-07-29 Managua Editathon with iD 2017-07-29 Taipei OpenStreetMap Taipei Meetup, MozSpace 2017-07-31 Rostock Rostocker Treffen 2017-08-01 Stuttgart Stuttgarter Stammtisch 2017-08-02 Dresden Stammtisch Dresden 2017-08-03 Brisbane Nundah Mapping Party 2017-08-04 Amagasaki 地図好きに送るオープンストリートマップの使い方 in みんなのサマーセミナー2017 2017-08-05 Taipei COSCUP OpenStreetMap Track, National Taiwan University Social Science College 2017-08-05 Kusatsu 真夏のマッピングパーティ in 草津 2017-08-06 Berlin 110. Berlin-Brandenburg Stammtisch 2017-08-11 Passau Mappertreffen 2017-08-14 Boston FOSS4G 2017 2017-08-14-2017-08-19 Aizu-wakamatsu Shi State of the Map 2017 (international conference) 2017-08-18-2017-08-20 Patan State of the Map Asia 2017 2017-09-23-2017-09-24 Colorado Boulder]] State of the Map U.S. 2017, [[Boulder 2017-10-19-2017-10-22 Buenos Aires FOSS4G+State of the Map Argentina 2017 2017-10-23-2017-10-28 Brussels FOSS4G Belgium 2017 2017-10-26 Lima State of the Map LatAm 2017 2017-11-29-2017-12-02 Bonn FOSSGIS 2018 2018-03-21-2018-03-24

Note: If you like to see your event here, please put it into the calendar. Only data which is there, will appear in weeklyOSM. Please check your event in our public calendar preview and correct it, where appropriate.

This weeklyOSM was produced by Nakaner, Peda, PierZen, Polyglot, Rogehm, SK53, SomeoneElse, Spec80, YoViajo, derFred, doktorpixel14, jinalfoflia.


jeu 27 jui 2017 - 17:03

This is a review test

Wochennotiz Nr. 366

jeu 27 jui 2017 - 15:03


    SotM Africa in Kampala – mittlerweile sind zwei Blog-Beiträge erschienen 1 | © Harry Wood

  • Martijn van Exel berichtet in seinem Blog ein wenig über MapRoulette, stellt die Seite der populärsten und der neuesten Aufgaben vor und bittet aber auch um Vorschläge, wie man interessante Aufgaben in MapRoulette besser finden kann.
  • PandaMusubi schlägt eine Erweiterung des Baum-Taggings für das JOSM-Preset vor.
  • Borut Maricic fragt auf der Mailingliste Talk-at nach einem passenden Tag für Jagdhütten, da dafür bereits verschiedene Tags verwendet wurden.
  • Stuart Reynolds regt auf der Mailingliste Talk-gb mit der Frage, ob die Abkürzung „St“ für „Saint“ in Namen verwendet werden kann, zur Diskussion an.
  • Vivek Bansal, ein Angestellter des Verkehrsverbundes Santa Clara Valley, will eine Aufgabe im US-Tasking-Manager zum Erfassen von allen Gehwegen mit sidewalk=* im gesamten Santa Clara County einrichten.
  • Mapillary lädt zu einem Mapathon in Medllín ein, bei dem noch bis zum 03. August Bilder in einem abgegrenzten Bereich der Stadt auf Mapillary hochgeladen werden können.
  • Benutzer krza wundert sich, dass ein Fußgänger-Router ihn über eine Schnellstraße (highway=trunk) navigiert hat und hakt im Forum nach, ob Schnellstraßen grundsätzlich für Fußgänger und Fahrradfahrer zugänglich sind.
  • Auch Mapillary ruft zur Teilnahme am US-amerikanischen Summer Bus Mapathon auf, um die Bushaltestellen und andere Dinge entlang der Route zu erfassen und erklärt, wie man das mit und auch ohne Mapillary am besten machen kann.
  • OpenStreetMap Belgien kürt den Kanadier Jamie Nadeau alias LogicalViolinist zum Mapper des Monats Juli.
  • Ein Eintrag im Blog von Malte Kiefer über StreetComplete hat zu einer kleinen Welle an Neuanmeldungen geführt. Bislang ist das aber kaum jemandem (negativ) aufgefallen?

    Eine weitere Welle an Neuanmeldungen und Wiederaktivwerden von teils recht alten Benutzerkonten könnte möglicherweise durch die Erwähnung von OpenStreetMap in der Ausgabe 201 des Podcasts Freakshow (ab 2:08:13) „verursacht“ sein.

  • Die Data Working Group der OSMF sucht einen Mapper, der sich am Hermannsberg bei Oberschönau (Kreis Schmalkalden-Meiningen) ein paar Waldwege vor Ort anschaut, weil es dort eine Beschwerde gegeben hat.
  • Die diesjährigen OpenStreetMap-Awards stehen an! Nachdem die nominierten Personen bereits feststehen, kann nun jeder mit einem OSM-Profil über die Gewinner abstimmen.
  • Zum Treffen des Regionalverbandes Ruhr mit Städtevertretern aus NRW und der OSM-Community gibt es ein offizielles Protokoll. Die Konferenz in Essen war sehr erfolgreich. Es wird eine neue Mailingliste „Stadtkarte Rhein-Ruhr“ geschaltet.
  • Am 27. Juli findet in Lübeck der 100. OSM-Stammtisch statt. Jan Tappenbeck blickt auf Nr. 1 (2. April 2009) zurück.
  • Mapmeld begründet, warum er OpenStreetMap in Divehi, die lokale Sprache der Malediven übersetzt.
  • Es sieht aus, als ob Robin Paulson einen Import ohne Dokumentation entdeckt hat.
  • Sam Libby arbeitet an einer Anbindung des iD-Editors an ArcGIS-REST-Schnittstellen, damit man „autoritative“ Daten ohne den Umweg über JOSM importieren kann. Mehrere Mapper haben das auf Github schon kommentiert.
OpenStreetMap Foundation
  • Am 18. Juli fand eine Sitzung des Vorstandes der OSMF statt. Themen waren u.a. „Microgrants“, und die Corporate Editing Policy. OSM France wurde als Regionalvertretung anerkannt (der Vertrag ist im OSMF-Wiki nachzulesen). Das Protokoll war bei Redaktionsschluss noch nicht online.
Veranstaltungen Humanitarian OSM
  • Die Einladung zu einem Webinar zur Erfassung von landuse=residential auf der Mailingliste Talk löst eine Welle an Kritik an der systematisch falschen Verwendung von landuse=residential in Regionen aus, in denen die Menschen überwiegend in der Landwirtschaft tätig sind.
  • Du fragst Dich, wie Du eine OSM-basierte Karte auf ein Garmin-Gerät ohne externen Speicher bekommst? Dieser Blog-Beitrag von robbieonsea enthält detaillierte Anweisungen.
  • OpenMapTiles hat eine Karte entwickelt, mit der man ganz leicht Ortsnamen in verschiedenen Sprachen ansehen kann.
  • Mapbox stellt einen Kartenstil namens „Whaam!“ vor, der die Welt komplett im Pop-Art-Stil darstellt. Dabei wurden die Entwickler von berühmten Künstlern wie Andy Warhol, James Rosenquist und Roy Lichtenstein inspiriert.
  • Dmitrij Kožuch plant eine offene Karte der Landnutzung in verschiedenen afrikanischen Ländern. Als Quelle will er dafür neben anderen offenen Datenbanken hauptsächlich OSM benutzen.
  • Die Overpass-API-Instanz des FOSSGIS e.V. ( hatte nach einem Stromausfall Probleme. Abfragen mit Metadaten (out meta;) funktionierten deshalb nicht.
Programmierung Releases Kennst du schon …
  • … die Untersetzer mit OSM-Kartendruck, die im Netz angeboten werden? Per Gelbstich auf „alt“ getrimmt, aber leider (noch) ohne Attributierung.
  • Mike Bostocks „command-line-cartography“ – Teil 1 und Teil 2?
  • … die Seite, mit der man verschiedene Blogs zu OSM verfolgen kann?
  • … das Open Source Projekt Plan4all? Die Dachorganisation mit 26 Partnern aus 14 Ländern bietet offene Daten zur Verwendung in Forschung, Entwicklung und Innovationen an. OpenStreetMap spielt eine wichtige Rolle.
Weitere Themen mit Geo-Bezug Wochenvorschau

Diese Wochennotiz wurde erstellt von Michael Reichert, Peda, Manfred Reiter, doktorpixel14.

HOT Mapathon

jeu 27 jui 2017 - 14:27

Hello all, Namasthe! 🙏 We had an amazing HOT Mapathon on July 21st at Mapbox India office. We had the local OSM community along with folks who were mapping for the first time adding approximately 3000 buildings in Cambodia for Eliminate Malaria task.

The good thing about this event was that most of them knew about OpenStreetMap and very few people were new into mapping activity. At first, we introduced to OpenStreetMap, it’s data model, and good practices one should know while editing and a short demo of editing in iD editor.

Few Photos

Upendra introducing the HOT and it's objectives

Jinal Foflia helping the participant for mapping

Many of us discussed about ongoing mapping activities in Africa with more emphasis on FGM and Malaria issues and how non profit organisations are utilising the data that people produce to save many lives. Also, we've discussed about upcoming State of the Maps in Japan, US and Nepal. Some of the questions they asked are like, how data produced by many people been validated? who will take care of ground truth? and what is the community capacity right now? and so on. Hope we cleared all of them!

We hope to have many more events in the future with the community and help for humanitarian purposes.

Best, Chetan

OSM Awards 2017 nomination

jeu 27 jui 2017 - 13:58

Nominations for the 2017 OSM Awards have been published and voting has started.

I was surprised to learn today that I’ve been nominated as a candidate in the “Core System Awards” category ….

ملعب الفقيد علي اسعد المصري المضو

jeu 27 jui 2017 - 13:26

هذا ملعب الفقيد علي اسعد المصري المضو مديرية الشعيب محافظة الضالع مع تحيات الشيخ غسان المصري

Public Transport Mapping, why do we add the stop details several times over?

jeu 27 jui 2017 - 13:07

When we started mapping public transport stops, some people insisted on mapping them on nodes next to the way, others thought the right way to do it, was to add them as nodes being part of the highway, thereby losing the information on which side of the road the bus stop was.

Then somebody came by with the idea to unite both ways of mapping. In itself that sounds great. But where do we add the details then? On both? That doesn't really make sense. It's a maintenance nightmare.

So we still have some people adding the stops as stop_position nodes on the highways and others mapping them as isolated nodes next the ways as public_transport=platform. But of course a node is not a platform, so others map those as ways and areas. Nothing wrong with that, but why do we need to add all the details to these ways?

For some reason it was decided that both these stop_postion nodes and the platform ways/nodes need to be added over and over again to the route relations. These route relations represent each and every variation of the public transport lines, so there are thousands of them. Another maintenance nightmare.

Why can't we have a node next to the way, with all the relevant details and add those nodes to the route relations, then followed by a continuous string of ways? The node gets tagged public_transport=platform/highway=bus_stop.

The node isn't always representing an actual platform. If there is a platform, nothing wrong with representing it as a way or an area. But there is no real need to duplicate all the details like name/ref/route_ref/zone to these ways. And there isn't really a need to add them to the route relations.

For the simplest bus stops a node next to the way public_transport=platform/highway=bus_stop is all that is needed. It contains all the relevant information and it has coordinates, which makes it convenient to compare it to data from operators.

For more completely mapped bus stops, benches and waste_baskets can be added.

If you want to make explcit where the vehicle stops, a public_transport=stop_position can be added on the highway. For the first and last stops, the way should be split there, as it's the beginning or end of the route.

But these stop_position nodes are not all that important, so no real need to map them for every stop. Also no reason why the stop details should be repeated on them and no real need to add them to the route relations. It's enough to add them to stop_area relations.

Wanderrouten im Pfälzerwald

jeu 27 jui 2017 - 12:07

Die Kartierung der Wanderrouten bzw. der Wanderwege ist dank der zahlreichen Mapper gut vorangekommen. In den Jahren sind aus lokalen Rundwegen sehr oft Themenwege geworden. Dabei sind nummerierte Wege auch entfernt worden. Zumindest auf den neuen Infotafeln. Im Gelände findet man weiterhin alte Markierungen aller Art, leider. Ein Schwachpunkt ist die Aktualität der Daten. Einmal erfasst, so lässt die Aktivität der Kartierung an den Wanderwegen nach. Es gibt zwar zwar Mapper, die sich darum kümmern, jedoch nicht so viele wie zur Zeit der Ersterfassung. Mir ist bisher nicht bekannt, dass von Gemeinden, Vereinen, Verbänden ein aktiver Beitrag zum Datenbestand stattgefunden hat.


jeu 27 jui 2017 - 9:09

Urgensi sistem informasi kesehatan sangat dibutuhkan setiap orang dan oleh semua kalangan. Dengan begitu diharapkan, website kesehatanweb mampu memberikan sebuah informasi yang dapat membantu dan memberikan manfaat bagi kita semua.

Itulah sedikit pengenalan kami mengenai website kesehatanweb. Semoga dengan sedikit pengenalan tersebut bisa menjadikan anda lebih mengenal lebih dalam lagi mengenai

Untuk mencari informasi kesehatan silahkan kunjungi situs kami

100. Stammtisch für Lübeck und Umgebung

jeu 27 jui 2017 - 8:21


heute findet in Lübeck der 100. Stammtisch für Lübeck und Umgebung statt.

Gruß Jan

Forest Service Road notes

jeu 27 jui 2017 - 0:16

ref = FS xx

highway = unclassified
  • maintained as a through road connecting other roads OR lenghty and provides access to a significant point of interest
  • generally maintained to a level usable by a standard passenger car without AWD/4WD (smoothness = bad, or better)
  • paved or unpaved
  • Example: Cooper Creek Road (FS 33) and Blue Ridge Road (FS 42), in Georgia
highway = track
  • not a through road
  • unpaved
  • generally unmaintained, AWD/4WD is recommended or necessary (smoothness = very_bad, or worse)
highway = service
  • not a through road
  • paved or unpaved
  • short or medium length
  • provides access to a point of interest

Autobuses de transporte público en Málaga

mer 26 jui 2017 - 22:37

He terminado de recopilar las relaciones de las líneas de transporte público en autobús de Málaga. Las he ido anotando todas en la tabla de la página wiki dedicada al transporte público de la ciudad.

En los próximos meses espero encontrar tiempo para revisarlas todas en detalle. Me puede llevar meses si pretendo hacerlo solo, así que me lo tomaré con calma. Habrá que comprobar si las líneas están completas y correctamente mapeadas, añadir las líneas que faltan y, sobre todo, mapear las paradas. Hay mucho trabajo por hacer, pero también debo reconocer que hay mucho trabajo previo hecho y bien mapeado por otros colaboradores. Casi todas las líneas de autobús de Málaga están en el mapa y etiquetadas correctamente.

Paralelamente, seguiré con el mapeado de edificios del casco urbano. También quiero retomar lo que fueron mis primeros trabajos de mapeo, los relativos al trazado de caminos, arroyos y localización de caseríos y lagares abandonados de los Montes de Málaga.

En las últimas semanas he tenido algunas experiencias ingratas en lo relativo a la traducción del wiki, así que me desentenderé un tanto de esa tarea por ahora. Tengo que replantearme esos trabajos. Supongo que lo mejor para no perder la ilusión del principio será volver a los orígenes, a mapear esos caminos solitarios de los montes por donde suelo salir a caminar.

Welcome to the team, Liz Shigetsohi!

mer 26 jui 2017 - 19:43

By: Jake Pruitt

We’re thrilled to welcome Liz Shigetoshi to Mapbox!

Liz joins our design and engineering teams in San Francisco. She’ll focus on developing and maintaining our front end infrastructures.

Prior to Mapbox, Liz built data visualizations, feedback tools, and map-based dashboards for the University of California, Davis. She holds a bachelor’s degree in computer science and computational biology.

When not tinkering with code, she enjoys “leg day” at the gym, discovering up and coming music artists, and exploring a new country on her bucket list.

Welcome aboard, Liz!

Jake Pruitt

Welcome to the team, Liz Shigetsohi! was originally published in Points of interest on Medium, where people are continuing the conversation by highlighting and responding to this story.

Welcome, Ann Millspaugh!

mer 26 jui 2017 - 19:09

By: Sam Matthews

We’re excited to have Ann Millspaugh join the Core Tech team in our San Francisco office! She will work with members of the engineering division to ensure that our mapping infrastructure continues to grow quickly and efficiently.

Prior to joining Mapbox, Ann worked as a software engineer and civic tech advocate in DC, NY, & CA. She has worked on small business development in San Diego & Syracuse, pushed for nationwide ethical investing programs and practices, and lead initiatives for open internet policies in DC.

Welcome to the team, Ann!

Sam Matthews

Welcome, Ann Millspaugh! was originally published in Points of interest on Medium, where people are continuing the conversation by highlighting and responding to this story.

test – please ignore

mer 26 jui 2017 - 18:42


Put more text here

Choose the best bloggers and mappers for the OSM Awards 2017

mer 26 jui 2017 - 15:13

The community voting for the OpenStreetMap Awards 2017 continues! We have 45 nominees, any number of which you can support, and only nine of them will receive the award. This is a hard choice, and to help you, we are continuing the series of posts about the work nominees did.

Influential Writing Award

For the best tutorial, documentation, blog or a blog post. A text or series of texts that attracted many new people to OSM, provided an interesting outlook on the project, or inspired the community to do better things.

  • Carto’Cité: there are few blogs about GIS in non-English languages, and we are lucky to have this one. Carto’Cité is a geomatics agency in Nantes, France, and not only they do work for their clients, they also regularly publish very detailed tutorials for using OpenStreetMap data in QGIS, uMap and other open tools.
  • Joost Schouppe: being the most visible member of the belgian community, he organizes local events and publishes a very diverse and useful diary. He writes in detail about analysing OSM data, using data from government, about impact of mapping parties and Missing Maps events, and interviews interesting people.
  • BushmanK: he has posted many thoughtful diary posts about various aspects of the OpenStreetMap, which make you question everything: mapping time zones, adding name translations, tagging man-made structures, using signs for names, and even governance of the map. He may seem rude at times, but that’s because his native language is Russian.
  • Ramani Huria: they are the very active community in Tanzania, and their blog is full not only with event reports, but with tutorials on JOSM, QGIS and mapping techniques, in both English and Swahili. Their articles are useful both to people from their country and to everyone else.
  • Arun Ganesh: better known as PlaneMad, he is the leader of the Mapbox’s data team, always watching for errors on the map and analysing data, examining mapping applications or styling maps in his spare time. All of that you can see in his blog, complete with diagrams, screenshots and funny pictures.
Greatness in Mapping Award

For significant contributions to the map data, or exemplary mapping: micro-mapping, clean-up, mapping towns from scratch, proper imports.

  • xscvxc: while most of us map cities we live in, xscvxc is busy mapping small towns in his region, not on the radar of urban mappers. In his 2.8 mln edits he perfected his home town and proceeded to improve many other rural areas of Novosibirsk Region in Russia.
  • Russell Deffner: to predict and prevent malaria disease spread, you need all the settlements and their buildings on the map. Russel has coordinated a global effort to map more than 4 million buildings across 7 countries, which is a lot. Read about this on the HOT project page.
  • Jochen Topf: in March there were quarter million old-style multipolygons, and now there is none. All thanks to Jochen, who is coordinating the continuing series of polygon fixing tasks, complete with statistics, maps and explanations. Subscribe to this github issue to learn about new tasks, and help him make the OSM data simpler to use.
  • Bishal Bhandari: for a year and a half he has been actively mapping cities in Nepal: Kathmandu, Pokhara, Tikapur and others. There are few days he goes without adding something to the map: even today he’s drawn a lot of school buildings there.
  • katpatuka: if you’ve been in OpenStreetMap for at least a year, you’ve sure seen edits by katpatuka. In his 10 years of editing he made 30 mln changes, mostly to Turkey and China. There is no point in showing his editing heat map: he has touched almost every point on Earth, focusing on less-developed areas. And he had not slowed down: it’s like if everyone else leaves OSM, thanks to katpatuka the map will still be complete eventually.

We hope you have made your choices — head to the OSM Awards website and mark people and groups that you think did the best job. You can choose any number of nominees, and the choice can be altered at any moment before the voting closes on 16th of August. We’ll return next week to look at the regional categories.

Подлипки на 13-е

mer 26 jui 2017 - 8:43

Тринадцатый день рождения OpenStreetMap в этому году отмечается тринадцатого августа. Как мы в России отмечаем эти годовщины? Картой для проекта и шашлыком для нас, конечно. Москвичи, освобождайте воскресенье и приезжайте! Ехать недалеко: всего час на электричке от Белорусского вокзала и метров триста пешком до озера.

План такой: в 12:30 приезжаем на электричке и встречаемся на платформе Портновская (или в поезде), разбираем обходные листы и идём гулять. Вокруг есть пара деревень и лес совершенно без тропинок. Около 16 возвращаемся к разливу Сетуни и жарим шашлык, знакомимся, травим байки, рассказываем про интересные задачи и новости.

Если едете, записывайтесь в вики или отмечайтесь на форуме. Жду каждого, независимо от опыта в осме. Мы такие же интроверты, как и вы!

Тем, кто живёт далеко от Москвы, советую организовать встречу в своём городе. Не обязательно картировать или планировать выезд: достаточно выбрать кафе или паб и объявить время. Праздновать годовщину лучше вместе с другими картографами, а не по-одиночке за компьютерами.