Tools › Entity types

Location data

Redact GPS coordinates from text, JSON, and CSV

Coordinates are the most precise location data there is: six decimal places locates a doorway. They are also bare numbers that no model can identify without a pattern.

Try it on the live API No signup. 2,000 characters, 20 runs per 10 minutes.
Output appears here.

How Redactly detects GPS coordinates

  • Matched by regex for a decimal latitude and longitude pair separated by a comma.
  • Signs are optional, so southern and western coordinates match too.
  • Runs independently of the model, so coordinates in an otherwise empty field are still found.

Why redact GPS coordinates?

Precise coordinates can locate a person's home or workplace to within metres.

Example request

curl -X POST https://api.bitbanger.in/v1/redact \
  -H "X-API-Key: rdct_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"text": "Drop point 51.507351, -0.127758 confirmed by driver.", "style": "replace"}'

Every hit in the response carries entity, text, start, and end. The offsets index into the text you sent, so you can apply the redactions to your own copy of the document. The full response schema is in the API reference.

Questions

Does Redactly redact GPS coordinates automatically?

Yes. Send text to the API and every detected type is redacted, including GPS coordinates. To redact only this type, pass the value location.gps_coordinates in the entities filter. No training or configuration is required.

What happens to GPS coordinates after redaction?

With style set to replace, each match becomes [location.gps_coordinates] — the entity type in square brackets. Setting style to mask replaces every character with a block character, and remove deletes the span entirely.

Related entity types

Redact GPS coordinates in production

Get an API key and send your first request in a minute. Plans start at $24/month.

See pricing