The page of an item

Click any row in the Datastore to open the page of that item. Layers, files, web maps and web apps all use the same page: what changes between them is the detail, not the shape.

Everything on this page is edited where it is read. There is no separate edit form and no Save button at the bottom: click a value, change it, and it is kept.

The header

At the top of the page:

The mark, on the left. A layer or a file shows the format it is stored in; a web map or a web app shows its picture.
The name, which you can rename by clicking it.
The star, which files the item in your Favorites. It is personal to you.
The description, under the name. Write what the next person needs to know: where the data comes from, what it covers, what to watch out for.

Next to the tabs sit the actions the item allows: open it in the map viewer, open a web app in the App Builder, download it, transfer its ownership, delete it.

Download asks you to confirm first, because downloading draws on your organization’s monthly egress allowance. If the item has no stored file, a web service reference or a web app project, the button says so rather than failing silently. If your role does not allow taking data out, the button stays visible and disabled, with the reason.

Transfer ownership reattributes the item to another member. It is offered to organization admins and owners.

Details

The first tab holds the properties of the item and, below them, two cards.

Sharing is the one control that decides who else can reach this item. It has its own page: Sharing.

What uses what shows the item’s graph in the direction that makes sense for it. A web map or a web app lists the layers it consumes. Anything else lists the web maps and web apps that consume it. Each entry opens the other item’s page, which is worth a look before you delete or restrict something.

An item referenced here that you cannot read, or that no longer exists, is shown as not available rather than hidden. A map that points at something you cannot see is a fact about the map.

Metadata

The second tab is the metadata sheet of the item. It exists so that a layer still makes sense to someone who did not create it, months later, and so that your catalogue can be searched on more than a file name.

Four kinds of value sit side by side, and the difference matters before you type:

Yours, which you fill in and edit in place.
Inherited from your organization’s defaults, marked with a chip. The editor opens empty: clearing a field hands it back to the organization.
Enforced, an inherited value your organization made a rule. It is marked, and it has no editor.
Derived from the data itself: coordinate reference system, extent, feature count, format, revision date. These are read from your file and cannot be typed over.

The title is shown here but edited in Details, so that one value never has two places to change.

If your organization leaves it to you, an AI draft can pre-fill some fields for you to review. A drafted field opens with the suggestion in it, nothing is recorded unless you actually change something, and clearing a field keeps it cleared.

Indexing an item for the AI Assistant

When your organization has turned off automatic indexing, an item can still be indexed one at a time, from this tab, by whoever can edit it. Indexing lets the AI Assistant find the item by meaning rather than by name. Before anything leaves, a dialog states what is sent: a compact profile of the item, not its features.

OGC API

The third tab publishes a layer as a standards-based web service, so that QGIS, another GIS or a colleague’s application can consume it directly.

From here you can publish the layer as a new service in one click, or add it to an existing service. The tab lists the services that already expose this layer.

Everything else about a service, its address, its access keys and who may reach it, is managed on the service’s own page, so there is a single place where a service is configured. See OGC services.

Datastore: the listing, folders, exports and the trash.
Sharing: who can reach this item, and what changes when you restrict it.
OGC services: publishing a layer for QGIS and other GIS software.
QGIS plugin: how an item published from QGIS gets its provenance, its style and its metadata.
Web maps: what a saved map carries, and how it is published.