Open danrademacher opened 3 months ago
This looks like an issue where we have a bunch of buildings on top of each other:
On the benchmarking side, we have five buildings with similar names and exact same latlng
I went to https://cityenergy-seattle.carto.com/dataset/benchmarking_production and did this query to confirm same latlng:
SELECT the_geom FROM public.benchmarking_production where property_name like 'UNIVERSITY VILLAGE SHOPPING CENTER%' and year = '2022' group by the_geom
Then to get the IDs and names, I did:
SELECT id,property_name FROM public.benchmarking_production where property_name like 'UNIVERSITY VILLAGE SHOPPING CENTER%' and year = '2022' group by id,property_name
That output this:
id,property_name
819,UNIVERSITY VILLAGE SHOPPING CENTER BLDG D
20047,UNIVERSITY VILLAGE SHOPPING CENTER BLDG A
20048,UNIVERSITY VILLAGE SHOPPING CENTER NW BLDG
20050,UNIVERSITY VILLAGE SHOPPING CENTER BLDG C
20052,UNIVERSITY VILLAGE SHOPPING CENTER WEST BLDG
So we have 5 building IDs with 2022 data
Then I went to https://cityenergy-seattle.carto.com/dataset/footprints_production and did this query:
SELECT * FROM public.footprints_production where buildingid in (819,20047,20048,20050,20052) order by buildingid
That nets us only three results:
We do not have footprints for:
20047,UNIVERSITY VILLAGE SHOPPING CENTER BLDG A
20050,UNIVERSITY VILLAGE SHOPPING CENTER BLDG C
But at least they are not on top of each other:
So it seems like we need to:
The U Village complex is kind of a mess. It’s multi-building outdoor shopping center. I think the addresses were probably entered pretty haphazardly (i.e. using the same address for multiple buildings), which would result in the Seattle Geodata using the same lat/lon for multiple buildings. Fortunately, I did diagram the buildings required for benchmarking in the complex using a sitemap I found on the internet. I should be able to cross reference that with the Seattle Geodata Address map and correct the addresses upstream. I can then provide an updated list of lat/lons for those buildings.
┆Issue is synchronized with this Asana task