kopia lustrzana https://github.com/openmaptiles/openmaptiles
2b95d1cffa
* All functions that access database must be declared as `STABLE`, not `IMMUTABLE` -- because database can change at any moment, e.g. during an update * there are a few functions that could be made `STRICT` -- passing `NULL` as a parameter will always result in a `NULL`, but for some reason that causes a significant decrease in perf. * tagged one function as parallel safe NOTE: somehow `ST_AsMVT()` method of tile generation is showing 70-90% slowdown with this patch. I am not sure of why this is happening. If the reason is the `IMMUTABLE` -> `STABLE` change, we may have to dig deeper into PG optimization |
||
|---|---|---|
| .. | ||
| README.md | ||
| capital.sql | ||
| city.sql | ||
| etl_diagram.png | ||
| island_rank.sql | ||
| layer.sql | ||
| mapping.yaml | ||
| mapping_diagram.png | ||
| place.yaml | ||
| types.sql | ||
| update_city_point.sql | ||
| update_continent_point.sql | ||
| update_country_point.sql | ||
| update_island_point.sql | ||
| update_island_polygon.sql | ||
| update_state_point.sql | ||
README.md
place
Docs
Read the layer documentation at http://openmaptiles.org/schema#place
Mapping Diagram
ETL diagram
