OSM geometry rendering doesn't reflect space origins (but IDF does)

[shorowit]

Issue overview

I have a residential multifamily model where the three multifamily units are offset by 100 meters. This is accomplished by changing the spaces' y-axis origin value.

When I import the IDF, it correctly shows the units as offset. (Ignore the fact that each unit is comprised of surfaces floating in space and don't look like an enclosed building model.)

But when I open the OSM from which the IDF was generated, the three units are right on top of each other.

I would expect to see the same rendering either way.

OSM: in.osm.txt
IDF: in.idf.txt

Details

Environment

Some additional details about your environment for this issue (if relevant):

• Platform (Operating system, version): Windows 10
• Version of OpenStudioApplication (if using an intermediate build, include SHA): v1.6.0

[macumber]

Hey @shorowit I'm not able to reproduce this. When I open in.osm.txt I see three spaces, when I export to IDF and then re-import I see three spaces again. When I import the in.idf.txt I see 9 spaces (units 0, 1, 2). Are you sure in.osm.txt is the right input that generated in.idf.txt? What process did you use to translate the in.osm.txt to in.idf.txt, did that process add the new spaces and translate their origins?

[shorowit]

Ugh, sorry @macumber, I think I must have used the wrong OSM. I tried again to reproduce the issue and now I get the correct behavior. I hope I didn't waste too much of your time! 😞

[macumber]

No worries, thanks Scott!