Glossary
Plain-language definitions of the terms used across OrionGIS and its documentation.
Answers — the area of OrionGIS where you ask Orion AI questions in plain language.
App user — a named login for a data collector, used in the Orion Collect app instead of a personal account.
Basemap — the background map (streets, satellite, dark…) that your layers sit on.
Catalogue — the searchable index of datasets, also called the Spatial Data Hub.
Collect — the OrionGIS area for designing forms and gathering field data.
Dashboard — a page of widgets (numbers, charts, tables, maps) built on your data.
Dataset — a single set of data in the catalogue: a vector layer, a raster, or a table.
Draft — a form or map that is not yet published and is visible only to you.
Entity list — a shared reference list that several forms can read from and write to.
Form — a survey that is filled in on a phone or browser.
Form layer — a form's submissions drawn on a map as a live data layer.
GeoJSON / GeoPackage / Shapefile / GeoTIFF — common spatial file formats. See Supported formats.
GPS question — a form question that records a location, line or area.
Layer — one set of data drawn on a map.
Map Studio — the browser map editor.
OGC (WMS, WFS, WCS) — open standards for serving maps, features and rasters over the web.
Project — the container for a piece of work: its maps, data, forms and dashboards.
Provenance — where a dataset came from, its licence and version.
Published map — a map with a public share link, made from a frozen copy of the map.
Raster — gridded data such as imagery or elevation.
Review state — Received, Approved, Has Issues or Rejected: how you have classified a submission.
Scratch map — a quick map with no project; it must be filed into a project to be published.
Share link — the URL of a published map (or a public form).
Submission — one completed form.
Vector — points, lines and polygons with attributes.
Widget — one tile on a dashboard.
Something missing or unclear? Tell us — we update the guide as the platform grows.