I think you are misinterpreting the one feature "rule". It's about trying to avoid situations where there are two versions of the same thing (eg an area-which-can-be-resolved-to-a-point and a node), not situations where there are multiple parts to a single whole.
The Danube river is perfectly adequately made whole by looking for name:en=Danube. Get the computer to do the work, not mappers. On Tue, Jan 29, 2013 at 11:01 AM, Janko Mihelić <[email protected]> wrote: > At the moment the "no big relations" and "no big areas" rules go directly > against the "one feature in osm for one real world feature". I think those > first two rules should be solved with more code. Maybe get a feature to osm > api to crop the gigantic areas and other relations when downloading, > defined by a bbox. > > Until then we have to cut them up and ignore the "one feature" rule. > > Janko > > _______________________________________________ > Tagging mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/tagging > >
_______________________________________________ Tagging mailing list [email protected] http://lists.openstreetmap.org/listinfo/tagging
