A location data generator returns synthetic addresses, cities, countries, GPS coordinates and zip codes for tests, prototypes and fixture screens. Spotzee bundles 20 methods in one endpoint with method-scoped controls for latitude/longitude ranges, origin coordinates, country-code variants and address inclusion flags.Documentation Index
Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt
Use this file to discover all available pages before exploring further.
Generate sample location data at
spotzee.com/tools/location-generator.
Why this matters
Maps, geo apps, shipping flows, ride-share simulators, store locators and rendezvous tools all rely on believable location data. Tests need addresses that pass parser checks, GPS points that sit inside a sensible bounding box, and zip codes that match a market format. A location data endpoint keeps those rules in one well-tested place. Use a numeric seed for reproducible address sets across runs. UsenearbyGPSCoordinate with an origin and radius when fixtures must cluster around a city or store. Use abbreviated state and country-code variants when downstream systems expect short codes.
Generated values are synthetic placeholder strings. Each Extended API call deducts a small per-call amount from your Spotzee credit balance. See the Spotzee pricing page for live per-tool pricing.
How it works
Send the request
POST to
/generic/data/generate/location with count. The count is a
string from 1 to 100.Choose a method
Pick
address for the bundled record, or one of 19 single-field methods
such as city, country, state, zipCode, latitude, longitude or
nearbyGPSCoordinate.Set scoped options
Latitude/longitude ranges scope coordinate methods. Origin latitude,
longitude, radius and metric flag scope
nearbyGPSCoordinate. Address
methods accept include flags for coordinates, country code, time zone,
language, directions and secondary address.Method reference
| Method | Output | Scoped options |
|---|---|---|
address | Bundled street, city, state, zip | All include flags (coordinates, country code, time zone, language, directions) |
streetAddress | Street address line | useFullAddress |
street | Street name | none |
buildingNumber | Building number | none |
secondaryAddress | Apartment, suite, unit | useFullAddress |
city | City name | none |
county | County name | none |
state | State name or abbreviation | abbreviated |
country | Country name | none |
countryCode | ISO country code | countryCodeVariant (alpha-2, alpha-3, numeric) |
continent | Continent name | none |
zipCode | Zip code | zipCodeFormat (e.g. #####-####) |
latitude | Latitude value | latitudeMin, latitudeMax, precision |
longitude | Longitude value | longitudeMin, longitudeMax, precision |
nearbyGPSCoordinate | Coordinate near a fixed origin | originLatitude, originLongitude, radius, isMetric, precision |
cardinalDirection | N, S, E, W | abbreviated |
ordinalDirection | NE, SE, SW, NW | abbreviated |
direction | Combined cardinal/ordinal | abbreviated |
language | Language with name, alpha2, alpha3 | none |
timeZone | IANA time zone identifier | none |
address when fixtures need every related field together. Pick a single method when a parser, dropdown or field expects one shape per record.
What to watch for
- Count outside
1to100. One request returns up to 100 records. Call the endpoint again for larger datasets. - Method-scoped option mismatch. Each option is forwarded only to methods that support it. For example, latitude/longitude ranges only apply to coordinate methods, and include flags only apply to
address. - Latitude/longitude ranges and origin pairing. Latitude minimum and maximum should bracket realistic values. Origin latitude and longitude must be sent together for
nearbyGPSCoordinate. - Treating fixtures as real customer addresses. Generated addresses are synthetic. Do not treat them as real customer records, deliverable shipping targets or operating-area test cases without a downstream geocoder.
- Unseeded snapshots. Send a numeric
seedwhen tests assert exact strings or snapshot the rendered output.
FAQs
What is a location data generator?
What is a location data generator?
A location data generator creates synthetic address, city, country, GPS
coordinate and zip code values for tests, examples and seed scripts.
Spotzee returns those fields from one endpoint with method-scoped
options.
Can I cluster GPS coordinates around a fixed origin?
Can I cluster GPS coordinates around a fixed origin?
Yes. Pick
nearbyGPSCoordinate, send originLatitude, originLongitude
and a radius. Toggle isMetric to choose kilometres or miles.Can I generate just a country, city or zip code?
Can I generate just a country, city or zip code?
Yes. Pick
country, city, state or zipCode to return one field per
record. Use countryCodeVariant (alpha-2, alpha-3 or numeric) when
a downstream system expects a specific country-code shape.Does the address output include coordinates and a time zone?
Does the address output include coordinates and a time zone?
Yes when those include flags are on. Send
includeCoordinates=true,
includeTimeZone=true, includeCountryCode=true, includeLanguage=true,
includeDirections=true or includeSecondaryAddress=true to enrich the
address record.Are these real customer addresses?
Are these real customer addresses?
No. Generated addresses are synthetic placeholder strings. Treat them as
fixture copy and do not use them as real customer records, shipping
targets or compliance evidence.
Where can I learn more about location data generation?
Where can I learn more about location data generation?
Read the location data generator
guide
for endpoint options, response fields and integration patterns. The guide
also shows where location data fits beside phone, person, contact and
developer fixture generators.