Open-Historical-Map-Labs / openhistoricaltiles

First iteration of vector tiles from OHM Planet data
BSD 2-Clause "Simplified" License
3 stars 0 forks source link

Catalog usage of non-OHM data #11

Closed gregallensworth closed 6 years ago

gregallensworth commented 6 years ago

Per discussion today, we should document what non-OHM data are being used, in preparation for potentially removing it. Off the cuff, this would seem to include NaturalEarth data (water bodies at large scale, per #7 ) and vanilla OSM data (some of the data-prep steps at https://github.com/OpenHistoricalMap/openmaptiles/).

gregallensworth commented 6 years ago

water

NaturalEarth

NaturalEarth data are used exclusively (no OSM) through z5 to display water at large scales:

At z6 exactly the ne_10m_ocean is used to provide ocean/coastline content, and all other water comes from OSM/OHM.

At z7+ per issue #7, solely OHM/OSM data are used.

OHM / OSM

Ocean data are from pure non-historical OSM during the import-water stage of setup:

Keep this, as coastline needs to be visible.

waterway

NaturalEarth

NaturalEarth data are used exclusively (no OSM) through z8 to display waterways at large scales:

At z9+ is changes over to osm_important_waterway_linestring derivatives.

landcover

NaturalEarth

NaturalEarth data are used through z6 to display glaciers:

At z7+ these are no longer displayed, and osm_landcover_polygon derivatives are used instead.

landuse

NaturalEarth

NaturalEarth data are used through z8 to display urban areas:

At z9+ these are no longer used, and osm_landuse_polygon derivatives are used instead.

mountain_peak

OK. Confirmed OHM only.

park

OK. Confirmed OHM only.

boundary

NaturalEarth

NaturalEarth data are brought in through z5:

At z6+ the OSM osm_border_linestring derivatives are used.

OHM / OSM

The import-osmborder step loads a CSV dataset in order to create the osm_border_linestring table and its _gen1 through _gen10 derivatives. This would be non-historical OSM data, and potentially outdated to boot. The osm_border_linestring tables are then used to provide the boundary layer.

Reference: https://github.com/openmaptiles/import-osmborder/blob/master/import/import_osmborder_lines.sh and https://github.com/openmaptiles/import-osmborder/releases/download/v0.4/osmborder_lines.csv.gz

Per chat today, Jeff asked that we remove the existing boundary data as it is not serving a purpose yet. The more complex alternative would be to modify the later stages which load the OHM PBF, to load boundary data from that PBF.

transportation

OK. Confirmed OHM only.

building

OK. Confirmed OHM only.

water_name

NaturalEarth

NaturalEarth data are used, but are not displayed:

transportation_name

OK. Confirmed OHM only.

NaturalEarth data are used for a data-processing task, but are not displayed. Great Britain is pulled from the ne_10m_admin_0_countries table, in order to do some sort of adjustment to omt-gb-motorway and omt-gb-trunk road features.

place

NaturalEarth

OK. Confirmed OHM only.

NaturalEarth data are used, but are not displayed:

poi

NaturalEarth

OK. Confirmed OHM only.

Same as with the place layer: NaturalEarth data are used for ranking, but not as displayed geodata.

aeroway

OK. Confirmed OHM only.

aerodrome_label

OK. Confirmed OHM only.

gregallensworth commented 6 years ago

Boundary

https://openhistoricalmap.github.io/openhistoricaltiles/prettymap/#5.97/42.08134/-116.51183/ https://openhistoricalmap.github.io/openhistoricaltiles/prettymap/#6.50/42.08134/-116.51183/

gregallensworth commented 6 years ago

Landcover & Waterway

Reworked the views, so that NE is no longer used by z6