On Wed, 13 May 2009 15:54:36 +0100, Dave Stubbs <osm.l...@randomjunk.co.uk> wrote: >> The first thing I thought of when reading this is, to use a relation. >> 'Relations are not categories' applies to people making relations out of >> "all hotels" or "All hotels in London", doesn't really apply here. >> >> type=zone >> name=Dublin Centre >> maxspeed=20kph >> parking=no >> > > Where "zone" is a known geographic area? > A bounding way with tags like: > zone = restriction > maxspeed = 20kph > parking = no > > seems like the best way to do it to me if you don't want to just > replicate the tags on everything (and I can understand why you > wouldn't want to do that). > There's no software that'll pay attention to it atm, but then it's not > long ago that everything ignored route relations too. > > I really wouldn't recommend relations for specifying what things are > inside an area. It's a waste of two entire dimensions our dataset > happens to have.
I completely agree here. A polygon is a simpler, easier to evaluate, to tag and much, much less error-prone way to do this compared to a relation that has all ways in that area as members. Marcus _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
