Which order do mapping tools expect?

Most expect latitude then longitude, but GeoJSON expects longitude first. Check before you plot, since a swapped pair lands in the wrong hemisphere.

Why did my coordinates lose precision?

Almost always a spreadsheet reformatting the column. Import as text or set the decimal places explicitly.

Location field

The listing's longitude in decimal degrees, the companion to latitude for mapping, radius filters and route planning.

A decimal degrees value, positive east of the prime meridian, paired with the latitude column.

Taken from the listing's own coordinates, not derived from the address text.

28.9773

01Feed a mapping tool, a BI dashboard or a GIS layer directly.
02Run a proper radius query instead of filtering on city names.
03Detect duplicate storefronts that sit implausibly close together.
04Split a dense metro into balanced territories by geography rather than by name.

Longitude alone is meaningless — always carry the latitude with it, and keep both as numbers so a spreadsheet does not round them into uselessness.

Which order do mapping tools expect?: Most expect latitude then longitude, but GeoJSON expects longitude first. Check before you plot, since a swapped pair lands in the wrong hemisphere.
Why did my coordinates lose precision?: Almost always a spreadsheet reformatting the column. Import as text or set the decimal places explicitly.

This is one of 41 columns on every row, on every plan. See the full field reference or check pricing.