> It's not good practice to say there's a bug without providing a > demonstrator. >
I wasn't stating there was a bug in the Google API. I was just stating there's a bug. In our application until otherwise proven. > > The reason we can't supply the code is we're a premium user whose > > software is marketed towards the British National Health Service. > > Why not ask your Premier rep? That's what you're paying for! I personally don't currently have the ability to get in touch with him unfortunately. Not quickly, anyway. > > > we have poured through our audit log just in case that wasn't strong > > enough evidence, leads me to believe it is reasonable to politely > > inquire as to whether the version number has, not unreasonably, been > > incremented in the meantime. > > You can check that by outputting G_API_VERSION. However, updates to > 2.s are trailed well in advance and the last update to 2.140 was ages > ago. Thanks! That helps me rule out quite a bit. I didn't know the previous version to check against. > > A good idea would be to check the issues log, but you don't say > whether you're using encoded polylines or not (which is where a link > comes in handy: we can see what you're doing). How > abouthttp://code.google.com/p/gmaps-api-issues/issues/detail?id=15? There > is the distinct possibility that any issue is data-related (again, a > good reason for a link); a change to the data rather than your code > may well change polyline characteristics enough to trigger Issue 15. > But you haven't said whether your code rebuild reinstated data from > three months ago as well. > > Andrew The code and data was stored inside a virtual machine, so the environment is identical with the exception of the network surrounding it. I have checked the issues log and unfortunately came up empty on similar circumstances. That's the closest, but doesn't actually appear to represent the same problem. I was asking a single question and felt it necessarily to explain why I was asking it. I wasn't reporting a bug, nor looking for advice on how to fix such a bug if it existed. There seems to be a strong assumption that was what I was after. -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to google-maps-...@googlegroups.com. To unsubscribe from this group, send email to google-maps-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
