An interactive, grid-based Geographic Information System. workspace dashboard featuring zooming dials, layers drag handles, polyline/polygon drawing anchors, and interactive element deletion triggers.
- Allowing users to draw, edit, and capture spatial map structures (points, lines, regions) within form views.
- Binding geographic coordinates or feature vectors directly into database records via standard GeoJSON structures.
Locked by default until paired inside a form frame context. Connection opens when clicking the ‘+’ data trigger to establish Element ID and Field Path references.
- An internal delivery form where warehouse teams sketch distribution route tracks or drop pins on fulfillment hubs.
- A real estate platform page forcing managers to explicitly draw property boundary perimeters using dynamic drawing tools.
- Squeezing the map into compact boundaries below 7 rows or 7 columns, which heavily breaks spatial workspace tools and edit flows.
- Attempting to map or establish data context properties before a parent default_form element is drop-placed on the page canvas.
Pairs well with
- Form — Acts as the parent data engine tracking field spatial mutations and managing global submission states.
Configure these in the Application Designer property panel. Group headings mirror the editor where possible. Data Source is where the element gets its rows or field binding (a view/query, a connector operation, or a parent form field). References appear only for view-backed sources and map foreign-key ID columns to readable labels from another view.
- The GeoJSON value payload rendered and edited by the map control.Example
{ "type": "FeatureCollection", "features": [] }Default: none
- When true, the control cannot be edited.Example
falseDefault: none
- The layout path for custom visual map layers (e.g. .png tilesets). Leave completely empty to leverage OpenStreetMaps protocols automatically.Default: none
- Floating point string pinpointing map centering configurations.Good to know
- Must comply with geographic latitude regex configurations: \d{2}.\d{2}
Default: none - Floating point string pinpointing map centering configurations.Good to know
- Must comply with geographic longitude regex configurations: \d{2}.\d{2}
Default: none - An integer scaling baseline parameter defining the initial layout focus size level.Default: none
Inside dataSource: (dataSource)
- Another element on the page whose data backs this field.Default: none
- Path into the source element’s data (property segments).Default: none
- Minimum size: 2 × 2 grid cells (width × height).
- Default size when dropped on a page: 4 × 4.
label— Main screen header text framing the drawing area canvas task.
Workspace tool headers provide readable alt contexts, mapping operations yield dynamic screen announcements as text payloads mutate live.
Other parts of your app can read live values from this element in custom expressions:
elements.myGeojsonInput.<property>
value
any
Current input value of this control.
elements.myGeojsonInput.value
When The drawn geometry as a GeoJSON object. Feed it to a map display or a spatial query parameter; it is empty until the user draws something.
errors
any
The data validation errors.
elements.myGeojsonInput.errors
touched
boolean
Indicates whether the user has typed anything in the input.
elements.myGeojsonInput.touched
disabled
boolean
True while the control is locked and cannot be edited.
elements.myGeojsonInput.disabled
To use one of these, open the property you want to drive on the other element, switch it to expression mode in the Expression Editor, and enter:
| |
Replace myGeojsonInput with this element’s unique id. Select the element in Application Designer and copy the id chip at the top of the right-hand property panel.
Drag this element into one of these containers:
| |