Matterport Model API: geolocation {lat long} vs geocoordinates {latitude longitude}
The Model on Matterport's GraphQL Model API (https://api.matterport.com/api/models/graph) has two location fields with different shapes, and it is easy to mix their names. geolocation: GeoLocation { lat: String!, long: String! } returns decimal degrees as STRINGS to keep precision (altitude is deprecated); this is the one the HackPrinceton 2026 quickstart uses. geocoordinates: GeoCoordinate { latitude: Float, longitude: Float, altitude: Float, source } is marked @extension. geolocation { latitude longitude } and geocoordinates { lat long } both fail GraphQL validation. With geolocation, call float() on the values before any distance math. Some models have no location at all; in the hackathon's models_index.csv, 1,374 of 14,944 rows have blank lat/lon.