openmaptiles/layers/park
Yuri Astrakhan 6457419e0d
NOOP: Format all layer's SQL code (#917)
I would like to reformat all of our SQL to have a concise coding style.
This makes it far easier to understand the code for a casual contributor,
and lets us spot errors more easily.

Most importantly, it makes it much easier to grep (search) the code because it is more likely to be in the same syntax

Some key changes:
* SQL keywords are always UPPERCASE, e.g. `SELECT WHEN AS END ...`
* types, variables, aliases, and field names (identifiers) are always lower case
* `LANGUAGE 'plpgsql'` is now `LANGUAGE plpgsql` (no quotes)
* a few minor spacing/semicolon cleanups

P.S. Per @TomPohys request, `TABLE` is spelled using upper case despite being a type for consistency with PG Docs. Same for `LANGUAGE SQL` vs `LANGUAGE plpgsql`.
2020-06-08 12:19:55 -04:00
..
README.md Update diagrams 2017-12-04 12:06:28 +01:00
etl_diagram.png Updated etl diagrams from latest tools 2020-02-14 16:22:48 -05:00
layer.sql NOOP: Format all layer's SQL code (#917) 2020-06-08 12:19:55 -04:00
mapping.yaml Merge branch 'master' into protected_area 2020-04-04 12:50:03 +03:00
mapping_diagram.png Add `boundary=protected_area` parks 2020-01-27 11:12:57 +02:00
park.yaml Add `boundary=protected_area` parks 2020-01-27 11:12:57 +02:00
update_park_polygon.sql NOOP: Format all layer's SQL code (#917) 2020-06-08 12:19:55 -04:00

README.md

park

Docs

Read the layer documentation at http://openmaptiles.org/schema#park

Mapping Diagram

Mapping diagram for park

ETL diagram

ETL diagram for park