Non way element X in multipolygon Y
I get a lot of warnings of the form "Non way element X in multipolygon Y" (e.g. Non way element 247735163 in multipolygon 339577) in which X is a correct "admin_centre" node of a boundary multipolygon relation. Would it be possible to detect "admin_centre" tag when the MP is processed to avoid this warnings in the log?
I get a lot of warnings of the form "Non way element X in multipolygon Y" (e.g. Non way element 247735163 in multipolygon 339577) in which X is a correct "admin_centre" node of a boundary multipolygon relation. Would it be possible to detect "admin_centre" tag when the MP is processed to avoid this warnings in the log?
Of course it is possible. Would it be ok (for you and other) if I lower the log level to info? I don't want to start hardcoding a list of complex exceptions in which cases it is ok to have non way elements in a multipolygon. WanMil
El 25/04/11 18:57, WanMil escribió:
I get a lot of warnings of the form "Non way element X in multipolygon Y" (e.g. Non way element 247735163 in multipolygon 339577) in which X is a correct "admin_centre" node of a boundary multipolygon relation. Would it be possible to detect "admin_centre" tag when the MP is processed to avoid this warnings in the log? Of course it is possible. Would it be ok (for you and other) if I lower the log level to info? I don't want to start hardcoding a list of complex exceptions in which cases it is ok to have non way elements in a multipolygon. As in other cases the warning is correct you can leave it as it is now. I will just add them to my logging.ignore until I have finish correcting all other multipolygon errors detected by mkgmap.
On 26/04/2011 10:19, Carlos Dávila wrote:
El 25/04/11 18:57, WanMil escribió:
I get a lot of warnings of the form "Non way element X in multipolygon
Y" (e.g. Non way element 247735163 in multipolygon 339577) in which X is a correct "admin_centre" node of a boundary multipolygon relation. Would it be possible to detect "admin_centre" tag when the MP is processed to avoid this warnings in the log? Of course it is possible. Would it be ok (for you and other) if I lower the log level to info? I don't want to start hardcoding a list of complex exceptions in which cases it is ok to have non way elements in a multipolygon. As in other cases the warning is correct you can leave it as it is now. I will just add them to my logging.ignore until I have finish correcting all other multipolygon errors detected by mkgmap.
Why is the warning correct? The wiki says that a boundary multipolygon can contain a node tagged admin_centre. Isn't this mkgmap warning a false positive? -- Charlie
Charlie Ferrero schrieb am 28.04.2011 09:46:
Why is the warning correct? The wiki says that a boundary multipolygon can contain a node tagged admin_centre. Isn't this mkgmap warning a false positive?
Actually this is depending on the type of the relation. With type=multipolygon there shouldn't be any non-way member in the relation, with type=boundary the role admin_centre is defined. There is no such thing as a "boundary multipolygon", you have either one or the other. Gruss Torsten
Torsten Leistikow (de_muur@gmx.de) wrote:
Charlie Ferrero schrieb am 28.04.2011 09:46:
Why is the warning correct? The wiki says that a boundary multipolygon can contain a node tagged admin_centre. Isn't this mkgmap warning a false positive?
Actually this is depending on the type of the relation. With type=multipolygon there shouldn't be any non-way member in the relation, with type=boundary the role admin_centre is defined. There is no such thing as a "boundary multipolygon", you have either one or the other.
You're right - I wrote "boundary multipolygon" but I meant "boundary relation". -- Charlie
participants (5)
-
Carlos Dávila -
Charlie Ferrero -
charlie＠cferrero.net
-
Torsten Leistikow -
WanMil