Re: [Qgis-developer] What will be in QGIS 2.0
On Thu, Jul 12, 2012 at 10:12 AM, Martin Dobias wrote: >> I have doubts for example, if the quantity of circular dependencies is >> good. See for example >> http://qgis.org/api/classQgsMapCanvas.html > > Personally, I do not see a problem in this particular instance, do > you? The only circular dependencies shown there are between > QgsMapCanvas and QgsMapTool / QgsMapCanvasMap / QgsMapOverviewCanvas - > and those are fine because they need to communicate with QgsMapCanvas. As I said, I have doubts, I am not sure if it is a problem or how it is important. I remember, that once I was looking for something around QgsMapCanvas and I found it quite difficult due to the circular dependencies. I think that it is especially a problem for readability, which I consider very important in OS project. For example, QgsMapCanvasMap is using QgsMapCanvas in 2 methods to get QgsMapRenderer (QgsMapCanvas member) and call its methods. When reading QgsMapCanvasMap source, you don't see that calling QgsMapCanvasMap methods modifies QgsMapRenderer: void QgsMapCanvasMap::resize( QSize size ) { ... mCanvas->mapRenderer()->setOutputSize( size, mPixmap.logicalDpiX() ); } it is used in QgsMapCanvas: mMap->resize( size() ); I would prefer to set QgsMapRenderer size in QgsMapCanvas, either simply something like mMap->resize( size() ); mMapRenderer->setOutputSize( mMap->size() ); or with a resize signal from QgsMapCanvasMap. The second method is void QgsMapCanvasMap::render() { ... mCanvas->mapRenderer()->render( &paint ); } which may be simply changed to void QgsMapCanvasMap::render( QgsMapRenderer* renderer) { ... renderer->render( &paint ); } We would have one circular dependency less with just 2 simple changes. In this case I don't see any real reason for circular dependency, it does not seem to be intentional design, it seems that this constellation appeared somehow itself during code evolution. I believe that 2.0 API break is good opportunity to review such places. Radim ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] shapefile editing memory issue
Hi On Thu, Jul 12, 2012 at 8:00 PM, Thorp, Kelly wrote: > Hello List: > > > > I am developing a QGIS plug-in for the purpose of running simulation models > for unique land units, as represented by polygons in a polygon shapefile. > Essentially, the plug-in uses spatial information in the polygon layer to > write a simulation model input file. It then uses Python's 'subprocess' > module to call the model executable and run the simulation. It then reads > an output file generated by the model, sets the polygon shapefile to be > editable, changes some attributes based on the model output, and then > commits those changes. Then repeating this in a loop for each feature in > the polygon shapefile. > > > > I've also included an optimization routine for the purpose of model > calibration. This essentially means doing the above procedures repeatedly > tens or hundreds of thousands of times. After each model simulation, the > updated 'simulated' attribute values are compared with other attributes that > contain 'observed' data. The optimization then repeatedly adjusts the model > parameters until simulated and observed data are in best agreement. > > > > This process can take many hours or days, while I am repeatedly editing the > shapefile and commiting the edits. However, I am not adding or removing any > features or attributes. Problem is the memory slowly creeps up and if the > optimization takes too long, I'll run out of memory and QGIS will crash. I > notice that if my optimization routine does finish, I can completely shut > down my plugin's dialog window, but the memory usage remains high. This > makes me think the problem is not in my plug-in. Any ideas for me? > > You would probably need to run your plugin under a memory profiler like valgrind to see where the leaks are occurring. My apologies if that is too low level an answer. Regards Tim > > Thanks, > > Kelly > > > > ~ > > Kelly Robert Thorp, Ph.D., P.E. > > Research Agricultural Engineer > > USDA-ARS > > U.S. Arid Land Agricultural Research Center > > 21881 N Cardon Lane > > Maricopa, AZ 85138 > > 520-316-6375 (Phone) > > 520-316-6330 (Fax) > > kelly.th...@ars.usda.gov > > ~ > > > > > > > > This electronic message contains information generated by the USDA solely > for the intended recipients. Any unauthorized interception of this message > or the use or disclosure of the information it contains may violate the law > and subject the violator to civil or criminal penalties. If you believe you > have received this message in error, please notify the sender and delete the > email immediately. > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Given the planned work on the composer I wonder if you're considering to move the print code (e.g. [1]) outside of the GUI/app control, and make it available for the python API, maybe in a QgsComposerPrinter class. This would also make Atlas simpler... giovanni [1] https://github.com/qgis/Quantum-GIS/blob/master/src/app/composer/qgscomposer.cpp#L528 2012/7/12 Tim Sutton > Hi > > On Thu, Jul 12, 2012 at 5:15 PM, Marco Hugentobler > wrote: > > Hi > > > > In my opinion, it is better to use the Qt classes for the network > requests > > than curl. In QGIS, we have QgsNetworkAccessManager, which picks up > > automatically the network settings from the options tab (proxy settings, > > exclusion list, password, disk cache). It has nice progress reporting by > > signal/slot, the possibility to interrupt the network request and a disk > > cache. And the possibility to provide custom implementations for all > that if > > necessary. > > > > Like this, WFS, WPS, WMS providers, plugin installer and open layers > plugin > > (and third party python plugins) have a unified method to do network > > requests. No need to use a different network library for each one (and > the > > mapping is never 1:1, there is always loss). > > > > So while it might be quicker (in terms of development time) to use the > GDAL > > provider, a standalone provider is always more native and flexible > (that's > > also the reason there are QGIS vector providers for postgres, wfs, gpx, > > spatialite, grass while everything can be read with the OGR provider). > > > > Thanks Marco for filling in the background to the debate we had when > developing the proposal with WorldBank/GFDRR on whether to implement > the WCS provider natively or use GDAL. All of the reasons Marco > mentions make extremely good sense. > > Regards > > Tim > > > > > Regards, > > Marco > > > > Am 12.07.2012 15:51, schrieb Even Rouault: > >>> > >>> Yes - Radim already made a first pass implementation using GDAL WCS > >>> though he said there were some problems with it - I think the most > >>> critical being that it doesn't support proxy access (I am speaking > >>> under correction here as I haven't looked into it in that much detail > >>> myself). > >> > >> This should be rather easy to add. It is just a matter of setting the > >> right > >> option to CPLHTTPFetch() (and thus the curl library), namely : > >> > >> PROXY=val, to make requests go through a proxy server, where val is > of > >> the > >> form proxy.server.com:port_number > >> PROXYUSERPWD=val, where val is of the form username:password > >> > >> Note: They can also already be used by setting the GDAL_HTTP_PROXY and > >> GDAL_HTTP_PROXYUSERPWD configuration options/environmenet variable, > which > >> will > >> act on all GDAL/OGR drivers that go through the CPLHTTPFetch() function. > >> > >> I see Radim is already a GDAL committer, so there shouldn't be too much > >> overhead > >> if he wants to hack in the WCS driver. > >> > >>> I will let Radim comment on any other issues. I think from > >>> the project perspective we don't mind too much which approach is used > >>> if the result is efficient and integrates nicely into QGIS. > >>> > >>> Regards > >>> > >>> Tim > >>> > >>> > >>> > >>> -- > >>> Tim Sutton - QGIS Project Steering Committee Member (Release Manager) > >>> == > >>> Please do not email me off-list with technical > >>> support questions. Using the lists will gain > >>> more exposure for your issues and the knowledge > >>> surrounding your issue will be shared with all. > >>> > >>> Visit http://linfiniti.com to find out about: > >>> * QGIS programming and support services > >>> * Mapserver and PostGIS based hosting plans > >>> * FOSS Consulting Services > >>> Skype: timlinux > >>> Irc: timlinux on #qgis at freenode.net > >>> == > >>> > >> > >> ___ > >> Qgis-developer mailing list > >> Qgis-developer@lists.osgeo.org > >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > > > > > -- > > Dr. Marco Hugentobler > > Sourcepole - Linux & Open Source Solutions > > Weberstrasse 5, CH-8004 Zürich, Switzerland > > marco.hugentob...@sourcepole.ch http://www.sourcepole.ch > > Technical Advisor QGIS Project Steering Committee > > > > > > ___ > > Qgis-developer mailing list > > Qgis-developer@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > -- > Tim Sutton - QGIS Project Steering Committee Member (Release Manager) > == > Please do not email me off-list with technical > support questions. Using the lists will gain > more exposure for your issues and the knowledge > surrounding your issue will be shared with all. > > Visit http://linfiniti.com to find out about: > * QGIS programming and support services > * Mapserver and PostGIS based hosting pl
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Hi On Thu, Jul 12, 2012 at 5:15 PM, Marco Hugentobler wrote: > Hi > > In my opinion, it is better to use the Qt classes for the network requests > than curl. In QGIS, we have QgsNetworkAccessManager, which picks up > automatically the network settings from the options tab (proxy settings, > exclusion list, password, disk cache). It has nice progress reporting by > signal/slot, the possibility to interrupt the network request and a disk > cache. And the possibility to provide custom implementations for all that if > necessary. > > Like this, WFS, WPS, WMS providers, plugin installer and open layers plugin > (and third party python plugins) have a unified method to do network > requests. No need to use a different network library for each one (and the > mapping is never 1:1, there is always loss). > > So while it might be quicker (in terms of development time) to use the GDAL > provider, a standalone provider is always more native and flexible (that's > also the reason there are QGIS vector providers for postgres, wfs, gpx, > spatialite, grass while everything can be read with the OGR provider). > Thanks Marco for filling in the background to the debate we had when developing the proposal with WorldBank/GFDRR on whether to implement the WCS provider natively or use GDAL. All of the reasons Marco mentions make extremely good sense. Regards Tim > Regards, > Marco > > Am 12.07.2012 15:51, schrieb Even Rouault: >>> >>> Yes - Radim already made a first pass implementation using GDAL WCS >>> though he said there were some problems with it - I think the most >>> critical being that it doesn't support proxy access (I am speaking >>> under correction here as I haven't looked into it in that much detail >>> myself). >> >> This should be rather easy to add. It is just a matter of setting the >> right >> option to CPLHTTPFetch() (and thus the curl library), namely : >> >> PROXY=val, to make requests go through a proxy server, where val is of >> the >> form proxy.server.com:port_number >> PROXYUSERPWD=val, where val is of the form username:password >> >> Note: They can also already be used by setting the GDAL_HTTP_PROXY and >> GDAL_HTTP_PROXYUSERPWD configuration options/environmenet variable, which >> will >> act on all GDAL/OGR drivers that go through the CPLHTTPFetch() function. >> >> I see Radim is already a GDAL committer, so there shouldn't be too much >> overhead >> if he wants to hack in the WCS driver. >> >>> I will let Radim comment on any other issues. I think from >>> the project perspective we don't mind too much which approach is used >>> if the result is efficient and integrates nicely into QGIS. >>> >>> Regards >>> >>> Tim >>> >>> >>> >>> -- >>> Tim Sutton - QGIS Project Steering Committee Member (Release Manager) >>> == >>> Please do not email me off-list with technical >>> support questions. Using the lists will gain >>> more exposure for your issues and the knowledge >>> surrounding your issue will be shared with all. >>> >>> Visit http://linfiniti.com to find out about: >>> * QGIS programming and support services >>> * Mapserver and PostGIS based hosting plans >>> * FOSS Consulting Services >>> Skype: timlinux >>> Irc: timlinux on #qgis at freenode.net >>> == >>> >> >> ___ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > -- > Dr. Marco Hugentobler > Sourcepole - Linux & Open Source Solutions > Weberstrasse 5, CH-8004 Zürich, Switzerland > marco.hugentob...@sourcepole.ch http://www.sourcepole.ch > Technical Advisor QGIS Project Steering Committee > > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] shapefile editing memory issue
Hello List: I am developing a QGIS plug-in for the purpose of running simulation models for unique land units, as represented by polygons in a polygon shapefile. Essentially, the plug-in uses spatial information in the polygon layer to write a simulation model input file. It then uses Python's 'subprocess' module to call the model executable and run the simulation. It then reads an output file generated by the model, sets the polygon shapefile to be editable, changes some attributes based on the model output, and then commits those changes. Then repeating this in a loop for each feature in the polygon shapefile. I've also included an optimization routine for the purpose of model calibration. This essentially means doing the above procedures repeatedly tens or hundreds of thousands of times. After each model simulation, the updated 'simulated' attribute values are compared with other attributes that contain 'observed' data. The optimization then repeatedly adjusts the model parameters until simulated and observed data are in best agreement. This process can take many hours or days, while I am repeatedly editing the shapefile and commiting the edits. However, I am not adding or removing any features or attributes. Problem is the memory slowly creeps up and if the optimization takes too long, I'll run out of memory and QGIS will crash. I notice that if my optimization routine does finish, I can completely shut down my plugin's dialog window, but the memory usage remains high. This makes me think the problem is not in my plug-in. Any ideas for me? Thanks, Kelly ~ Kelly Robert Thorp, Ph.D., P.E. Research Agricultural Engineer USDA-ARS U.S. Arid Land Agricultural Research Center 21881 N Cardon Lane Maricopa, AZ 85138 520-316-6375 (Phone) 520-316-6330 (Fax) kelly.th...@ars.usda.gov ~ This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze dynamic labels in advanced labeling
Hi Régis, On Thu, Jul 12, 2012 at 6:45 AM, haubourg wrote: > > Larry_S wrote >> >> >> Is there a means to have PAL layout the labels, then do something to >> freeze (write) *all* labels' x/y coords to the data source? >> > > Hi, +1 for that functionnality. > > I wrote a plugin to duplicate a layer and add advanced labeling fields in > order to quickly make a "labeling ready layer". having XY prelocated thanks > to PAL is big feature I miss. > (I have some more things to fix before releasing it.. ) I have an immediate need on my current project for just such a plugin! Please contact me directly if you don't mind sharing it a bit before release. The logic in my patch to freeze dynamic labels comes just after the labels are drawn to the canvas using PAL. It currently can't write all layer labels to its source (or a duplicated layer) unless all the labels can be shown in the canvas when zooming to the layer's extent, which is possible in some labeling setups. In other words, with my approach, it requires some specific setup or interactivity from the user. The freeze labels tool I'm working towards (need it on my project with thousands of labels right now) is basically an interactive one, similar to the other labeling tools. It may be possible to mimic those actions in a plugin, to freeze all labels for a layer, but it won't be very elegant until the Python access is crafted, as mentioned by Martin (unless you are coding your plugin in C++, I guess). Regards, Larry Shaffer Dakota Cartography Black Hills, South Dakota ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] New test run
Hi Tim, Looping this into the dev list, your updates seem to have gotten all the non-expression tests in order on OSX. Perhaps someone else will pick up the mantle on the expression test. Cheers, John On Jul 12, 2012, at 5:05 AM, Tim Sutton wrote: > On Thu, Jul 12, 2012 at 1:12 AM, John C. Tull wrote: >> Hi Tim, >> >> I just posted another make Experimental run if that's helpful. I'm on IRC or >> mail if you prefer. If I'm around, I'll do what I can. >> >> Cheers, >> John > > I think the only test left failing on your system after my last commit > will be the expression builder one - an I have no clue what the error > is :-P > > Just posting your Experimental builds there regularly is great we can > get most all the diagnostics we need from that. > > Regards > > Tim > > > -- > Tim Sutton - QGIS Project Steering Committee Member (Release Manager) > == > Please do not email me off-list with technical > support questions. Using the lists will gain > more exposure for your issues and the knowledge > surrounding your issue will be shared with all. > > Visit http://linfiniti.com to find out about: > * QGIS programming and support services > * Mapserver and PostGIS based hosting plans > * FOSS Consulting Services > Skype: timlinux > Irc: timlinux on #qgis at freenode.net > == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Hi In my opinion, it is better to use the Qt classes for the network requests than curl. In QGIS, we have QgsNetworkAccessManager, which picks up automatically the network settings from the options tab (proxy settings, exclusion list, password, disk cache). It has nice progress reporting by signal/slot, the possibility to interrupt the network request and a disk cache. And the possibility to provide custom implementations for all that if necessary. Like this, WFS, WPS, WMS providers, plugin installer and open layers plugin (and third party python plugins) have a unified method to do network requests. No need to use a different network library for each one (and the mapping is never 1:1, there is always loss). So while it might be quicker (in terms of development time) to use the GDAL provider, a standalone provider is always more native and flexible (that's also the reason there are QGIS vector providers for postgres, wfs, gpx, spatialite, grass while everything can be read with the OGR provider). Regards, Marco Am 12.07.2012 15:51, schrieb Even Rouault: Yes - Radim already made a first pass implementation using GDAL WCS though he said there were some problems with it - I think the most critical being that it doesn't support proxy access (I am speaking under correction here as I haven't looked into it in that much detail myself). This should be rather easy to add. It is just a matter of setting the right option to CPLHTTPFetch() (and thus the curl library), namely : PROXY=val, to make requests go through a proxy server, where val is of the form proxy.server.com:port_number PROXYUSERPWD=val, where val is of the form username:password Note: They can also already be used by setting the GDAL_HTTP_PROXY and GDAL_HTTP_PROXYUSERPWD configuration options/environmenet variable, which will act on all GDAL/OGR drivers that go through the CPLHTTPFetch() function. I see Radim is already a GDAL committer, so there shouldn't be too much overhead if he wants to hack in the WCS driver. I will let Radim comment on any other issues. I think from the project perspective we don't mind too much which approach is used if the result is efficient and integrates nicely into QGIS. Regards Tim -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Dr. Marco Hugentobler Sourcepole - Linux & Open Source Solutions Weberstrasse 5, CH-8004 Zürich, Switzerland marco.hugentob...@sourcepole.ch http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
On Thu, Jul 12, 2012 at 2:44 PM, Tim Sutton wrote: > Yes writing tests into the project plan and explaining the value of > investing in them to the clients is the way to go! In this case it was > an easy sell since we are using the work in the project to build > software that 'must just work' and having tests will be critical in > providing that assurance. That said I think in all cases, if a client > has paid for something the will want to know that it 'just works and > keeps working down the line' too. Hopefully other QGIS developers who > are creating contracts will follow suite I think that implicitly answers the only question I had about this project - that all the stuff would be properly documented too! The World Bank are doing a lot of good things - I listened to a few talks at this http://www.data.gov/communities/conference the other day. Congrats. Barry ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Il 12/07/2012 15:44, Tim Sutton ha scritto: > keeps working down the line' too. Hopefully other QGIS developers who > are creating contracts will follow suite lesson taken ;) thanks for all -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Sorry for butting in - but I think it would be much more productive to fix/enhance the gdal WCS driver than to implement a standalone qgis provider. Etienne On Thu, Jul 12, 2012 at 10:51 AM, Even Rouault wrote: > >> Yes - Radim already made a first pass implementation using GDAL WCS >> though he said there were some problems with it - I think the most >> critical being that it doesn't support proxy access (I am speaking >> under correction here as I haven't looked into it in that much detail >> myself). > > This should be rather easy to add. It is just a matter of setting the right > option to CPLHTTPFetch() (and thus the curl library), namely : > > PROXY=val, to make requests go through a proxy server, where val is of the > form proxy.server.com:port_number > PROXYUSERPWD=val, where val is of the form username:password > > Note: They can also already be used by setting the GDAL_HTTP_PROXY and > GDAL_HTTP_PROXYUSERPWD configuration options/environmenet variable, which will > act on all GDAL/OGR drivers that go through the CPLHTTPFetch() function. > > I see Radim is already a GDAL committer, so there shouldn't be too much > overhead > if he wants to hack in the WCS driver. > >> I will let Radim comment on any other issues. I think from >> the project perspective we don't mind too much which approach is used >> if the result is efficient and integrates nicely into QGIS. >> >> Regards >> >> Tim >> >> >> >> -- >> Tim Sutton - QGIS Project Steering Committee Member (Release Manager) >> == >> Please do not email me off-list with technical >> support questions. Using the lists will gain >> more exposure for your issues and the knowledge >> surrounding your issue will be shared with all. >> >> Visit http://linfiniti.com to find out about: >> * QGIS programming and support services >> * Mapserver and PostGIS based hosting plans >> * FOSS Consulting Services >> Skype: timlinux >> Irc: timlinux on #qgis at freenode.net >> == >> > > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
> Yes - Radim already made a first pass implementation using GDAL WCS > though he said there were some problems with it - I think the most > critical being that it doesn't support proxy access (I am speaking > under correction here as I haven't looked into it in that much detail > myself). This should be rather easy to add. It is just a matter of setting the right option to CPLHTTPFetch() (and thus the curl library), namely : PROXY=val, to make requests go through a proxy server, where val is of the form proxy.server.com:port_number PROXYUSERPWD=val, where val is of the form username:password Note: They can also already be used by setting the GDAL_HTTP_PROXY and GDAL_HTTP_PROXYUSERPWD configuration options/environmenet variable, which will act on all GDAL/OGR drivers that go through the CPLHTTPFetch() function. I see Radim is already a GDAL committer, so there shouldn't be too much overhead if he wants to hack in the WCS driver. > I will let Radim comment on any other issues. I think from > the project perspective we don't mind too much which approach is used > if the result is efficient and integrates nicely into QGIS. > > Regards > > Tim > > > > -- > Tim Sutton - QGIS Project Steering Committee Member (Release Manager) > == > Please do not email me off-list with technical > support questions. Using the lists will gain > more exposure for your issues and the knowledge > surrounding your issue will be shared with all. > > Visit http://linfiniti.com to find out about: > * QGIS programming and support services > * Mapserver and PostGIS based hosting plans > * FOSS Consulting Services > Skype: timlinux > Irc: timlinux on #qgis at freenode.net > == > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Hi On Thu, Jul 12, 2012 at 3:08 PM, Sandro Santilli wrote: > On Thu, Jul 12, 2012 at 02:47:32PM +0200, Andreas Neumann wrote: > >> I also like the requirement to have tests. > > Yah, me too ! > It's really good to see all those tests as part of the plan :) > > Thanks to everyone involved in this ! > Yes writing tests into the project plan and explaining the value of investing in them to the clients is the way to go! In this case it was an easy sell since we are using the work in the project to build software that 'must just work' and having tests will be critical in providing that assurance. That said I think in all cases, if a client has paid for something the will want to know that it 'just works and keeps working down the line' too. Hopefully other QGIS developers who are creating contracts will follow suite Regards Tim > --strk; > > ,--o-. > | __/ |Delivering high quality PostGIS 2.1 > | / 2.1 |http://strk.keybit.net - http://vizzuality.com > `-o--' > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Hi Even On Thu, Jul 12, 2012 at 2:58 PM, Even Rouault wrote: > Hi Tim, > >> - Implement support for WCS as a native QGIS raster driver > > Just curious : has levering and/or improving the GDAL WCS driver been > considered > ? Yes - Radim already made a first pass implementation using GDAL WCS though he said there were some problems with it - I think the most critical being that it doesn't support proxy access (I am speaking under correction here as I haven't looked into it in that much detail myself). I will let Radim comment on any other issues. I think from the project perspective we don't mind too much which approach is used if the result is efficient and integrates nicely into QGIS. Regards Tim -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
On Thu, Jul 12, 2012 at 02:47:32PM +0200, Andreas Neumann wrote: > I also like the requirement to have tests. Yah, me too ! It's really good to see all those tests as part of the plan :) Thanks to everyone involved in this ! --strk; ,--o-. | __/ |Delivering high quality PostGIS 2.1 | / 2.1 |http://strk.keybit.net - http://vizzuality.com `-o--' ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Hi Tim, > - Implement support for WCS as a native QGIS raster driver Just curious : has levering and/or improving the GDAL WCS driver been considered ? ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] WCS and Raster improvements for QGIS
Hi, That sounds fantastic - looking forward to all these improvements! The WCS is one more OGC implementation that brings us closer to more complete GDI support. Personally I am excited about the composer improvements. Together with the serial printing initiative from the Atlas plugin we will get a quite powerful map and report generation engine. I also like the requirement to have tests. Once this is all implemented one can see what could be exposed in QGIS server and webclient. Thanks for the information, Andreas On Thu, 12 Jul 2012 14:11:11 +0200, Tim Sutton wrote: Hi All I just wanted to share some development plans we have in order to prevent possible duplication of effort. We have been funded by the World Bank/GFDRR (Global Fund for Disaster Reduction and Recovery) to add the following functionalities to QGIS: Web Coverage Service Support: - Implement test suite for WCS integration - Implement support for WCS as a native QGIS raster driver - Support addition of WCS layers from python - Implement WCS test server and document setup procedure so it can be replicated - Implement a consistent user interface for adding WCS layers Raster Improvements: - Resampler branch integration - merge to master and integrate WCS branch and ensure that all QGIS tests pass - Implement sensible default colour scaling for rasters using 2% and 98% cumulative pixel count cut off where no style exists - Implement (with c++ and python tests) range based floating point raster transparency support in QGIS (singleband rasters only) - Implement (with c++ and python tests) save as support for rasters in QGIS. (Mainly tests required as builds on existing work). - Implement support for user manipulation of raster null values in QGIS when doing Save as.. (e.g. to specify a new null value). - Support specification of region, pixel size and output CRS when doing Save as... for rasters - Add option (default behaviour) to enable OTF reprojection whenever a new layer is added that differs in CRS from existing project layers. The work will be carried by Radim Blazek under subcontract to Linfiniti Consulting CC In addition Sourcepole has been contracted by the World Bank/GFDRR to add the following improvements to the composer: Improvements to QGIS composer: - Support graticule labels on specified sides only and ensure garticule labels on inside are supported via python API - Draw 'zebra style' graticule on borders - Support printing degree marker (°) and N/E/S/W in graticule for EPGS:4326 maps - Support scale bar calculations based on ellipsoid for EPGS:4326 maps - Support placement of html elements on map composer - Support overview map bounding box overlay based on extent of another map frame - Support multipage map compositions with pagination (this will be limited to nominating a single table/html frame which can overrun the primary frame and then paginate) - Ensure composer render to pdf works with python bindings in non-gui contexts (raster pdf renderer only) - Ensure composer templates can be rendered from python by specifying a template file path - Allow tokenisation of template elements via python (e.g. by passing strings of file paths to replace composer elements in template) - Compile a test suite that validates all composer functionality works in C++ - Compile a test suite that validates all composer functionality works in python This work is being carried out in order to support the ongoing work we are doing with the InaSAFE (Scenario Assessment for Emergencies) project that we have been co-developing here at Linfiniti. The purpose in particular is to support the development of a realtime scenario report generator for post earthquake events. The InaSAFE project is being developed by BNPB, AusAID and the World Bank/GFDRR. You can find more details about the project at http://inasafe.org Regards Tim -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- -- Andreas Neumann Böschacherstrasse 10A 8624 Grüt (Gossau ZH) Switzerland ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze dynamic labels in advanced labeling
Larry_S wrote > > > Is there a means to have PAL layout the labels, then do something to > freeze (write) *all* labels' x/y coords to the data source? > Hi, +1 for that functionnality. I wrote a plugin to duplicate a layer and add advanced labeling fields in order to quickly make a "labeling ready layer". having XY prelocated thanks to PAL is big feature I miss. (I have some more things to fix before releasing it.. ) Régis -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Freeze-dynamic-labels-in-advanced-labeling-tp4987087p4987950.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] WCS and Raster improvements for QGIS
Hi All I just wanted to share some development plans we have in order to prevent possible duplication of effort. We have been funded by the World Bank/GFDRR (Global Fund for Disaster Reduction and Recovery) to add the following functionalities to QGIS: Web Coverage Service Support: - Implement test suite for WCS integration - Implement support for WCS as a native QGIS raster driver - Support addition of WCS layers from python - Implement WCS test server and document setup procedure so it can be replicated - Implement a consistent user interface for adding WCS layers Raster Improvements: - Resampler branch integration - merge to master and integrate WCS branch and ensure that all QGIS tests pass - Implement sensible default colour scaling for rasters using 2% and 98% cumulative pixel count cut off where no style exists - Implement (with c++ and python tests) range based floating point raster transparency support in QGIS (singleband rasters only) - Implement (with c++ and python tests) save as support for rasters in QGIS. (Mainly tests required as builds on existing work). - Implement support for user manipulation of raster null values in QGIS when doing Save as.. (e.g. to specify a new null value). - Support specification of region, pixel size and output CRS when doing Save as... for rasters - Add option (default behaviour) to enable OTF reprojection whenever a new layer is added that differs in CRS from existing project layers. The work will be carried by Radim Blazek under subcontract to Linfiniti Consulting CC In addition Sourcepole has been contracted by the World Bank/GFDRR to add the following improvements to the composer: Improvements to QGIS composer: - Support graticule labels on specified sides only and ensure garticule labels on inside are supported via python API - Draw 'zebra style' graticule on borders - Support printing degree marker (°) and N/E/S/W in graticule for EPGS:4326 maps - Support scale bar calculations based on ellipsoid for EPGS:4326 maps - Support placement of html elements on map composer - Support overview map bounding box overlay based on extent of another map frame - Support multipage map compositions with pagination (this will be limited to nominating a single table/html frame which can overrun the primary frame and then paginate) - Ensure composer render to pdf works with python bindings in non-gui contexts (raster pdf renderer only) - Ensure composer templates can be rendered from python by specifying a template file path - Allow tokenisation of template elements via python (e.g. by passing strings of file paths to replace composer elements in template) - Compile a test suite that validates all composer functionality works in C++ - Compile a test suite that validates all composer functionality works in python This work is being carried out in order to support the ongoing work we are doing with the InaSAFE (Scenario Assessment for Emergencies) project that we have been co-developing here at Linfiniti. The purpose in particular is to support the development of a realtime scenario report generator for post earthquake events. The InaSAFE project is being developed by BNPB, AusAID and the World Bank/GFDRR. You can find more details about the project at http://inasafe.org Regards Tim -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Freeze dynamic labels in advanced labeling
Hi Martin, On Wed, Jul 11, 2012 at 1:58 PM, Martin Dobias wrote: > Hi Larry > > On Tue, Jul 10, 2012 at 6:11 AM, Larry Shaffer wrote: >> Hi, >> >> I'm working on a fairly detailed map for print output at a known scale >> (1:24000 @ 300 dpi, 1.2 m x 2.4 m). I'm using the new label engine, >> and manually adjusting many of the labels for x/y and rotation. Labels >> are in map units, with parallel-to-line feature layout. >> >> Is there a means to have PAL layout the labels, then do something to >> freeze (write) *all* labels' x/y coords to the data source? > > I'm not aware of any straightforward solution. I have heard of some > plans to provide PyQGIS wrappers for classes responsible for (PAL) > labeling, so with your Python skills you could create a script/plugin > that would take care of freezing labels - though the API would > probably need some tweaks to allow not only draw the resulting labels, > but also fetch the label positions. > > Freezing the labeling and editing of label placement were things I > wanted to do from the early times when playing with PAL, but never got > to it close enough :-) Thanks for taking the time to address my question. I've actually coded this in C++ and it works pretty well, as a rough proof-of-concept [0]. I'd appreciate it if you checked it out, if you have the time. It's my first attempt at an actual C++ feature. There's no GUI, but it can be bluntly toggled for testing like this: * Load a line vector layer with x, y, and rotation fields in its attribute table * Configure label engine settings (I only tested with parallel-to-line settings noted above) * Enable editing for layer and the labels of its features within the map canvas extent have their coords and rotation written to the attribute table * Try move, rotate, and change label tools to test (all work well for me, and no longer 'reset' the label on first edit) The caveat here is that, on every canvas update while the layer is still editable, labels are always written to the table, even if they have already been and are identical. This causes a lot of writes that can take time to undo if layer editing is cancelled. This can be fixed. It only writes what's visible in the extent (actually a good feature), but panning around at different zoom levels, or just zooming out to layer extent if using map units and showing all labels, eventually writes most or all labels to the table. I'm thinking of wiring it to a toggle-able button in the adv. labeling toolbar. Then a user can leave it on or off while they pan. A user can then zoom in on a troublesome area, freeze the labels there, toggle freezing off, then adjust the frozen labels, while leaving the rest dynamic. There can be other settings, like only freezing selected feature's labels. [0] https://dl.dropbox.com/u/4058089/qgis/qgspallabeling-cpp_patch.diff Regards, Larry Shaffer Dakota Cartography Black Hills, South Dakota ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
Dear All, I followed your discussion with interest and I have a feeling there are two aspects to be considered: One is the developer's perspective and one is the user's perspective. From a developer's perspective there is the api change, new raster architecture (and a lot more I cannot name, basically "under the hood"). From a user's perspective 2.0 should be clearly distinguishable from 1.* (icons, GUI) and things long introduced (new symbology, new labelling) should be standard and work reliably but without regression compared to the old methods. So the project should take its time to satisfy both perspectives. my two cents Bernhard __ Information from ESET Mail Security, version of virus signature database 7290 (20120711) __ The message was checked by ESET Mail Security. http://www.eset.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
On Thu, Jul 12, 2012 at 8:44 AM, Andreas Neumann wrote: > I agree the old versions of symbology and labeling should be removed rather > sooner than later. It would increase pressure on developers, financers and > users to implement the really important bits that are missing. > > If we do this in the master version it won't hurt existing users. > > We have been discussing this for two years now and noone seems to be really > acting about the missing bits other than complaining? Someone has to do the > work or pay someone to do it. It won't happen by itself. this is fine with us, as we will continue to donate developer time through the qgis friendly courses initiative. cheers -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
Il 12/07/2012 10:12, Martin Dobias ha scritto: > My optimistic estimate would be mid-2013, though Radim will be probably > closer! In this case, IMHO we should be prepared releasing another version before the end of this year. All the best. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
Hi Radim! On Thu, Jul 12, 2012 at 9:45 AM, Radim Blazek wrote: > On Wed, Jul 11, 2012 at 3:13 PM, Tim Sutton wrote: >> API is already broken . > > While I agree with all the suggestions to cleanup GUI, I think that > GUI changes may be also done after 2.0 release, in minor releases and > continuously. API changes may not! IMO, in 2.0 we should focus on API > cleanup instead of GUI. I agree that API changes are more important during the transition to 2.0. However it also makes sense to do some highly visible GUI changes before 2.0 rather than between minor 2.x versions (where users do not expect drastic changes). > I have doubts for example, if the quantity of circular dependencies is > good. See for example > http://qgis.org/api/classQgsMapCanvas.html Personally, I do not see a problem in this particular instance, do you? The only circular dependencies shown there are between QgsMapCanvas and QgsMapTool / QgsMapCanvasMap / QgsMapOverviewCanvas - and those are fine because they need to communicate with QgsMapCanvas. > We should probably run some code analysis tools on source. Anybody > already done that? > >> Personally I was thinking / hoping we could do a 2.0 release by year's end. > > Do you also mean the end of 2013? That seems feasible. My optimistic estimate would be mid-2013, though Radim will be probably closer! Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] python problem
I want to use qgis in pytnon environment. but got some problem. as http://www.qgis.org/pyqgis-cookbook/intro.html#python-applications says but i can set up qgis 1.8 environtment. I find that grass has ability to use in python, and i succeeded. use the same method i move to qgis, it seemly worked, but actually something is wrong. can anyone have ideas for this. below is my script to set up qgis envriontment in python... import os,sys qgisdir=r'C:\Program Files\Quantum GIS Lisboa' def initqgisenv(qgisdir): os.environ['PYTHONPATH']=os.path.join(qgisdir,r'apps\qgis\python') os.environ['PYTHONPATH']=os.path.join(qgisdir,r'apps\Python27\Lib\site-packages') sys.path.insert(0,os.path.join(qgisdir,r'apps\qgis\python')) sys.path.insert(0,os.path.join(qgisdir,r'apps\Python27\Lib\site-packages')) os.environ['PATH']=os.path.join(qgisdir,r'apps\qgis\python;')+os.environ['PATH'] sys.path.insert(1,os.path.join(qgisdir,r'apps\qgis\bin')) sys.path.insert(2,os.path.join(qgisdir,'bin')) os.environ['PATH']=os.path.join(qgisdir,'bin;')+os.environ['PATH'] os.environ['PATH']=os.path.join(qgisdir,r'apps\qgis\bin;')+os.environ['PATH'] if __name__=='__main__': initqgisenv(qgisdir) from qgis.core import * # supply path to where is your qgis installed QgsApplication.setPrefixPath(qgisdir, True) # load providers QgsApplication.initQgis() print 'set up qgis environment' #QgsApplication.exitQgis() print 'exit qgis properly' ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
Il 12/07/2012 09:44, Andreas Neumann ha scritto: > We have been discussing this for two years now and noone seems to be really > acting > about the missing bits other than complaining? Someone has to do the work or > pay > someone to do it. It won't happen by itself. Agreed fully. However, given the recent experience with plugins repos (lots of very useful plugins are still to be migrated, a 10-min work, with the result they are of difficult access for new users) I'm a bit worried that we can get stuck, with the alternative of either: * releasing qgis with missing important functions, or * postponing a release with nice new features. Opinions? All the best. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
On Wed, Jul 11, 2012 at 3:13 PM, Tim Sutton wrote: > API is already broken . While I agree with all the suggestions to cleanup GUI, I think that GUI changes may be also done after 2.0 release, in minor releases and continuously. API changes may not! IMO, in 2.0 we should focus on API cleanup instead of GUI. I have doubts for example, if the quantity of circular dependencies is good. See for example http://qgis.org/api/classQgsMapCanvas.html We should probably run some code analysis tools on source. Anybody already done that? > Personally I was thinking / hoping we could do a 2.0 release by year's end. Do you also mean the end of 2013? That seems feasible. Radim ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
I agree the old versions of symbology and labeling should be removed rather sooner than later. It would increase pressure on developers, financers and users to implement the really important bits that are missing. If we do this in the master version it won't hurt existing users. We have been discussing this for two years now and noone seems to be really acting about the missing bits other than complaining? Someone has to do the work or pay someone to do it. It won't happen by itself. Andreas On Thu, 12 Jul 2012 09:22:34 +0200, Denis Rouzaud wrote: As master version is a development version, there is still 1.8 which has full symbology and labelling. Removing old stuff in master would probably accelerate improvement of the new labelling and symbology. Otherwise, waiting for full completion of requirements would probably be much longer. I am no dev so my opinion is worth my 2 cents ;) On 07/12/2012 08:53 AM, Giovanni Manghi wrote: The new ones are missing features that are available in the old ones and that are quite important when styling a map. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- -- Andreas Neumann Böschacherstrasse 10A 8624 Grüt (Gossau ZH) Switzerland ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Failing expression builder tests
Hi On Wed, Jul 11, 2012 at 11:43 AM, Nathan Woodrow wrote: > h strange. > Similar propblem on OSX for 'hawkeye': http://dash.orfeo-toolbox.org/testDetails.php?test=10717979&build=90010 I have fixed the renderer issue listed for that host. Regards Tim > On Wed, Jul 11, 2012 at 7:02 PM, Tim Sutton wrote: >> Hi >> >> Could someone who knows expression builder look at the test failures >> we are getting on some platforms e.g. >> >> http://dash.orfeo-toolbox.org/testDetails.php?test=10813294&build=89939 >> >> Thanks! >> >> -- >> Tim Sutton - QGIS Project Steering Committee Member (Release Manager) >> == >> Please do not email me off-list with technical >> support questions. Using the lists will gain >> more exposure for your issues and the knowledge >> surrounding your issue will be shared with all. >> >> Visit http://linfiniti.com to find out about: >> * QGIS programming and support services >> * Mapserver and PostGIS based hosting plans >> * FOSS Consulting Services >> Skype: timlinux >> Irc: timlinux on #qgis at freenode.net >> == >> ___ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
Hi Martin, > would you volunteer for creating a list of missing features in both > new symbology and labeling - compared to the old ones? We have a wiki > page for that, however it has been merely converted to a page with > feature requests... it would need cleaning to a bare minimum to > actually get the idea what is really missing - and how important the > missing features are. > http://hub.qgis.org/wiki/17/Switching_from_Old_to_New_Symbology_and_Labeling I will do that. I recently had to style a large amount of vectors and I hit several times this issue, so I have pretty clear what is missing in the new symbology/labelling. Moreover I know pretty well the redmine tickets and so I have also an idea about feature requests and what is not working as expected. cheers ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
As master version is a development version, there is still 1.8 which has full symbology and labelling. Removing old stuff in master would probably accelerate improvement of the new labelling and symbology. Otherwise, waiting for full completion of requirements would probably be much longer. I am no dev so my opinion is worth my 2 cents ;) On 07/12/2012 08:53 AM, Giovanni Manghi wrote: The new ones are missing features that are available in the old ones and that are quite important when styling a map. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
Hi Martin, > would you volunteer for creating a list of missing features in both > new symbology and labeling - compared to the old ones? We have a wiki > page for that, however it has been merely converted to a page with > feature requests... it would need cleaning to a bare minimum to > actually get the idea what is really missing - and how important the > missing features are. > http://hub.qgis.org/wiki/17/Switching_from_Old_to_New_Symbology_and_Labeling I will do that. I recently had to style a large amount of vectors and I hit several times this issue, so I have pretty clear what is missing in the new symbology/labelling. Moreover I know pretty well the redmine tickets and so I have also an idea about feature requests and what is not working as expected. cheers -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] What will be in QGIS 2.0
On Thu, Jul 12, 2012 at 8:53 AM, Giovanni Manghi wrote: >> That would be great. IMHO, the single most important thing in releasing 2.0, >> from an >> user point of view, is to get rid of the duplications. All the rest comes >> second, > > about duplications please remember that right not it now possible to > just "get rid" of both the old symbology and labelling. The new ones > are missing features that are available in the old ones and that are > quite important when styling a map. Giovanni, would you volunteer for creating a list of missing features in both new symbology and labeling - compared to the old ones? We have a wiki page for that, however it has been merely converted to a page with feature requests... it would need cleaning to a bare minimum to actually get the idea what is really missing - and how important the missing features are. http://hub.qgis.org/wiki/17/Switching_from_Old_to_New_Symbology_and_Labeling I would suggest that at some point we have to switch to new symbology even if there are missing features, otherwise we could postpone the switch forever, waiting for re-implementation of some features. Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer