mapcomplete

History

pietervdvn a6e8714ae0 Refactoring of image detection, fix loading wikimedia images		2021-09-29 23:56:59 +02:00
..
DynamicGeoJsonTileSource.ts	Add blacklist of ids to geojson source in order to avoid duplicate features to be loaded multiple times	2021-09-29 17:48:15 +02:00
DynamicTileSource.ts	Add initial clustering per tile, very broken	2021-09-26 17:36:39 +02:00
OsmFeatureSource.ts	Refactoring: LayoutToUse is a simple value now	2021-09-28 18:00:44 +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	Refactoring of image detection, fix loading wikimedia images	2021-09-29 23:56:59 +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	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

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