On Tue, Nov 10, 2009 at 5:46 PM, andrzej zaborowski <[email protected]> wrote: > Hi, > > 2009/11/10 Marcus Wolschon <[email protected]>: >> <?xml version='1.0' encoding='UTF-8'?> >> <osmChange version="0.6" generator="Osmosis 0.31.2"> >> <modify> >> <relation id="168084" version="8" timestamp="2009-10-10T20:59:02Z" >> uid="2680" user="xylome" changeset="2807996"> >> <member type="way" ref="37280470" role="outer"/> >> <member type="way" ref="37277113" role="outer"/> >> <member type="way" ref="37277401" role="outer"/> >> <member type="way" ref="37365654" role="outer"/> >> <member type="way" ref="29413278" role="outer"/> >> <member type="way" ref="29413320" role="outer"/> >> <tag k="FIXME" v="only guessed"/> >> <tag k="admin_level" v="8"/> >> <tag k="boundary" v="administrative"/> >> <tag k="name" v="Mössingen"/> >> <tag k="type" v="multipolygon"/> >> <tag k="TMC:cid_58:tabcd_1:LCLversion " v="8.00"/> >> <tag k="TMC:cid_58:tabcd_1:LocationCode" v="42035"/> >> </relation> > > Very cool results if this is automatic matching.
It is. > Out of curiosity why are those relations type multiploygon instead of > type boundary? Why not? Most software can not handle having multiple "type"-tags, so why should the author have tagged it as both? I have long since given up to care. Marcus _______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
