midgard/mapcomplete
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
mapcomplete/Logic/FeatureSource/TiledFeatureSource
History
pietervdvn 23ae9d39c8 Add the possibility to snap onto another layer with imports, add location confirm on input, add metalayer exporting all nodes, various fixes
2021-10-31 02:08:39 +01:00
..
DynamicGeoJsonTileSource.ts Add possibility to load external data as mercator tiles, add bbox tile possibilities, add CRAB and GRB as datasources in the GRB theme 2021-10-27 03:52:19 +02:00
DynamicTileSource.ts Huge refactoring of state and initial UI setup 2021-10-15 05:20:02 +02:00
FullNodeDatabaseSource.ts Add the possibility to snap onto another layer with imports, add location confirm on input, add metalayer exporting all nodes, various fixes 2021-10-31 02:08:39 +01:00
OsmFeatureSource.ts Add the possibility to snap onto another layer with imports, add location confirm on input, add metalayer exporting all nodes, various fixes 2021-10-31 02:08:39 +01: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 Force cache clearing when a new point is added, fix #522 2021-10-25 21:08:44 +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

README.md

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