osm2vectortiles/src/import-sql
lukasmartinelli be7daedfb2 Move subdivide into import-osm 2016-06-28 09:16:29 +02:00
..
classes Add leisure=track 2016-05-26 11:03:13 +02:00
layers Rename table to subdivided and remove split SQL 2016-06-28 08:38:03 +02:00
Dockerfile Add subdivide file 2016-06-17 10:14:52 -04:00
README.md Add component description for import-sql 2016-05-01 20:58:16 +02:00
functions.sql Refactoring imposm3 varname "osm_id" to "id" #304 2016-04-30 02:51:00 +02:00
generate_sql.py Improve Python code generation 2016-04-19 14:12:13 +02:00
indizes.sql Use pseudoarea in landuse 2016-06-28 08:09:37 +02:00
prepare.sh Move subdivide into import-osm 2016-06-28 09:16:29 +02:00
requirements.txt Better naming for SQL import 2015-11-04 21:29:26 +01:00
tables.yml Update place_point table to create points 2016-04-25 13:43:16 +02:00
triggers.sql Deal with non existent delete tables 2016-05-06 10:58:17 +02:00
xyz_extent.sql Simplify queries for example landuse 2016-04-18 20:47:52 +02:00

README.md

import-sql

The import-sql component is responsible to import the SQL used for the different layers. It will also generate SQL code for different classifications and code to detect changed tiles and table management commands for different layers.

Usage

Docker

This needs to run after import-external and import-osm. Only after import-sql has been run can you start generating vector tiles.

docker-compose run import-sql