Bonjour Legueux,

bienvenue chez OSM. OSM est un projet cartographique complètement différent. Dans OSM, ce sont les utilisateurs qui créent la carte. Si vous allez voir la carte, vous pouvez appuyer “modifier” (ou quelque-chose comparable, dépendant de votre langue).

Dans la mode de modification, vous pouvez changez tout que vous voulez. Vous pouvez dessiner des nouvelles rues, vous pouvez sélecter une rue, et donner un nom. Ou tant d’autre choses.

Voir la guide complète ici: osm.wiki/FR:Beginners%27_guide

Merci en avant pour nous aider, Sander

Spam spam eggs and spam

I agree with you, Robert.

It doesn’t only depend on the things added, but also on the resources available.

I remember, when we had no images available, I mapped a single building by doing GPS tracing while walking straight towards the building corners. This was multiple days work. Now, I can add hundreds of buildings per day. But buildings without extra information (like address) don’t hold much value.

Now, there are still regions without good images, so where building are a lot of work and should be valued highly, but in a lot of areas, this isn’t the case anymore.

So even if you would succeed to award more points to one feature than to an other (which would be a lot of work), it would have to change per region.

I think the tools we have are good. They’re not too easy to find, so people who can’t be bothered with gamification don’t get them “in their face”. But for people who really want it, they can look up the stats.

There’s an OSM fight: http://osmfight.neis-one.org/ Or personal statistics (which can be compared): http://www.hdyc.neis-one.org/ In the stats, you can also see the biggest editors of the day, week or month: osm.org/stats/data_stats.html

So there is a bit of gamification, but we shouldn’t advertise it too much. As it’s not our meaning to produce as much changes as possible (with armchair mapping, you can improve data quickly and cause a lot of changes), but it’s our aim to make sure people go out and map what they see outside. Data that can’t be simply derived from satellite images, and that can’t be found on other maps.

The chat could maybe be handy, but I think that the internal messaging system is good enough as it is now. In any way, I never work via the OSM site anymore, so you would have to include the chat in all editors available, I don’t think this is possible.

Welcome.

How were you using the data? Via an app or so?

Mapping isn’t that hard. If you’re dedicated, you can easily do a place of 5000 inhabitants on your own (if they are a bit concentrated that is).

My village is bigger than the island you showed, and I did it mostly on my own (even in the days without aerial images). Detailed to every single address.

You should first map the most important things: roads, paths and POI. Landuse looks nice. But satellite images offer the same filling of land.

With those roads, paths and POI, the names are also very important. Names make sure people are able to find stuff on the map.

Also, if you want to become a power editor, I suggest you look into the power tools. JOSM is a bit more complicated than Potlatch, but it works so much faster.

I wish you good luck. And be sure to promote OSM, even if not for your own island. It could still be handy when you want to travel somewhere ;)

alles ist schon besser als vor der Lizenzwechsel. Es dauerte weniger als einen Monat

I haven’t mapped any sidewalks (to avoid the problems mentioned here), but I agree that pedestrian routing should happen over surfaces rather than lines.

So what we should do is, instead of mapping the footway paths, we should map the footway surfaces, the road surfaces, and the barriers between them (buildings, curbs, walls …). So that routing software knows, if they are connected, and that connection isn’t a major barrier, you can go from the one to the other surface.

I did have to “invent” a footway once. A walking route went through a meadow, but there wasn’t a path there (just a few poles showing the way). But to add it to the relation, I needed a way. In fact, the entire meadow (and every meadow) should be routable for pedestrians (but with limited access restrictions). Given that the barriers (such as fences) are also mapped.

Of course, this needs extra data, and extra calculation power, but according to the Moore’s law, this can’t be too much of a problem.

The normal river boundaries is the line of “average maximum water height”. Comparable to the shore line on the sea.

So we don’t tag exceptional floods, but if water comes regularly to a certain point, then the river boundary is there.

Of course, regularly can be quite ambiguous, but let’s say, if you don’t expect it to be there on a normal day, it doesn’t regularly get there.

Of course, you can tag fields and wetlands through the river. There’s no problem with that. See this as example: osm.org/?lat=51.5225&lon=0.7632&zoom=13&layers=M

Bienvenue sur OSM. Merci pour votre contributions.

Si vous voulez plus de contact avec des membres Belges, n’oublier pas de vous inscrire sur le mailing list: osm.wiki/MailingLists#Country-Specific_Lists:

Les discussions sont normalement en anglais (comme compromis), mais en demande, on peut avoir des discussions dans des autres langues.

Notre wiki est aussi en anglais: osm.wiki/Belgium

What’s on our menu today?

https://www.youtube.com/watch?v=anwy2MPT5RE

I agree completely with Vclaw. It was also my idea when reading this.

Housenumbers are most important in search tools, and this approach will work with all search tools.

