My colleagues and I are willing to help if there is interest from the community in having prepair included in QGIS.
However, I believe, like Nathan, that including the current version is sub-optimal: we’re just calling the binary and pass the WKT of the geometries, and read the WKT returned. Rather slow for big polygons. Hugo On Fri, Jun 6, 2014 at 2:26 PM, <qgis-developer-requ...@lists.osgeo.org> wrote: > Send Qgis-developer mailing list submissions to > qgis-developer@lists.osgeo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.osgeo.org/mailman/listinfo/qgis-developer > or, via email, send a message with subject or body 'help' to > qgis-developer-requ...@lists.osgeo.org > > You can reach the person managing the list at > qgis-developer-ow...@lists.osgeo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Qgis-developer digest..." > > > Today's Topics: > > 1. Re: Realease and blockers (Tim Sutton) > 2. Re: Realease and blockers (Matthias Kuhn) > 3. Re: Realease and blockers (Paolo Cavallini) > 4. Re: Realease and blockers (Paolo Cavallini) > 5. Re: Realease and blockers (Vincent Picavet) > 6. Re: Opinion on plugin named prepair (and possible likes) > (Paolo Cavallini) > 7. Re: Opinion on plugin named prepair (and possible likes) > (Nathan Woodrow) > 8. Re: ogr osm provider seems broken (Even Rouault) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 6 Jun 2014 18:46:38 +0700 > From: Tim Sutton <li...@linfiniti.com> > To: Andreas Neumann <a.neum...@carto.net> > Cc: qgis-developer <qgis-developer@lists.osgeo.org> > Subject: Re: [Qgis-developer] Realease and blockers > Message-ID: > <CALCNqkYRTJtCg7fR2JNek8A=j6m_5Sjh1iX=apxudvh+rqx...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi > > > On Fri, Jun 6, 2014 at 4:42 PM, Andreas Neumann <a.neum...@carto.net> wrote: > >> Hi, >> >> I kind of agree. I also think the one month testing phase is too short >> to properly deal with all of the bugs. >> >> Maybe a six month release cycle with 4 month development and 2 month >> testing would be more useful in the future. >> >> Furthermore, we would probably need at least one bugfix release. >> >> But I know you have discussed this back and forth ... and there is no >> single solution that fits for everyone. >> >> --------- >> >> BTW: I believe our finances would allow to again sponsor 1 week of paid >> bug fixing from the QGIS funds. Like with the past two releases. Has the >> PSC discussed this? >> >> Not yet but we can table it in our PSC meeting tonight. And yes there is > no single release cycle that will keep everyone happy. The other suggestion > we had once was to make every third (or other increment) release purely a > bug fix release. Those enterprise orientated folks could hold out for those > instead of doing incremental upgrades. > > Regards > > Tim > > >> Andreas >> >> Am 06.06.2014 09:36, schrieb R?gis Haubourg: >> > BTW, the very short release cycle is really complicated for us. Deploying >> > prod version and testing new versions periods overshoot here. I'm alone >> on >> > that topic, and partial time only. Having longer release candidate >> period, >> > and a 6 months release cycle could help for me. >> > >> > >> > >> > >> > -- >> > View this message in context: >> http://osgeo-org.1560.x6.nabble.com/Realease-and-blockers-tp5144366p5144375.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 mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> > > > > -- > Tim Sutton - QGIS Project Steering Committee Member > ============================================== > 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. > > Irc: timlinux on #qgis at freenode.net > ============================================== > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140606/ee0cc789/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Fri, 06 Jun 2014 13:57:51 +0200 > From: Matthias Kuhn <matthias.k...@gmx.ch> > To: vincent...@oslandia.com, Nyall Dawson <nyall.daw...@gmail.com> > Cc: qgis-user <qgis-u...@lists.osgeo.org>, qgis-developer > <qgis-developer@lists.osgeo.org> > Subject: Re: [Qgis-developer] Realease and blockers > Message-ID: <5391acbf.7010...@gmx.ch> > Content-Type: text/plain; charset=ISO-8859-1 > > While testing and reporting is important without a doubt, the currently > outstanding issues could be fixed easily by the end of the month as soon > as resources are available. > > The main point is, that we should start improving where there is the > biggest effect - and that's paid bugfixing time. There are some > extremely capable and effective core devs available for this job as has > been proven in the past. > > That means: go out, tell your neighbours and social media buddies and > customers about the RC and testing. But if you want the bugs they report > to be fixed, make sure that there's somebody taking care of them. The > main problems normally are not the bugs not found while testing, but the > ones not fixed before the release. This in turn also means that I don't > think a two months bugfixing period will improve a lot. If there's two > months with developers spending time on other projects because there's > no funding available for bugfixing we haven't won anything. > > Regards, > Matthias > > > ------------------------------ > > Message: 3 > Date: Fri, 06 Jun 2014 14:01:27 +0200 > From: Paolo Cavallini <cavall...@faunalia.it> > To: qgis-developer@lists.osgeo.org > Subject: Re: [Qgis-developer] Realease and blockers > Message-ID: <5391ad97.2000...@faunalia.it> > Content-Type: text/plain; charset=ISO-8859-1 > > Il 06/06/2014 13:46, Tim Sutton ha scritto: > >> Not yet but we can table it in our PSC meeting tonight. And yes there is no >> single >> release cycle that will keep everyone happy. The other suggestion we had >> once was to >> make every third (or other increment) release purely a bug fix release. Those >> enterprise orientated folks could hold out for those instead of doing >> incremental >> upgrades. > > Yet another interesting option, already discussed, is to maintain a stable > release, > backporting fixes to it. Some work has already gone in that direction, > merging and > coordinating them would be a major improvements IMHO. > I personally think this effort should be funded by one or more of the many > big users > we increasingly have, and cannot rely on our efforts only. > All the best. > -- > Paolo Cavallini - www.faunalia.eu > Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html > > > ------------------------------ > > Message: 4 > Date: Fri, 06 Jun 2014 14:03:06 +0200 > From: Paolo Cavallini <cavall...@faunalia.it> > To: qgis-developer@lists.osgeo.org > Subject: Re: [Qgis-developer] Realease and blockers > Message-ID: <5391adfa.9080...@faunalia.it> > Content-Type: text/plain; charset=ISO-8859-1 > > Il 06/06/2014 13:57, Matthias Kuhn ha scritto: > >> That means: go out, tell your neighbours and social media buddies and >> customers about the RC and testing. But if you want the bugs they report >> to be fixed, make sure that there's somebody taking care of them. The >> main problems normally are not the bugs not found while testing, but the >> ones not fixed before the release. This in turn also means that I don't >> think a two months bugfixing period will improve a lot. If there's two >> months with developers spending time on other projects because there's >> no funding available for bugfixing we haven't won anything. > > agreed. please spread this word to users as much as possible, using the MLs, > SNs, and > any other possible medium. > that was the idea behind my post starting this thread. > thanks. > > -- > Paolo Cavallini - www.faunalia.eu > Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html > > > ------------------------------ > > Message: 5 > Date: Fri, 6 Jun 2014 14:06:43 +0200 > From: Vincent Picavet <vincent...@oslandia.com> > To: Alexander Bruy <alexander.b...@gmail.com> > Cc: qgis-user <qgis-u...@lists.osgeo.org>, Qgis Developer List > <qgis-developer@lists.osgeo.org> > Subject: Re: [Qgis-developer] Realease and blockers > Message-ID: <201406061406.43596.vincent...@oslandia.com> > Content-Type: Text/Plain; charset="iso-8859-1" > > Hi, > > Le vendredi 6 juin 2014 13:34:12, Alexander Bruy a ?crit : >> 2014-06-06 13:16 GMT+03:00 Vincent Picavet <vincent...@oslandia.com>: >> > Could we make a more visible RC release on the website, encouraging >> > testing ? >> > >> > I think that our user are not used yet to our new release cycle. We >> > really should educate them, and lower the barrier to RC testing and bug >> > reporting. As for now, even installing the RCs is complicated, so is bug >> > reporting. >> >> We already have a big banner at main page about RC and testing. Seems most >> users don't visit main page too often to notice it. > > I tried with a "standard" user yesterday, watching him use the site to get > qgis, and it was still _very_ complicated for him. He expected to click on a > "QGIS 2.4 preview download" button and the download to begin immediatly, which > is far from happening. > > Instead, the small RC link leads to a page with a lot of links, he had > difficulties to find the preview release (not knowing what a "release > candidate" > is), hesitating with osgeo4w download, then being redirected once again on the > same page, lost in the web page, finally finding a small link to a dull page > listing a lot of files (what the hell is a md5sum file ?? what is this 2.3 > version ?? where is the preview ?), of which he finally chose a random exe and > installed it. Even I was totally lost trying to get the right file. > > I think we can do much better. > > Then it is a matter of advertising the preview at large : official "call for > testing" from qgis project on osgeo mailing lists, twitter, linkedin, and if > possible on a qgis-news mailing list where we have gathered a lot of user > beforehand (with their approval of course). > > Vincent > > > > > ------------------------------ > > Message: 6 > Date: Fri, 06 Jun 2014 14:16:22 +0200 > From: Paolo Cavallini <cavall...@faunalia.it> > To: qgis-developer@lists.osgeo.org > Subject: Re: [Qgis-developer] Opinion on plugin named prepair (and > possible likes) > Message-ID: <5391b116.3080...@faunalia.it> > Content-Type: text/plain; charset=ISO-8859-1 > > Il 06/06/2014 13:17, Hugo Ledoux ha scritto: > >> A windows Installer would be nice, but, Paulo, do you mean that QGIS would >> add >> prepair? That would be tricky, since we use CGAL too. But that would be >> great. >> >> The plugin should remember the path of the EXE, it does on all computers >> we've >> tested. Report bug on the issue page with details please. > > Hi. > Hugo, would you object in tagging the plugin as experimental for now? > Yes, I meant to include prepair (the plugin+the exe+des) in the standalone > installer, > as well as making it easy to install it in other OSs. > Are you willing to help with that? > All the best. > > -- > Paolo Cavallini - www.faunalia.eu > Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html > > > ------------------------------ > > Message: 7 > Date: Fri, 6 Jun 2014 22:24:23 +1000 > From: Nathan Woodrow <madman...@gmail.com> > To: Paolo Cavallini <cavall...@faunalia.it> > Cc: "qgis-developer@lists.osgeo.org" <qgis-developer@lists.osgeo.org> > Subject: Re: [Qgis-developer] Opinion on plugin named prepair (and > possible likes) > Message-ID: > <caai8yg_r0i8fkp4a_aww0wjdwbbyve0l7zbjfv3fo3ooupn...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I'm not sure just adding it to QGIS like that is the best idea really, it's > a bit bolt on. It would be better to port the prepair C++ logic into QGIS > itself to use QGIS geometry rather then GDAL. We could then just expose the > API and wrap it in Python to expose in Processing. > > - Nathan > > > On Fri, Jun 6, 2014 at 10:16 PM, Paolo Cavallini <cavall...@faunalia.it> > wrote: > >> Il 06/06/2014 13:17, Hugo Ledoux ha scritto: >> >> > A windows Installer would be nice, but, Paulo, do you mean that QGIS >> would add >> > prepair? That would be tricky, since we use CGAL too. But that would be >> great. >> > >> > The plugin should remember the path of the EXE, it does on all computers >> we've >> > tested. Report bug on the issue page with details please. >> >> Hi. >> Hugo, would you object in tagging the plugin as experimental for now? >> Yes, I meant to include prepair (the plugin+the exe+des) in the standalone >> installer, >> as well as making it easy to install it in other OSs. >> Are you willing to help with that? >> All the best. >> >> -- >> Paolo Cavallini - www.faunalia.eu >> Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html >> _______________________________________________ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140606/5937703a/attachment-0001.html> > > ------------------------------ > > Message: 8 > Date: Fri, 6 Jun 2014 14:26:47 +0200 > From: Even Rouault <even.roua...@mines-paris.org> > To: qgis-developer@lists.osgeo.org, rich...@duif.net > Subject: Re: [Qgis-developer] ogr osm provider seems broken > Message-ID: <201406061426.47643.even.roua...@mines-paris.org> > Content-Type: Text/Plain; charset="iso-8859-1" > > Le vendredi 06 juin 2014 08:55:39, Richard Duivenvoorde a ?crit : >> Hi Devs, >> >> to me the way qgis handles .osm files seems broken, see: >> >> http://hub.qgis.org/issues/10000 >> >> http://hub.qgis.org/issues/10427 >> >> apparently ogr returns -1 on the number of features, but more important >> the feature interator seems broken >> >> Problems: loading an osm file and viewing the attribute table only shows >> 2 records (while all points are shown on the map). >> Iterating over the features with python also raises errors. >> >> Not sure if we should make this a blocker, because I'm not convinced of >> the importance of .osm files. > > Richard, > > Jukka pretty much answered rightly the questions in the tickets. The OGR OSM > driver is rather tuned to handle multi-gigabyte .osm/.pbf files, and due to > the > structure of those files, it is impossible to count efficiently the number of > features without reading it entirely. Hence -1 returned as the feature count. > If you issue an explicit SELECT COUNT(*) FROM, it means that you know what you > want, and you're ready to wait for it... > > And, also related to the structure of the data, the driver is a bit particular > in the sense that the iteratation over features with GetNextFeature() might > not work if the osm file is of a "sufficient size". See the "Interleaved > reading" > paragraph of http://www.gdal.org/drv_osm.html. > > For such cases, it might be interesting to develop a new concept in OGR, a > whole dataset feature iterator, that could return features from different > layers as soon as they are available. > > Best regards, > > Even > > > -- > Geospatial professional services > http://even.rouault.free.fr/services.html > > > ------------------------------ > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > > End of Qgis-developer Digest, Vol 104, Issue 28 > *********************************************** _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer