Merci beaucoup.

Donc, quand quelqu'un a besoin d'une carte de Paris, je peux dire que tout les données sur OpenStreetMap (des 11 arondissements que vous avez revisez) sont correct mais peut-être pas 100% complète.

Merci pour votre travail, je connais des gens pour qui ça sera très utile.

It seems that mapquest implements their own api. so you can just go to http://open.maquest.com (this uses openstreetmap data), there you can right-click on the map or search by address to enter locations. You set the first and last location like you want and finally, check the "Allow MapQuest to re-order stops" checkbox under driving options.

It will take a while before you get your route. the Travelling Salesmen problem is an NP-complete problem. So it asks a lot of work, and the mapquest site is optimised to update all the time, not to do big calculations. So wait a bit before you force the site.

I do not know if the mapquest site has an export feature or what export format you should like. But it is at least as good as what you got.

I do not know your technical skills, but mapquest has an api for this. You call e.g.

http://open.mapquestapi.com/directions/v0/optimizedroute?json={locations:[{latLng:{lat:51.524410144966154,lng:-0.12989273652335526}},{latLng:{lat:51.54495915136182,lng:-0.16518885449221493}},{latLng:{lat:51.52061842826141,lng:-0.1495479641837033}},{latLng:{lat:51.52850609658769,lng:-0.20170525707760403}}]}

and as response, you get a JSON file, including a field like

"locationSequence":[0,2,1,3]

which means that the best order of locations is 0-2-1-3, it will always begin with the first (0) and end with the last.

It also contains a route description.

I do not know if there is some website with an easy GUI that implemnts this feature.

Pieren, j'ai une question pour vous: quand vous revisez des arrondissements, quesque vous revisez alors? Seulement les addresses? Ou aussi les restaurants et autre POI?

Je le demande parceque, il-y-a quelque temps, j'ai été en Paris, dans une hôtelle dans le rue des deux gares. Et l'hôtelle n'était pas sur la carte. Il s'agit de l'hôtelle d'Amiens. Maintenant, je l'ai ajouté, mais je le trouve bizarre que vous ne l'avez vas vu. C'est la seule hôtelle que je connus en Paris.

Voulez vous verifier que c'est vraie ce-que je dis? Peut-être l'hôtelle n'existe plus et vous avez raison.

http://www.hoteldamiens.com/

osm.org/browse/node/1289533540

Ton travail en Paris est vraiement fantastique. Je veux vivre dans une region si dévellopé mais c'est pas le cas pour moi.

First: sorry to answer in English, but my German is quite bad. I can read German, so you can just write German if you want, but if I would write it, it would be unreadable for you.

Second: You mean a tool to change a route relation (like this osm.org/browse/relation/1447152 ) to some GPS format? Well, GPS formats can differ quite a bit, so I think you would need to say the format. If GPX is a good format, you can look at this page: osm.wiki/Relations/Relations_to_GPX

For the printed maps, maybe you can get a look at this tool: osm.wiki/Hikingbook.pl It's a route-to-book processor. I think you need Linux to run it. You could also ask Gary68 to add a export-to-gpx feature to its tool. It seems like a logical addition and in fact not much work if you have the other script.

I do not know your technical level, but if you want to try it, setting up a virtual Linux box is quite easy and afterwards, the installation of the tools will be easy too. Contact me if you want to have some other tips about installing.

Been there. The positive side is that you learn to save very quickly.

@ThePromenader: The best solution to the problems you give would be a good preprocessor. One standard preprocessor that makes all data consistent.

That way, users can just input data the way they want and apps just need to know one tagging schema per feature.

The preprocessor could even be run on the OSM servers so that users of the data can download consistent data without problems.

Is het maar nu verschoven?

Dan is het waarschijnlijk een ongeluk. In editors als JOSM kan je een hele selectie in een keer verschuiven. Stel dus dat een gebruiker het station en de sporen geselecteerd had om een tag toe te voegen, dan kan die per ongeluk alles verschuiven.

Als je het niet maar ziet in Potlatch, dan heeft de gebruiker het waarschijnlijk al verbeterd, maar is de verbetering nog niet in de kaarten opgenomen (=gerendered). Het duurt even voor aanpassingen gerendered worden.

@wieland: removing things will not help, it will make the work harder for a possible fork.
This just popped in my mind: if the license is that important, why not allow different licenses in the database? If an OSM'er only agrees to CC-BY-SA or to ODBL, he can only edit a node/way/relation that already has those license, if he agrees to both, a new way is licensed under both licences until another user edits it (then it becomes the license that user has agreed to).

A user of the data could choose:
* only use CC-BY-SA data and comply to that license
* only use ODBL data and comply to that license
* use all OSM data and comply to both licenses

From a technical point of view, this causes some overhead (but all the ODBL tests they do now also cause overhead) and I think it is possible from a legal point of view.

If they are going to delete all non-ODBL data, I am sure that there will be a fork of OSM.

Off coarse it's not optimal, a fork is never good, but that way we will see what users think is the best. And if OSM can survive as is, this or its fork will also survive.

For the record: I have agreed to the new terms (I don't really care about the license) but I don't know if it's a goog idea to switch.

The advanced tagging schema for buildings is the building="building typology" tag.

So in your case, the outline of the building should be tagged

building=apartments

The tag building=residential is not so good because it doesn't describe how the building looks like. Is it a house? An apartment? A hut? For the most used tags, see the wiki: osm.wiki/Key:building

About the other tags (addr:xxx, building:levels, landuse ...), I agree with LivingWithDragons and Sundance.

But as always in OSM, every mapper does what he wants.

Ok, dan is alles in orde. Het is enkel omdat je een "gedrukte kaart" vermeldde dat ik wat argwaan kreeg. Auteursrecht is bij ons heel moeilijk om te controleren dus moeten we zorgen dat de gebruikers goed geïnformeerd zijn.

Groeten,
Sander

for ways on which both pedestrians and bicycles are allowed (and expected) to drive, you can use highway=path

Welkom bij OSM,

Het is goed dat er nieuwe gebruikers komen. Gebruik je potlatch 1 of 2? want er is een groot verschil in de interface.

Mag ik er nog eens op wijzen dat je geen info van beschermde kaarten mag halen (zoals google maps of gedrukte kaarten) om op OSM te zetten.

Happy mapping,
Sander

I always read those CU's and I really thank you guys who realise this.

PS !i!, how is it going with your video mapping things? No pressure, just a question.

And what about this one?

http://flandrensisgov.webs.com/

(you may need some translation service if you can't read Dutch)

welcome to osm, happy mapping

De pdf geeft inderdaad een server timout error. ik ben nu aan het proberen om het als svg te downloaden en het dan te converteren. Dat lijkt momenteel nog te lukken.

From what I see on OSM, there are tensions on the high level (e.g. defining standards or rendering the map). I don't even want to read the Public Trasport mailing list because of all the little fights.

But on the low level: the mapping itself, I haven't seen any dispute. I haven't seen edit wars like in wikipedia.

So as long as you don't bother with the mailing lists, you have an OSM life without tension.

welcome to OSM