I'm just wondering if anything has changed recently for the XML response of http://maps.google.com/maps/geo ?
Last Monday, 10th Nov, one of our web app contact forms stopped sending requests (code base hasn't changed for months). Its a Django site using the GeoDjango module for GIS functions. The form itself tries to geocode the address entered by the user, but was failing every time. I eventually traced the problem to some code that traverses the DOM of the XML response from http://maps.google.com/maps/geo?yada=yada. The existing code was traversing the DOM by index, ie. node.childNodes [index].data, and this was no longer working. It looked to me like the whitespace in the response had changed, so what was previous index 1 was now index 4, 2 was 6, etc. The whitespace between the nodes in the XML response had caused this problem. Unfortunately the web app developers' exception handling was vague at best, and took me a while to track this problem down in the source. In the end, the solution was to get the node data by name, ie. node.getElementsByTagName('coordinates') But I'm baffled as to why the bug surfaced, because our code base hasn't changed for months. The only other suspect I can think of is Google Maps API, but it seems unlikely that they'd risk breaking backwards compatibility... Thanks in advance for any clues! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
