On Tue, Nov 5, 2013 at 3:05 PM, Janko Mihelić <jan...@gmail.com> wrote:
> The problem is, some admin borders are supposed to be glued to roads or > rivers, and they change when the flow of a road or river changes. How do you > deal with that? Like in real world. In my country, when the road or the river is changing, the admin border may or may not change. And it can take time until the administration reacts. This depends on local/regional/national authorities who decide if the admin border has to be updated or not and when. So, if the river changes, move the river and keep the admin border at its current definition. This might require some "unglueing" nodes or ways. Admin boundaries are useful for geocoding and you ask devs to use a second source and conflate. And why we should stop with admin boundaries ? Post code is also useful and breakable. Should we move post codes to a third db ? etc... Another risk of keeping boundaries seperate is that OSM data might differ between the 2 db's, e.g. a road changing its ref at state border line. But what you can do is monitor the boundaries and repair them quickly. This is working in Europe. This is also working for coastlines. Check the QA tools monitoring borders on the wiki. Check this one for instance: http://layers.openstreetmap.fr/?zoom=6&lat=38.7541&lon=-78.4042&layers=B0000FFFFFFFFFFTFFFFFFFFFF The QA tool could also render the admin boundaries with different colors when their are modified or broken: http://layers.openstreetmap.fr/?zoom=9&lat=48.56074&lon=0.366&layers=B0000FFFFFFFFFFFFTFFFFFFFF Pieren _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
