Geocoding problems and precision/ambiguous fields

Hi all,

I just fixed a bug that was preventing many geocoded events from being
returned with latitude and longitude in our API. Distances may have been
affected as well, but are now correct. However, during the fix, I also
was not able to preserve the meaning of geocoding_precision and
geocoding_ambiguous fields. In order to maintain compatibility, i've
just stuffed every result with geocoding_precision="address" and
geocoding_ambiguous="0".

If you use these fields for anything, please let me know.

Thanks,

Gordon

Messages in this topic (1) Reply (via web post) | Start a new topic

.