Dataset Detail

Ce contenu n’est pas encore disponible dans votre langue.

A dataset is the unit of content in GeoLens: every layer on a map, every record in a search, every export comes from a dataset. The detail page is where you see all of it: a quick overview, the actual feature rows, the full metadata form, the structure (columns, CRS, extent), the source COGs behind a virtual raster, and the access controls that govern who can see what.

Tabs

The detail page uses a tab strip across the top. Tabs are URL-hash-driven, which means each tab has its own deep-link URL:

https://your-instance/datasets/<id> (defaults to Overview)
https://your-instance/datasets/<id>#overview
https://your-instance/datasets/<id>#data
https://your-instance/datasets/<id>#metadata
https://your-instance/datasets/<id>#structure
https://your-instance/datasets/<id>#sources
https://your-instance/datasets/<id>#access

Bookmarking a tab-specific URL takes you straight to the right view: useful for handing a colleague a “look at this metadata” link, or for embedding a preview deep-link in a ticket.

Not every tab appears for every dataset. Overview, Metadata, and Access are always present; Data and Structure appear for vector and table datasets; and Sources appears only for virtual-raster (VRT) datasets. Deep-linking to a tab that isn’t shown for a given dataset falls back to Overview.

Overview tab

The overview tab is the dataset’s at-a-glance card:

Map preview: a small interactive map showing the dataset’s spatial extent and (for vector layers) a styled preview of the geometry. The preview uses default styling; for full styling control, open the dataset in the Map Builder.
Summary card: title, description, owner, last-updated timestamp, feature/row count, and primary geometry type.
Quality score badge: a 0-100 score reflecting metadata completeness and structural integrity (see the Quality score section below).
Quick actions: Add to map, Add to collection, Export, Edit metadata (if you have permission), Re-import (likewise).

The overview is intentionally minimal so you can see whether you’ve found the right dataset before diving into specifics.

Data tab

The data tab is a table view of the actual feature attributes: one row per feature, one column per attribute. It’s deliberately spreadsheet-like to make ad-hoc inspection fast.

Sorting: click any column header to sort ascending; click again for descending.
Filtering: use the search box above the grid to text-match across all columns, or apply per-column filters from the column-header menu.
Pagination: the data tab paginates large datasets; the footer shows current page and total row count. Use the page-size dropdown to adjust how many rows render at once (25, 50, or 100; default 50).
Geometry preview: clicking a row opens a side panel with that feature’s geometry highlighted on a small map.

The data tab is read-only in the UI. To edit feature attributes, export the dataset, edit externally, and re-import. See Importing data for the round-trip flow.

Metadata tab

The metadata tab is the editable metadata form. If you have the editor role on this dataset, every field is editable inline; if you’re a viewer, fields appear read-only.

Standard metadata fields:

Title: short, human-readable name (required).
Description: markdown-supported longer description (required for full quality score; see below).
Tags: comma-separated; auto-completes against the catalog’s tag set.
License: choose from the configured license list.
Owner: defaults to the uploader; can be reassigned by an admin.
Spatial extent: automatic from feature geometry; can be manually overridden.
Temporal extent: start/end timestamps for time-aware datasets.
Custom fields: anything your administrator has configured as a custom metadata field.

Quality score

The quality score is a 0-100 number computed from four dimensions, each weighted as it appears on the metadata tab:

| Dimension | Weight | What’s checked | |-----------|:---:|---| | Metadata completeness | 30% | Title, description, tags, license, attribution, contact | | Geometry integrity | 30% | Percentage of valid geometries (ST_IsValid) | | Attribute completeness | 25% | Non-null rates per attribute; presence of an ID column | | CRS defined | 15% | A CRS/SRID is declared (yes/no) |

Hovering the quality score shows the breakdown by dimension. Improve a low score by filling in missing metadata, fixing geometry errors at re-import time, or declaring a CRS during import. A score above 80 is generally fine for production sharing; below 50 is a warning sign and worth investigating.

Structure tab

The structure tab is the dataset’s schema view: useful for confirming a dataset’s columns before exporting, joining, or building against it.

