[gdal-dev] Scripting OGR and KML

[Brian Hamlin]

I am new to scripting OGR, and for better or worse, I have chosen to 
work with the Perl interfaces for now. I am writing a few test scripts 
as part of the 1.5 testing phase.

You may be interested to know that the KML driver can be opened as a 
Datasource, so writing to it effectively writes directly to KML from a 
script.  KML is interesting because a) it is becoming widely accepted 
in the various geobrowsers, and b) it simplifies the projection model 
to a single case. It is essentially a simple display format.

So the Question is this:

  In OGR terms I see the Layer, Features and Geometry.. A Feature has a 
FeatureDefinition.

  In KML terms, a Layer is a Folder, and Features are the Placemarks. I 
can see by conversion testing that a Layer/Folder can have a name , and 
Feature/Placemark can have a Name and a Description. The description 
can be quite long.

   But using the class interfaces in a script, I dont see how to set 
these things.  ???

   It looks like the name in a Feature Definition could be the name of a 
Placemark. But that leaves Layer - Name, and Feature - Description ??

   pointers/insights appreciated
     -Brian


On Dec 7, 2007, at 6:56 PM, Lucena, Ivan wrote:

> Howard,
>
> I was helping someone that needed to use gdal2types.py from the latest 
> distribution of FWTools and we got into trouble because Phyton 2.4 
> couldn't find gdal_fw.dll even tough it was on the PATH. The reason 
> for that is probably because the user doesn't had enough power to 
> register environment variable during the running of the installer. I 
> tried to set the PYTHONPATH on the command prompt but it didn't worked 
> so we finally called the IT guy to re-install FWTools as administrator 
> and it worked. Do you know exactly what is missing in a case like 
> that?
>
> Best regards,
>
> Ivan
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev