mapcomplete

History

pietervdvn 69f21f29eb Dynamic JSON: only request existing tiles if a whitelist is given		2021-10-13 03:10:46 +02:00
..
DynamicGeoJsonTileSource.ts	Dynamic JSON: only request existing tiles if a whitelist is given	2021-10-13 03:10:46 +02:00
DynamicTileSource.ts	Add initial clustering per tile, very broken	2021-09-26 17:36:39 +02:00
OsmFeatureSource.ts	Make metatagging lazy (fix #503 ), fix null-distances (#504 ), various other small fixes	2021-10-10 23:38:09 +02:00
README.md	More refactoring, move minimap behind facade	2021-09-21 02:10:42 +02:00
TiledFeatureSource.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
TiledFromLocalStorageSource.ts	Fix bounds and loading with overpass	2021-10-11 22:30:22 +02: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	Better tracking of cached data, only load data if needed	2021-09-30 04:13:23 +02: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