Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Data Formats

Galdera works with two data layouts and auto-detects which one you're using:

Wide format (also called pivot format):

  • Each numeric column becomes its own measure
  • Example: columns named "revenue", "costs", "units" create three separate measures
  • Best when your spreadsheet has one row per time period with multiple value columns
Long format:
  • One column contains the measure names, another contains the values
  • Example: a "metric" column with values like "Revenue", "Costs", "Units" paired with a "value" column
  • Best when your data comes from an ETL system or database export

Dimensions work the same in both formats -- any categorical column (like Region, Product, or Department) can be selected as a dimension during column mapping. Galdera creates dimension values automatically from the distinct entries in each column.

Date column:
  • Galdera needs to know which column holds your dates for time-based forecasting
  • Common names: "date", "month", "quarter", "period"
  • Dates should be in a standard format (e.g., 2024-01-01 or Jan 2024)
  • For Snowflake sources, select a native DATE or TIMESTAMP column; use a view to cast other representations before connecting them

Cohorted measures in chat

A file with more than one date column is a cohort file: one column is the cohort date and one the report date. The assistant does not create a source from a cohort file or load one into a source that is not set up for its cohort date. Set up a cohort source on the source page.