QUAC (Quite Useful Additions for Catalogs) is a profile of STAC 1.1.0 that adds map layer settings to a catalogue.
What QUAC lets you know about a catalogue
Map
- the layer to make active when it opens
- the view it opens on
- which layers start switched on
- groups that show one layer at a time
Layers
- read-only layers, and locked edits: adding, changing, moving, deleting
- private layers, such as lookup tables to keep out of a layer list
- related layers, such as inspections that belong to a site
- the field that names each feature in a list
- scale range and opacity
Fields
- choices from a fixed list or from another layer
- number ranges, steps and units
- date formats and checkbox values
- required and unique fields, and rules with their messages
- default values, and fields that keep the last value entered
- fields that can't be changed, or only while a condition holds
Forms
- field order
- fields shown only while a condition holds, such as "Cause of damage" once "Damaged" is ticked
Sources
- QGIS projects and QGIS Server, WFS, WMS, OGC API Features and ArcGIS
A STAC catalogue says what data exists, where it is and how to read it, and Portolan says how to publish one for cloud-native data with no server to run.
A catalogue does not say how a map should show that data or how people should edit it. That lives in a QGIS project, a GIS server's configuration or an ArcGIS Web Map, each in a format mostly read only by the software that wrote it.
QUAC puts it in the catalogue, beside the data. A QUAC Collection is an ordinary STAC Collection with quac: fields added.
- A Portolan catalogue with QUAC fields tells an application how to show each layer and what its form holds. QUAC and Portolan says how the two fit.
- The fields for forms, rules, relations and styles are the same for a GeoParquet file, a QGIS Server or WFS layer and an ArcGIS Feature Service. Only a field that says where the data is, such as
quac:wfs_endpoint, belongs to one kind of source. - A field that carries a setting QGIS, QField, Mergin Maps or an ArcGIS client already acts on is marked stable in the spec. A field that only one application gives meaning to is marked experimental.
- Every field is optional, so an application can read the fields it knows and ignore the rest. A missing field means the source said nothing.
Portolan sets the conventions a reader of a cloud-native catalogue relies on. QUAC follows them where they apply:
- Data and tiles. QUAC finds a layer's data by the asset's
datarole, and reads PMTiles from arel: "pmtiles"link or avisualasset, the two places Portolan registers them. - Styles. A style is a Collection asset with the
stylerole, and the default style also carries thedefaultrole, as Portolan's core specification sets out. - Fields. Portolan describes a dataset's columns with the Table extension's
table:columns. QUAC's settings for a field sit on that field's entry.
Portolan's core specification has no fields for forms, field rules, edit locks or relations between layers. QUAC adds them under the quac: prefix and leaves Portolan's fields as they are.
The package writes a catalogue as one document, with each Catalog carrying its Collections inline. It also writes a rel: "child" link to where each Collection would sit as a file of its own, ./collections/<id>.json, which is how a Portolan catalogue is laid out. The demo is published both ways.
An application can read QUAC one Collection at a time, as a STAC client opens it:
- A layer's settings are all on its Collection: its form and field rules on the Collection's
table:columns, and its locks, relations, display field and style on the Collection itself. The package'sreadCollection…functions each take one Collection (the package's README has an example). - A field that names another layer names its Collection id, such as a Value Relation's list of choices or a child layer's parent. Reading those choices or records means opening that Collection too.
- The map's own settings are on the top-level Catalog: the layer to make active, the view the map opens on, and a service's address. A group's settings are on its Catalog.
Two entries from a street-tree layer's table:columns, taken from the example catalogue that carries every field. name and type are the Table extension's; the rest are QUAC's.
[
{
"name": "species",
"quac:control": "buttons",
"quac:value_relation": {
"collection": "species",
"key": "code",
"value": "common_name",
"filter": "\"in_use\" = 1",
"allow_null": true,
"order_by": "field",
"order_field": "sort_order",
"descending": true
}
},
{
"name": "height",
"type": "double",
"quac:range": {
"min": 0,
"max": 80,
"step": 0.5,
"precision": 1,
"suffix": " m"
},
"quac:constraints": {
"not_null": "warn",
"expression": {
"expression": "\"height\" < 80",
"description": "Taller than any tree in the city",
"strength": "warn"
}
}
}
]The species field offers its choices as buttons, taken from the species layer of the same catalogue: it stores a species' code and shows its common_name. The height field takes a number from 0 to 80 metres, and a form warns when it is left blank or is 80 or more. The field reference describes every field.
Each setting below has an example under packages/quac/spec/examples/: a small QGIS project holding that one setting, the catalogue it gives, and a README naming the setting in QGIS's own words. An application that reads QGIS projects itself can open each project.qgs and check what it reads against the README, whether or not it reads QUAC.
Attributes Form, in a layer's Layer Properties:
| QGIS setting | QUAC field | Example |
|---|---|---|
| Alias | the column's title |
|
| Comment (QGIS 4.2 and later) | the column's description |
|
| Label on top | quac:label_on_top |
label-on-top |
| Value Map widget | quac:values |
value-map |
| Value Relation widget | quac:value_relation |
value-relation |
| Range widget | quac:range |
range |
| Checkbox widget | quac:checkbox |
checkbox |
| Date/Time widget | quac:date_format |
date-format |
| Attachment widget | quac:attachment |
attachment |
| Color widget | quac:color |
color |
| Hidden widget | quac:hidden |
hidden |
| UUID Generator widget | quac:editable and quac:default |
|
| Constraints | quac:constraints |
constraints, constraint-expression |
| Default value | quac:default |
default |
| Editable, unticked | quac:editable |
column-editable |
| Reuse Last Entered Value | quac:reuse_last_value |
reuse-last-value |
| Duplicate policy | quac:duplicate_policy |
duplicate-policy |
| Drag and Drop Designer: the fields placed, in order | quac:form_order and quac:in_form |
form-order |
| Drag and Drop Designer: a container's visibility expression | quac:visible_when |
visible-when |
| Drag and Drop Designer: a field's data-defined Editable | quac:editable_when |
editable-when |
The rest of Layer Properties, and the Layers panel:
| QGIS setting | QUAC field | Example |
|---|---|---|
| Fields tab: Not searchable | quac:searchable |
searchable |
| Display tab: Display Name | quac:display_field |
display-field |
| Symbology tab: a Categorized style | quac:categorised_field |
categorised-field |
| Symbology tab: Opacity | quac:opacity |
opacity |
| Rendering tab: Scale Dependent Visibility | quac:min_scale and quac:max_scale |
scale-range |
| Legend tab: Legend placeholder image | quac:legend_image |
legend-image |
| Source tab: Provider Feature Filter | quac:feature_filter |
feature-filter |
| The layer's kind of geometry | quac:geometry_type |
geometry-type |
| A layer per geometry type, from a file holding several | quac:geometry_filter |
geometry-filter |
| A table chosen from a GeoPackage | quac:layer_name |
layer-name |
| A Delimited Text layer | quac:delimited_text |
delimited-text |
| A WFS layer's CRS | quac:wfs_srs_name |
qgis-wfs-layer |
| A WMS layer's CRS and version | quac:wms_crs and quac:wms_version |
wms-link |
| A WMTS layer's tile matrix set and style | quac:wmts_tile_matrix_set and quac:wmts_style |
wmts-link |
| An XYZ connection's Max. Zoom Level | quac:max_zoom |
max-zoom |
| Layers panel: the layer's tick | quac:visibility_checked |
layer-visibility |
| Layers panel: Mutually Exclusive Group | quac:mutually_exclusive |
mutually-exclusive |
Project Properties:
| QGIS setting | QUAC field | Example |
|---|---|---|
| Relations | quac:related_to |
related-to |
| Data Sources: Read-only | quac:editable |
editable |
| Data Sources: Identifiable | quac:identifiable |
identifiable |
| Data Sources: Private | quac:private |
private |
| General: units for area and distance | quac:measurement |
measurement |
| The map view saved with the project | quac:initial_view |
initial-view |
| QGIS Server: a layer's published names | quac:qgis_server_wms_name and quac:qgis_server_wfs_type_name |
server-names |
| QGIS Server: WMS CRS restrictions | quac:wms_crs |
server-wms-crs |
The field apps' QGIS plugins, which save their settings in the project:
| Setting | QUAC field | Example |
|---|---|---|
| QFieldSync: Initial active layer | quac:active_collection |
active-collection |
| QFieldSync: Disable feature addition, attribute editing, geometry editing or deletion | quac:locks |
locks |
| Mergin Maps: filters | quac:filters |
filters |
QUAC's own layer variables, for what QGIS has no setting for:
| Variable | QUAC field | Example |
|---|---|---|
quac_icon, for the layer |
quac:icon |
layer-icon |
quac_icon_<field>, for a field |
quac:icon |
column-icon and icon-other-library |
quac_control_<field>, buttons or a dropdown |
quac:control |
control |
The field reference gives each field's full shape, and the fields that other sources, such as WFS and ArcGIS, write.
The site publishes a small made-up catalogue of street trees, their species and their inspections, from the QGIS project beside it. A STAC client can open it from that address. Its README lists what each field of the trees layer shows.
QUAC says what an edit may do: which fields can be changed, what each accepts, and which edits are locked. It does not say how an edit is saved. That is left to the application and the source, such as a WFS-T service or a file the application can write to.
The JavaScript package makes no network request. It builds a catalogue from what an application has already fetched, such as a QGIS project's text or a QGIS Server GetProjectSettings response, and reads a catalogue it is given.
The schema is packages/quac/src/schema/quac.schema.json, a JSON Schema (draft-07) whose $id is https://vectoriahq.github.io/quac/v0.3.0/schema.json. Any draft-07 validator checks a Catalog with its Collections inline, or a single Collection, against it. It checks only quac: fields: any other field passes, and a quac: field the schema does not define fails. A catalogue says it follows QUAC by listing the schema's address in stac_extensions.
- The spec, the field reference and its per-field examples:
packages/quac/spec/. - The JavaScript package,
@vectoriahq/quac, which writes QUAC catalogues from QGIS projects and other sources and reads them back:packages/quac/. - The QGIS Server plugin, which serves a project's QUAC catalogue from QGIS Server at
SERVICE=QUAC&REQUEST=GetCatalogue&MAP=<project>, with the Python port of the JavaScript reader it is built on:packages/quac-qgis-server/. It is in the QGIS plugin repository as QUAC Catalogue. - The site's front page and the demo catalogue, published at
https://vectoriahq.github.io/quac/:site/.
| Implementation | Writes | Reads |
|---|---|---|
@vectoriahq/quac, JavaScript |
from QGIS projects, QGIS Server, WFS, OGC API Features, ArcGIS, and folders and files of data | each Collection's settings |
| QUAC for QGIS Server, a QGIS Server plugin in Python | from a project QGIS Server publishes | |
| Groundwork, Vectoria's web app | through @vectoriahq/quac |
every map it opens, through @vectoriahq/quac |
An application that reads or writes QUAC can be listed here: open an issue naming it.
QUAC began inside Groundwork, Vectoria's web app for capturing and editing spatial data. Groundwork reads each source a map connects to, from a QGIS project to an ArcGIS Web Map or a STAC catalogue, as a STAC catalogue, and QUAC holds what STAC has no field for. Groundwork is QUAC's first reader, which is why the spec marks a field experimental where Groundwork alone gives it meaning.
QUAC is pre-1.0. The JavaScript package is on npm as @vectoriahq/quac, and the QGIS Server plugin is in the QGIS plugin repository as QUAC Catalogue.
Copyright 2026 Vectoria Pty Ltd.
- The spec, the schema, the examples and the JavaScript package are under the Apache License 2.0, the licence of the STAC specification and its extension template.
- The QGIS Server plugin,
packages/quac-qgis-server/, is under the GNU General Public License, version 2 or any later version, as the QGIS plugin repository asks of a plugin.