Metadata can give you away
Hiding the features is not enough if the metadata tells people what and where they are. GIS portals, web maps, files and services often expose descriptive information that users overlook during a sensitivity review.
What can leak
| Metadata | Possible disclosure |
|---|---|
| Dataset title | identifies a sensitive subject or locality |
| Description | explains what the hidden layer contains |
| Thumbnail | shows the landscape or map extent |
| Geographic extent | narrows the search area |
| Owner or author | identifies a knowledge holder or researcher |
| Tags | reveal cultural categories |
| Attachment filename | contains a person or place name |
| Service URL | exposes a backend endpoint or layer name |
| Field names | reveal that restricted categories exist |
| Schema | exposes relationships or classifications |
| Edit history | identifies who supplied or changed information |
| File path | exposes machine, share or database names |
| Search index | makes an otherwise obscure item discoverable |
A layer called Restricted_Sites_Final is not harmless metadata merely because the geometry is private.
Web GIS creates an item as well as a map
Modern GIS platforms frequently store an item record containing title, owner, thumbnail, description, tags, extent and other details. That item can have different visibility from the underlying feature service or map.
This creates two reviews:
- can the user access the spatial data?
- what can the user learn from the item, catalogue or search metadata?
Both matter.
Extent can be sensitive
A bounding box can reveal a small search area even where precise coordinates are hidden. A thumbnail may do the same visually.
For highly sensitive material, a generic thumbnail and non-locational description can be safer than automatically generating a preview map.
Filenames survive longer than expected
Attachments, exports and emailed files often retain names created for internal work. Before external sharing inspect:
- attachment names
- zipped folder names
- layer names
- database table names
- PDF titles
- image EXIF metadata
- embedded document properties
A well-generalised map can still be undermined by Urupa_exact_locations.xlsx sitting beside it.
ArcGIS item details
Esri's current ArcGIS Online documentation confirms that item details can include title, summary or description, owner information, thumbnail, tags and geographic extent. Esri also documents metadata-management and export tools because machine paths, database information and other details may need to be removed before metadata is shared externally.
The practical lesson is not specific to Esri. Any catalogue or portal should be reviewed as an information source in its own right.
A metadata publication review
Before releasing a sensitive map or service:
- Search the portal while signed out.
- Check the title and description.
- Inspect the thumbnail.
- Inspect the displayed extent.
- Review owner and author names.
- Review tags and categories.
- Check attachment filenames.
- Inspect service and API endpoints where visible.
- Review field names and pop-up configuration.
- Download a permitted export and inspect its embedded metadata.
- Check search-engine indexing if the item is public.
Do not assume the map viewer is the only place a user will encounter the item.
Public and internal metadata can differ
An organisation may need rich internal provenance while exposing a smaller public metadata record. Preserve the authoritative metadata internally. Create a public-safe description deliberately rather than deleting source context from the authoritative record.
Related pages
Sources
Last verified: 16 August 2026
Māori GIS example
For an iwi or hapū project, the map can be hidden while its title, thumbnail, extent or item description still reveals the kaupapa or place. This is especially relevant to whenua, marae and historical-research collections. Pair this page with Metadata and documentation and Map sharing and data access.