We need to figure out how to manage the data in the graph. Specifically with the following cases in mind:
We don't want to reprocess all routeable tiles when the routeplanner restarts.
We want to be able to update the graph while the routeplanner is running and still keep the graph consistent.
We want to store and keep meta-data about what tiles have been loaded and what their timestamps. This to prevent the routeplanner having to rerequest alle tiles in use on restart.
At minimum we need the following features:
A way to persist to disk individual tiles.
A way to update the graph by writing to it but only 'committing' the data once the loading is finished.
Store meta-data in the data provider along with the tiles or the routerdb.
Open questions:
Do we store this data along with the tiles on disk or in a global structure?
We need to figure out how to manage the data in the graph. Specifically with the following cases in mind:
At minimum we need the following features:
Open questions: