Date: Fri, 29 Mar 2024 12:51:39 +0000 (UTC) Message-ID: <609535465.17.1711716699848@2c41d75624af> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16_661886784.1711716699847" ------=_Part_16_661886784.1711716699847 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Notes from the discussion about the resilient cities pilot discu= ssion
Present: Philipp, SteveM, SteveR, ericP, Bill, PhilA, PeterW
What is the goal of the data integration. what are questions. Mode= l exists already.
What is impact of change x to transportation system on infant mortality/= pulmonary disease
resilience-- how will city respond to bridge collapse, power station fai= lure, bus driver strike
Model focus is planning. Scenario exploration; (predicting effects of fu= ture decsions)
Problem of correlation not necessarily indicating causality. (trying to = establish effects of actual decisions)
Data survey from https://docs.google.com/spreadsheets/d/1I= EBHtAXsmHqP8QKpxcW3510vyM7GAz_QKVXGOjQ1bq0
Data specification description of spatial data = is insufficient to understand how it works
Many of the datasets have lat long,
Travel inventory has locations by city, community, and neighborhood (but= many trips don't have neighborhood). There is also an identifier for house= hold, but couldn't tell if households are located. Data also include whethe= r trips on food, by bus, by car. Spatial resolution possible by household, = possible by barrio (neighborhood), reliable by community. Need centro= ids for the town, district and neighborhood designations.
hospitalization diagnosis data is aggregated by year, need better = resolution; air quality data from sensors is reported by hour.
need higher temporal resolution on hospitalization to correlate with air= quality data.
In general data in the inventory appears well curated.
Data we've looked at generally contains a geography.
Situation is as simple as it gets: single city/administration so there i= s already some harmonisation.
The data is basically fine - could do with some enhancement, connecting = to metadata, identifying code lists etc.
Some linkages were apparent. We should think about generalising to the o= ther pilots.
We should offer some steps that would make things easier. It took a whil= e to notice that the hospital data was yearly, a very different granularity= from the sensor data. Discovery metadata and variable metadata should incl= ude that.
We need datatypes for geospatial, the existence of geospatial. Some data= had by name, some by lat/long etc. Need a gazeteer.
Household travel - data had household identifiers, could possibly add ge= o info.
Need to be able to say run this program that has this key in it that can= then make a query behind the hospital firewall.
Is this scalable?
{SteveM is making notes separately}
Note-- W3C spatial data on the Web best practices (a sp= cialisation of Data on the Web Best Practices) has important reco= mmendations that can inform spatial data reporting needed for integrating s= patial data.
Looking forward:
get together with people of medillin to assess the cost of what th= ey have done in the data aggregation/collection.
What would it cost to achieve more granular data for a higher reso= lution model?