On 27.04.2012 10:12, Pieren wrote: > You have to know anyway if your feature can be either a closed way or > an area and therefore need some special handling in your apps.
Unfortunately, yes. I wish we already had a proper area primitive so this whole discussion would be obsolete. > The question is then more to consider certain features as "area" or > "closed way" by default. On this point, I'm always standing on the > contributors side and wont ask them to add an unnecessary tag for > 99.99% of the cases. Having to type "area=yes" less frequently is in the contributors' interest, sure. But having simple rules for defaults is also in the contributors' interest. Right now, we already have to distinguish three types of tags: * always area * always way * way unless area=yes is present. I simply do not think that the possibility to decrease of the number of tags is worth introducing "area unless area=no is present" in addition to these. Particularly because whether area or way is the default would depend on what is assumed to be more likely in reality. And people might easily have different assumptions here, making that kind of default non-obvious. Tobias _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
