How to Find Geospatial Data Where It Lives: Inside Voyager's Data Connectors
Introduction
Most spatial data isn’t on a map. Voyager’s data connectors reach ArcGIS, OGC services, SharePoint, databases, cloud storage and open data catalogs, index the data where it lives, and find the location in all of it, so you can search everything you have by place.

Date
11.16.26
Author
Voyager Search
Type
Product
Most spatial data isn't on a map.
It's in a thirty-year-old field report on a file share. It's a bridge inspection PDF in SharePoint. It's a borehole record in an Oracle table, a survey on Amazon S3, a dataset listed in someone else's catalog. All of it describes a place. Almost none of it is searchable by place.
The data exists. It always does. The problem is everything after collection.
Why is geospatial data so hard to find?
Geospatial data is hard to find because it lives in two kinds of systems that were never built to work together.
The first kind is GIS: ArcGIS Online and Portal, ArcGIS Server, OGC web services, geodatabases and shapefiles. These systems understand location, but they only see data that's already a map layer.
The second kind is everything else: document libraries, file shares, databases and cloud storage. These systems hold most of an organization's information, including reports, permits, inspections and spreadsheets that are about specific places. They don't understand location at all.
So teams search one system at a time, miss what they can't see, and re-collect or re-buy data they already own.
What is a data connector?
A data connector is the component that reaches into a source system, such as SharePoint or ArcGIS Server, and reads its contents so they can be indexed and searched. In Voyager, connectors index data where it lives. Nothing is moved, migrated or duplicated.
Voyager's connectors cover four groups of sources:
GIS and spatial services | ArcGIS Online and Portal, ArcGIS Server, Map and Feature Services, OGC WMS, WFS and WMTS, STAC, Esri geodatabases, shapefiles, GeoJSON |
Documents and storage | Microsoft SharePoint, Office 365, Azure Blob Storage, Amazon S3, Box, Dropbox, Google Drive, FTP, file shares |
Databases | PostGIS, Oracle Spatial, Oracle, SQL Server, PostgreSQL, MySQL, any JDBC database, CSV |
Open data catalogs | CKAN, DCAT, OGC Catalog Service for the Web (CSW), Project Open Data, GBIF |
How does Voyager find location in documents and databases?
Voyager finds location in documents and databases by reading each item, then enriching it with location before it reaches the search index.
Connect. A connector reaches the source and walks through its contents in place.
Extract. Each item goes to an extractor built for its format. The extractor reads it: the text of a report, the fields of a database record, the footprint of a map layer.
Enrich. Voyager adds location, context and consistent metadata. Place names in the body of a PDF are matched to real locations, a process called gazetteering.
Index. The enriched record goes into a single index that can be searched by place, topic and time.
A PDF that mentions three counties becomes findable on a map, right next to the layers your GIS team publishes.
How is this different from a data catalog or a GIS portal?
Voyager differs from both because it combines their strengths.
Data catalogs connect to many systems, but they list what exists. They don't read location inside the content.
GIS portals understand location, but they only connect to GIS sources.
Integration tools move and transform data between formats. Voyager leaves data where it is.
Voyager connects broadly and understands location in every format. That's what lets teams find the right data for the question they're actually asking, not just a list of everything that exists.
What can teams do with it?
Transportation: find every inspection, as-built and project file for a corridor, including the PDFs, next to the GIS layers.
Science agencies: search agency holdings, STAC catalogs and open data together before starting a new collection.
Mining: find decades of scanned reports, drill logs and surveys for a tenement before anyone drills.
The data was always there. Voyager finds it, so you can finally put it to work.
FAQ
What is Voyager Search? Voyager Search is an enterprise software company that turns geospatial and enterprise data into an intelligence layer for real-world decisions. Since 2008, it has helped government agencies and enterprises find, index and enrich their spatial data.
Does Voyager move or copy my data? No. Voyager's connectors index data where it lives. Systems of record stay in place.
Which GIS systems does Voyager connect to? ArcGIS Online, Portal for ArcGIS, ArcGIS Server, Esri Map and Feature Services, geodatabases and shapefiles, plus OGC WMS, WFS, WMTS and STAC, and the PostGIS and Oracle Spatial databases.
Can Voyager find location in PDFs and Word documents? Yes. Extractors read the text, and enrichment matches place names to real locations so documents become searchable by place.
Does Voyager support open data catalog standards? Yes: CKAN, DCAT, OGC CSW, Project Open Data and GBIF.
Can Voyager add a custom connector for a system not on the existing list? Yes. Our team of Customer Solution Architects will work with your team to assess so new connectors can be built.
start a conversation

