[QGIS-Developer] Plugin [1516] QGIS Full Motion Video approval notification.
Plugin QGIS Full Motion Video approval by pcav. The plugin version "[1516] QGIS Full Motion Video 1.1" is now approved Link: http://plugins.qgis.org/plugins/QGIS_FMV/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] 32 by 3.2?
great news, thanks for taking care of this. Cheers. On 08/02/2018 12:57 AM, Nyall Dawson wrote: > On Fri, 22 Jun 2018 at 09:20, Nyall Dawson wrote: > >> - I'd love to see us get below 25 open PRs (so that they fit on a >> single page on GitHub), but honestly I think it's probably not a >> realistic (or even desirable) goal for a project the size of QGIS. >> Maintaining a queue size of between 30-40 open requests is an >> achievable target IMO. It's small enough to be able to track them all >> without any being neglected. > For those who don't follow the github activity religiously: we are > current down to just 9 PRs, and have been averaging about 15 open PRs > for the last couple of weeks. > > We've almost hit a new milestone: having less open PRs then GDAL! > > Nyall > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Question on FGDB support for "Save As" / "Export"
Hi Nyall, I agree - these are valid reasons not to replace the open source FGDB driver with the closed source one. However - I wonder if there would be a way to support both drivers? The Open Source driver as default for reading. And the FGDB driver for writing? Note that I don't want to encourage usage of FGDB - I am no fan either. But it would be nice if we could write them in case a client demands delivery in FGDB format - which can be the case in some contracts. Thanks for keeping the discussion going. Andreas On 2018-07-31 23:28, Nyall Dawson wrote: > On Tue, 31 Jul 2018 at 20:06, Andreas Neumann wrote: > >> About issue 2: >> >> @Jürgen: can you include the necessary gdal-filegdb package also in the >> standalone installer - or are there license problems? > > -1 to packaging the gdal-filegdb package by default. My rationale: > > - I've experienced lots of issues with this driver. For one, it's much > slower to open gdbs, especially over networks. I've also hit bugs in > the past where the driver doesn't handle certain subset queries in the > same way as other ogr drivers (I can't recall the exact details, but I > think the particular issue I hit was fixed.) > > - The driver has known issues. From > https://www.gdal.org/drv_filegdb.html, there's e.g. this important > one: "The SDK is known to be unable to open layers with particular > spatial reference systems.". And then on > https://www.gdal.org/drv_openfilegdb.html there's a list of features > that we'd lose by changing to the filegdb driver: > > "Advantages of the OpenFileGDB driver: > > Can read ArcGIS 9.X Geodatabases, and not only 10 or above. > Can open layers with any spatial reference system. > Thread-safe (i.e. datasources can be processed in parallel). > Uses the VSI Virtual File API, enabling the user to read a Geodatabase > in a ZIP file or stored on a HTTP server. > Faster on databases with a big number of fields. > Does not depend on a third-party library. > Robust against corrupted Geodatabase files. > > Drawbacks of the OpenFileGDB driver: > > Read-only. > Cannot use spatial indexes. > Cannot read data from compressed data in CDF format (Compressed Data Format)." > > That's a pretty significant loss in my opinion - especially the point > about the closed source driver being non thread-safe. > > - The OpenFileGDB driver is very heavily tested for robustness and > security issues with the ongoing fuzz testing of GDAL drivers. > > - Last, but not least, we'd lose the ability to actually fix issues. > We'd be dependent on bug fixes in the ESRI SDK, and be powerless to > get fixes we need implemented. > > These are all significant issues, and the moment we make the switch to > the closed source driver and give users write support, there's no way > we can revert this decision and remove the ability to edit GDB files. > It's not a decision we can make lightly. > > I'd rather leave this decision up to individual users (and those who > make in-house software packages for deployment in their organisation) > to make. I.e. leave it as is, where it's effectively an "opt-in" > change. And push people to helping make the open driver better, as > it's a more sustainable solution in the long term. > > (Lastly, a rant: I hate file geodatabases. They are the WORST format > for spatial data that I've seen. It's like ESRI took everything which > people disliked about shapefiles and magnified those. Instead of a > handful of files, we get hundreds. Instead of minor user confusion > about how they need to package all the dependent files, we get this > super-confusing folder/file mix, which causes all sorts of issues for > non-ArcGIS software because it just breaks fundamental file management > assumptions. And they are SLOW. So SLOOW. Even in ArcGIS they are > slow to open and manage. GIve me shapefiles over this monstrosity any > day.) > > Nyall___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Question on FGDB support for "Save As" / "Export"
Hi Andreas, On Tue, 31. Jul 2018 at 12:05:52 +0200, Andreas Neumann wrote: > 2. Currently, it can only be enabled in the OSGeo4W version by selecting > the "gdal-filegdb" package. The standalone installer does not include > this package. > About issue 2: > @Jürgen: can you include the necessary gdal-filegdb package also in the > standalone installer - or are there license problems? The standalone is just a partly snapshot of OSGeo4W (ie. the (virtual) qgis-full package and all it's dependencies). Any issues would already apply to OSGeo4W. The standalone includes the OSGeo4W Installer so you can add not included packages afterwards. Not very convienient of course for people that always need filegdb. Inclusion wouldn't be a problem - and just require adding gdal-filegdb as dependency to the qgis-full. Lack of (obvious) control which driver to use might be a problem for use (i.e. setting the environment variable OGR_SKIP) - if you want to switch between the two drivers. I don't have much experience with FileGDB. I only very rarely got data in FileGDB. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: PGP signature ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] QGIS 3.x $scale in expression ?
Hi Alain, This has been changed in 3.x as there is no single map anymore, but there could be multiple map canvases per project. However, there is a new variable called "@map_scale" which you can use instead. Note that this variable is only available in some context, e.g. if you work on the symbology or labeling of a layer representation, where it is clear what canvas you are refering to. Hope this helps, Andreas On 2018-08-02 07:51, FERRATON Alain (Chef de groupe) - SG/SPSSI/CPII/DOO/ET wrote: > Hi, > > I no longer see in QGIS 3.x the $scale function in expressions? > > is there a possibility to recover the scale of the canvas ? > > Regards > Alain___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Question on FGDB support for "Save As" / "Export"
чт, 2 серп. 2018 о 12:35 Nyall Dawson пише: > I'm not sure how this change would need to be made though. At the > moment if you install the closed driver in osgeo4w it's always used, > for both reading and writing layers. Even/Jürgen is this an osgeo4w > thing or a GDAL thing? Is it possible to have two drivers installed > for the one format and always read using the closed driver? AFAIK, you can select which driver to use with envronment variable. > Another complication is that we'd still need a way for users to opt in > to using the closed driver for reading - as that may sometimes be > required too... So not a straightforward change, but still one that > I'd support! As I understand, we need something like existing rasters drivers list in the QGIS setttings where one can choose which drivers should be used. There is already ticket about this https://issues.qgis.org/issues/10313 -- Alexander Bruy ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Question on FGDB support for "Save As" / "Export"
On Thu, 2 Aug 2018 at 18:21, Andreas Neumann wrote: > However - I wonder if there would be a way to support both drivers? The Open > Source driver as default for reading. And the FGDB driver for writing? That's a great idea! In the QGIS world we'd have to compromise a bit here and not allow editing of existing layers (as you'd normally get with the closed driver). I.e. we'd only use it when writing an existing layer out to a copy on disk (e.g. via right click menu on a vector layer). But still, allowing layers to be saved as a geodatabase would be a step forward. I'm not sure how this change would need to be made though. At the moment if you install the closed driver in osgeo4w it's always used, for both reading and writing layers. Even/Jürgen is this an osgeo4w thing or a GDAL thing? Is it possible to have two drivers installed for the one format and always read using the closed driver? Another complication is that we'd still need a way for users to opt in to using the closed driver for reading - as that may sometimes be required too... So not a straightforward change, but still one that I'd support! Nyall ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Question on FGDB support for "Save As" / "Export"
On jeudi 2 août 2018 19:34:54 CEST Nyall Dawson wrote: > On Thu, 2 Aug 2018 at 18:21, Andreas Neumann wrote: > > However - I wonder if there would be a way to support both drivers? The > > Open Source driver as default for reading. And the FGDB driver for > > writing? > That's a great idea! > > In the QGIS world we'd have to compromise a bit here and not allow > editing of existing layers (as you'd normally get with the closed > driver). I.e. we'd only use it when writing an existing layer out to a > copy on disk (e.g. via right click menu on a vector layer). But still, > allowing layers to be saved as a geodatabase would be a step forward. > > I'm not sure how this change would need to be made though. At the > moment if you install the closed driver in osgeo4w it's always used, > for both reading and writing layers. Even/Jürgen is this an osgeo4w > thing or a GDAL thing? Is it possible to have two drivers installed > for the one format and always read using the closed driver? As the FileGDB driver is loaded as a plugin by GDAL, it is registered first, and then probed first when opening a dataset. Banning one of the driver can be done by defining GDAL_SKIP=FileGDB or GDAL_SKIP=OpenFileGDB and calling GDALAllRegister() again. It is also possible to control which drivers are allowed at dataset opening with GDALOpenEx() and the papszDriversAllowed argument (but that means you need to know this is a FileGeodatabase) Even -- Spatialys - Geospatial professional services http://www.spatialys.com ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1515] DSGTools Op approval notification.
Plugin DSGTools Op approval by pcav. The plugin version "[1515] DSGTools Op 1.1" is now approved Link: http://plugins.qgis.org/plugins/DSGTools_Op/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
