Data

Field Types Reference

Complete reference for all available field types.

Field Types Reference

Fields define the structure of your map data. Each feature on your map has a set of fields that store information like names, descriptions, categories, and images. This page covers every available field type and how to use them.

Overview

Type Label Sortable Description
text Single line text Yes Short text, max 255 characters. HTML is sanitized.
multiline_text Long text No Multi-line text for descriptions and notes. HTML is sanitized.
number Number Yes Numeric values. Supports integer and decimal formats with custom formatting.
date Date No Date and date ranges. Supports from/to date pairs.
image Image No Image field. Stores a URL pointing to an image.
single_select Single select No Dropdown with predefined options. Each feature picks one value.
multi_select Multi select No Multiple selectable options. Features can have multiple values (tags).

Text (text)

Single-line text field for short values like names, titles, or identifiers.

  • Max length: 255 characters.
  • HTML sanitization: Any HTML tags in the value are stripped for security.
  • Sortable: Yes — features can be sorted alphabetically by this field.
  • In the UI: Renders as a standard text input in the edit form. Displays as plain text in popups and cards.
  • Import: Accepts any string value from CSV or API. Values longer than 255 characters are truncated.

Long text (multiline_text)

Multi-line text field for longer content like descriptions, notes, or addresses.

  • HTML sanitization: HTML tags are stripped.
  • Sortable: No.
  • In the UI: Renders as a textarea in the edit form. Displays with line breaks preserved in popups and cards.
  • Import: Accepts any string value. Line breaks in CSV fields are preserved.

Number (number)

Numeric field for quantities, prices, ratings, or any numerical data.

  • Formats: Supports both integer and decimal number formats. You can configure the display format (e.g., number of decimal places) in field settings.
  • Sortable: Yes — features can be sorted numerically by this field.
  • In the UI: Renders as a number input in the edit form. Displays with the configured formatting in popups and cards.
  • Import: Accepts numeric values. Use dots for decimal separators (1234.56), not commas. Non-numeric values are rejected.

Date (date)

Date field that supports single dates and date ranges.

  • Date ranges: A date field can store a from/to date pair, useful for events or time-bound entries.
  • Sortable: No.
  • In the UI: Renders as a date picker in the edit form. Displays formatted dates in popups and cards.
  • Import: Accepts standard date formats (e.g., 2024-01-15, 01/15/2024). For date ranges via API, provide from and to values.

Image (image)

Image field that stores a URL pointing to an image.

  • Value: Must be a valid, publicly accessible URL to an image file.
  • Sortable: No.
  • In the UI: Renders as a URL input in the edit form with an image preview. Displays the image in popups and cards.
  • Import: Accepts a full URL string (e.g., https://example.com/photo.jpg). Invalid or inaccessible URLs will show a broken image.

Single select (single_select)

Dropdown field where each feature picks exactly one value from a predefined list of options.

  • Configuration: Define the list of options in field settings. Each option has a label (display text) and a value (stored internally).
  • Sortable: No.
  • In the UI: Renders as a dropdown select in the edit form. Displays the selected option's label in popups and cards.
  • Import: The imported value must match an existing option's value exactly (case-sensitive). Unmatched values are ignored.

Multi select (multi_select)

Tag-style field where each feature can have multiple values selected from a predefined list.

  • Configuration: Define the list of options in field settings, same as single select. Each option has a label and a value.
  • Sortable: No.
  • In the UI: Renders as a multi-select input in the edit form. Displays selected options as tags/badges in popups and cards.
  • Import: From CSV, separate multiple values with commas. From the API, send an array of values. Values must match existing options exactly (case-sensitive).

Field slug

Every field has an auto-generated slug derived from the field label (e.g., a field labeled "Phone Number" gets the slug phone_number). The slug is used:

  • In the API — as the property key when creating or updating features.
  • In templates — to reference field values using token syntax.

Field weight

Each field has a weight value that controls the display order. Fields with lower weight appear first in forms, popups, and cards. You can reorder fields by adjusting their weight in field settings.

Fields in templates

You can reference field values in your card and popup HTML templates using the token syntax:

{{field_slug}}

For example, if you have a field with the slug phone_number, use {{phone_number}} in your template to display that field's value for each feature.