Skip to main content
Back to Numbers generators

Numbers

Random GPS Coordinate Generator

Used by developers, writers, and creators worldwide.

A random GPS coordinate generator gives you valid latitude and longitude pairs instantly, without hand-crafting test data or scraping real addresses. Developers use it to seed spatial databases, mock geolocation APIs, and stress-test map components before production data exists. Set the count, pick a region (World, UK, Europe, USA, or Australia), choose decimal precision, and select whether output follows lat/lng or GeoJSON lng/lat order. The result pastes straight into fixtures, seed scripts, or Postman mocks. Six decimal places resolves to roughly 10 cm on the ground; four gives about 11 m — matching your production schema avoids false-precision errors in PostGIS or Spatialite inserts.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Set the Count field to the number of coordinate pairs your test case requires.
  2. Choose a Region to constrain output to World, UK, Europe, USA, or Australia coordinates.
  3. Adjust Decimal Places to match the precision your API or database column expects (6 is a safe default).
  4. Select the Format that matches your stack — lat/lng for Google Maps, lng/lat for GeoJSON pipelines.
  5. Click Generate, then copy the output directly into your seed file, fixture, or API mock.

Use Cases

  • •Seeding a PostGIS staging table with 500 randomised UK delivery locations for performance testing
  • •Mocking GPS telemetry payloads in Postman to test a vehicle-tracking dashboard's polyline rendering
  • •Populating Leaflet or Google Maps marker-clustering demos with dense coordinate sets across Europe
  • •Generating radius-search fixtures for a Jest integration test against a proximity-query endpoint
  • •Creating realistic sample map data for a client demo or portfolio project without exposing real addresses

Tips

  • →Set decimals to 4 when testing UI rendering — it reduces visual noise and maps handle 11 m accuracy fine for display.
  • →Generate coordinates in the same region as your real users; bounding-box differences between UK and USA catch timezone and projection bugs early.
  • →Combine two separate batches — one dense cluster and one sparse spread — to properly test marker clustering and spatial index performance together.
  • →If your app stores coordinates as DECIMAL(9,6) in MySQL, generate with exactly 6 decimal places to avoid silent rounding on insert.
  • →For GeoJSON FeatureCollections, generate with the lng/lat format and wrap each pair manually in a Point geometry object before inserting.
  • →Use the USA region to surface antimeridian-adjacent edge cases if your app handles Pacific coordinates, as western US longitudes approach -125.

FAQ

how many decimal places should gps coordinates have for mapping

Six decimal places resolves to roughly 10 cm on the ground, which is the right precision for street-level navigation and tight geofencing logic. Four places gives about 11 m accuracy, fine for city-level features but potentially problematic for turn-by-turn routing. Match the decimals setting to whatever your PostGIS column or mapping API stores to avoid rounding mismatches.

difference between lat lng and geojson coordinate order

Lat/lng order (latitude first) is used by Google Maps, most GPS devices, and the majority of human-readable formats. GeoJSON officially reverses this, putting longitude first to follow the x/y mathematical convention. This mismatch is one of the most common sources of geospatial bugs, so use the format selector here to output whichever order your library expects before pasting into code.

are randomly generated coordinates guaranteed to be on land

No — the generator constrains points to a region's bounding box, so some will land in the ocean, over water, or on uninhabited terrain. For API testing and database seeding this is usually fine, since you're validating logic rather than real-world accuracy. If you need land-only or address-linked points, run the output through a reverse-geocoding API like Google's or Nominatim to filter.