The Scenario
A logistics analyst has just processed 200 delivery-completion records. Each row has the GPS coordinates logged when the driver confirmed the drop-off in the mobile app. Before the proof-of-delivery report goes to the client, every coordinate needs to be annotated: which Radar geofence did it land inside, and what is the nearest named place? The client is checking that deliveries happened at the right locations — not in a parking lot down the street.
The bad version:
- Call Radar's context API manually for the first row using Postman. Read the JSON, find the geofence name, find the nearest place, type both values into the workbook. Repeat 199 more times.
- Two hundred API calls, each requiring a manual result-read, takes the better part of the afternoon.
- At row 88 the context API returns a place name with a special character in it. Pasting it into Excel corrupts the cell. Fix the encoding issue, continue.
The report is due to the client this afternoon.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent inside your Excel workbook. It reads the coordinate pairs, calls Radar's context API for each row, and writes the geofence tag, place name, and city back into the workbook — 200 rows in one pass.
Enrich all 200 rows in this Excel workbook (lat in A, lng in B) with Radar context — write the matched geofence tag, place name, and city to columns C, D, and E
What You Get
- Column C: geofence tag for each delivery coordinate, or "None" if no geofence matched
- Column D: nearest place name from Radar's place database
- Column E: city at each coordinate
- The "None" rows in column C flag deliveries that fell outside all defined geofences — the client can investigate those specifically
What If the Data Is Not Quite Ready
You need the geofence name rather than the tag for the client report
For each row in this workbook (lat in A, lng in B), call Radar's context API and write the matched geofence name to column C, nearest place name to column D, and country/region to column E
Some coordinates are 0,0 or clearly invalid
For each row (lat in A, lng in B): if coordinates are 0,0 or outside valid global range, write Invalid Coordinates to column C and skip the API call — otherwise call Radar context and write geofence tag, place name, and city to columns C, D, and E
You want all matching geofence names, not just the first
For each row (lat in A, lng in B), call Radar's context API and write all matching geofence names (comma-separated) to column C, the nearest place name to column D, and the city to column E
Validate coordinates, enrich with context, and add a delivery verification flag in one pass
For all 200 rows (lat in A, lng in B): validate coordinates are non-zero and in range, call Radar context, write geofence tag to column C and place name to column D — then add a Verification column E: "Confirmed" if a geofence matched, "Outside Zone" if none, "Invalid" if the coordinates were bad
The verification column is what the client asked for in the proof-of-delivery contract.
Try It
Get the 7-day free trial of SheetXAI and open any Excel workbook with delivery GPS coordinates — ask it to enrich each point with Radar context and write geofence and place data into the workbook. For full reverse geocoding to street addresses, see bulk reverse geocoding, or return to the Radar integration overview.