The stats seem to be quite compatible with the numbers I generate now and then here http://qa.poole.ch/addresses/

While I typically tend to add the address to the building outline if there is no further information available, there is no doubt in my mind that the best solution is to add it to an entrance node on the building outline (forgetting about indoor mapping and multiple addresses in the same building for now).

Adding the address information to the building itself can and does lead to routing artifacts (being routed to the nearest street to the building and not to the nearest to the entrance) that can be avoided if the entrances are mapped and hold the address info.

Youo need to report this on the talk-au mailing list, it is rather unlikely that posting it here will have any effect.

Für “crowd sourced” Übersetzungen gibt es schon 2 Platforme: translatewiki (wird von der zentralen OSM infrastruktur gebraucht) und transifex (wird von iD, vsepucci und anderem verwendet).

The main issue is that for the most mainstream mobile device category (Android with roughly 80% global maket share) none, well at least none that I know of, of the surveying apps add the information. If I can get the code I added to osmtracker to work stable enough for general use I will make it available.

Well in reality these typically do measure the mangetic field on three axis, and are a bit more complicated than a conventional compass. But the net effect is that you can determine which direction you were pointing the phone camera. There are a couple of “ifs” like for example that you should naturally calibrate the sensors before you set off on a mapping tour and other things you may have to take in to account to get reasonable results, but in principle it works.

Die Fehler in Vechta sind mit hoher Wahrscheinlickeit von der Lizenzumstellung im letzen Jahr.

Ich hoffe du bist fleissig dabei die Schäden zu beheben :-).

The US is interesting because it shows that obviously (at least currently) imports are slower than simply collecting the addresses. But I suspect that large scale imports in the US are unavoidable.

Naturally I did the numbers too, but ~2 million addresses a year implies that we just started collecting them two years ago :-).

So yes, the current rate is too low for the Web 2.0 generation, but in all likelihood it is still increasing and we will just have to see where it levels out to the typical OSM linear growth mode.

There is ongoing work on your questions 2, 3 and 5.

As to question 1) searching for Café, Montreal will give you the desired results, and nominatim does AFAIK take the current viewbox in to account, however it is primarily an address search and not a POI locator.

A more general remark: while we are not very clear about it, OpenStreetMap.org is mainly about collecting and editing our data and not about providing services to end-users. On the other hand it is naturally the primary place our contributors and other end users go for such services.

Service development on the main site, adding a POI display and routing, is for the above reasons mainly thought as adding further tools for mappers and not as a google maps look-a-like. Deplyoment of such additional serives is not just dependent on more funds for hardware, we need volunteers to actually look after whatever we choose to add to the main site.

IMHO it is actually not such a common practice (legally naturally countries differ greatly in what actually has a number, the lot, the building or an entrance) and doesn’t seem to be documented osm.wiki/Addresses (not that that means very much).

In any case it would be rather expensive to change the queries so that such a node would get included simply by expanding the building polygon or similar (not to mention that it would generate tons of false negatives). It might be possible to support it if the node is actually on a fence polygon enclosing the house, which however doesn’t seem to be the case in your example.

Hi DaCor

You are correct it is a new feature that hasn’t been “announced” yet. There will be a further “has_address” layer too. Right now, i’m pre-rendering some of the tiles and am working on getting a coupel of technical issues resolved, as soon as that has happened I’ll write a blog post.

Simon

Thanks!

PS: could you change the data licence to ODbL?

What works reasonably well if you have building outlines already available in the OSM data (or have added them yourself before going out on a survey is to use vespucci to add house numbers directly to the buildings. I would suspect that this works just as well with the iOS based mobile editor.

@dcp

we actually have something over 300’000 contributors that have made edits (the numbers on alltogetherlost only count the last editors of objects). As to the 1’000’000 accounts, I believe reporting the number is quite valid (well at least in marketing terms). Particularly since we know that we have a substantial number of contributors that register an account, go away and come back a long time later and start editing.

I am myself such a case with a good year between creating the account and my first edit.

Ed

First question: not easy to answer and I don’t have a strong opionion on if it makes sense to duplicate the information.

Wrt site relations: currently that would seem to be very expensive to implement, I will have a look at it asap.

Simon

None of the “noname” tagging proposals was ever “accepted” so using the validate:* schema is just as valid as what I’m currently supporting. There is no reason I can’t support this tagging variant going forward and probably I will.

Wrt *_link: I have no strong feelings about this, and will probably move that to the “orange” might have a nome or might not category.

The problem with both “nosurface” and “nospeed” that that there is no global consensus if they are really needed. For example in Western Europe you would always assume surface asphalt unless specified otherwise, similar with speed limits where you would assume the national max speeds (for the road type and location) for roads that don’t have maxspeed tagged.

As the blog post says

red: major and minor roads, service with service=alley without name or ref tag

and it has been that way since day one.

And yes you are quite correct, there are masses of roads in France that should have name or ref tags and don’t.

That is a bit of a tricky question.

The main reason that the overlay supports unsigned and noname tags is to avoid mappers constantly resurveying the same roads (false positive suppression). If you live in an area that normaly doesn’t have street names the overlay doesn’t really make a lot of sense and insofar it is not necessary to weed out the false positives anyway.

Bitte in der Schweiz -keine- maxspeed Einträge machen, die Sache ist rechtlich klar und maxspeed voll redundant. Wir müssen ja nicht jeden Blödsinn unserer nördlichen Nachbarn mitmachen.