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

if you look to the taginfo stats about the tag addr:housenumber, you will see that it has a nice system.

• it starts with 1, and higher numbers are used less and less
• round numbers (10,20,30,…) are used more than others
• the number 13 is used a lot less

it also struck me when i discovered it.

The only thing that really bothers me is the classification. Why have a motorway or motorway_link between a secondary and tertiary road?

A way with highway=steps is not really different from any other kind of highway.

The only difference are the implied access values.

highway=motorway has implied access as

• agricultural=no

• vehicle=yes

• foot=no

• etc (depending on your country laws)

A highway=footway has implied access tags as

• vehicle=no

• horse=no

• foot=yes

• wheelchair=yes

• etc (again depending on your country)

and higway=steps have access tags as

• foot=yes

• vehicle=no

• wheelchair=no

So those are the only differences between footways and steps.

I agree with your views on JOSM, I only recommend it to users who are used to OSM, but need more power, or to users who are used to gis.

And I never considered the source tag as important. I don’t add it. Bing doesn’t obligate us to add it, and if it’s my own work, I’m not obligated either.

How did you map those steps? If they are just lines, you can just connect them as they were a footpath. If they are areas, I don’t think there is a default yet.

btw, to edit custom tags in Potlatch, you need to go in advanced mode.

When I create tracklogs and pictures via the OSMtracker app, and I import the track and the pictures in JOSM, I always see two buttons.

One is from the EXIF info, another is a link created by the GPX track. Those locations are always a bit off.

So there are certainly more phones that have the problem. But do we really care? We normally don’t stand on the place of the feature itself to take a picture. We normally take a picture from a further distance.

Proper,

je kan je resultatie hier zien: http://openwandelkaart.nl/?zoom=14&lat=51.35458&lon=3.31758&layers=00BFFFTFF

Ah, ok.

Ik dacht dat het om een hernoeming ging. In Ieper zijn een 100-tal straten hernoemd vorig jaar. Maar de meeste namen zijn tamelijk triviaal. Zoals van “Arthur Merghlinkstraat” naar “Merghlinkstraat”.

Soms zijn er wel conflicten ontstaan (twee personen met dezelfde familienaam), dan zijn er nieuwe namen uitgevonden.

Bedankt voor je bijdragen.

Bussen mappen vind ik iets heel duur (ik heb geen abo) en ook tijd rovend. Ik heb dan ook nog maar enkele routes gedaan. Maar het is goed die op de kaart te zien.

Groeten, Sander

C’est presque juste, mais tu as oublié une way: osm.org/browse/way/148880252

Si vous voulez supprimer ce way, c’est complètement juste.

Et bienvenue sur OSM

Vergeet niet de oude namen als “old_name” te houden. Het kan handig zijn voor mensen die nog een adres zoeken via de oude naam.

Definately export your tracks to GPX, and upload them to OpenStreetMap: osm.org/user/whison/traces

But the most important thing is to remember interesting stuff while you drive by: * how is this street called, * there is a pub at that corner * A bakery over there * …

And when you get home, you can place those on the map.

If almost everything is in place, you should’t import it. Instead, rendering a layer that can be traced in editors might be better.

That way, help is provided to the local mappers, while nothing gets broken.

I agree with !i!. Our reputation is not in danger. Even in Germany they are complaining about the maps, while everyone knows that the German maps are almost perfect.

I also agree with !i! that we do have lost some other rights though, such as exporting the data, or even checking if we are allowed to use the data. Also, if data gets mixed, everything should be provided under ODBL. But there is no way we are able to check that this happens. Apple can be mixing data without us knowing.

@dietrdreist, you shoud know that mentioning “copyright” does not change anything. Everything is always considered as copyrighted. Not mentioning “copyright” doesn’t make it PD. But on the other side, not linking to our terms makes it private data, which infringes the license on the other side. Unless you assume that every user is smart enough to find the correct license when he only has the name of our project. So that’s debatable.

Probably I don’t get it, but here, irrigation sprinklers are something that’s easy movable, so farmers can use it on the fields where they need it.

If you do make it into a proposal, or document it, please make it very clear that it’s only for fixed stuff. Nothing movable.

If you want to create a proposal, you can read this page: osm.wiki/Proposal A proposal will make your tag better known, and you get a bit of “official support” from it.

If you don’t have the time for a proposal, please do make a wiki page with a “documentation of use”. Make a page and say “I use this tag for A and B, but it isn’t good for C blablabla”.

Welcome to OSM, nice to see (not so) new Belgians.

Regarding the connection of nodes between fiels, I do agree with your views.

Streets and streams have a certain width, big enough to mention. So the ways representing them should represent the middle line, while the field already stop at the border of the way, not on the middle line.

For fences and hedges, it’s different, as they normally have a very small width, they exactly represent the boundary of the field, so they can be mapped on the end nodes.

1. I guess American addresses are difficult with all those numbers. Normally, our streets don’t have numbers. Apart from that, it would only work if someone already put that address on OSM. As we can’t use other data, there’s no way we can know where that address is if not someone before you put it there.

2. JOSM is primarily an offline program. You also download your data for offline use, so it works faster.

3. For your last question, tags don’t “work”. It’s not because it’s not shown on the map, or even in the renderer, that it isn’t correct.

The office key isn’t directly shown on the website, but it is included in search, and perhaps in other maps based on this data.

If you’re sure you use the correct tag (according to the wiki), and something isn’t shown on the map, it’s the fault of the one who compiles the maps (or intentional behaviour to not clutter the map).

If you can’t find a correct tag in the wiki, you can create your own and document it on the wiki.

You (as mapper) are always correct if you give the tags according to the real world.