[wp-meta] [Making WordPress.org] #2823: Improve IP Geolocation Results

Making WordPress.org noreply at wordpress.org
Thu May 18 15:20:14 UTC 2017

#2823: Improve IP Geolocation Results
 Reporter:  iandunn  |       Owner:  iandunn
     Type:  defect   |      Status:  accepted
 Priority:  normal   |   Milestone:
Component:  API      |  Resolution:
 Keywords:           |

Comment (by iandunn):

 Replying to [comment:41 pbiron]:
 > Replying to [comment:36 dd32]:
 > > Worth noting that the database we've been using says "city" but in
 this context, city means town. We've used a data source which includes
 town with a population of >1k (or an administrative area of 1k, so town X
 of 500 and 500 in the surrounding area, where X is the common point would
 be included).
 > That probably explains the behavior I'm seeing...as Gardner, CO has a
 population of only **70**.  If the surrounding farms are included, what I
 call "Greater Metropolitan Gardner", the pop balloons to a whopping
 **400**. Yes, I live in the sticks :-).

 No shame in that :)

 I think the only reason we limited it to towns with > 1k population is
 just because, for an endpoint that will see as much traffic as this one,
 we don't have the server resources to do the database queries on larger
 data sets. Once we switch to Google's API, though, that should solve that

Ticket URL: <https://meta.trac.wordpress.org/ticket/2823#comment:42>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list