Create Vision Zero incidents list page #2074
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| table: | ||
| name: vz_incidents_view | ||
| schema: public | ||
| select_permissions: | ||
| - role: editor | ||
| permission: | ||
| columns: | ||
| - incident_numbers | ||
| - location_ids | ||
| - record_tables | ||
| - record_tables_str | ||
| - responding_agencies | ||
| - responding_agencies_str | ||
| - id | ||
| - record_count | ||
| - in_austin_full_purpose | ||
| - address | ||
| - record_timestamp | ||
| - point_feature | ||
| filter: {} | ||
| allow_aggregations: true | ||
| comment: "" | ||
| - role: readonly | ||
| permission: | ||
| columns: | ||
| - incident_numbers | ||
| - location_ids | ||
| - record_tables | ||
| - record_tables_str | ||
| - responding_agencies | ||
| - responding_agencies_str | ||
| - id | ||
| - record_count | ||
| - in_austin_full_purpose | ||
| - address | ||
| - record_timestamp | ||
| - point_feature | ||
| filter: {} | ||
| allow_aggregations: true | ||
| comment: "" | ||
| - role: vz-admin | ||
| permission: | ||
| columns: | ||
| - incident_numbers | ||
| - location_ids | ||
| - record_tables | ||
| - record_tables_str | ||
| - responding_agencies | ||
| - responding_agencies_str | ||
| - id | ||
| - record_count | ||
| - in_austin_full_purpose | ||
| - address | ||
| - record_timestamp | ||
| - point_feature | ||
| filter: {} | ||
| allow_aggregations: true | ||
| comment: "" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| DROP VIEW IF EXISTS vz_incidents_view; | ||
|
|
||
| DROP MATERIALIZED VIEW public.vz_incident_records_view; | ||
|
|
||
| CREATE OR REPLACE VIEW public.vz_incident_records_view AS | ||
| SELECT | ||
|
|
||
| 'crashes'::text AS record_table_name, | ||
| case when | ||
| -- 'AUSTIN POLICE DEPARTMENT' -> 'apd' | ||
| c.investigat_agency_id = 74 | ||
| then 'apd' | ||
| else agency.label | ||
| end AS record_responding_agency, | ||
| c.id AS record_id, | ||
| c.case_id AS record_incident_number, | ||
| c.crash_timestamp AS record_timestamp, | ||
| c.address_display AS record_address, | ||
| c.position AS geom, | ||
| c.vz_incident_id AS vz_incident_id, | ||
| c.vz_incident_match_status AS vz_incident_match_status | ||
| FROM crashes c | ||
| LEFT JOIN lookups.agency agency on agency.id = c.investigat_agency_id | ||
| WHERE c.is_deleted is false | ||
| UNION ALL | ||
| SELECT | ||
| 'cad_incidents'::text AS record_table_name, | ||
| ci.agency_type_short AS record_responding_agency, | ||
| ci.id AS record_id, | ||
| ci.master_incident_number AS record_incident_number, | ||
| ci.response_date AS record_timestamp, | ||
| ci.address AS record_address, | ||
| ci.geom AS geom, | ||
| ci.vz_incident_id AS vz_incident_id, | ||
| ci.vz_incident_match_status AS vz_incident_match_status | ||
| FROM cad_incidents ci | ||
| UNION ALL | ||
| SELECT | ||
| 'ems__incidents'::text AS record_table_name, | ||
| 'ems' AS record_responding_agency, | ||
| ems.id AS record_id, | ||
| ems.incident_number AS record_incident_number, | ||
| ems.incident_received_datetime AS record_timestamp, | ||
| ems.incident_location_address AS record_address, | ||
| ems.geometry AS geom, | ||
| ems.vz_incident_id AS vz_incident_id, | ||
| ems.vz_incident_match_status AS vz_incident_match_status | ||
| FROM ems__incidents ems | ||
| WHERE ems.is_deleted is FALSE | ||
| UNION ALL | ||
| SELECT | ||
| 'afd__incidents'::text AS record_table_name, | ||
| 'afd' AS record_responding_agency, | ||
| afd.id AS record_id, | ||
| afd.incident_number::text AS record_incident_number, | ||
| afd.call_datetime AS record_timestamp, | ||
| afd.address AS record_address, | ||
| afd.geometry AS geom, | ||
| afd.vz_incident_id AS vz_incident_id, | ||
| afd.vz_incident_match_status AS vz_incident_match_status | ||
| FROM afd__incidents afd; | ||
|
|
||
| COMMENT ON VIEW public.vz_incident_records_view IS 'Unified view of crash-related records (crashes, cad_incidents, ems__incidents, afd__incidents) exposed under a common schema for cross-type queries and geo-temporal matching.'; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,138 @@ | ||
| DROP VIEW IF EXISTS vz_incidents_view; | ||
| DROP VIEW public.vz_incident_records_view; | ||
|
|
||
| -- | ||
| -- add additional columns to view in_austin_full_purpose, location_id, is_location_reviewed | ||
|
Member
Author
There was a problem hiding this comment. adding columns to the incident_records_view so that we can use it as the basis for the list view. |
||
| -- | ||
| CREATE OR REPLACE VIEW public.vz_incident_records_view AS | ||
| SELECT | ||
|
|
||
| 'crashes'::text AS record_table_name, | ||
| case when | ||
| -- 'AUSTIN POLICE DEPARTMENT' -> 'apd' | ||
| c.investigat_agency_id = 74 | ||
| then 'apd' | ||
| else agency.label | ||
| end AS record_responding_agency, | ||
| c.id AS record_id, | ||
| c.case_id AS record_incident_number, | ||
| c.crash_timestamp AS record_timestamp, | ||
| c.address_display AS record_address, | ||
| c.position AS geom, | ||
| c.latitude AS latitude, | ||
| c.longitude AS longitude, | ||
| c.vz_incident_id AS vz_incident_id, | ||
| c.vz_incident_match_status AS vz_incident_match_status, | ||
| c.in_austin_full_purpose AS in_austin_full_purpose, | ||
| c.location_id AS location_id, | ||
| case when c.latitude != cris.latitude or c.longitude != cris.longitude THEN TRUE ELSE FALSE END | ||
| AS is_location_reviewed | ||
| FROM crashes c | ||
| LEFT JOIN lookups.agency agency on agency.id = c.investigat_agency_id | ||
| LEFT JOIN crashes_cris cris on c.id = cris.id | ||
| WHERE c.is_deleted is false | ||
| UNION ALL | ||
| SELECT | ||
| 'cad_incidents'::text AS record_table_name, | ||
| ci.agency_type_short AS record_responding_agency, | ||
| ci.id AS record_id, | ||
| ci.master_incident_number AS record_incident_number, | ||
| ci.response_date AS record_timestamp, | ||
| ci.address AS record_address, | ||
| ci.geom AS geom, | ||
| ci.latitude AS latitude, | ||
| ci.longitude AS longitude, | ||
| ci.vz_incident_id AS vz_incident_id, | ||
| ci.vz_incident_match_status AS vz_incident_match_status, | ||
| ci.in_austin_full_purpose AS in_austin_full_purpose, | ||
| ci.location_id AS location_id, | ||
| FALSE AS is_location_reviewed | ||
| FROM cad_incidents ci | ||
| UNION ALL | ||
| SELECT | ||
| 'ems__incidents'::text AS record_table_name, | ||
| 'ems' AS record_responding_agency, | ||
| ems.id AS record_id, | ||
| ems.incident_number AS record_incident_number, | ||
| ems.incident_received_datetime AS record_timestamp, | ||
| ems.incident_location_address AS record_address, | ||
| ems.geometry AS geom, | ||
| ems.latitude AS latitude, | ||
| ems.longitude AS longitude, | ||
| ems.vz_incident_id AS vz_incident_id, | ||
| ems.vz_incident_match_status AS vz_incident_match_status, | ||
| ems.austin_full_purpose AS in_austin_full_purpose, | ||
| ems.location_id AS location_id, | ||
| FALSE AS is_location_reviewed | ||
| FROM ems__incidents ems | ||
| WHERE ems.is_deleted is FALSE UNION ALL | ||
| SELECT | ||
| 'afd__incidents'::text AS record_table_name, | ||
| 'afd' AS record_responding_agency, | ||
| afd.id AS record_id, | ||
| afd.incident_number::text AS record_incident_number, | ||
| afd.call_datetime AS record_timestamp, | ||
| afd.address AS record_address, | ||
| afd.geometry AS geom, | ||
| afd.latitude AS latitude, | ||
| afd.longitude AS longitude, | ||
| afd.vz_incident_id AS vz_incident_id, | ||
| afd.vz_incident_match_status AS vz_incident_match_status, | ||
| afd.austin_full_purpose AS in_austin_full_purpose, | ||
| afd.location_id AS location_id, | ||
| FALSE AS is_location_reviewed | ||
| FROM afd__incidents afd; | ||
|
|
||
|
|
||
| COMMENT ON VIEW public.vz_incident_records_view IS | ||
| 'Unified view of crash-related records (crashes, cad_incidents, ems__incidents, afd__incidents)' | ||
| 'exposed under a common schema for cross-type queries and geo-temporal matching.'; | ||
|
|
||
|
|
||
| CREATE MATERIALIZED VIEW vz_incidents_view AS | ||
|
Member
Author
There was a problem hiding this comment. After many attempts at tuning this query, i opted for a materialized view that takes ~5s to create locally. This feels good enough while we're still in proof-of-concept. Long term, I think we'll want to consider possibly setting up a proper table with the triggers that keep it current, or maybe we can live with having this be on an hourly refresh ( a la I'm still uncertain about what the finally shape of this view needs to be, so I think for now we can just create this materialized view once via migration and let it become stale while we further refine the future state.
Contributor
There was a problem hiding this comment. 👍 and I clocked this migration at about 7 Mississippis to apply on my machine
Contributor
There was a problem hiding this comment. this migration took only like 4 ms for me! |
||
| SELECT | ||
| id, | ||
| record_count, | ||
| incident_numbers, | ||
| record_tables, | ||
| '$' || array_to_string(record_tables, '$,$') || '$' AS record_tables_str, | ||
| responding_agencies, | ||
| '$' || array_to_string(responding_agencies, '$,$') || '$' AS responding_agencies_str, | ||
|
Member
Author
There was a problem hiding this comment. We need these string-concatenated fields for search purposes. This is a work around for the fact that Hasura does not have a |
||
| address, | ||
| location_ids, | ||
| record_timestamp, | ||
| point_feature, | ||
| latitude, | ||
| longitude, | ||
| in_austin_full_purpose | ||
| FROM ( | ||
| SELECT | ||
| v.vz_incident_id as id, | ||
| COUNT(*) AS record_count, | ||
| ARRAY_AGG(DISTINCT record_incident_number ORDER BY record_incident_number) as incident_numbers, | ||
| ARRAY_AGG(DISTINCT record_table_name ORDER BY record_table_name) as record_tables, | ||
| ARRAY_AGG(DISTINCT record_responding_agency ORDER BY record_responding_agency) AS responding_agencies, | ||
| (ARRAY_REMOVE( | ||
| ARRAY_AGG(v.record_address ORDER BY is_location_reviewed desc, v.record_timestamp, v.record_id), NULL | ||
|
Member
Author
There was a problem hiding this comment. So what we're doing here is picking a single member record to serve as the representative record in the list view. We select that based on:
Again, this is just for the proof of concept: we may find a more sophisticated/informed way of doing this later. |
||
| ))[1] AS address, | ||
| ARRAY_AGG(DISTINCT location_id ORDER BY location_id) as location_ids, | ||
| MIN(v.record_timestamp) as record_timestamp, | ||
| (ARRAY_REMOVE( | ||
| ARRAY_AGG(v.geom ORDER BY is_location_reviewed desc, v.record_timestamp, v.record_id), NULL | ||
| ))[1] AS point_feature, | ||
| (ARRAY_REMOVE( | ||
| ARRAY_AGG(v.latitude ORDER BY is_location_reviewed desc, v.record_timestamp, v.record_id), NULL | ||
| ))[1] AS latitude, | ||
| (ARRAY_REMOVE( | ||
| ARRAY_AGG(v.longitude ORDER BY is_location_reviewed desc, v.record_timestamp, v.record_id), NULL | ||
| ))[1] AS longitude, | ||
| BOOL_OR(v.in_austin_full_purpose) AS in_austin_full_purpose | ||
| FROM vz_incident_records_view v | ||
| WHERE vz_incident_id is not null | ||
| GROUP BY v.vz_incident_id | ||
| ) sub | ||
| ORDER BY record_timestamp desc; | ||
|
|
||
| COMMENT ON VIEW public.vz_incidents_view IS | ||
| 'Aggregate view of vz_incidents which aggregates attributes from the member records ' | ||
| '(crashes, cad_incidents, ems__incidents, afd__incidents) via the vz_incident_records_view'; | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just realized that we should name this
vz_incidents_list_viewto be consistent with our other record views. i'm going to fix this in later because I already have a branch going.