Pieren has commented on the following diary entries

Post When Comment
Über Imports 10 days ago

Your example in France is outdated:

Don't copy others complains withtout rechecking ;-)

And I see no issue of importing buildings before tracing highways. Nothing in OSM is forcing a priority in features mapping. If you want to start with roads, good for you. If someone else wants to map postbox, forest, fire hydrants or buildings before any roads, why not !? ^^

Happy mapping

new useful proposal 18 days ago

For history, just remember that the wiki page has been create a 1st april -> April Fool's joke

highway=bus_stop - Mappen für den Renderer 20 days ago

Problem with public_transport is a birth defect : since its first porposal and during approval process, it was never clearly asking to deprecate "highway=bus_stop" for the simple reason that the new solution was more complex than the previous one for simple bus stops and the submitters knew they would fail in such way (by experience, all proposals starting with "depecrates this and that" are always slaped by responders).
The PT is nice for complex stations and multimodal connections. It's also nice when you map PT networks from the operator point-of-view. But it is too complicate for the simple contributor who just care about a simple bus stop/halt.
My proposal : keep simple scheme for simple stops, "bus_stop" for a bus stop, "tram_stop" for a tram stop. And switch to the PT scheme for complex/multimodal cases only.

highway=bus_stop - Mappen für den Renderer 21 days ago

+1 with Richard's comments.

I mapped several bus stops as a public transport (PT) user in the past but I stoped with the new tagging approved. See why:

The old scheme (ignore all optional/common tags like 'name', 'operator', 'ref', etc):
1 node where PT users are waiting + 1 tag ("highway=bus_stop")

The new scheme:
1 node where PT users are waiting + 2 tags ("public_transport=platform" + "bus=yes")
1 node where the vehicle itself stops + 2 tags ("public_transport=stop_position" + "bus=yes")
1 relation "type=public_transport" + "public_transport=stop_area"

The new scheme is nice for complex cases, especially stop areas mixing several types of transportation (e.g. tram+bus). But this is painfully over-complicated for the ~95% simple bus stops. How can you convince newcomers that 2 nodes, 1 relation and 6 tags is "better" than 1 node + 1 tag ?

OpenStreetMap Isn't All That Open, Let's Change That and Drop Share-Alike about 1 month ago

If the NYC government wanted to copy buildings that have changed from OpenStreetMap to the NYC building dataset they couldn't as their data needs to remain in the public domain.

In the other way, if OSM license becomes PD, it will not be be possible to import data sources others than PD themselves. And many public data in Europe still gets some licenses which are ODbL or compatible but not PD.

OpenStreetMap Isn't All That Open, Let's Change That and Drop Share-Alike about 1 month ago

Well, I'm not a lawyer but ... I agree with Bart about legal expertise. The argument saying "odbl is complicated, move to public domain" is true in first part but is not enough for promoting the second. OSM could be more widely used if we (or the foundation) could provide a better support to developers, projects or companies questions about the license (better than "I'm not a lawyer but ..").

Remove a spam user in French about 1 month ago

Reporting something on trac doesn't required power-users expertise. Between some hypothetical "easy reporting in one-click tool" and nothing, the "trac" tool already exists and the process of using it could be set-up quickly.

Remove a spam user in French about 1 month ago

Do we really need a new reporting system ? we could reuse the trac tool with a special category "spam"

Mapbox and the lake of attribution to OSM about 2 months ago

I checked again Mapbox site because we find at regular intervals online maps on the web with Mapbox/OSM in background layers but the OSM attribution is most of the time missing (see my previous blog). I think that Mapbox is not informing their potential users about the attribution. Otherwise I cannot explain why it is so often missing.

The wrong side of mapping transient events in OSM about 2 months ago

