A GPS reading, a geotagged photo, or a pin dropped on a map only gives you a coordinate. /point turns that coordinate into a place: elevation, plus the country, state, and district it falls in, in one call instead of stitching /elevation and a reverse lookup together.
Out in the ocean, place fields come back null while elevation still returns. Lakes and rivers resolve normally, they belong to whatever country and state surround them. District codes cover US counties (FIPS), French departments (INSEE), and GB districts (GSS), each resolvable at /district/{code}.
Try it
$ curl "https://api.parseapi.com/point?lat=36.0726&lon=-79.792" \ -H "X-API-Key: YOUR_API_KEY" // 200 · ~16ms · USA { "latitude": 36.0726, "longitude": -79.792, "country": "US", "country_name": "United States", "state": "NC", "state_name": "North Carolina", "district": "37081", "district_name": "Guilford", "elevation": 253, "elevation_ft": 830, "resolution": 30 }
Response fields
SPEED
Median time for a core lookup to reach a real city, first byte back, measured live from 16 cities.
US
16ms
EU
19ms
APAC
45ms
LatAm
20ms
ME
127ms