Datahub¶
Reference documentation for the Datahub object in EnergyAtlas.
Overview¶
The Datahub is the central repository for all data in an EnergyAtlas project. It stores building data, geospatial information, weather files, archetypes, retrofit measures, and other project assets.
Object Structure¶
Properties¶
id (string, required) - Unique identifier for the datahub - Format: UUID or custom identifier
name (string, required) - Human-readable name for the datahub - Example: "New York City Building Stock"
description (string, optional) - Description of the datahub contents - Provides context about the dataset
created_at (datetime, required) - Timestamp when datahub was created - Format: ISO 8601
updated_at (datetime, required) - Timestamp of last update - Format: ISO 8601
entries (array, required) - List of datahub entries (buildings, weather files, etc.) - See entry types below
Entry Types¶
Building Entries¶
Stores building data:
1 2 3 4 5 6 7 8 9 | |
Weather File Entries¶
Stores weather data:
1 2 3 4 5 6 7 8 9 | |
Geospatial Data Entries¶
Stores geographic data:
1 2 3 4 5 6 7 8 | |
Operations¶
Create Datahub¶
1 2 3 4 5 | |
Add Entry¶
1 2 3 4 5 | |
List Entries¶
1 | |
Get Entry¶
1 | |
Update Entry¶
1 2 3 4 | |
Delete Entry¶
1 | |
Usage Examples¶
Creating a Datahub¶
- Navigate to Datahub section
- Click "Create New Datahub"
- Enter name and description
- Save datahub
Adding Building Data¶
- Select datahub
- Click "Add Entry"
- Choose "Building" type
- Upload or enter building data
- Save entry
Importing Multiple Entries¶
- Select datahub
- Click "Import"
- Choose file format
- Map fields
- Import entries
Best Practices¶
- Organize by project: Create separate datahubs for different projects
- Name clearly: Use descriptive names
- Document entries: Add descriptions to entries
- Version control: Keep track of datahub versions
- Backup regularly: Export datahub contents
Related Objects¶
- Geospatial Data - Geographic data entries
- Weather File - Weather data entries
- Archetype - Building archetype definitions
API Reference¶
Full API documentation available at /api/docs