Trust your yield, GFA, and dwelling numbers by fixing the most common reasons Analytics shows a value you didn't expect.

Analytics needs geometries and a project boundary to calculate. An empty table or blank values usually means one of these is missing.

The usage filter in a calculation shows a dropdown only when your project has fewer than 50 distinct usages. A project with 50 or more distinct usages shows a Value text box instead. Type the usage name exactly as it appears in your project to filter by it.

The usage filter sits under Apply to features with specific filter(s) when you edit a calculation in Analytics. Giraffe counts the usages assigned to geometries in your project. A usage in your library that no geometry uses doesn't count. Geometries with no usage count as one value.

Analytics calculates every geometry in your project, whether its layer is visible on the map or not. Hiding a layer on the map doesn't change your Analytics totals.

To leave a layer out of Analytics:

OR

Add a filter to the calculation under Apply to features with specific filter(s) so it only counts the geometries you want.

A few properties come from how geometries stack, so Analytics only counts them for geometries visible on the map. The component picker marks these with "(visible features only)".

These properties are base height, height, building ID, stack order, top of stack, and base section. Every other property counts all geometries, whether they are visible or hidden.

Show the layer on the map to include its geometries in a calculation that uses one of these properties.

Analytics shows up to 30 columns when you group it. A property with more than 30 values shows a yellow warning icon, and the Group by... dropdown adds "(Too many groups)" after the property name. Hover the icon to read "Only the first 30 groups are shown!"

To see every value, group by a property that has 30 or fewer values. Ticking groups under Hide Groups in Analytics settings removes columns from the 30 shown. It doesn't bring the rest into view.

When you group by Layer, ticking layers under Hide Layers removes them before Analytics picks the 30 to show.

Analytics settings show Hide Groups for every grouping except Layer. When Analytics is grouped by Layer, use Hide Layers to remove columns instead.

Grouping Analytics by Layer Group gives one column per layer group. Every layer inside the same layer group adds up into that one column.

To compare options side by side, set Group by... to Layer. Analytics then shows one column per layer. You can also put each option in its own layer group.

Analytics can only group by text values. A property that holds a number, like an integer custom property, doesn't appear in the Group by... dropdown. Properties whose names start with _ or end in ID are also left out.

To group by it, give the property a Text or Select type in its property definition so its values are text.

Analytics calculates gross building area, net area, and saleable area only for building geometries with Levels and Floor to Floor set. A geometry with a Height value uses that height instead, and Giraffe drops its levels and floor to floor. Those area values then stay blank.

To fix it, select the building and check the Properties app:

A calculation skips any geometry that is missing a value for one of its components. Analytics doesn't count that geometry as zero. It leaves it out of the total.

Click the calculated value to open its breakdown. Step through the geometries with Previous feature and Next feature. A component letter shown in red means that geometry is missing the property. Set the property on that geometry, and the total updates.

When Analytics is grouped by Layer, the result in the calculation editor shows the first layer only. The result label reads "(first layer only)". The Analytics table still shows every layer, so its total can be higher than the editor's result.

A calculation needs at least one property component to use an operation or a filter. A calculation built only from other calculations or from site values has its operation fixed to Sum and its filter turned off.

Add a property component to the calculation to choose a different operation or add a filter.

The Constant operation works the other way. It is only available when the calculation has no components. Remove every component to use it.

Analytics calculates every scenario in your project at once. Switching which scenario is visible on the map doesn't change the totals.

Set Group by... to Scenario to see each scenario in its own column. A geometry assigned to more than one scenario counts in each of those scenario columns.

An Analytics export follows each category's usage settings by default. A usage that a category doesn't split out won't get its own rows.

To export every usage separately, open settings, go to Export, and set Subcategorize usages to All.

The Split layers? switch on the Export screen is always off and reads "This feature is not yet available." An Analytics export can't split columns by layer.

Log out of Giraffe, log back in, and refresh your browser. If Analytics still doesn't load, contact support.

The calculation editor lists problems under Evaluation errors. Use this table to find what each one means and how to fix it.

These warnings show in the Analytics app when something limits what it can show.

Importing Analytics into a project that already has its own settings asks before it replaces them. Each pop-up has a Yes, overwrite and a No, keep existing button.

Tabs, categories, and units already in this project stay as they are. An imported calculation replaces a calculation in this project with the same ID.

These toasts confirm that something worked, or tell you something needs fixing.