[Qgis-developer] OpenStreetMap Hackday - September 9th
Hi QGIS Devs, Just to let you know, OpenStreetMap is holding a Hackday in Birmingham the day after our "State of the Map" conference. Tickets are still available for the conference if you are wanting to attend on the 6-8th September: http://2013.stateofthemap.org/info/booking/ For the hackday on Monday 9th September, please register for a free ticket through the eventbrite page: http://2013.stateofthemap.org/blog/introducing-sotm-hackday/ I hope to see some of you there. :) Cheers, Rob ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Fwd: Call for Presentations - SotM 2013 (annual conference)
Just to add a little more to the Call for Presentations: This year I personally want to try and get as many people involved as possible. We are therefore hoping to have a Poster Exhibition for people who may not be able to attend in person (we can print them locally). If this sounds interesting to you, please use the same form and specify "Poster" as the "Session Format". Posters can be mainly pictorial, or include text. You can bring it yourself or send an electronic copy for local printing (Sponsorship to cover printing costs would be much appreciated - If you know a company who would be interested, please let us know). http://www.stateofthemap.org/info/call-presentations/ (Call for Presentations closes on Monday 10 June 2013.) ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Fwd: Call for Presentations - SotM 2013 (annual conference)
Hi QGIS community, - please forward this on as you see fit - It's that time of year again when OpenStreetMap reaches out to the community to find out what you've been up to. That's right - it time to submit your presentation ideas for OpenStreetMap's annual "State of the Map" conference. If you have something interesting to present about your work with OpenStreetMap and would like to tell the world, we would love to hear about it. Simply fill out the "Call for Presentations" form explaining the topic of your presentation. To keep things easy, at this stage we just need a few words, not a full presentation. :-) http://www.stateofthemap.org/info/call-presentations/ (Call for Presentations closes on Monday 10 June 2013.) === A bit more information === The State of the Map 2013 Conference to be held in Birmingham, United Kingdom, from 6 to 8 September is calling for presentations. The theme of this year’s conference is “Change” so we are particularly interested in presentations addressing this theme. Our programme will cover a wide range of topics that will interest everyone from the new OpenStreetMapper to the professional contemplating using our data. We are seeking presentations from businesses, the public sector, charities, and individuals. If you have something to say, for example, about switching to OSM, barriers to its use, apps for mobile mapping, changing community organisation or behaviour, historical mapping, or just anything that you want to present, then make sure you register your proposal with a a few words to describe the topic. Tutorial sessions are especially welcome! === That link again === http://www.stateofthemap.org/info/call-presentations/ (Call for Presentations closes on Monday 10 June 2013.) ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Welcome to our newest core commiter: Victor Olaya
That's fantastic news. There's been some fantastic work in the SEXTANTE svn over the last few weeks so it will be great to see some of this in QGIS core (e.g. the fTools and SEXTANTE native algorithms can now write to memory layers in the latest development version) :-) Rob ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] New Plugin - Edit Any Layer
Hi All, It seemed a little bit odd to me that QGIS is able to open many file types but you can only edit a couple of them. Being new to the world of GIS and therefore not understanding any of its history, this seemed as odd as photoshop being able to open but not edit jpeg files! In part of my work looking at adapting fTools / SEXTANTE to write to memory layer / any ogr format, I have created a standalone plugin that converts any vector layer to a memory layer (and therefore allows you to edit the layer). This plugin is hosted at [1], if you like I will move it to a more permanent location. Notes: * Filters for just vector layers (but could be further filtered to vector layers that cannot be edited in their current format). * No progress bar at the moment (at 1000's of features the plugin can take a little while so will add a progress bar at a later date). [1] http://ubuntuone.com/3Zl1ojo3ZMUJxMqj2kcZaX Regards, Rob ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] fTools dev - write to any ogr format or to memory layer
Hi all, Thanks for the support earlier in the month when I was asking about how to improve the fTools plugin so that it can save to any ogr file format. I have now had the time to get up to speed with the qgis documentation and have had a quick play with the code. In my original question I was provided 2 solutions: 1. Nathan W suggested that I change the plugin so that it writes to a memory layer (I've got this working in a test case). 2. Giuseppe S pointed me in the correct direction to allow saving to any ogr format (I believe I could do this) Question: Which is preferred? Is the memory layer quicker? How does the memory layer compare when working with large datasets? To me it seemed odd that the fTools was asking to save the result to a new file (after all I was asking for some geometry analysis), but a memory layer has to be manually saved otherwise you risk loosing it. If someone can point me in the direction of a snippet of python that would pull up the Layer->Save As... window that would be awesome. Otherwise if this is not possible, in order to have a save dialogue at the end of the plugin execution you would be looking at implementing save to any ogr format again!! All thoughts welcome, Rob ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Save dialog for plugin development
Fantastic. I'll take a better look next week and will see if I can forward a patch to get one of fTools functions writing to any ogr format. If the qgis team are happy with this I will look at the other functions in ftools. Probably best to use git for that so may need a quick heads up on how to use just the ftools folder of qgis git repository. Also would be nice to know what tools people use for python (e.g. IDEs etc). I'm new and so far most of my python work has been small but with something like ftools it is tricky to follow over several .py files. Rob On Thursday, 5 July 2012, Giuseppe Sucameli wrote: > Hi Rob, > > On Thu, Jul 5, 2012 at 9:30 PM, Rob Nickerson wrote: >> I noted >> that gdal tools have a hard coded look up table. If this is the only way >> then can i suggest we bring such a table into the core so that all plugins >> can make use of it. Alternatively we switch to write to a memory layer - >> however I do not know how to do this... > > you're right, GdalTools has a map containing all the drivers > informations, it gets everything from the gdal module but that > part was developed about 2 years ago as workaround for some > old QGis bugs. > > Have a look at QgsVectorFileWriter static methods, > supportedFiltersAndFormats() [1] should be the one you need. > > Regards. > > [1] http://qgis.org/api/classQgsVectorFileWriter.html#a6a21cf775f777b9ed4ba445db33aa08d > > -- > Giuseppe Sucameli - Faunalia > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Save dialog for plugin development
Hi List, Just wondering if anyone has had any thoughts re my earlier question. To recap I am trying to edit the fTools plugin so that you can save to any ogr format. I have found QgsEncodingFileDialog().selectedNameFilter() which returns the file name format however this is not compatible with the way QgsVectorFileWriter() works. The file writer requires the "driver name" as a format (e.g. ESRI Shapefile) whereas selectedNameFilter() returns the hard coded name in the save dialogues drop down box (e.g. ESRI Shapefiles [OGR] (*.shp *.SHP) ). My question was: Is there an easy way to get just the driver name. I noted that gdal tools have a hard coded look up table. If this is the only way then can i suggest we bring such a table into the core so that all plugins can make use of it. Alternatively we switch to write to a memory layer - however I do not know how to do this... On an related note: Sextante includes ftools - is this by link or has the ftools code been moved into part of sextante? How does this effect development of ftools? Thanks, Rob ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] plugin dev - save to ogr vector file
On Wednesday, 4 July 2012, Paolo Cavallini wrote: > Il 03/07/2012 20:17, Rob Nickerson ha scritto: > >> I am brand new to QGIS (having got here from my work with OpenStreetMap) so apologies >> if I am posting this in the wrong place. What I am trying to do is adapt the fTools >> plugin so that it can save to any ogr verctor file format. The reason behind this is >> that I found the ESRI shapefile format to be restrictive (e.g. attribute values are >> limited to 254 chars - 80 in QGIS??). > > that would be a very welcome addition, thanks. please note that fTools are now > incorporated also in Sextante plugin. The plugin also saves by default in shp, but > users can select other formats as well. > could this solve your problem? > all the best. > -- Sounds like this solves my problem.:-) Is it worth spending a few moments to bring qgis online documentation up to date? I struggled to find the info I needed :-( rob > 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 > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] plugin dev - save to ogr vector file
Hi All, I am brand new to QGIS (having got here from my work with OpenStreetMap) so apologies if I am posting this in the wrong place. What I am trying to do is adapt the fTools plugin so that it can save to any ogr verctor file format. The reason behind this is that I found the ESRI shapefile format to be restrictive (e.g. attribute values are limited to 254 chars - 80 in QGIS??). So far Carson has kindly pointed me in the direction of the QGIS repo and I have exposed the other ogr formats in the save file dialog. This is where I get stuck. I can call QgsEncodingFileDialog().selectedNameFilter() to get the file name format however this is not compatible with the way QgsVectorFileWriter() works. The file writer requires the "driver name" as a format (e.g. ESRI Shapefile) whereas selectedNameFilter() returns the hard coded name in the save dialogues drop down box (e.g. ESRI Shapefiles [OGR] (*.shp *.SHP) ). Q: Is there an easy way to get just the driver name? - - - - - - - - - - - - - - - FYI I have looked at gdal tools. They set up a dictionary to be able to lookup any "LONGNAME" and return the driver name (SHORTNAME). The longnames are hard coded in the plugin and represent the QGIS save dialogues drop down format names (with the [OGR] and bracketed file extensions cut). The shortnames are the driver names from ogr. This code can be seen here: http://hub.qgis.org/projects/quantum-gis/repository/revisions/master/entry/python/plugins/GdalTools/tools/GdalTools_utils.py#L562 Although this should work, it would seem odd to have this hard coding in every plugin that wants to write to any ogr format!! Any ideas appreciated Regards, Rob ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
