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
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging

Reply via email to