> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/integrations-and-api/external-map-layers/civillo-set-up-guide.md). # Connect Civillo Layers {% hint style="info" %} **Things to know before you get started:** * This feature is available on Pro+ or Enterprise plans * You need to be a Project Admin to set up the integration * Aphex supports two Civillo layer types: ESRI Vector Tile Service and WMTS * WMTS is a paid-premium feature in Civillo. Check with your Civillo Customer Success Manager if you're unsure whether your account has access. {% endhint %} If your team uses Civillo to manage geospatial data (utilities, design models, boundaries, work zones, and permits) you can bring those same layers directly into Aphex. The Civillo integration lets your site teams access up-to-date spatial context right alongside their short-range plan, without switching between systems. This guide walks you through how to retrieve your Layer URL from Civillo, add it to your project in Aphex, and set a Layer Policy where applicable. ## Publishing the Layer in Civillo *** {% hint style="warning" %} WMTS is a paid-premium feature in Civillo. Check with your Civillo Customer Success Manager if you're unsure whether your account has access. {% endhint %} #### Initiate the Publishing Process 1. Navigate to your project space in Civillo and select the desired layer you wish to publish. 2. From the selected layer's view, click the three-bar menu to access the admin view. 3. Go to Administration > Layers > Edit. 4. Scroll to the bottom of the page to find the Published Layer box. 5. Click the box to initiate the publishing process. #### Access the Published Layers After you trigger the publishing process, you'll receive an email notification that is essential for accessing your published layers: * Locate the email from Civillo that confirms the layer publishing has started. * This email contains a direct link to the project's publishing page. This link is important because the publishing area can be difficult to access through standard navigation. * Save or bookmark this URL for future use. The page provides a summary of all published layers within your project. ## Retrieving the Layer URL *** Once you have published the layer, you will be able to copy the layer URL to paste into Aphex. All Civillo layer URLs are accessed through your Civillo Publish portal.
Navigate to your project, then choose the service type you need. Civillo exposes its geospatial data through two service types that Aphex supports:
Service TypeDescription
ESRI Vector Tile Service Vector data including design models, utilities, boundaries, and work zones. These layers do not require credentials in Aphex and connect directly without a login. Layer Policy and Quantity options are not available for this layer type.
Web Map Tile Service Pre-rendered raster imagery such as aerial photography. These layers follow the same rules as other WMTS connections in Aphex, including Layer Policy support.
#### To retrieve your Vector Tile Layer URL: * Log in to your Civillo Publish portal and open your project * Click ESRI Tile Service. This opens the ArcGIS REST Services Directory, listing all available layers with their service name and code * Locate your layer by name, then click into it to open the layer detail page * Click in the top-right corner to view the layer in JSON format * Copy the `url` value. This is the Layer URL you'll use in Aphex A Civillo Vector Tile URL will appear in a format similar to the below; {% code overflow="wrap" %} ``` https://pub.civillo.com///arcgis/rest/services//VectorTileServer ``` {% endcode %} #### To retrieve your WMTS URL: * Log in to your Civillo Publish portal and open your project * Click Web Map Tile Service. This opens a list of available imagery datasets for the project * Click in the top-right corner * Copy the URL from your browser's address bar. This is your WMTS Capabilities URL A Civillo WMTS URL will appear in a format similar to the below; {% code overflow="wrap" %} ``` https://pub.civillo.com//wmts/WMTSCapabilities.xml ``` {% endcode %} ## Adding Layers to the Map *** Once you’ve got your Layer URL handy, you can plug it into any real-world Location in your Project.
Visit our Add Map Layers doc for step by step instructions on how to add layers to the Map. {% hint style="info" %} **Vector Tile layers** connect without credentials - you won't be prompted to log in and no Layer Policy options will appear.\ \ **WMTS layers** may prompt you to select credentials if the layer requires authentication, and support Layer Policy configuration. {% endhint %} ## Setting a Layer Policy (WMTS Only) *** Layer Policies apply to Civillo WMTS layers and control which sublayers are brought into your project. They do not apply to ESRI Vector Tile Service layers. Visit our Layer Policies doc for step by step instructions on how to define a layer policy. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.aphex.co/docs/integrations-and-api/external-map-layers/civillo-set-up-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.