The geometry field can be used to:
- Deduct the zipcode from the geometry using the lookup service get-directions.
- Compute the area using the geometry with the fiona and
pyshp libraries. However it produced a unitless result, for example
6.374564927874783e-08which I am not sure how to interpret.
In order to compare the results to a known building, when applicable, all the examples will feature the Sabina property, 3400 Harmon Avenue, Austin TX, 78705.
Relevant facts for our effort:
| Item | Value 1 | Value 2 |
|---|---|---|
| # of units | 298 | |
| Land area | 2.565 acres | 111731.5 sqft |
| Ground floor area | 1.978 acres | 86187 sqft |
Sources:
- Austin Open Data Portal: Building Footprints Year 2013
- OpenStreeMap: Austin, TX
- TCAD: Austin, TX
This is what the final data set should look like and where the data comes from:
| Column | Source |
|---|---|
| Building info | TCAD - aggregated data |
| # of units(*) | |
| # of occupants | |
| acreage (sqft) | TCAD |
| footprint (sqft) | OSM - computed from geometry |
| impervious cover (%) | computed |
| impervious cover per occupants | computed |
(*) The # of units is not necessary per say, but would help in case we cannot get the number of occupants per building.
The detailed conclusions of our research can be found on the dedicated page.