[wp-meta] [Making WordPress.org] #5562: Events: Exact city matches fail because of state abbreviations

[Making WordPress.org]

#5562: Events: Exact city matches fail because of state abbreviations
------------------------+---------------------
 Reporter:  iandunn     |       Owner:  (none)
     Type:  defect      |      Status:  new
 Priority:  normal      |   Milestone:
Component:  Events API  |  Resolution:
 Keywords:              |
------------------------+---------------------

Comment (by iandunn):

 Ah, yes, complexity abounds :) Thanks for digging into it!

 Weighting the preferred name sounds like a good approach. I'll play around
 a bit with that too, and see if I can add some more tests around the
 various situations.

 Although, this might be a reason to revisit the idea of switching to an
 external API to handle this kind of thing. I remember Josepha and I looked
 into Google's Geocoding API after the WP 4.8 release; I'll try to find the
 details of where that left off.

 Another idea: Instead of the API trying and pick the perfect match, maybe
 it should just return all the likely ones, and Core could give the user a
 dropdown to pick the right one. [https://developers.google.com/places/web-
 service/autocomplete Google's Places Autocomplete API] is designed for
 that (h/t https://developers.google.com/maps/documentation/geocoding/best-
 practices).

 ---

 I initially had problems getting PHPUnit working on my sandbox, but it's
 working well for me now, using v9.5. If you're running into the same
 problems I was, disabling xdebug should fix it. Check out the new readme
 file in the API root if you haven't already, it has some details.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5562#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org