Build with VertiGIS Studio Search

VertiGIS Studio Search delivers fast, configurable search across millions of GIS features. Users can quickly find data using advanced indexing and tailored results. With flexible deployment (SaaS or on-premises), simple management tools, and support for large datasets, it streamlines data exploration while saving time and resources.

1. Integrate Studio Search with Studio Web (10-minute read)

   • VertiGIS Studio Search can be integrated with VertiGIS Studio Web to deliver faster search results and greater control over search fields, behavior, and results while preserving the familiar Studio Web experience. The recommended approach is Option A (Native Integration), where you create a Search configuration using the VertiGIS Studio Web type, add the Studio Search URL in the Web Designer Services tab, and enable VertiGIS Studio Search for selected layers through Layer Extensions. Detailed search settings are then managed in Studio Search Designer. Option B uses a Search Workflow template and requires additional setup, including configuring a Studio Search app, access tokens, workflows, and app integration.

2. Configure Reindexing Options (5-minute read)
   • Reindexing options in VertiGIS Studio Search help keep search results synchronized with source data. You can configure automatic updates using a Change Date Field, which tracks record edits and updates the index incrementally. Data Integrity Checks periodically compare indexed data with source records and flag discrepancies. You can also schedule full reindexing on specific days and times. Because reindexing can be resource-intensive, configure only the options needed for your environment.
3. Designer UI Concepts  (15-minute read)
   • The three main components of the Search Designer are the Sidebar, New Search Configuration and Configured Searches. 
4. How to Deploy VertiGIS Studio Search Configurations Across Deployment Stages (15-minute read)
   • By default, deployed VertiGIS Studio Web apps use the original VertiGIS Studio Search configuration to avoid duplicate indexes. If separate search indexes are needed per environment (dev, test, prod), create a Universal Search configuration for each environment and use Environment Values in Web Designer to map environment-specific Search Config IDs, tokens, subindex IDs, service URLs, and portal item URLs. After deployment, values are automatically replaced so each app uses its own search index. Add new subindex entries whenever new searchable layers are configured.
5. How to avoid missing search indices due to expired tokens on secured resources that have been configured via Web Designer (5-minute read)
   • VertiGIS Studio Web can automatically create Search resources for secured layers, but the access token used for indexing expires over time. To keep the search index healthy, open each newly created secured-layer resource in VertiGIS Studio Search Designer and save it after creation, even if no changes are needed. This refreshes the required Esri token and allows future reindexing. Repeat this for every secured layer added to Search. Periodically reopening and saving resources may also be required to prevent token expiry and reindexing failures.
6. Enabling Cross-Origin Resource Sharing (CORS) for On-prem Installations of VertiGIS Studio Search (10-minute read)
   • If VertiGIS Studio Search is installed on-premises and accessed from a different origin than VertiGIS Studio Web (such as SaaS Web or separate on-prem servers), CORS must be enabled. Edit the Search backend .env file, uncomment or add the required %search-api.quarkus.http.cors settings, and specify the allowed Web app origin(s) in cors.origins. Save the file and restart the VertiGIS Studio Search Engine (API) service. Once configured, Web apps should be able to access Search without CORS-related errors.
7. Search Product Showcase (58-minute view) 
   •  
8. Search Release Notes
   •  
9. Search FAQ document (
   • pdf below
10.  Tutorial – Create a Search App
    •