Skip to main content
Public map layers allow residents to view geographic data on your public website without signing in. By making specific map layers public, you can share infrastructure, flood zones, facilities, and other community information transparently with residents. Public map layers are custom map data that your Customer Success Manager configures to be visible to anyone accessing your public website—no login required.
FeatureDescription
No authentication requiredAnyone can view public map layers without signing in
Interactive mapsResidents can zoom, pan, and explore geographic features
Read-only accessResidents can view data but cannot edit or modify anything
Layer controlResidents can toggle public layers on and off in the layers panel
Mobile-friendlyWorks on all devices with responsive design

Common use cases

Make map layers public to promote transparency and help residents access community information:
  • Infrastructure systems - Show stormwater assets, facilities, or utility networks
  • Flood zones - Display FEMA flood zone boundaries for resident lookup
  • Community boundaries - Share neighborhood, district, or service area boundaries
  • Points of interest - Highlight parks, facilities, and public resources
  • Historical data - Show previous flood events or other historical information

How public map layers work

When you make a map layer public:
  1. Your Customer Success Manager configures the layer to be visible to guest users
  2. The layer appears in the public layers panel on your website
  3. Residents can toggle the layer on and off alongside other public data
  4. Features are viewable but residents cannot edit or modify any data
  5. The layer works with public table views, search, and other public website features
Residents access public map layers through:
  • Your public website homepage with embedded maps
  • Public table views that include map toggle features
  • Direct links to map-based public content

Making a map layer public

To make a custom map layer visible to residents, work with your Customer Success Manager.

Request process

1

Identify the layer

Determine which map layer you want to make public. Consider:
  • Is this information already public record?
  • Will residents find this data useful?
  • Does it promote transparency?
  • Is the data current and accurate?
2

Contact your Customer Success Manager

Reach out to your CSM and provide:
  • Layer name - Which map layer you want to make public
  • Purpose - Why you want to share this data publicly
  • Restrictions - Any specific features that should remain hidden
  • Context - How residents will use this information
3

CSM reviews and configures

Your Customer Success Manager will:
  • Review the layer for public-appropriate content
  • Configure the layer visibility settings
  • Test the public experience
  • Confirm the layer is ready
4

Layer becomes available

Once configured, the layer appears in the public layers panel for all residents to use.
Your map layer is now visible to residents on your public website. They can toggle it on and off in the layers panel.

What to discuss with your CSM

When requesting a public map layer, be prepared to discuss: Data sensitivity - Confirm the layer contains only public information with no sensitive or private data Feature-level hiding - Whether specific features within the layer should remain hidden from public view Styling and appearance - How the layer should look (colors, opacity, labels) for public viewing Legend and description - Whether the layer needs a legend or explanatory text for residents Integration - How the layer should work with public table views or other public website features Updates - How often the layer data changes and whether it needs regular updates

What residents can do with public layers

When residents access your public website, they can:

View and explore

  • Open the map - Access the interactive map on your public website
  • Toggle layers - Open the layers panel and turn public layers on and off
  • Zoom and pan - Navigate around the map to explore different areas
  • Switch basemaps - Choose different background map styles

Interact with features

  • Click on features - Click map features to view basic information
  • View details - See attributes and data you’ve made public
  • Search - Search for addresses or locations on the map
  • Geolocate - Center the map on their current location

Use with public table views

  • Combine with tables - View public map layers alongside public table data
  • Filter and explore - Use table filters that affect what appears on the map
  • Switch between views - Toggle between table and map views of public data
Public map layers work best when combined with public table views, giving residents both geographic and structured access to your data.

Restrictions and limitations

Not all map layers or features can be made public. Your Customer Success Manager will help ensure appropriate data sharing.

Layers that cannot be made public

  • Internal workflow layers - Task tracking, administrative data
  • Sensitive infrastructure - Security-critical facilities or systems
  • Private property data - Information not appropriate for public record
  • Draft or incomplete data - Unverified or work-in-progress information

Feature-level restrictions

Even within a public layer, specific features can be hidden:
  • Features marked as confidential or sensitive
  • Draft features not yet ready for public view
  • Features with incomplete or unverified data
  • Features that reference private property details
Your CSM can configure these restrictions when making the layer public.

Data fields and attributes

When residents click on public map features, they only see:
  • Fields explicitly marked as public
  • Basic identifying information (names, IDs)
  • Attributes configured for public display
  • Links to related public content
Internal notes, staff comments, and administrative fields remain hidden.

Managing public layers

Updating public layers

To update or modify a public map layer:
  1. Contact your Customer Success Manager
  2. Explain what needs to change (styling, visibility, features)
  3. Your CSM will make the updates and notify you when complete
Changes take effect immediately for all residents accessing your public website.

Removing public access

To make a public layer private again:
  1. Contact your Customer Success Manager
  2. Request that the layer be hidden from public view
  3. Your CSM will update the visibility settings
The layer remains available for your internal team but is no longer visible to residents.

Monitoring usage

Work with your Customer Success Manager to:
  • Track which public layers are most viewed by residents
  • Understand how residents use public map features
  • Gather feedback on data needs and questions
  • Identify opportunities for additional public layers

Best practices

Make layers public only when the data is clearly public record and benefits residents. Focus on transparency, education, and access to community information.
Work with your CSM to add legends explaining what colors, symbols, or patterns represent. This helps residents interpret the data correctly.
Regularly update map layers or work with your CSM to establish an update schedule. Outdated public data can confuse or mislead residents.
Before promoting a new public layer, view it in an incognito browser window to see exactly what residents will see. Verify the information is clear and useful.
Public map layers work best alongside public table views. Residents can explore data geographically and in structured table format.
Let residents know about available public map data through newsletters, social media, website announcements, and communications. Many residents don’t know this information is available.

Troubleshooting

Solution: Contact your CSM to verify the layer is configured for public visibility. The layer may be set to internal-only or may have been hidden unintentionally.
Solution: Individual features can be hidden within a public layer. Check with your CSM whether specific features are marked as hidden from public view.
Solution: Large map layers can affect performance. Work with your CSM to optimize the layer, simplify geometries, or split into multiple smaller layers.
Solution: Your CSM can configure feature-level hiding so only appropriate features are visible to residents. You don’t have to make the entire layer public.
Solution: Public table views share filtered data in table format with an optional map view. Public map layers make geographic data visible directly on the map. They work together—residents can view public layers while exploring public table views.