Perharps we should distinguish a permanent attribute (e.g. "access=no" because it's always 'no') to a temporary attribute ("access=no" because the road is repaired), not by using sub-tags like "start/end_date" which doesn't say which attribute/s is/are temporary, can be easily ignored by data consumers or never updated by the contributors but with a special namespace which would be automatically destroyed at a planned time (a bot). Something like "transient:access:=no". It should be all defined in a single tag, including its validity period (a time duration or a date), to avoid incomplete information (which could be the case if you split the details in 2 or more tags).
Advantage of this method is that permanent attributes are clearly separated from the transient ones. Data consumers could decide to take into account the transient details or not in their use. For instance, a car navi system could ignore the "transient:*" tags in OSM (or just the ones covered by the validity period) but a disaster map renderer could highlight all these "transient:" atributes in his rendering style.

The wrong side of mapping transient events in OSM about 2 months ago

disasters which by definition is transient

We don't map disasters but the consequences of disasters. A collapsed building is something more than "transient" I guess. But some tiles of a roof damaged by wind which can be quickly repaired is more "transient". Add an "end_date" tag doesn't help since no one is able to predict the future (for instance, damaged buildings can be just repaired or renovated or fully rebuilt from scratch). "start/end_date" should be reserved for dates in the past. My concern is more about access tags which have a possible long term impact on offline copies e.g. in small devices like navi systems. Also some contributors are just attracted by the project when "events" are widely present in the media. But once the rescue teams and TV reporters are gone, the armchair mappers are just leaving the "transient" data.

How to add batch watermarks to video? about 2 months ago


How to watermark an image by time settings? about 2 months ago


Ajouter des adresses avec JOSM 2 months ago

Oui, ça peut s'améliorer.

OSM mapping at regional or national scales: aiming at creating consolidated reference layers / La cartographie OSM à échelles régionales et nationales : l'objectif de créer des couches de référence consolidées 2 months ago

This attempt to map by "areas of interest" instead of "by zone" is not new. For a long time (and even today), it has been organized in the wiki itself, with tables where users can subscribe and later, with special icons showing the progress. Some hints:

Ajouter des adresses avec JOSM 2 months ago

Le problème des ter, bis, c'est qu'il y a aussi des rues avec des A, B, C. Il faudrait donc 3 commandes : une pour les numéros normaux, une pour les bis, ter et une pour les a, b, c. Le tout devrait aussi être configurable suivant les préférences des contributeurs : "25 bis" ou "25bis" (espace), "25 t" ou "25 ter" (raccourcis), "25 Bis", "25 bis" (majuscule). Bref, beaucoup d'options mais rien d'insurmontable.

Ajouter des adresses avec JOSM 2 months ago

Pour les bis, ter, etc,, j'ai déjà songé à le faire aussi dans le plugin (dont je suis l'auteur). Mais pour l'instant, avec l'outil addresses, tu peux facilement dupliquer le dernier numéro en appuyant sur la touche 'maj'. Après, il faut juste éditer le champ "addr:housenumber" et ajouter la/les lettre/s manquante/s. Il y a plein d'autres facilités : tu peux aussi cliquer sur un numéro déjà existant pour reprendre une numérotation en cours de route; tu peux aussi sauter des numéros en appuyant sur la touche 'ctrl'; tu peux aussi augmenter la valeur d'un numéro déjà présent en cliquant 'ctrl' sur l'addresse existante; etc. Faudrait que je fasse une video tutorial pour montrer tous les trucs...

nommer les rues de Brazzaville 2 months ago

Ben oui, mais là, non, Google Maps/Earth, c'est nos concurrents. Il ne faut pas venir ici pour demander à améliorer leur cartographie.
Par contre, OpenStreetMap (OSM) sera très certainement un jour ou l'autre bien plus célèbre et meilleur que Google Maps/Earth, Autant contribuer à OSM tout de suite et oublier Google :-)

nommer les rues de Brazzaville 2 months ago

Je suis étonné par le niveau de ces question de la part de quelqu'un qui vient de créer un site internet spécialement pour améliorer la carto de Brazzaville dans OSM. Ou bien, est-ce pour améliorer la carto de Google Maps/Earth ? Auquel cas cet appel à contribuer pour Google sur le site internet d'OpenStreetMap serait tout à fait indécent.

qu'appelez vous:" l'éditeur en ligne id "?

Aller sur, cliquer sur "Editer"; ça ouvre une application sur le navigateur internet qui permet de modifier les données géographiques d'OSM.

Si je complete un plan avec OpenStreetMap, les modifications apparaitront-elles dans Goole Earth et Google Maps?

Non. C'est deux projets totalement séparés. Google Earth et Google Maps, c'est des données qui appartiennent ou qui sont achetées par Google. C'est un projet commercial dont le but principal est de vendre de la publicité ciblée et de connaitre la vie privée des internautes.
OpenStreetMap, c'est des données géographiques libres et ouvertes. N'importe qui peut s'en servir et de nombreux projets externes, y compris commerciaux mais aussi des projets libres, en profitent tous les jours (à condition de respecter la licence libre ODBL).

En serat-il de mème avec les images aériennes Bing?

On a le droit d'utiliser les images aériennes de Bing pour éditer et tracer les données dans OpenStreetMap. Mais uniquement les images aériennes. On ne peut pas, par exemple, copier les noms de rues d'une carte Bing Maps. Lorsque tu utilises un éditeur OSM comme iD ou JOSM, on peut facilement charger les images aériennes de Bing comme fond d'écran et tracer les routes et les rues par dessus.


nommer les rues de Brazzaville 2 months ago

Effectivement, cette démarche est interdite pour OSM. Ni les noms des rues, ni leur tracé ne peuvent être pris sur Google Maps ou Google Earth. Si vous connaissez ces rues, faites-le directement avec l'éditeur en ligne iD ou n'importe quel autre éditeur, éventuellement en utilisant les images aériennes de Bing, qui nous avons le droit d'utiliser légalement. Je conseille fortement de ne pas suivre ce site internet.