Locations, Floorplans and other Visualizations

[gt.f...@berkeley.edu]

Hello Brick Community!

A recent ask that we have seen more and more of is how Brick can support visualizations of floorplans, equipment and sensor placement and related viz tasks. I wanted to reach out to the community to get more clarity on what kinds of use cases are out there with respect to visualization, so that Brick can better support these workflows.

Here are some questions to seed the conversation, but please respond with whatever you feel is relevant or interesting.

How should Brick indicate the location of an entity, to a degree of specificity beyond the broad "hasLocation" property that currently exists? Image coordinates? XYZ coordinates in some building-specific coordinate space? Latitude/Longitude?

Are there ways of capturing location that we can adopt, such as from asset management systems or BIM models? What would we need to embed in a Brick model in order to refer to the external location information?

Best,

Gabe

[Erik Paulson]

One thing I was reminded of today was that Modelica includes some graphical/visualization annotation. A lot of it seems to be local to modelica components, like how to draw one of these entities in the visualizer, but there's also annotations on how to connect elements together. 

https://mbe.modelica.university/components/connectors/annotations/

Maybe we leave all of that to CDL (which I think would pick all of the graphical annotations from Modelica?)  because that's only for visualizing the block diagrams, but I wanted to flag it as another aspect to consider. 

(My modelica understanding is pretty basic so this could all be complete nonsense) 

-Erik

ps this came top of mind because the Modelica Buildings Library had a big release today: 

https://www.linkedin.com/pulse/modelica-buildings-library-built-in-energyplus-coupling-wetter/

--
You received this message because you are subscribed to the Google Groups "Brick User Forum (Unified Building Metadata Schema)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brickschema...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/d3b396f4-4fe8-4b4a-a00f-282d35514020n%40googlegroups.com.

[Martin Webrant]

I would go with real latitude/longitude due to the amount of floorplan coordinate systems (some bottom left, some top left, scale different per floorplan etc). 

To be able to use the data easily it was either GeoSPARQL/CRS84 or WGS84 with geospatial extension was the alternatives I found if one for example use GraphDB.

RealEstateCore looks to have gone with GeoSPARQL. 

Cheers,

Martin

To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/CAKJO4n6TZm-RZsRj%3DqXgi2tYXOmTS504iVdPCqLtKM%3DxgWY1Hw%40mail.gmail.com.

[peter yang]

There are many different use cases:

(1)visualize on GeoMap, 

(2)visualize on 2d floor plan

(3)visualize on 3D earth

(4)visualize on 360 image

(5)visualize on 3D model

[Jason Koh]

Hey everyone, I create a document summarizing discussion points here: https://docs.google.com/document/d/1zqziYcSg7U-Ibz83BRgsLzmgj98UUjGYPM6OUDWRGhA/edit#heading=h.poeupb2sm2mk

Please feel free to add comments (or ask me for editing permission)

I have some opinion on this, but didn't specify that in the doc yet. We will discuss this more on today's Ontology WG meeting, and then summarize the outcome in this thread after then.

Thanks!

With regards,

Jason Koh
jbkoh.github.io

To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/dcc4f2d2-c3b4-49bf-80d1-544579a00574n%40googlegroups.com.

[gt.f...@berkeley.edu]

Hi everyone:

Please make sure to review the above document and thread; we will be discussing locations as part of the Ontology working group meeting tomorrow. (Working group schedule + links here)

Best,

Gabe