Understanding datasets
Datasets are the foundation of your energy dashboards - they store all your data whether it’s wind turbine locations, energy production over time, or weather measurements. The Rebase Dashboard API supports two main types of datasets, each optimized for different use cases and providing powerful data management capabilities.Dataset types
Timeseries datasets
Perfect for data that changes over time - energy production, consumption, prices, and other time-based metrics.- Automatic timestamp parsing and indexing
- Single value per timestamp (multiple metrics not supported)
- Optimized for time-based queries and visualizations
- Perfect for ECharts timeseries components
Geospatial datasets
For location-based data like wind turbines, solar panels, or power plants.- Geographic indexing for fast spatial queries
- Support for point, line, and polygon geometries
- Perfect for map layers and spatial analysis
- Can include additional properties for each location
Live datasets
Connect to external APIs for real-time data updates and automatic synchronization.- URL with params: The url is your external API endpoint, and params can use
{start}and{end}placeholders that get replaced with actual timestamps when fetching data - Column mapping: Use aliases to map your API’s column names to the expected timestamp and value format
- Flexible formats: Supports both JSON and CSV responses
- Custom datetime formatting: If your API needs a specific datetime format, you can specify it with
datetime_format - Headers: Add authentication or other headers as needed
- Column mapping is limited to
timestampandvaluefields only - Start and end parameters are required when fetching data
- Only JSON and CSV formats are supported
Working with datasets
Retrieving datasets
Updating datasets
Deleting datasets
Important Limitations
- Static datasets: Time filtering is not supported for static timeseries datasets
- Live datasets: Both
startandendparameters are required when fetching data - Data updates: You can only update dataset metadata (name, description, metadata). The actual data cannot be modified after creation
- Column mapping: Live datasets only support mapping to
timestampandvaluecolumns - Single value per timestamp: Only one value per timestamp is supported in timeseries datasets
Best practices
Data organization
- Use descriptive names and descriptions
- Include relevant metadata in your data
- Structure your data consistently
- Consider data volume and update frequency
Performance optimization
- Use appropriate data types for your use case
- Index frequently queried fields
- Consider data compression for large datasets
- Use live datasets sparingly for real-time needs
Data quality
- Validate data before uploading
- Include data source information
- Document data transformations
- Monitor data freshness and accuracy