mapcomplete

History

pietervdvn 695a0867c7 Fix duplicate buildings for grb layer; add default flag for filters, performance improvement		2022-02-11 03:57:39 +01:00
..
DynamicGeoJsonTileSource.ts	Fix duplicate buildings for grb layer; add default flag for filters, performance improvement	2022-02-11 03:57:39 +01:00
DynamicTileSource.ts	Add option to force loading of a layer, even if it is hidden + automatically set this flag is another layer depends on this layer	2022-02-07 01:59:07 +01:00
FullNodeDatabaseSource.ts	Full code cleanup	2022-01-26 21:40:38 +01:00
OsmFeatureSource.ts	Full code cleanup	2022-01-26 21:40:38 +01:00
README.md	Full code cleanup	2021-11-07 16:34:51 +01:00
TiledFeatureSource.ts	Fix duplicate buildings for grb layer; add default flag for filters, performance improvement	2022-02-11 03:57:39 +01:00
TileHierarchy.ts	More refactoring of the featurepipeline, introduction of fetching data from the OSM-API directly per tile, personal theme refactoring	2021-09-28 17:30:48 +02:00
TileHierarchyMerger.ts	Fix duplicate buildings for grb layer; add default flag for filters, performance improvement	2022-02-11 03:57:39 +01:00

Data in MapComplete can come from multiple sources.

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