[Google Maps API v3] Inconsistent KML overlay response

[Matt]

I am hosting a few kml files and adding them to a map in development.
The problem is sometimes the KmlOverlayService returns a 200 (OK)
response and everything works and sometimes it returns 400 (Bad
Request). I can't consistently make it do one or the other.

An example of the kml is http://ww3.tdot.state.tn.us/traffichistory/trfchistr2.kmz
I've tested them successfully in the feedvalidator
http://beta.feedvalidator.org/check.cgi?url=http%3A%2F%2Fww3.tdot.state.tn.us%2Ftraffichistory%2Ftrfchistr2.kmz
I've tested them successfully in google maps
http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=http:%2F%2Fww3.tdot.state.tn.us%2Ftraffichistory%2Ftrfchistr2.kmz&sll=37.0625,-95.677068&sspn=39.184175,66.533203&ie=UTF8&z=8

Any ideas?

--
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-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[Rossko]

I think you might be getting up to the limits with a 6Mb KML, as per
http://code.google.com/apis/kml/documentation/mapsSupport.html
I suspect things are not as clear-cut as stated there, and the limits
can very dynamically with Google's server loading, as they are after
all set to protect it from resource hogging.

[William]

On May 19, 6:51 am, Matt <mattlan...@gmail.com> wrote:
>
> An example of the kml ishttp://ww3.tdot.state.tn.us/traffichistory/trfchistr2.kmz
>

this kml has 2495 Placemarks, which is greater than the limit of 1000
features (on the page that Rossko posted). What happens if you limit
the kml files to 1000 features?
...

[Matt]

I'll try breaking the files into smaller sets to get below 1k. I was
well below the KMZ and KML limit and it was working fine until the
18th, so maybe something changed with the update. It's just weird to
me that it is inconsistent, maybe that hints to the server load.

Thanks, I'll let you know how it goes.

[Matt]

So I broke the KML files into smaller files and it was going great and
then yesterday I started getting errors again. From Google I was
getting some 400 Bad Response errors, some 500 Internal Server errors,
and some kmloverlay tiles were just never delivered. I'm chalking
these issues up to something temporarily wrong at the Google servers.

Thanks again for the feedback.

[Ben Appleton]

The limit of 1000 features there refers to the size of the navigational panel UI on maps.google.com.  The Maps API can show up to 50000 features on the map, subject to the other restrictions such as file size.

Ben

On 20 May 2010 09:26, "William" <willia...@gmail.com> wrote:

On May 19, 6:51 am, Matt <mattlan...@gmail.com> wrote:
>
> An example of the kml ishttp://ww3.tdot.state.tn.us/traffichistory/trfchistr2.kmz
>
this kml has 2495 Placemarks, which is greater than the limit of 1000
features (on the page that Rossko posted).  What happens if you limit
the kml files to 1000 features?
...

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScri...

[William]

Thanks Ben for the clarification, that's really useful information.
50000 features is a very generous limit.

The limits are subject to change at any time, for example when this
thread was posted a week ago, the uncompressed KML limit was 6mb, but
now it's 10mb.

http://code.google.com/apis/kml/documentation/mapsSupport.html

On May 26, 5:50 am, Ben Appleton <apple...@google.com> wrote:
> The limit of 1000 features there refers to the size of the navigational
> panel UI on maps.google.com.  The Maps API can show up to 50000 features on
> the map, subject to the other restrictions such as file size.
>
> Ben
>