Ok I'm back.  Sorry for the delay in posting updates, I wanted to be
sure the MIME filetype settting was the problem.

I had my server load the MIME .kml filetype setting, and so now I can
see my .kml files from my server.

I still am having a hell of a time with this thing though, primarily,
getting the maps to work right in the Google Earth setting.  These
questions below shouldn't be really too hard for someone with
experience to guide me with... hopefully.

1.) So, for the .kml file I have on my map set up here at
http://www.iongeo.com/aram_test_dev/map4.html,  to get it to show up
on my map I had to a. create it in google earth.  b.

On Apr 1, 12:04 pm, Barry Hunter <[email protected]> wrote:
> On 01/04/2009, Michael <[email protected]> wrote:
>
>
>
>
>
> >  On Apr 1, 2:12 am, String <[email protected]> wrote:
>
> >  > It's not within the KML file itself, it's a question of its
> >  > availability via the web. GGeoXml serves the KML file via Google's
> >  > servers, so if they can't access the file, neither can your map. This
>
> > > is why Ross was pointing out 
> > > thathttp://iongeo.com/aram_test_dev/ion_acquired_spans.kml
>
> > > is returning a 404. That file needs to be on your web server, and it
> >  > doesn't appear to be.
>
> > Hmm ... this is weird, because I can see my kml file that I've
> >  uploaded on my web server with the "aram_test_dev" directory as well
> >  as an example,
>
> It may be there, but IIS will only serve it if it knows the MIME type.
> You need to get whoever  (if its not you) admins your server to set it
> up for you.
>
> Again see this 
> link:http://code.google.com/apis/kml/documentation/kml_tut.html#kml_server
--~--~---------~--~----~------------~-------~--~----~
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