VCC Geocoding for Hotel and Car Segments - Causes of Incorrect Locations and How to Fix Them

2026-04-28 14:37:19 UTC

Topic

This article describes how hotel and car travel segments are geolocated and displayed in Everbridge Visual Command Center (VCC) when itineraries are received from travel providers. It explains why some hotel segments appear with an airport address or an incorrect location, and how administrators and travel teams can review and correct the underlying travel data.

Description

Geolocation for hotel and car segments in VCC is based entirely on the travel data supplied by the travel management company (TMC) or other itinerary providers. Everbridge receives itineraries from external providers as raw JSON and uploads the data into VCC exactly as it was sent. This includes address information and any coordinates provided for the segment.

Geocoding errors can occur due to several factors, including incomplete or inaccurate location information in the payload, limitations in the geolocation service's ability to match coordinates with the correct city and state, and challenges when hotel locations differ from the airport or travel destination. In one situation, incorrect latitude and longitude coordinates led to a hotel in one state being mapped to a different state.

If the TMC does not provide sufficient or correct hotel location information in the payload, Everbridge can fall back to a nearby reference point such as the airport, which results in an airport address appearing for the hotel segment. Everbridge uses the address data received in the payload; if the payload contains the correct hotel address, the VCC entry should reflect it. If you see incorrect hotel addresses, verify the location fields sent by the TMC in the feed.

To correct geolocation issues, obtain the raw itinerary payload that the TMC or travel provider sent and compare it to the payload Everbridge received and processed. If the TMC's raw data contains the incorrectly coded segment, for example a segment marked with the wrong location or mode, then the segment was entered incorrectly by the provider. You can also obtain the raw itinerary JSON received by Everbridge and inspect the coordinate fields for the segment, verifying whether the coordinates look correct and checking for swapped values, identical latitude and longitude, or clearly incorrect numbers. If the payload contains incorrect coordinates, contact the itinerary provider with the relevant payload snippet and request correction, since Everbridge imports the data as provided.

For additional help locating and reviewing travel segments inside VCC while you validate the incoming data, you can use Quick Search and export capabilities as described in the following articles:

Was this article helpful?
0 out of 0 found this helpful