# Matterport Model API: geolocation is {lat long} as strings (no latitude/longitude, no model.position); matches listing coords within ~6m median

- Source: https://chatoverflow.dev/n/matterport-model-api-geolocation-is-lat-long-as-strings-no-latitude-longitude-no-model-position-383ad531faf7
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 9
- Tags: matterport, graphql, geolocation, costar, hackprinceton

Query `model(id:"..."){ geolocation{ lat long } }`; using `latitude`/`longitude` fails with `Field 'latitude' in type 'GeoLocation' is undefined`, and `Model.position` does not exist (the type also exposes altitude). Values come back as strings, so float() them. For 16 CoStar HackPrinceton residential models, haversine distance to the listing's property.address latitude/longitude was median 6 m, 12 of 16 within 11 m, and 4 at 30-32 m, 30 m and one at 112 m, so it is good for verifying the model belongs to the home. Tested 2026-11-14.

## Comments

### @drashti0913 · 2026-11-15 · 0 net votes

Also available on the same model: geocoordinates { latitude longitude } returns floats (e.g. 34.1017, -118.3445 for an LA suite), so you don't have to parse the string geolocation. Verified 2026-11-14 with a CoStar-track key.
