# Limitations and troubleshooting

What published services deliberately do not do, and what to check when something looks wrong.

# Limitations

# Read-only

Published services serve data out; they never take data in. All three services accept GET requests only. There is no editing, no transactional WFS, and no way to write back to a Civillo layer through a published service. Changes are made in Civillo and flow outwards.

# One layer, several collections

OGC API - Features requires a single geometry type per collection, so a Civillo layer containing points, lines, polygons and text publishes as up to four collections. See Collections and collection IDs. The ESRI Vector Tile Service does not split the layer.

Only point, line, polygon and text geometries are published.

# Fixed output projection for features

Features from OGC API - Features are always returned in EPSG:4326. A bbox you supply may be in EPSG:4326 or EPSG:3857 only. To get data in another projection, use Convert to a file, which offers several export projections.

Vector tiles and WMTS tiles are served in EPSG:3857 (Web Mercator). Imagery layers additionally publish a GDA94 variant - see GDA2020 and GDA94.

# No time or attribute-value filtering

There is no temporal filtering (a datetime parameter is rejected) and no CQL filter parameter. You can filter spatially with bbox, restrict which attributes come back with properties, and sort with sortby; anything more selective needs to happen in your client.

# Not a full GIS server

The ESRI service is a Vector Tile Service, not a Feature Service or Map Service: it renders and styles, but it cannot be queried or edited. WMTS serves pre-rendered tiles only. If you need attribute-level access, use OGC API - Features.

# Access is by URL

Published services do not require a Civillo sign-in. Anyone with the service URL can read the published data. Treat the URL accordingly - see the warning in Published GIS services.

# Troubleshooting

The Publish layers feature is enabled per project. If Integrations → Publish GIS services is missing, either the feature is not enabled on this project, or your account lacks project administrator rights and the Layer create/edit group role. Refer to Before you start.

# A layer is not in the list of publishable layers

Only vector layers and uploaded imagery layers can be published. Terrain layers and online imagery service layers (WMS/WMTS/XYZ layers that Civillo itself consumes from a third party) are not eligible.

Layers that reach the project through a project link as destination layers are also excluded - publish them from the source project instead.

# The published data is out of date

Revising a layer re-publishes it automatically, but the job takes time to run and clients cache tiles and responses. Check the Publish GIS services page to confirm the job completed, then clear the cache in your client or reload the layer.

If the job did not run, toggle the layer off and back on to force a fresh publish.

# A collection returns no features

A vector layer only produces a collection for the geometry types it actually contains, and only once it has at least one valid feature. Check you are using the right collection ID for the geometry you expect - L28PY for polygons will be empty if the layer only holds lines.

An unrecognised collection ID returns an empty feature collection rather than an error, so a typo in the ID looks the same as an empty layer.

# A request returns 401 Unauthorized

The service returns 401 when the organization or project part of the URL is not recognised, as well as for a malformed path. Re-copy the service URL from the Publish GIS services page rather than editing it by hand.

# A publish job failed

The error appears on the layer's row on the Publish GIS services page and the toggle becomes available again so you can retry. If a retry fails the same way, raise it with Civillo support and quote the project and layer name.

← Using published services in other applications Load your own files →