Re: [OSM-talk-be] Overdreven gedetailleerde mapping ? Exaggerated detailed mapping?

2019-11-09 Thread Marc Gemis
> And to be honest: I don't think OSM will really surpass commercial maps for > car navigation, because up to date traffic information is part of that. > I don't see how volunteers can arrange that quickly. In some countries (including Belgium) traffic information from the government is open

Re: [OSM-talk-be] Overdreven gedetailleerde mapping ? Exaggerated detailed mapping?

2019-11-09 Thread marc marc
If it'sn't a place=locality, but only a cadastral name with known boundary, a boundary=cadastral + name is better the problem is that it is often places said that the elders used without precise limits and it is then taken up by the land registry and notaries, for example to locate a famrland Le

Re: [OSM-talk-be] Overdreven gedetailleerde mapping ? Exaggerated detailed mapping?

2019-11-09 Thread Karel Adams
Mij lijkt dit enkel een kwestie van "minder-dan-perfecte" tagging: in plaats van "name=HoutchiPloutch" hoort het voor mij te zijn "name:land_register=..." of iets dergelijks.De tag "place=locality" lijkt mij trouwens ook aanvechtbaar. A mon avis, il suffit d'appliquer un tag plus correcte ou

Re: [OSM-talk-be] Overdreven gedetailleerde mapping ? Exaggerated detailed mapping?

2019-11-09 Thread Chris Van Bael
Hi Eebie, you have a point that indeed those maps are confusing the way OSM renders them at the site. But with mapping: there is a difference between what is in the database and what is displayed. If what you see is not clear, then perhaps the renderer should be adapted. As I said in an earlier

Re: [OSM-talk-be] Overdreven gedetailleerde mapping ? Exaggerated detailed mapping?

2019-11-08 Thread EeBie
I have a problem with a kind of exaggerated detailed mapping that makes the map difficult to read and use. That is by giving fields and meadows their cadastral name by mapping them as place=locality and name=*. You can find this in some parts of Wallonie as