forked from MapComplete/MapComplete
More refactoring, move minimap behind facade
This commit is contained in:
parent
c11ff652b8
commit
d5c1ba4cd1
79 changed files with 1848 additions and 1118 deletions
|
@ -1,3 +1,27 @@
|
|||
Data in MapComplete can come from multiple sources.
|
||||
|
||||
In order to keep thins snappy, they are distributed over a tiled database
|
||||
Currently, they are:
|
||||
|
||||
- The Overpass-API
|
||||
- The OSM-API
|
||||
- One or more GeoJSON files. This can be a single file or a set of tiled geojson files
|
||||
- LocalStorage, containing features from a previous visit
|
||||
- Changes made by the user introducing new features
|
||||
|
||||
When the data enters from Overpass or from the OSM-API, they are first distributed per layer:
|
||||
|
||||
OVERPASS | ---PerLayerFeatureSource---> FeatureSourceForLayer[]
|
||||
OSM |
|
||||
|
||||
The GeoJSon files (not tiled) are then added to this list
|
||||
|
||||
A single FeatureSourcePerLayer is then further handled by splitting it into a tile hierarchy.
|
||||
|
||||
|
||||
|
||||
In order to keep thins snappy, they are distributed over a tiled database per layer.
|
||||
|
||||
|
||||
## Notes
|
||||
|
||||
`cached-featuresbookcases` is the old key used `cahced-features{themeid}` and should be cleaned up
|
Loading…
Add table
Add a link
Reference in a new issue