Falke Design
ebeafc65fa
Add requires.tables to <layer>.yaml ( #1236 )
...
**NOTE** this can only be merged after the next tools version is released.
Added required Postgres tables to the `<layer>.yaml` definition.
Close : #1220
PR of tools: https://github.com/openmaptiles/openmaptiles-tools/pull/370
2021-11-05 10:04:54 +01:00
Brian Sperlongano
d427d58e36
Water layer river mapping bug fixes ( #1182 )
...
This PR is a bugfix for the `water` layer.
* `waterway=stream`, `waterway=river`, `waterway=canal`, `waterway=ditch`, and `waterway=drain` are all linear features, not area features. Thus, these objects are being unnecessarily mapped into the `osm_water_polygon` polygon table, and this PR removes these unneeded mappings.
* The combination `natural=water` + `water=river` is the most popular tagging for river areas. However, the current mapping causes rivers tagged in this way to be rendered in the vector tiles as a `lake`. This PR adds a check for the `water=river` tag and tags both variants of river areas as `class=river`.
`natural=water` + `water=river` river mapping:
![image](https://user-images.githubusercontent.com/3254090/129825551-388491de-549e-4843-80cc-01dba358c360.png )
`waterway=riverbank` river mapping:
![image](https://user-images.githubusercontent.com/3254090/129825618-4239eae7-a2bc-4a82-9931-fda2c02c2b40.png )
Lake mapping for a `natural=water` (with no other tagging):
![image](https://user-images.githubusercontent.com/3254090/129825554-9394b3d3-988a-4e92-a9f8-b198c695ec37.png )
2021-09-01 08:24:01 +02:00
zstadler
893d1df4c5
Update descritopn of the water layer's class ( #1166 )
...
Clarify that OSM water bodies that do not have a `waterway` tag are classified as `lake`.
This refers to the following tags:
9e4be3e3b0/layers/water/mapping.yaml (L86-L95)
2021-08-10 16:16:40 +02:00
Yuri Astrakhan
0b1511d60d
NOOP water - Move updating sql into separate file ( #920 )
...
Use `update_water.sql` for all queries that update db
to be consistent with the other layers.
2020-06-08 12:32:09 -04:00
Yuri Astrakhan
1614a4656c
Manage field mapping in SQL declaratively
...
Simplify some of the OSM->OMT field value mappings using declarative syntax.
This approach is not for all cases, but in many it removes
the need of storing the same field in both the .yaml and .sql files.
TODO: support more complex AND/OR cases
2019-12-19 11:25:29 -05:00
Yuri Astrakhan
39dcfc2072
Fix missing description for the new brunnel field ( #709 )
2019-11-19 14:47:34 -05:00
Guillaume Gomez
23358f18af
add brunnel info for water
2019-10-11 17:57:26 +02:00
zstadler
7a3ac079ae
Add intermittent field to water* layers ( #430 PR #585 )
2019-05-24 13:21:43 +02:00
Eva J
f09a2edd12
import-water 1.0, update osmdata URL
2019-05-20 11:58:34 +02:00
Lukas Martinelli
f6a7e4ec92
Improve docs of water and water_name
2017-01-05 16:36:55 +01:00
stirringhalo
bab5c3d4b6
Switch from geom to geometry
2016-12-20 22:32:34 -05:00
lukasmartinelli
90f2203e7c
Document water and remove obsolete mapping
2016-10-28 20:49:20 +02:00
lukasmartinelli
ea2530788f
Filter out large rivers
2016-10-28 16:53:29 +02:00
lukasmartinelli
9c50026f16
Remove osm_id in vector tiles coz of huge size savings
2016-10-25 19:15:51 +02:00
lukasmartinelli
c86f5b9a26
Switch water layer to imposm3
2016-10-10 19:39:47 +02:00
lukasmartinelli
480d720585
Move to new modular layer structure
2016-10-09 21:27:09 +02:00