Google Maps Integration with Modular Solutions
Modular Solutions integrates with Google Maps to search, validate and map risk-location addresses wherever they are captured in the platform, and to give claims teams a live geographic view of catastrophe activity. This page explains exactly what Google powers inside Modular Solutions, what it doesn’t, and how the integration works.
About Google Maps
Google Maps is a mapping and location platform operated by Google LLC. Through Google Maps Platform, it provides map rendering, address search, address validation, geocoding, and location services used across many industries.
In insurance operations, accurate location data matters at every stage — from the risk address captured at quote or policy setup through to the incidents reported during a catastrophe. Modular Solutions brings selected Google Maps Platform services into risk-location and catastrophe workflows so teams can capture, validate and visualize location data inside the platform.
Modular Solutions Integration with Google Maps
Risk addresses are entered and reviewed at many points in the insurance lifecycle — policy setup, underwriting, broker submissions, and incident reporting. Inconsistent or unverified addresses at any of those points weaken everything downstream, including the maps claims teams rely on during an event.
Modular Solutions integrates with Google Maps on both fronts. Google powers risk-location address search, validation and geocoding wherever risk addresses are captured, and renders risk-location maps. In event and catastrophe workflows, Google also powers a live, interactive map where teams can view incident locations, see related claims, and move directly from the map into the records they need to work on.
The platform’s standard map view is rendered by an open-source map provider, with Google as the fallback if that provider is unavailable.
Where The Integration Is Used
Google’s address search and validation apply to risk-location addresses, so they appear wherever those addresses are captured or reviewed — including policy, underwriting, broker and incident workflows. The Canada Post AddressComplete integration handles mailing address locations.
The catastrophe event map is specific to claims and event workflows.
How the Integration Works
The integration operates across four connected functions.
1. Configuration and authentication
Modular Solutions is configured to use Google Maps through a centrally managed Google Maps API key. The key is maintained in application settings and is not exposed to end users. It allows the platform to use Google Places, Google Address Validation, geocoding, and map rendering.
2. Risk-location address search and validation
When a user begins entering a risk-location address, the platform retrieves suggested matches from Google Places and validates the selected address through Google Address Validation. Selecting a result populates structured address details automatically.
3. Geocoding and coordinate capture
When a supported address is selected — whether a risk location or a mailing address returned by Canada Post — the platform can store latitude and longitude against the record. These coordinates are then available for map display and location-based context.
Where a user types an address manually instead of selecting a returned result, coordinates may not be captured automatically.
4. Map visualization in claims workflows
In claims and catastrophe workflows, the platform renders event and incident maps from stored coordinates. Users can:
- See incidents displayed as map markers
- View clustered incident locations
- See a calculated boundary drawn around the incidents linked to the event
- Open related claim or customer records from marker details
This gives claims teams a practical geographic view of event-related loss activity without leaving the platform.
Key Features & Benefits
Risk-location address search and validation: Reduce manual entry and improve address consistency wherever risk addresses are captured.
2Geocoding: Store coordinates against supported records so locations can be mapped accurately.
3Risk-location mapping: View a validated risk address on a map from the record itself.
4Live event map with incident markers: View reported incident locations on a live map within event workflows.
5Incident detail popups: Open marker details to see incident information and linked claims.
6Direct claim navigation: Move from the map to related customer or claim records in fewer steps.
7Incident clustering: See where incidents are concentrated across an event.
8Calculated event boundary: See a circle fitted around the incidents linked to the event, with a fixed buffer, for visual context.
9Faster catastrophe response: Give claims teams a clearer view of where losses are happening and where to focus first.
Some Notes on the Google Maps Integration
- The event boundary is not a predefined impact zone. It is calculated from the incidents already linked to the event — a circle fitted around them, plus a fixed buffer — so every linked incident sits inside it. It shows the spread of known incidents and cannot be used to test whether an incident falls within an affected area.
- The boundary appears only when an event has more than one linked incident.
- Google is not the platform’s default map provider. It renders risk-location maps and the catastrophe event map, and serves as the fallback for the standard map view.
- No routing or navigation. The integration does not include routing, turn-by-turn directions, distance optimization, or real-time traffic analysis.
- Coordinates depend on address selection. Manually typed or later-edited addresses may have missing or out-of-date coordinates.
Frequently Asked Questions About Google Maps Integration with Modular Solutions
What does the Google Maps integration do within Modular Solutions?
It handles risk-location address search, validation and geocoding wherever risk addresses are captured — including policy, underwriting, broker and incident workflows — and it renders risk-location maps. In claims, it also powers the catastrophe event map, where teams can view incident locations and related claims.
Where is Google address search used in the platform?
Wherever a risk-location address is entered or reviewed. Because the scope follows the address type rather than the module, that includes policy, underwriting, broker and incident workflows. Mailing addresses are a separate flow handled by Canada Post.
Does Modular Solutions use Google for address autocomplete?
For risk locations, yes — those suggestions come from Google Places, with Google Address Validation confirming the selected address. Mailing address autocomplete is provided by Canada Post instead; Google is called afterwards only to obtain coordinates for the chosen address.
What appears on the catastrophe event map?
Incident markers plotted on a live map, with clustering to show where activity is concentrated. Marker details can include the incident number, location information, and related claims. Where an event has more than one linked incident, the map also draws a calculated boundary around those incidents.
Does the event map show a catastrophe impact zone?
No. The circle on the event map is calculated from the incidents already linked to the event, plus a fixed buffer — it is not an independently defined impact area. It is useful for seeing how far reported incidents are spread, but because it is fitted around those incidents, it cannot tell you whether an incident falls inside an affected zone.
Can users open claims directly from the map?
Yes. From the map view, users can move directly to related customer or claim records.
Which countries does the integration support?
Risk-location search and address validation currently cover Canadian addresses. Google Maps Platform itself operates internationally, but the Modular Solutions integration is Canada-focused today.
Which map provider does Modular Solutions use?
The standard map view uses an open-source map provider. Google renders risk-location maps and the catastrophe event map, and acts as the fallback for the standard view if the primary provider is unavailable.
Why are coordinates stored with records?
Stored coordinates make map-based workflows possible. They allow supported records to be displayed on maps and help provide geographic context in claims and event workflows.
Does the integration help with catastrophe response?
Yes. It helps teams see where incidents are concentrated, review related claims in context, and respond more efficiently during active event handling.
Does the integration support routing or turn-by-turn directions?
No. The integration covers mapping, risk-location address search and validation, geocoding, and record navigation within the platform.
Are coordinates always captured for every address?
Coordinates are typically captured when a user selects a supported address result. If an address is typed manually, or edited after selection, coordinates may be missing or may no longer match the address shown.
Ready to see it in action?
Interested in learning more about the Google Maps integration with Modular Solutions? Schedule a demo today.