openmaptiles/layers/waterway
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 Refreshed all diagrams, fixed automation & 2 broken graphs (#692) 2019-10-26 21:28:43 -04:00
mapping.yaml Use one pass docs image generation (#751) 2020-01-22 21:55:22 -05:00
mapping_diagram.png Refreshed all diagrams, fixed automation & 2 broken graphs (#692) 2019-10-26 21:28:43 -04:00
update_important_waterway.sql NOOP: Format all layer's SQL code (#917) 2020-06-08 12:19:55 -04:00
update_waterway_linestring.sql NOOP: Format all layer's SQL code (#917) 2020-06-08 12:19:55 -04:00
waterway.sql NOOP: Format all layer's SQL code (#917) 2020-06-08 12:19:55 -04:00
waterway.yaml Add `requires` to 2 layer definitions (#797) 2020-04-21 12:36:44 -04:00

README.md

waterway

Docs

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

Mapping Diagram

Mapping diagram for waterway

ETL diagram

ETL diagram for waterway