[davewritescode]

If it's just to route to regional sites, that's fine. Letting the user select just makes sense.

However, there's a lot of use cases that semi-accurate geo-locations make sense. The first of which is analytics. If I'm a marketing person at a SaaS company, I want to know where my customers physically are if possible for a variety of useful reasons.

Good quality estimates for location also help with security and compliance use cases as well. If a user logs in from a new country on the opposite of the world, you can flag that and take whatever action you want whether it's to block them, fire off an email to the person who owns the account or whatever.

[reaperducer]

I want to know where my customers physically are if possible for a variety of useful reasons.

I hope you're factoring in error rates. Because right now Google, with its billions of dollars to spend on geolocation, tells me that my laptop is in Albuquerque, and my phone is in Los Angeles. Neither are within 500 miles of either.

[sneak]

> If I'm a marketing person at a SaaS company, I want to know where my customers physically are if possible for a variety of useful reasons.

What reasons? What makes you feel entitled to that information if not volunteered?

[jaywalk]

Any info that can be gleaned from the request is fair game.