вс, 17 февр. 2019 г. в 15:18, Sergio Manzi <[email protected]>: > > That's as old as data processing: "*garbage in, garbage out*". Let's > fix the data.
Fixing data is a good thing but from utilization in production point of view the choice between unstable and stable data is not questioned. Competeness of data is even more important than its stability, and that unfortunately cannot be achieved that quickly. One can create a waterway relation with a length defined and then there may be a long run until all waterway segments are drawn properly to finally be able to compare it to an official length. You'll probably can find many different estimations about its length. Which > one are you going to choose? I would take one from any encyclopedia (subject to its license) and that figure will at least serve other mappers as a guidence when searching for incomplete or broken rivers. Cheers, Eugene вс, 17 февр. 2019 г. в 15:18, Sergio Manzi <[email protected]>: > On 2019-02-17 12:55, Eugene Podshivalov wrote: > > > It will work but only if the entire river from its spring to mouth is > drawn precisely enough, all relation roles are labeled properly and nobody > breaks the labeling by intent or mistake some day. > > That's as old as data processing: "*garbage in, garbage out*". Let's fix > the data. > > And yes, the river you pointed at is particularly complex and probably > geographers are pulling each other's hairs about computing its length. > You'll probably can find many different estimations about its length. Which > one are you going to choose? > > Sergio > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
