About GetMyLocations
Last reviewed October 1, 2026 · Tested on real devices before publish
GetMyLocations is a small independent site that does one thing: it reads your GPS coordinates straight from the browser and turns them into a place name you can copy, share, or feed into a map. The site also hosts a handful of related tools (IP lookup, coordinate-format conversion, distance between two points) and a growing set of articles explaining how the underlying systems actually work.
Why this site exists
Most “find my location” pages on the web are wrappers around an ad-loaded IP lookup, which is why they place you in the wrong city about half the time. The browser already has a high-accuracy geolocation API that asks the operating system for a real GPS fix — the same signal Maps uses for turn-by-turn directions. GetMyLocations uses that API directly, in your browser, and never sends the coordinate to a server we run. The reverse-geocoding lookup that turns the coordinate into a city name goes to a third party (BigDataCloud or OpenStreetMap Nominatim) and the response stays in the tab. The Privacy Policy lists every third party in plain language.
About Ahmed Anwar
I’m Ahmed Anwar, a senior software engineer based in Karachi, Pakistan, and I build this site independently. I’ve been building production web apps for roughly five years, mostly around React, Next.js, and the kind of mapping tooling this site is built on — Leaflet, OpenStreetMap tiles, browser geolocation, and the free-tier IP-geolocation APIs you see referenced throughout the guides.
The reason I’m comfortable writing about this stuff is that I ship it. Every tool on this site — the my-location reader, the coordinates converter with live UTM math, the distance calculator using the haversine formula, the driving-directions embed — I wrote and debugged personally, on real devices, in real browsers, with the same API rate limits and CORS quirks any other developer would hit. The articles explain what I learned while building.
How the writing is done
Honest disclosure: the long-form articles and guides on this site are researched and drafted with the help of an AI writing assistant, then edited and fact-checked by me before they go live. I add the specific numbers, name the APIs the tools actually call, and cut anything that reads like filler. The code for every tool is hand-written and tested on a real phone and laptop before it ships. If you ever spot something that’s wrong, vague, or feels generated, email me at the address below — corrections go up the same day and are logged in Corrections below.
Corrections
Mistakes that made it past review, and what changed. Typos and wording tweaks are not listed; anything that was factually wrong is.
- October 1, 2026 — Why maps show the wrong street. Said address interpolation dates back to 1800s surveyors. It went mainstream with the US Census Bureau’s DIME files for the 1970 census and the later TIGER files.
- October 1, 2026 — GPS vs IP accuracy. Blamed a slow first GPS fix on downloading the almanac. The receiver is waiting for each satellite’s ephemeris, which repeats every 30 seconds.
- October 1, 2026 — Live Location. Android steps named a “High accuracy” mode removed in Android 10, and a tip about tethering a laptop to a phone’s GPS described a feature macOS and Windows do not have. The page also promised the place-name lookup runs at most once every 10 seconds, but the code could run it more often while driving; the code now keeps that promise. Its description and intro also said “nothing leaves the page,” although the place-name lookup is sent to OpenStreetMap, and quoted a battery cost of 5–12% per hour with no source; both are corrected.
- October 1, 2026 — Driving Directions. The FAQ said leaving the origin empty uses your location; it shows an error instead. The “Use my location” button is the way. A 1.4× road-to-straight-line ratio was described as unusual when it is the US average.
- October 1, 2026 — Homepage. Claimed eleven tools (there are nine), said “no tracking” although Google AdSense runs on the site, and named only OpenStreetMap as the reverse-geocoding service when BigDataCloud is tried first.
- October 1, 2026 — My Location. Said six decimal places is about one meter; it is about 11 centimeters. The Coordinates Converter FAQ said phones deliver five-decimal (~1.1 m) precision; they typically manage 3–5 m.
- October 5, 2026 — Coordinates Converter. The reference table’s UTM values had been typed in by hand and were up to 237 m off (Sydney Opera House); they are now generated by the converter’s own code and checked against an independent library. The page also claimed the tool flagged out-of-range values (it did not), honoured the Svalbard UTM zone exceptions (only Norway’s was implemented), and showed a live map (there was none). Editing a DMS field also left the UTM and DDM results stale. All of these are now fixed in the tool itself.
- October 5, 2026 — IP Location Lookup. Two answers said the lookup shows whether you are on a residential, mobile, hosting, or VPN connection; the tool has never shown a connection type. The page also gave two different, unsourced sets of accuracy figures; they are replaced with MaxMind’s published estimates. The page now also names the database it uses (ipapi.co).
- October 5, 2026 — Distance Calculator. Clicking a preset or the swap button showed the previous pair’s distance and bearing (London to Paris displayed 5,837 km). The reference table promised results within one kilometre but three rows were 8 to 17 km off, and the page understated the spherical formula’s error (up to about 0.56%, not “typically under 0.5%”). The tool now calculates on the WGS 84 ellipsoid, the table is generated from its own code, and both are checked against the GeographicLib reference library.
- October 5, 2026 — Address Finder. The worked-examples table no longer matched what the tool returns (the Statue of Liberty’s coordinates resolve to Flagpole Plaza and the Sydney Opera House’s to a nearby public toilet, not the landmarks the table claimed); it is replaced with dated real lookups. The FAQ also promised a confidence score the tool never showed and told readers to tap a Search button that did not exist.
- October 5, 2026 — Street View. The tool never showed a Street View panorama: the embed it used displayed an ordinary map for addresses and a blank box for coordinates, while the page described navigation arrows, a capture date in the corner, and a panorama that “jumps to the Eiffel Tower”. It also said Google had covered about five million miles; Google’s own figure is over 10 million. The tool now pins the exact spot and opens the real panorama through Google’s official Street View link.
- October 5, 2026 — Privacy Policy. Listed CARTO as a map-tile provider after the site had stopped using it, and did not mention the Google Maps embeds on the Driving Directions and Street View pages. Both are corrected.
- October 5, 2026 — Driving Directions. The embedded Google map never drew a route, yet the page said the route, its traffic-adjusted travel time, and turn-by-turn steps were shown on the page. The tool now previews both places with the straight-line distance and opens the real route in Google Maps; the page describes exactly that.
- October 5, 2026 — How to turn on location on a laptop. Told Windows users to find their browser’s own toggle in the per-app location list; Chrome and Firefox are desktop apps that Windows does not list there, and are controlled by a separate desktop-apps setting. Also gave the wrong macOS version for the switch to System Settings (it was Ventura, not after Big Sur), and wrongly said plugging in Ethernet turns off Wi-Fi.
- October 5, 2026 — What is IP location, and how accurate is it? Opened with unsourced accuracy figures (country 95–99%, city 50–75%) and a chart of made-up hit rates, and said this site uses free monthly database snapshots when its IP tool actually calls ipapi.co. The figures and chart now use MaxMind’s published estimates.
- October 5, 2026 — How to find your GPS coordinates. Told Windows users to open the built-in Maps app, which Microsoft withdrew in July 2025.
- October 5, 2026 — Turn on location on iPhone & Android. Gave a Chrome-on-iPhone menu path that does not exist (Chrome’s location access is set in the iPhone Settings app) and left out the Safari Websites switch that blocks every site when set to Never. Also said every iOS browser must use WebKit (no longer true in the EU since iOS 17.4), described Safari’s app prompt as the per-site prompt, pointed to Chrome’s old padlock icon, quoted an unsourced 3–5 m outdoor accuracy (now GPS.gov’s 4.9 m), and said Low Power Mode throttles GPS sampling, which Apple does not state.
- October 5, 2026 — Share your location safely. Said Signal offers live location sharing with durations and an “End share” button; Signal only sends a one-time pin. Said Apple’s shared location is always end-to-end encrypted and that Find My shares survive device wipes; Apple says it cannot access the location only when both people are on iOS 17 or later, and keeps it for up to 24 hours. Also misstated Google Maps’ durations, claimed an unsourced share-sheet history leak, called Plus Codes “formerly” Open Location Codes, implied AML works everywhere, and gave only Pakistan’s police number (Rescue is 1122). The opening anecdote was rewritten as a general example.
- October 6, 2026 — Browser Geolocation API explained. Said modern Macs have a GPS chip (they do not), that turning off location in the OS makes the browser fall back to IP (the request fails instead), that the API fails silently on HTTP (browsers report a permission error), and that some browsers require a click before prompting (the spec does not). It also told readers to toggle Precise Location in browser site settings, which do not have that switch, and repeated unsourced accuracy ranges and an unmeasured claim that a permission screen doubled successful retries; all are corrected or removed. The description of how this site calls the API now matches the code.
- October 6, 2026 — My Location. The page title and description promised your street address, but the tool only showed the city and country. It now shows the nearest street address, how precise the match is and how far it lies from your coordinates.
- October 6, 2026 — Homepage. The headline, title and description promised your address, but the location card only showed the city and region. It now shows the nearest street address, how precise the match is and how far it lies from your coordinates.
- October 12, 2026 — IP Location. The lookup service the tool used, ipapi.co, began rejecting requests from browsers, so the tool showed “Could not reach the lookup service”. It now uses freeipapi.com. Its time-zone data lists every zone in a country, so the tool only shows a time zone when the country has just one.
- October 15, 2026 — How to find GPS coordinates. Told Android users to press and hold the blue dot in Google Maps; Google’s instructions are to touch and hold an unlabeled spot on the map. Said a website’s location request goes only to that page and not to Google, although Chrome uses Google Location Services to estimate the position. Also listed the Compass app for iPad, which does not have it, and gave unsourced accuracy ranges, now replaced with GPS.gov and Android figures.
- October 15, 2026 — How GPS works. Said GPS has two civilian frequencies and that L2 is military only (L2C is a civilian signal, alongside L1, L5 and L1C); said A-GPS delivers the almanac (it delivers each satellite’s ephemeris); credited the iPhone’s U1 chip, an ultra-wideband radio, with GPS corrections; described Android location modes removed in Android 9 and 10; misdated and misdescribed the Newark airport jamming case; overstated RTK as sub-centimetre; said GPS stations detect motion that precedes earthquakes; and quoted unsourced accuracy and battery figures. All corrected, with sources.
Contact
Email ahmed@getmylocations.com for questions, feedback, corrections, or partnership ideas. I read everything; I reply to most things within a day or two.