[mkgmap-dev] Splitter caused a RestrictionRelation warning

Mon Feb 8 13:38:00 GMT 2010

Hi Marko,

MM> This is just FYI when you work on preserving relations.  Currently,
MM> I think that the current behaviour (discarding nodes or ways outside
MM> the
MM> cutting area) is OK for route relations but not for anything else
MM> (turn restriction, through-road, multipolygon).

Sounds reasonable, I'll make the above the default (or possibly just include 
everything). The hard part isn't deciding what types to keep though, it's 
finding an efficient way to hang on to the outliers at all!

Yesterday I was working on dealing with nested relations (including forward 
references) and, while the approach I was taking would have worked, I came 
to the conclusion that it was a bit complex (= hard to maintain) because 
I was trying to fit it in to the existing splitter architecture. Given that 
it sounds like no one objects to a compulsory cache, I've basically decided 
to shelve the work I've done so far and instead look at alternative approaches 
based around a more complex cache + indexes that will allow both nested rels 
and preserving entire relations to be implemented. Something like this will 
be required to preserve relations regardless and the effort I was making 
on the nested rels seemed like it might end up redundant anyway.