Adding geo-coordinates to your Data Exchange file lets BEACON display meter locations on the map in the Monitor and Assets pages. Service Point coordinates provide the most precise pin placement and are visible to both utility staff and EyeOnWater customers.
Note: If coordinates were set using the BEACON Field App, importing a Data Exchange file for the same service will overwrite them.
To populate latitude and longitude in BEACON, four geo-coordinate fields are supported in the Data Exchange Specification, all in decimal degrees format: Location_Latitude, Location_Longitude, Service_Point_Latitude, and Service_Point_Longitude.
Valid coordinate ranges:
- Latitude: between -90.0 and 90.0 (0.0 not accepted)
- Longitude: -180.0 and 180.0 (0.0 not accepted)
Important: Every record must include the correct Location_ID. If Service_Point_ID is not provided, Data Exchange defaults it to 1.
How Data Exchange Handles Coordinate Combinations
Location and/or Service Point coordinates provided
| Location coordinates | Service Point coordinates | System behavior | Geocode Status |
| Valid | Valid | Data Exchange accepts both sets of coordinates and stores each set in its corresponding fields. | Service Point |
| Valid | Invalid or Not provided |
Data Exchange accepts the Location coordinates and stores them only in the Location fields. | Location |
| Invalid or Not provided |
Valid | Data Exchange accepts the Service Point coordinates and stores them only in the Service Point fields. | Service Point |
Address-based geocoding
When both Location coordinates and Service Point coordinates are invalid or not provided, Data Exchange will attempt address-based geocoding. For address-based geocoding, provide Location_State and at least one of Location_City or Location_Zip.
- Data Exchange attempts to derive coordinates from the Location address fields using Google Maps. If successful, Geocode Status is set to Location. The map pin will show the center of the address and may not match the exact meter location.
- If address geocoding fails, Data Exchange falls back to the Utility coordinates. Geocode Status is set to Utility.
Correcting geo-coordinates
Choose the path that matches your situation.
Path A: You have the correct coordinates
-
- Create a Data Exchange file with a record for each affected location. For each record, provide:
- Location_ID
- Service_Point_ID (omitting this defaults to 1)
- Service_Point_Latitude and Service_Point_Longitude
- Import the file. The system stores the coordinates you provided.
- Create a Data Exchange file with a record for each affected location. For each record, provide:
Path B: You don’t have correct coordinates
BEACON uses Google Maps to derive coordinates from address fields.
Note: Each record must include Location_State and at least one of Location_City or Location_Zip for geocoding to succeed.
-
- Create a Data Exchange file with one record for each affected location. Provide the correct Location_ID and Service_Point_ID (omitting this defaults to 1).Use _CLEAR_ to remove existing data from these fields:
- Location_Address_Line1
- Location_Address_Line2
- Location_Address_Line3
- Location_City
- Location_State
- Location_County_Name
- Location_Country
- Location_Zip
- Location_Latitude
- Location_Longitude
- Service_Point_Latitude
- Service_Point_Longitude
- Import the file to clear the existing data.
- Create a second file with the correct address data for each location. Include all the fields you cleared in Step 1 but leave the four coordinate fields blank.
- Import the second file. BEACON queries Google Maps and stores the resulting coordinates.
- To verify geo coordinates (optional), use the Geo Data Review tool.
- Create a Data Exchange file with one record for each affected location. Provide the correct Location_ID and Service_Point_ID (omitting this defaults to 1).Use _CLEAR_ to remove existing data from these fields:
