Columns
Column | Required | Description |
ref_id | Yes | Unique identifier for the activity |
label | Yes | Display name |
category | Yes | GHG category code, for example |
active_at | Column required, value optional | Start date (YYYY-MM-DD) |
retired_at | Column required, value optional | End date (YYYY-MM-DD) |
Tag columns | No | One column per tag type. The header is the tag type and the cell is the tag name. |
Key: ref_id
All five core columns must be present, even if active_at and retired_at are blank.
Example
ref_id | label | category | active_at | retired_at | facility | fuel_code |
denver-office-electricity | Denver Office - Electricity | s2.1 |
|
| denver-office |
|
denver-office-natural-gas | Denver Office - Natural Gas | s1.1 |
|
| denver-office | 020104 |
corporate-air-travel | Corporate - Air Travel | s3.6 |
|
|
|
|
Linking tags
To link a tag to an activity, add a column whose header is the tag type and put the tag's name in the cell.
Use the name, not the title. If you enter Denver - Office (the title) instead of denver-office (the name), Measure creates a second, untitled tag called "Denver - Office," and your facility's data is split between two tags.
Leave a tag cell blank when it doesn't apply. For example, many Scope 3 activities don't belong to a facility.
Tags needed for emission factors
Add the tags each category needs to get an emission factor automatically, such as fuel_code for stationary combustion. See Automated Emission Factors.