[gdal-dev] in memory KML

[Clay, Bruce]

LibKml can do the in memory file and a lot of other things but the documentation / examples are rather thin.  There is documentation that tells you what the parameters of a call are supposed to be but not to tell you when to use a given method.  They have several test apps but for the most part they only test a single class at a time.  

For example, I am trying to set the attributes in a kml message.  The leverage expat to do a lot of the xml stuff and the attributes seem to relate directly to the expat attributes and not to the way they are used when OGR creates a KML file.

There are very few examples shown when I Google on the web for examples.

All in all it looks quite capable but it takes a bit of digging to find out how to do things.

Then there is the licenses issue.  I can use it in my app without problems but using it in an open source GDAL plug-in may be an issue.

Bruce

-----Original Message-----
From: gdal-dev-bounces at lists.osgeo.org [mailto:gdal-dev-bounces at lists.osgeo.org] On Behalf Of Mano Marks
Sent: Wednesday, April 01, 2009 3:13 PM
To: Mateusz Loskot
Cc: gdal-dev at lists.osgeo.org
Subject: Re: [gdal-dev] in memory KML

Seems like libkml would be a good candidate for handling KML in memory.

On Wed, Apr 1, 2009 at 3:23 AM, Mateusz Loskot <mateusz at loskot.net> wrote:
> Frank Warmerdam wrote:
>>
>> Clay, Bruce wrote:
>>>
>>> After a bit more digging I am not sure I asked the right question.
>>>
>>>
>>> What I want to do is read feature information from a shapefile or other
>>> data source and get a string that contains the feature information encoded
>>> in KML that I can pass directly into Google Earth.  I know I can do this
>>> operation is I open the shapefile write the KML data to disk then open the
>>> kml file up with fopen then read it into memory and send it t Google Earth
>>> but I would like to save the disk write the read operation.
>>>
>>>
>>> Any thoughts?
>>
>> Bruce,
>>
>> I've skimmed the KML driver and there is no sign that it uses the VSI*L
>> API for file access, so I don't see any way you can write results to a
>> memory buffer without substantial recoding in the kml driver.
>
>
> Looks like a candidate for proposal for the GSoC 2009
>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>



-- 
Mano Marks
Geo Developer Advocate
http://twitter.com/ManoMarks
Join me for Google I/O, Google's biggest Developer Conference, in San
Francisco, May 27th and 28th, 2009
http://code.google.com/events/io/
_______________________________________________
gdal-dev mailing list
gdal-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this  
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.