Hmm, don't think that's the issue. For testing purpose, I just
uploaded the file "test.kmz" (which I got from the .NET page) to my
server i.e. www.capetown-direct.com/test.kmz . Then in maps.google.com
I put that url into the search bar and it works!

Which means the kmz is fine, but the way in which it is being served
is not making G happy.

Thoughts?

On Sep 8, 12:41 pm, Barry Hunter <[email protected]> wrote:
> Not sure if it would cause this issue, but you do have a typo in the
> file (GE tends to be quite forgiving)
>
> http://beta.feedvalidator.org/check.cgi?url=http://www.capetown-direc...
>
> On 08/09/2009, jamesct <[email protected]> wrote:
>
>
>
>
>
> >  Hey thanks for the quick response Barry.
>
> >  Changed the Content-Type to application/vnd.google-earth.kmz and put a
> >  RewriteRule in the .htaccess so that the .NET page is accessed like
> >  http://www.capetown-direct.com/-34.0/-33.0/18.0/19.0/test.kmz(for
> >  example) but still no joy. Also tried the GET param trick but also
> >  without success.
>
> >  That file definitely works in GE4 but when I put the above URL into
> >  maps.google.com I get the error "File not found athttp://www.cape....";
> >  etc.
>
> >  Any more suggestions?
>
> >  Thanks, James
>
> >  On Sep 8, 12:13 pm, Barry Hunter <[email protected]> wrote:
> >  > Your application is returning
> >  > Content-Type:·application/kmz
>
> >  > Not
> >  > Content-Type:· application/vnd.google-earth.kmz
>
> >  > You can also add "&d=/file.kmz" which adds a 'fake' extension, which
> >  > might help foll the Google Maps server.
>
> --
> Barry
>
> -www.nearby.org.uk-www.geograph.org.uk-
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to