Boundless feature layers and routing topology creation
Status: Pre-Alpha
Brought to you by:
sakaal
Menu
▾
▴
#4 Boundless feature layers and routing topology creation
open
6
2010-02-17
2010-02-17
No
If the features and topology creation is enabled (default), it will always process the whole database. It makes no difference if the features and routing networks were imported with the current run or before. It should limit the operation to the current input data set by default.
The system now marks newly imported (changed) data with a status flag, which will enable targeting the relevant subset of data. The implementation is not finished yet, but it's already better than it used to. The user must now manually set the status flag if he wants to reprocess something that has already been processed:
UPDATE osm_<table> SET status=1 WHERE <filter>;
The system sets the flag automatically for new or changed data, but it's never set for existing data that remained unchanged during the import. There should be an option for the user to force setting the status.