colouring-montreal/maintenance/extract_data/export_attributes.sql

COPY (SELECT
    building_id,
    ref_toid,
    ref_osm_id,
    revision_id,
    location_name,
    location_number,
    location_street,
    location_line_two,
    location_town,
    location_postcode,
    location_latitude,
    location_longitude,
    current_landuse_group,
    current_landuse_order,
    building_attachment_form,
    date_change_building_use,
    date_year,
    date_lower,
    date_upper,
    date_source,
    date_source_detail,
    date_link,
    facade_year,
    facade_upper,
    facade_lower,
    facade_source,
    facade_source_detail,
    size_storeys_attic,
    size_storeys_core,
    size_storeys_basement,
    size_height_apex,
    size_floor_area_ground,
    size_floor_area_total,
    size_width_frontage,
    sust_breeam_rating,
    sust_dec,
    sust_retrofit_date,
    construction_core_material,
    construction_secondary_materials,
    construction_roof_covering,
    planning_portal_link,
    planning_in_conservation_area_url,
    planning_in_conservation_area_source_url,
    planning_conservation_area_name,
    planning_in_list,
    planning_list_id,
    planning_list_cat,
    planning_list_grade,
    planning_heritage_at_risk_url,
    planning_world_list_id,
    planning_glher_url,
    planning_in_apa_url,
    planning_local_list_url,
    planning_historic_area_assessment_url,
    likes_total
FROM buildings)
TO '/tmp/building_attributes.csv'
WITH CSV HEADER
Use Postgres COPY to extract data - COPY typically runs faster than going via Python - properly formatted JSON in edit history patches - assumes postgres and maintenance user both have access to /tmp 2019-10-02 10:03:54 -04:00			`COPY (SELECT`
Add data extract maintenance script 2019-08-29 08:17:09 -04:00			`building_id,`
			`ref_toid,`
			`ref_osm_id,`
			`revision_id,`
			`location_name,`
			`location_number,`
			`location_street,`
			`location_line_two,`
			`location_town,`
			`location_postcode,`
			`location_latitude,`
			`location_longitude,`
Add missed fields to bulk extract query, docs 2020-01-19 13:31:10 -05:00			`current_landuse_group,`
			`current_landuse_order,`
Add sustainability and type fields to bulk extract 2019-10-03 01:29:26 -04:00			`building_attachment_form,`
Add missed fields to bulk extract query, docs 2020-01-19 13:31:10 -05:00			`date_change_building_use,`
Add data extract maintenance script 2019-08-29 08:17:09 -04:00			`date_year,`
			`date_lower,`
			`date_upper,`
			`date_source,`
			`date_source_detail,`
Use Postgres COPY to extract data - COPY typically runs faster than going via Python - properly formatted JSON in edit history patches - assumes postgres and maintenance user both have access to /tmp 2019-10-02 10:03:54 -04:00			`date_link,`
Add data extract maintenance script 2019-08-29 08:17:09 -04:00			`facade_year,`
			`facade_upper,`
			`facade_lower,`
			`facade_source,`
			`facade_source_detail,`
			`size_storeys_attic,`
			`size_storeys_core,`
			`size_storeys_basement,`
			`size_height_apex,`
			`size_floor_area_ground,`
			`size_floor_area_total,`
			`size_width_frontage,`
Add sustainability and type fields to bulk extract 2019-10-03 01:29:26 -04:00			`sust_breeam_rating,`
			`sust_dec,`
			`sust_retrofit_date,`
Modify files for adding construction attributes 2020-04-01 07:18:19 -04:00			`construction_core_material,`
			`construction_secondary_materials,`
			`construction_roof_covering,`
Add data extract maintenance script 2019-08-29 08:17:09 -04:00			`planning_portal_link,`
Redesign interface listing protection Per @polly64 checkbox fields were removed and switch was made to using links as both as input method and for providing source. It is no longer possible to just claim that something is listed/featured, entering data will now be also faster 2022-09-20 04:34:22 -04:00			`planning_in_conservation_area_url,`
			`planning_in_conservation_area_source_url,`
Add data extract maintenance script 2019-08-29 08:17:09 -04:00			`planning_conservation_area_name,`
			`planning_in_list,`
			`planning_list_id,`
Use Postgres COPY to extract data - COPY typically runs faster than going via Python - properly formatted JSON in edit history patches - assumes postgres and maintenance user both have access to /tmp 2019-10-02 10:03:54 -04:00			`planning_list_cat,`
			`planning_list_grade,`
Redesign interface listing protection Per @polly64 checkbox fields were removed and switch was made to using links as both as input method and for providing source. It is no longer possible to just claim that something is listed/featured, entering data will now be also faster 2022-09-20 04:34:22 -04:00			`planning_heritage_at_risk_url,`
proper input form for UNESCO WHS 2022-09-24 06:37:58 -04:00			`planning_world_list_id,`
Add data extract maintenance script 2019-08-29 08:17:09 -04:00			`planning_glher_url,`
Redesign interface listing protection Per @polly64 checkbox fields were removed and switch was made to using links as both as input method and for providing source. It is no longer possible to just claim that something is listed/featured, entering data will now be also faster 2022-09-20 04:34:22 -04:00			`planning_in_apa_url,`
Add data extract maintenance script 2019-08-29 08:17:09 -04:00			`planning_local_list_url,`
Add sustainability and type fields to bulk extract 2019-10-03 01:29:26 -04:00			`planning_historic_area_assessment_url,`
			`likes_total`
Use Postgres COPY to extract data - COPY typically runs faster than going via Python - properly formatted JSON in edit history patches - assumes postgres and maintenance user both have access to /tmp 2019-10-02 10:03:54 -04:00			`FROM buildings)`
			`TO '/tmp/building_attributes.csv'`
			`WITH CSV HEADER`