tables descriptions

[allenday]

Document the tables.

• lines
  • description: OpenStreetMap "way" features that are recognized as non-area.
• multilinestrings
  • description: OpenStreetMap “relation” features that form a multilinestring (type = ‘multilinestring’ or type = ‘route’).
• multipolygons
  • description: OSM “relation” features that form a multipolygon (type = ‘multipolygon’ or type = ‘boundary’), and OSM “way” features that are recognized as area. Multipolygons may contain holes.
• osm_layers
  • description: a union of materialized views of the GDAL-style feature tables ((points, lines, multilinestrings, multipolygon, other_relations)
• osm_layers_partitions
  • description: partitioned version of osm_layers. Use this in conjunction with name2partnum to save significantly on query execution cost.
• other_relations
  • description: OpenStreetMap “relation” features that are not exclusively of either multilinestring nor multipolygon type. These are composite objects of all GDAL types above (points, lines, multilinestrings, multipolygon). This occurs rarely.
• points
  • description: OpenStreetMap "node" features that have significant tags attached

[allenday]

I've added the field descriptions. Table descriptions still not implemented.

[allenday]

Please see an example of how to create a table with description @zdenulo https://github.com/blockchain-etl/ethereum-etl-airflow/blob/fc99e0860d94ea1d6227b443a29e3ae3891e4b9e/dags/ethereumetl_airflow/build_load_dag.py#L162