Hi, today I've committed r288 in the problem-list branch. Changes compared to r283 in trunk: - Corrected: Some type=multipolygon relations were not treated as such in the keep-complete processing (this means that splitter did not calculate the bbox of the relation to calculate the writers to find totally enclosed tiles). - Changed: type=multipolygon relations with a boundary tag are now treated like type=boundary tags - Added: Filter for the boundary tag and new parameter --boundary-tags. Purpose: Allow to filter boundary relations in the problem-list-generator. It tells splitter an include list of tag values for the boundary tag. It is used to filter type=boundary or type=multipolygon relations. If these relations do also have a boundary tag, the parameter is used as follows: --boundary-tags=use-exclude-list (the default) means that the relation is added to the problem list if the boundary tag is not one of "administrative", "postal_code", "political" --boundary-tags= (empty list) means that the relation not is added to the problem list if it has a boundary tag --boundary-tags=a,b,c means that the relation is added to the problem list if it has a boundary tag with any of the given values. I hope this description is clear enough? Ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r288-tp5749227.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Gerd wrote:
I hope this description is clear enough?
I'm not sure what you mean with the new option --boundary-tags Default is to exclude "administrative", "postal_code", "political" boundaries from keep-complete. Not clear what you mean by --boundary-tags=use-exclude-list, can it read a custom file with other boundary values to exclude or do you mean "use the default hardcoded list" so the same as without the option --boundary-tags? With the parameter --boundary-tags does this mean exclude all boundaries from the keep-complete? With --boundary-tags=administrative means include them too (so only ignore political and postal_code?)
Hi Minko, Minko-2 wrote
Gerd wrote:
I hope this description is clear enough?
I'm not sure what you mean with the new option --boundary-tags Default is to exclude "administrative", "postal_code", "political" boundaries from keep-complete.
Not clear what you mean by --boundary-tags=use-exclude-list, can it read a custom file with other boundary values to exclude or do you mean "use the default hardcoded list" so the same as without the option --boundary-tags?
the latter one: "use the default hardcoded list" so the same as without the option --boundary-tags Minko-2 wrote
With the parameter --boundary-tags does this mean exclude all boundaries from the keep-complete?
the empty parm means: relations with type=boundary are added to the problem list if they don't have a boundary=* tag, type=multipolygon are not added if they have a boundary=* tag If such a relation is given in the problem-list, it will be still be used in keep-complete processing. Minko-2 wrote
With --boundary-tags=administrative means include them too (so only ignore political and postal_code?)
The parm gives an include list which means ignore the exclude list. That's why I've used --boundary-tags=use-exclude-list as default. So, with --boundary-tags=administrative splitter will not add political or postal_code boundaries. Quite complicated... Please let me know if you have a better solution. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r288-tp5749227p5749244.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (2)
-
GerdP -
Minko