As you can see from this API request, it fails with a "Not found" page. This error happens when there is too many decimal digits (more than 6 as it seems). It's curious Android location service would give a result with so many decimals, when I explicitly asked for "neighbor-level"...