This was broken again. Specifically, it was broken from about October 10th to about November 12th, 2018, which encompassed all of the dates when one could vote in Florida, meaning it took the service I built on this down during the exact dates it would have been useful.
Three things:
1) Why does this API keep losing support for lat/lng?
2) Is this API intended to support lat/lng? Some questions about this get answers like this one, saying sorry and it will be restored soon. Others say that it doesn't and will never, because that would not be an address and so, is invalid.
3) Can the documentation be updated to reflect a hard decision on yes or no? Ideally the answer is yes, but:
If yes, please modify the documentation to explicitly support lat/lng, and show how to do so.
If no, please modify the documentation to explicitly not support lat/lng, and show how one would, starting with lat/lng, get to an address you'd consider to have coped with the objections that you had that caused you to remove support for lat/lng.