See osm.org/user/jgpacker/diary/28266 for a related discussion.

@imagic: 2 comments > [..] Why do we need a status for a key? Why is it necessary to get a glowing-green “Approved” on a wiki page? Why is “Rejected” hellish-red? Those details support the impression, that only good, green, approved tags should be used, that they are official tags. This is not true and we should start with removing the status from the wiki. [..]

I disagree with removing status from the wiki, however they could be better defined. The color was added recently by a user. Feel free to remove it if you believe it shouldn’t be there.

[..] The usage numbers from taginfo are all we need.

Not true. Often the usage numbers come from an import, and even from bad imports (i.e. undiscussed/unskilful).

Bom trabalho!

Seria interessante você utilizar o JOSM para este tipo de tarefa, pois ele tem uma funcionalidade para refinar a geometria de linhas e polígonos que acelera muito esse detalhamento.

Veja uma descrição desta funcionalidade na seguinte ligação: https://josm.openstreetmap.de/wiki/Help/Action/ImproveWayAccuracy (em inglês)

Zarl, you indeed misunderstood Ivaldo. He didn’t touch these motorway links.

The import approval process indeed can be demanding, but that’s because it’s so easy to make a bad import and so hard to fix it. It is far from being silly, and in my experience almost all imports that skip the approval process are bad imports (mainly because they tend to be made by an inexperienced user).

The wiki doesn’t match reality.

Can you give some examples ? I’m not saying it does match, but we can always fix the problems.

There doesn’t seem to be a process for ever tidying the wiki, [..]

I can say there are always a number of users regularly improving the wiki. A wiki is never complete, and is always in need of more helping hands (especially for non-english languages).

It can be common in the wiki to describe both the current state of tagging and the community’s consensus. Nothing wrong with that.

Ótimo trabalho!

d1g, Taginfo already gives links to wiki pages in the “Wiki” tab. If a user want to know more about a tag, he can go to the wiki page through there.

Sidewalk as a separate way can be quite controversial in OSM, because it’s not backwards-compatible with the way data is used and adds a considerable degree of complexity with little to no advantage.

Wheelchair routing could be described simply by tagging how usable a path is instead of mapping every inch of the road.

Indeed! I share the same feeling.

Só um pequeno detalhe, hoje em dia o mapa do IBGE já vem embutido no JOSM, isto é, não é preciso adicioná-lo. :-)

Ivaldo, é preciso fazer upload da imagem em outro site, como o imgur ou imageshack, e então colocar o link como indica a referência do markdown.

Eitz, sempre é bacana ver conteúdo em português. Como outro catarinense, te dou as boas vindas ao OSM!

Then this should definitely be reported to the @talk mailing list.

Maybe there should be a policy that no note should be created automatically.

I’m afraid what Tordanik said is true. Adding such links on the wiki invites users to make mass edits.

In fact, there is an user that already did a little of this. See [1] and [2]. I happen to know this user. He is known in the brazilian community because of some of his poor decisions.

He changed amenity=sport_centre to amenity=sports_centre and leisure=grass to landuse=grass. The former seems trivial, however the latter may be worth discussing.

1. osm.org/changeset/24520020
2. osm.org/changeset/24520020

NZGraham, the underscore didn’t appear because there was a stray space character after the equals sign on the title of the page. I fixed it just now, so it should be working (I also made some quick changes on the wiki page).

Usually the values of the shop key don’t need to be documented, though I don’t think it’s bad to document them either.

Depending on the Wiki and page that might result in a lot of “spam” and users complaining.

Yes, but can’t the OSM wiki mantainers make it a default setting? I think it would help users. I struggled a bit in the beginning until I was sure I wasn’t getting notification from pages on my watchlist and how to enable them.

You can also set the wiki to notify you by email on your preferences page, turning on the checkbox “Email me when a page or file on my watchlist is changed”.

I wish this was a default setting. 😐

+1

I also think it would be great if people from countries that made imports from government data could document some of these external database tags. At the very least I think this would be helpful to beginners of these countries.

As an example of this, I recently documented the key IBGE:GEOCODIGO, present on Brazil. As can be seen on the wiki page, I simply documented it in portuguese (brazil’s official language), and created an page in english with only the following templates {{KeyDescription}} (giving a bare bones description of the tag) and {{Translate from Portuguese}} (indicating the content of this page can be seen in the portuguese version of this page). I believe this can make the job a lot easier, since people don’t really need to translate the page to english, after all the main readers would be from that country, and others could easily use some site to automatically translate that page.

Isso, foi manual. Fiz capturas de tela antes e depois de mandar o conjunto de alterações, abri as duas imagens no GIMP como camadas separadas e exportei a imagem como GIF.

Uma dica que posso dar é tirar a captura de tela em alguns zooms diferentes, e copiar o endereço dos trechos que você tirou captura de tela pra poder tirar outra captura de tela exatamente no mesmo lugar (por exemplo o endereço http://www.openstreetmap.org/#map=18/-26.22443/-48.80123).

I think it would be enough if there just was some checkbox “show/download administrative boundaries” either on your profile or in the editors, that is disabled by default and is semi hidden in some sub menu.

I think that’s a great suggestion. But what can be done when the administrative boundary is made with rivers and/or streets?