Oh, that way. strange coincidence. I hoped someone else would translate it. but today I became inpatient and went to look up the translation myself. To find out it has been translated but not visible on the main page.

The problem is that OsmAnd doesn’t have servers to rely on. All calculation has to happen on the device. Unless you use an online routing service. In that case, you will be able to calculate longer routes.

The “turn back” issue is also known. To save calculation, a part of the original route is kept. So if you deviate from that route, OsmAnd will try to find a new route towards that route, and not directly towards the end point.

But long distance trips will be a problem until phones get a lot faster I think.

Well, all code we use on the main site is open source. So even if some project is only controlled by one person, he can’t withdraw his work.

Of course, it would be a huge task to replace such an “indespensible person”, but it doesn’t need to happen immediately.

But you are right that there aren’t many indispensable people left. I also wouldn’t count Steve as indispensible. As far as I know, he has little influence on media (at least in German articles, it’s always one of the Germans being interviewed), and the SOTM talks are easy to replace.

I also don’t agree we’re not doing well with the addresses. Yesterday, I needed to search an address of a friend, so we could work together on a project. I just needed to give in the address in OsmAnd, and I was immediately send to the right house.

And no, I haven’t added that address myself. I have never been there.

A year ago, this wouldn’t be possible, but we’re moving fast.

I’d say, if you don’t like what Steve Coast is saying, just ignore him. It’s not like he’s that important.

Welcome to OSM.

As a GIS professional, you may feel more joy in using the JOSM editor.

Maybe one remark, try to avoid abbreviated names, it’s easy for software to abbreviate a name (Street -> St) but it’s hard to do the opposite (St -> Street/Saint/Strasse/???). osm.wiki/Names#Abbreviation_.28don.27t_do_it.29

You can always include a short_name tag if you would like to do the abbreviation manually.

Also, please make sure you are allowed to do your transferring (you’re responsible).

But thank you for your contributions.

I have got a lot of funny looks.

Anyway, regarding your question about rendering maps. You can look into tilemill. It’s open source, so you can install it on your own computer.

You can import OSM data to a gis database (yes, setting this up takes a while), and tilemill will help you render it.

If you try it, try setting it up with a small file first. So you don’t sit there importing the file, to notice that something went wrong.

http://mapbox.com/tilemill/

As you do not have areal images in your regions, you will have to use the old GPS methods (I’ve used that too, but it’s a while ago).

You go out with a GPS that’s able to save a track log, on smartphones, there are usually track log apps you can install (like osmtracker for Android).

When you come home, you upload the GPX track to OpenStreetMap (see here: osm.org/traces ) and you can start editing.

You should see a blue line where your GPS tracked you. If you remember where you walked, you can draw streets over the blue line, and give them the right names etc.

To get a better explanation, look at the beginners guide: osm.wiki/Beginners%27_guide

I’m also in doubt about this. Usually, when tools want to reverse geocode (transform a written address into coordinates), they have to bind houses with the streets and cities.

For binding to cities or countries, this is no problem if there are boundaries. It’s not so difficult to programatically check if a house is inside our outised a boundary. So I never add that info (it’s just easier for me, and it avoids typos).

For binding to streets, the address information on the wiki states the following:

• if addr:street=* is given, bind to the closest street with that name

• if the house is member of an associatedStreet relation, bind the house to the closest street in the same relation

• else: bind the house to the closest street with a name.

But, this is only in theory. I’ve meanwhile noticed that it’s a lot easier (as a data user), to not use the associatedStreet relations. If you use those relations, you still need to select the correct part of the road, and you have extra checks to preform such as member checks etc. If you also know that working with relations is very slow (certainly with big data sets), you will see that only the very well developed tools (such as Nominatim) use it.

The only advantage I still see in creating an associatedStreet relation is for the mapper. It makes it very easy to select all houses of the same street, to apply the same tags to it (such as the streetname), and to check if the right houses are present. Although it can be done via the JOSM search function too, it’s a bit easier for us. But you should only add it if it seems useful for you.

Summary: always include an addr:street, and only use associatedStreet relations if you think it’s useful.

2.

The “no exit” tag is only useful for other mappers, so they know I did finish that way, and it’s not connected in reality. It also makes sure that the quality assurance tools don’t complain about unconnected ways. I added it to the end note, precisely because it’s rendered in JOSM, which means mappers can see it, and so it’s more useful.

I know how difficult housenumbers are. I’m currently doing almost nothing but housenumber mapping.

One of the things I did before, just because I couldn’t find the house myself on any map, was this: osm.org/?lat=50.963833&lon=3.109209&zoom=18&layers=M

If you now search for the “Biezenhof D10, Roeselare”, Nominatim will point to the right house. But Google will fail at it miserably.

Btw, sorry for not giving the link previously, I was on my phone. Here it is: http://taginfo.openstreetmap.org/keys/?key=addr:housenumber#values