What you say makes perfect sense. But you got my situation wrong. When admin_level=6 *IS* specified on the way it doesn't render until z11. When it is only on the relation but NOT on the way then it renders at z9.
Toby On Wed, Feb 9, 2011 at 8:08 PM, Daniel Sabo <daniels...@gmail.com> wrote: > It's not really a bug, if you have the following setup: > > Member way: > boundary = administrative > > Relation: > boundary = administrative > admin_level = 6 > > What you're telling mapnik is that there are two boundaries, one is > admin_level 6, the other is admin_level undefined. The admin 6 one will > render at z11 or closer, the undefined one renders at z9 to z11. > > To map the boundary as a relation you should have: > > Member way: > no boundary tags (that includes the boundary name) > > Relation: > boundary = administrative > admin_level = 6 > name = Something > > Boundary relations are just specialized multipolygons once they reach the > renderer so all the rules here apply: > http://wiki.openstreetmap.org/wiki/Relation:multipolygon#Usage > > - Daniel > > On Feb 9, 2011, at 11:27 AM, Toby Murray wrote: > >> Well like I said, leaving the admin_level=6 on the ways is indeed >> tagging for the renderer. However isn't there still a mapnik bug here >> no matter how you look at it? Shouldn't an admin_level=6 boundary be >> rendered at the same zoom level whether it is mapped as a relation or >> as a way? >> >> Toby >> >> _______________________________________________ >> talk mailing list >> talk@openstreetmap.org >> http://lists.openstreetmap.org/listinfo/talk > > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk > _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
