So, why wouldn't you just load the KML through a layer in the server?
That can be done with the API packaged with Earth Server.

Mano Marks
Geo Developer Advocate
http://twitter.com/ManoMarks




On Mon, Jun 1, 2009 at 11:15 AM, pamela fox <[email protected]> wrote:
> Hey David-
>
> I hadn't thought of that; I suppose it would be a possibility. Do you
> have an enterprise sales rep? I would advise making the feature
> request in terms of that suggestion.
>
> Note: It could be that the Enterprise Earth team is already working on
> it -- I've just told you what I know of the free API's functionality.
>
> On Sun, May 31, 2009 at 1:44 PM, Bucci, David G <[email protected]> 
> wrote:
>> Thanks, Pamela, some good news here.  On the GGeoXML, I guess I don't 
>> understand why the server side parsing capability can't be included in the 
>> Enterprise distribution, for running on our own servers.  Does it simply 
>> depend too much on internal services unique to the Google infrastructure?  
>> (it doesn't _seem_ like it would)  is it a concern about licensing or 
>> someone competing on the public internet?  Surely that'd be addressable via 
>> licensing, or simply sell it only to closed-network-only environments ...
>>
>>
>> ________________________________
>>
>> From: pamela fox [mailto:[email protected]]
>> Sent: Sat 5/30/2009 2:20 AM
>> To: Bucci, David G
>> Cc: Brady Forrest; [email protected]
>> Subject: Re: [Geowanking] questions for the Google Maps Team?
>>
>>
>>
>> Next time, I'll live-record the answers to the chat. Answers inline.
>>
>> On Thu, May 28, 2009 at 12:17 PM, Bucci, David G <[email protected]> 
>> wrote:
>>> When will they promote the public-internet-only capabilities (e.g., GGeoXML)
>>> into the Enterprise version of Google Maps, that companies/agencies deploy
>>> on closed networks?
>>>
>> No immediate plans; that's rather tricky to do. We would have to fetch
>> the file over XMLHR, and then send all the KML data to our servers to
>> be parsed by our server-side KML parser. Since we can't POST data
>> using JSONP, that'd be near impossible. Our other option would be to
>> re-implement KML parsing in JavaScript - but at that point, you may as
>> well use one of the open-source extensions like EGeoXml.
>>
>>>
>>>
>>> What's the forward plan to more rapidly deploy Google Maps API versions into
>>> that Enterprise version of Google Maps (e.g., today, the Enterprise version
>>> is still at v2.109 of the API, I believe)?
>>>
>>
>> In the next version, they've architected it to allow for version
>> updates of the API without necessitating updates of GE-E. I believe
>> that's coming soon.
>>
>>>
>>>
>>> What's the forward plan for increased synergy (not that it's not already
>>> good) between Google Maps and the Google Earth web plugin?
>>>
>>
>> Well, we just made it a bit better yesterday! We'll keep working on
>> it, of course:
>> http://googlegeodevelopers.blogspot.com/2009/05/hey-maps-api-and-earth-api-developers.html
>>>
>>>
>>> From: [email protected]
>>> [mailto:[email protected]] On Behalf Of Brady Forrest
>>> Sent: Thursday, May 28, 2009 3:11 PM
>>> To: [email protected]
>>> Subject: [Geowanking] questions for the Google Maps Team?
>>>
>>>
>>>
>>> I am at Google I/O at the Fireside Chat for the Maps team. Any questions for
>>> them? Send them soon. :-)
>>>
>>> Any answers I get I will send to the list.
>>>
>>>
>>>
>>>
>>>
>>>             brady
>>>
>>>
>>>
>>> Brady Forrest
>>>
>>> O'Reilly Radar Team
>>>
>>> p: 206-428-7666
>>>
>>> e: [email protected]
>>>
>>> w: http://radar.oreilly.com <http://radar.oreilly.com/>
>>>
>>> tw: @brady
>>>
>>>
>>>
>>> < div>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Geowanking mailing list
>>> [email protected]
>>> http://geowanking.org/mailman/listinfo/geowanking_geowanking.org
>>>
>>>
>>
>>
>>
>
> _______________________________________________
> Geowanking mailing list
> [email protected]
> http://geowanking.org/mailman/listinfo/geowanking_geowanking.org
>

_______________________________________________
Geowanking mailing list
[email protected]
http://geowanking.org/mailman/listinfo/geowanking_geowanking.org

Reply via email to