[Google Maps API v3] Re: Some of my KML just stopped working
6:30 am and none of my kml feeds are working on my map of on the maps, regardless of whether they are technically compliant or not. All still work with Google earth. Chris: Are you still planning on rolling back? If not, can someone tell me why this KML is blowing up? Cheers, Mo On Aug 23, 1:19 am, Maurice Tamman maur...@tamman.org wrote: Larry: Those feeds in this thread are in one way or another consumed on ibiseye.com Cheers, Mo On Aug 22, 11:14 pm, geocode...@gmail.com geocode...@gmail.com wrote: On Aug 22, 7:49 pm, Maurice Tamman maur...@tamman.org wrote: It happened this evening. Everything was fine at 6 and not fine at 9:30. When I open the URL in Google Earth I see what I expect. When I test in maps.google.com, it says there is an error. And when I validate at feedvalidator.org, I do see what the errors are. (which I will now fix, in lieu of sleep.) What I don't get, is that that code hasn't been touched in months and months and months. Did Google change something this evening that made it more stringent? We don't really have any insight into when the server side KML processing changes. That seems to be shared between maps.google.com, the v2 API and the v3 API. Are you displaying the KML on an API map? -- Larry Rather frustrating. Here are a couple of examples:http://ibiseye.com/Models2KML/at201109http://ibiseye.com/storm2KML/at... Cheers, Mo -- You received this message because you are subscribed to the Google Groups Google Maps JavaScript API v3 group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
[Google Maps API v3] Some of my KML just stopped working
It happened this evening. Everything was fine at 6 and not fine at 9:30. When I open the URL in Google Earth I see what I expect. When I test in maps.google.com, it says there is an error. And when I validate at feedvalidator.org, I do see what the errors are. (which I will now fix, in lieu of sleep.) What I don't get, is that that code hasn't been touched in months and months and months. Did Google change something this evening that made it more stringent? Rather frustrating. Here are a couple of examples: http://ibiseye.com/Models2KML/at201109 http://ibiseye.com/storm2KML/at201109 Cheers, Mo -- You received this message because you are subscribed to the Google Groups Google Maps JavaScript API v3 group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
[Google Maps API v3] Re: Some of my KML just stopped working
will do ... Do you know when it will be rolled back? Maybe this will help: http://ibiseye.com/storm2KML/at201108 - this one does not validate because of duplicate placemark id and does not show with the API or on maps but worked earlier today http://mi5.ibiseye.com/storm2KML/at201108 - this one does validate but still doesn't show also http://ibiseye.com/Activity2Kml - this one does not validate because of Undefined description element: div and does not show with the API or on maps but worked earlier today also http://ibiseye.com/Models2KML/at201109 - this one does not validate because of duplicate placemark Ids and does not show with the API or on maps but worked earlier today http://mi5.ibiseye.com/Models2KML/at201109 - this one does not validate because of Undefined description element: div and does not show with the API or on maps. All work with Google Earth Cheers, Mo On Aug 22, 11:15 pm, Chris Broadfoot c...@google.com wrote: This may have been caused to an update of KML rendering - we're going to roll back and investigate. If you can, please retain the KML at that link so we can test against it. Cheers Chris --http://twitter.com/broady On Tue, Aug 23, 2011 at 12:49 PM, Maurice Tamman maur...@tamman.org wrote: It happened this evening. Everything was fine at 6 and not fine at 9:30. When I open the URL in Google Earth I see what I expect. When I test in maps.google.com, it says there is an error. And when I validate at feedvalidator.org, I do see what the errors are. (which I will now fix, in lieu of sleep.) What I don't get, is that that code hasn't been touched in months and months and months. Did Google change something this evening that made it more stringent? Rather frustrating. Here are a couple of examples: http://ibiseye.com/Models2KML/at201109 http://ibiseye.com/storm2KML/at201109 Cheers, Mo -- You received this message because you are subscribed to the Google Groups Google Maps JavaScript API v3 group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en. -- You received this message because you are subscribed to the Google Groups Google Maps JavaScript API v3 group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
[Google Maps API v3] Re: Some of my KML just stopped working
Larry: Those feeds in this thread are in one way or another consumed on ibiseye.com Cheers, Mo On Aug 22, 11:14 pm, geocode...@gmail.com geocode...@gmail.com wrote: On Aug 22, 7:49 pm, Maurice Tamman maur...@tamman.org wrote: It happened this evening. Everything was fine at 6 and not fine at 9:30. When I open the URL in Google Earth I see what I expect. When I test in maps.google.com, it says there is an error. And when I validate at feedvalidator.org, I do see what the errors are. (which I will now fix, in lieu of sleep.) What I don't get, is that that code hasn't been touched in months and months and months. Did Google change something this evening that made it more stringent? We don't really have any insight into when the server side KML processing changes. That seems to be shared between maps.google.com, the v2 API and the v3 API. Are you displaying the KML on an API map? -- Larry Rather frustrating. Here are a couple of examples:http://ibiseye.com/Models2KML/at201109http://ibiseye.com/storm2KML/at... Cheers, Mo -- You received this message because you are subscribed to the Google Groups Google Maps JavaScript API v3 group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
