Area Schemes in next gen connector models

[RyanHaunfelder]

I’m looking for area scheme information associated with the area objects pushed through the next gen connectors. I’ve found areas structured here: elements → elements → level → elements → name: Areas → elements. The parameters seem to identify the area name, type, level, and other instance parameters but there is nothing that relates the area to a specific area scheme. Is the area scheme information included in pushes with the next gen connector?

In general, what’s the best resource explaining the new schema introduced with the next gen connectors? It looks like things are generally nested deeper than they were previously so it would be helpful to have a reference for the taxonomy during our refactoring efforts. If there’s a community effort to build this, I’d love to contribute!

[RyanHaunfelder]

Any ideas @dimitrie or @jonathon ? Am I missing something fundamental?

[jonathon]

source application?
accessed how?

an example model would help us get to it faster - it might be we’re not extracting those properties out.

[RyanHaunfelder]

Shame on me for skipping the reprex, sorry about that!

This was sent from Revit 2025 using the next gen connector version 3.6.3. It’s a model with one room, one area scheme (rentable), and one area. I sent using categories “Rooms” and "Areas.

The published model is available here,

Speckle

The revit file is here,

AreaReprex.rvt (452 KB)

I’m trying to access the area scheme information for the area element (things like area scheme id, element id, area scheme name) but I don’t see any of those in the speckle object. I’m accessing in using the graphql api and the specklepy sdk, but also can’t find anything in the speckle viewer on the server.

Let me know if I missed any details that would be helpful.

[dimitrie]

We’ll need to look in the api handling of this - as those props are not visible in the props panel, which means we’re likely not looking for that.

I do find them, after some digging:

Team will take over and investigate, it’s a legit request - if it’s fast we can try to implement it soon. Based on some digging, can be easy

                    Area _area ;
                    AreaScheme _scheme = document.GetElement(_area.get_Parameter(BuiltInParameter.AREA_SCHEME_ID).AsElementId()) as AreaScheme;
                    string _AreaSchemeName = _scheme.get_Parameter(BuiltInParameter.AREA_SCHEME_NAME).AsString();

But i don’t know yet performance implications etc. etc.

We’re obviously curious for the extra context around what you’re cooking with those!

[RyanHaunfelder]

Thanks dimitrie!

The v2 connectors send area scheme information when choosing “send everything” and we used that as part of our ETL for space planning and benchmarking efforts. Our project teams use custom area schemes to capture high level square footage metrics. For example,

• Area scheme 1 - Defines the space in the model that should be included in a DGSF calculation
• Area scheme 2 - Areas define boundaries for specific departments

Along with room information, areas is one of the foundational tabular datasets we load from all of our Speckle models into our data warehouse.

I was just reaching out to make sure I wasn’t missing a way to get this information. I think it may be valuable for others, but I understand it may not be a high priority. Thank you for looking into it!

Is there a good reference for the schema of the objects pushed with the next gen connectors?