Dataset Detail

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), upstream sources, member datasets (for parent datasets), 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>#members
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.

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 (default 50, max 1000).
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%	Valid geometries, no self-intersections, consistent winding
Attribute completeness	25%	Non-null rates per attribute; presence of an ID column
CRS specificity	15%	EPSG declared (vs. unknown/unspecified); recognized CRS

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 in EPSG:4326 (always — the bbox is normalized regardless of native CRS).
Feature/row count — total number of features (vector) or pixel dimensions (raster).

For raster datasets, the structure tab also shows band count, pixel size, data type (e.g., Float32, UInt16), and any band-level metadata (min/max/mean per band).

Sources tab

The sources tab shows where this dataset came from — its provenance and ingestion lineage:

Original source URL or filename — the file uploaded, the WFS/ArcGIS/OGC service URL registered, or the upstream collection it was derived from.
Ingestion log — timestamped events from the import job: file received, validation passed, schema detected, geometry indexed, ingestion complete.
Re-import history — every time this dataset was updated by a re-import (a new file pointed at the same dataset ID), there’s a row here showing who, when, and what file/URL.
Derivation chain — for datasets created by transformation (e.g., a buffer, a clip, a join result), the chain of upstream datasets used.

The sources tab is your audit trail. When data quality is in question, this is where you start.

Members tab

The members tab is only visible for parent datasets — special datasets that act as containers for related sub-datasets (e.g., a multi-file collection, a time-series dataset where each timestep is its own dataset, or a virtual mosaic of raster tiles).

For ordinary datasets, the members tab is hidden. For parent datasets, it shows the list of member datasets with their per-member metadata and quick links to each member’s own detail page.

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.
GeoTIFF (.tif) — raster export.
Live OGC API URL — a URL you can plug into QGIS, GDAL, or a Python client.

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.

Below the tabs, the Related datasets section surfaces other catalog entries that are conceptually similar:

Datasets sharing tags
Datasets in the same collection
Datasets with overlapping spatial extent
Datasets the same owner uploaded

The matching is heuristic — useful for browsing, not authoritative. For a deterministic similarity-based match, 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.