The Scenario
A logistics analyst just finished processing 200 delivery-completion records. Each row has the GPS coordinates where the driver marked the delivery done. Before the proof-of-delivery report goes to the client, every coordinate needs to be annotated with the Radar geofence it fell inside (if any) and the nearest place name — so the client can verify that deliveries happened at the right locations, not in a parking lot two blocks away.
The bad version:
- For each coordinate, call Radar's context endpoint manually via curl or Postman, read the JSON response, find the geofence name field and place name field, type both into the sheet.
- Two hundred rows. Each API call takes about 10 seconds to set up and read. That's 30+ minutes of terminal work, assuming zero errors.
- On row 47 the context API returns a place name with a comma in it and the CSV paste breaks the column alignment. Spend 20 minutes fixing the column structure before continuing.
The client is expecting the report this afternoon.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent inside your Google Sheet. It reads the coordinate pairs, calls Radar's context API for each row, and writes the geofence name, place name, and region back into the columns you specify — handling all 200 rows in one pass.
For each coordinate pair in this sheet (lat in A, lng in B), call Radar's context API and write the matched geofence name, nearest place name, and country/region to columns C, D, and E
What You Get
- Column C: name of the Radar geofence covering each delivery point, or "None"
- Column D: nearest place name from Radar's place database
- Column E: country and region for each coordinate
- Any row where the context API returned no geofence gets "None" in column C — making it easy to filter for deliveries that happened outside defined zones
What If the Data Is Not Quite Ready
You need the geofence tag rather than the geofence name for the report
For each row (lat in A, lng in B), call Radar's context API and write the matched geofence tag to column C, the nearest place name to column D, and the city to column E
Some rows have clearly wrong coordinates (0,0 or out of range)
For each row (lat in A, lng in B): if the coordinates are 0,0 or clearly out of valid range, write Invalid Coordinates to column C and skip the API call — otherwise call Radar context and write geofence name, place name, and region to columns C, D, and E
You want to know if multiple geofences cover a delivery point
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 region to column E
Clean coordinates, enrich with Radar context, and flag deliveries outside expected zones in one pass
For all 200 rows (lat in A, lng in B): validate coordinates, call Radar context, write geofence name to column C and place name to column D — then add a column E flag: "In Zone" if a geofence matched, "Outside Zone" if none matched, "Invalid" if coordinates were bad
The flag column is what the client actually needs for the proof-of-delivery verification.
Try It
Get the 7-day free trial of SheetXAI and open any Google Sheet with delivery GPS coordinates — ask it to enrich each point with Radar context and write geofence membership and place data into the sheet. For reverse geocoding to full street addresses, see bulk reverse geocoding, or return to the Radar integration overview.