Urbanopt combined option generates weird geometry

I am testing Urbanopt 0.8.2 and noticed that the residential geometry generated with the --combined option creates weird geometry for the residential buildings when visualized in Openstudio application 3.4.0. More specifically, if you run the commands

uo create --combined -p project_test
uo create -s project_test/example_project_combined.json
uo run -s project_test/baseline_scenario.csv -f project_test/example_project_combined.json

the geometry of feature 15 (and all the subsequent features) in the in.osm file looks like this image description

It also has a single storey.

Am I doing something wrong?

145

MapMortar

asked 2022-08-04 00:25:39 -0500

14.1k

Aaron Boranian

updated 2022-08-04 10:28:03 -0500

edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

Sort by

oldest

newest

most voted

This is the expected residential geometry in URBANopt and other HPXML to OSM workflows, its described here in the single family URBANopt documentation. The 3D building surfaces stored in HPXML and OSM models represent the area and orientation of ground and exterior exposure of surfaces, but do not represent their position relative to each other.

20.4k

David Goldwasser

answered 2022-08-04 07:31:06 -0500

edit flag offensive 0 remove flag delete link

Comments

Completely missed that :-)

MapMortar (2022-08-04 07:34:00 -0500) edit

That is understandable. It also does this fro multifamily, but each 'unit in the building sits some distance apart. There may be the ability for HPXML too store complex unit geometry in the future, in such a way that they can be reassembled in URBANopt when combined to single OSM per building so that it looks more like the actual building. This would better support context shading and other interaction between buildings.