Columns: name, type (text, int, numeric, date, bool, geometry), nullable, and a sample value pulled from the first non-null row.
Coordinate Reference System (CRS): the EPSG code (e.g., EPSG:4326, EPSG:3857, EPSG:32610). Knowing the CRS matters before you export to a format that’s CRS-sensitive (Shapefile, GeoTIFF) or before you join to another dataset.
Bounding box: the dataset’s spatial extent, always in EPSG:4326 (the bbox is normalized regardless of native CRS).
Feature/row count: total number of features in the dataset.

The structure tab is shown for vector and table datasets only.

Sources tab

The sources tab appears only for virtual-raster (VRT) datasets and only when you are signed in. It manages the member COGs that make up the virtual raster:

Member COGs: the list of source Cloud-Optimized GeoTIFFs behind the VRT, each with its CRS, resolution, and band count.
Add / remove sources: editors can add another raster (COG) dataset from the catalog as a source, or remove an existing one.
Regenerate: rebuild the VRT after changing its sources.
Generation history: past VRT builds with their status, so you can see when the mosaic was last regenerated.

For non-VRT datasets, there is no sources tab.

Access tab

The access tab shows who can see and edit this dataset, and is the place to manage that visibility:

Visibility: one of public, private, or restricted.
- public means anyone (including unauthenticated visitors, if the instance allows that) can see the dataset.
- private means only the owner (and admins) can see it.
- restricted means the owner has explicitly granted access to specific users or groups.
Access list: for restricted datasets, the list of users/groups with access, plus their permission level (read-only or read-write).
Audit log: recent access events (who viewed, who exported, who edited).

If you encounter a restricted dataset and need access, the access tab shows the owner. Request access from them. If your administrator has set up automatic role-based access (e.g., everyone in the “analysts” group has read access to the “operations” tag), that mapping shows up here too. See User management & RBAC for the admin-side of how restricted access works.

The export menu is reachable from the Export button in the page header (top-right) and is identical regardless of which tab you’re on. Common formats:

GeoPackage (.gpkg): vector with metadata + style preserved; the best general-purpose format.
GeoJSON (.geojson): portable, web-friendly; good for embedding in another system.
Shapefile (.zip): legacy GIS interop; required by some older tools.
CSV (.csv): tabular only; geometry is preserved as WKT in a single column.
Live OGC API URL: a URL you can plug into QGIS, GDAL, or a Python client.

Raster datasets aren’t part of this vector export menu. Download them as a Cloud-Optimized GeoTIFF from the dataset’s detail page instead.

You can apply filters at export time (bbox, CQL2 attribute filter, CRS reprojection) so the exported file is a subset rather than the entire dataset. See Exports & Integrations for the full reference, including machine-client examples.

Ask AI about this dataset

When AI features are enabled on the instance and your role holds the use_ai_chat capability, an Ask AI button appears on the dataset detail page. It opens a chat panel scoped to this one dataset, so you can ask questions in plain language instead of writing a filter or export first:

“How many features are there, and what’s the range of the population column?”
“Which records have no name?”
“Show the ten largest polygons by area.”

The panel is read-only: the assistant queries the dataset’s data to answer, but it never edits attributes, metadata, or access. When an answer comes from a query, a compact result table appears beneath the reply.

For datasets with geometry, a result also offers Open in builder — this creates a new map and opens the Map Builder with this dataset added and the query’s matching features carried in, so you can style and share what the answer surfaced. Non-spatial tables can still be chatted with, but have no map handoff.

Below the tabs, the Related datasets section surfaces other catalog entries that are conceptually similar, such as datasets sharing tags or with overlapping spatial extent.

The matching is heuristic: useful for browsing, not authoritative. To find related datasets on your own terms, run an explicit search with the same tags or in the same bbox; see Search & Discovery.

Change history

The change history block (visible at the bottom of the overview tab when expanded) is a timeline of edits to this dataset:

Metadata edits (who, when, what fields changed)
Re-imports (who, when, source file/URL)
Permission changes (who, when, granted-to)
Visibility changes (e.g., private -> restricted)

Change history is filtered to events on this dataset only. The instance-wide audit log lives under Admin -> Audit Log and requires admin permissions.