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

Making WordPress.org noreply at wordpress.org
Tue Jun 6 17:51:36 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):

 r5543 merges the last bits of [attachment:2823.diff], so the performance
 issues should be sorted now.

 The two things still left in this ticket are:

 1. Switching to an external geocoding API for better accuracy. I'm talk to
 a Google rep today about ToS, pricing, etc. If that goes well, I'll work
 on merging [attachment:2823.2.diff]. I'd like to keep the geonames stuff
 around as a fallback, though, at least for a few weeks. Depending on
 pricing, we may also want to keep it around permenantly, and use it for
 queries that we are confident will return good results from the
 geonames.org data, and then only use the external API for requests that
 are likely to be get better results from it.
 1. Automating the ip2location updates. I think I have everything I need to
 finish the script now, so I'll be working on this today.

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

More information about the wp-meta mailing list