Chris Miller wrote:
I'm thinking the best thing to do is to make the cache compulsory (which in turn would make --mixed redundant) and once the cache is generated and all the multipolygons have been found, an additional pass can be made over the ways cache file to determine which nodes fall in which multipolygons and dealt with accordingly. Without a compulsory cache in place this would be very expensive.
The upside to a compulsory cache is that the code doesn't get too messy and performance doesn't suffer much, plus there will likely be other benefits in the future too. The downside is that a chunk of disk space will always be required by the splitter for writing the cache.
Does anyone have any objections to this? If not I'll take a look sometime in the next few days. I'll also look at fixing the lack of support in the splitter for relations containing other relations.
No objections here. Disk space due to cache isn't really a problem, even when processing the entire planet file.