Fwd: [Qgis-developer] ms_export.py : some modifications and questions

[Gary Sherman]

Begin forwarded message:

> From: Gary Sherman <sherman at mrcc.com>
> Date: September 4, 2006 11:10:48 AM AKDT
> To: Matthew Perry <perrygeo at gmail.com>
> Subject: Re: [Qgis-developer] ms_export.py : some modifications and  
> questions
>
>
> On Sep 4, 2006, at 10:18 AM, Matthew Perry wrote:
>
>> Hello QGIS folks,
>>
>>  This weekend, I began looking at the ms_export.py script for
>> converting .qgs projects to mapserver map files. I would love to see
>> an almost 1:1 conversion of qgis contructs into a mapfile so I  
>> started
>> to make a few modifications/hacks to the script:
>> - support for postgis, raster and wms layers
>> - some additional mapfile metadata for automatically creating wms  
>> servers
>> - very basic support for labelling
>> - support for graduated symbol classification
>> - a few other minor tweaks.
>>
>> I've attached the ms_export.py script along with some screenshots
>> showing the qgis project then the mapserver rendered version without
>> any manual tweaking to the mapfile. There's still alot of room for
>> improvement ... if folks find this line of work helpful, i'm more  
>> than
>> willing to continue working on this.
>>
> Ah! Finally a champion steps forward. I've been hoping someone  
> would take this on. Please continue to work on it. If you want SVN  
> access let me know.
>
>> Please give it a shot and let me know how it works for you.
>>
>> On to the questions....  I'm a bit confused as to how the  
>> ms_export.py
>> script is meant to interact with qgis.   It appears as if svn  
>> build as
>> of last week still uses the c++ version of the mapfile exporter and
>> there are calls to the python script as well as the c++ methods in
>> qgsmapserverexport.cpp. Is this still in transition or is  
>> ms_export.py
>> only meant to be a standalone tool?
>>
>
> What you see is transitional. The thought (at least mine) is to  
> provide the standalone application msexport (currently built in the  
> tools/mapserver_export dir) which drives the ms_export.py script.  
> This would be launched from the QGIS interface similar to the way  
> the help viewer is. This give folks two options: use msexport (from  
> QGIS or standalone) or run the ms_export.py script from a wrapper  
> script such as test_export.py.
>
> We would like to include this in 0.8.
>
> Thanks!
> -gary
>
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
> Gary Sherman
> Micro Resources: http://mrcc.com
>   *Geospatial Hosting
>   *Web Site Hosting
> "We work virtually everywhere"
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
>
>
>

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Gary Sherman
Micro Resources: http://mrcc.com
   *Geospatial Hosting
   *Web Site Hosting
"We work virtually everywhere"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-