What's a good way to convert 25 meters (for example) to layer
coordinates? I want to create a buffer of 25 meters on my geometries,
and handle the case when they layer is in wgs84.
/Magnus
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
Hey Andreas,
On the digitizing toolbar, try "Split Parts" instead of "Split Features" on
multipart polygons.
HTH,
James
Sent from my iPhone
> On May 22, 2017, at 06:49, Andreas Wicht wrote:
>
> Hi all,
>
> I have a question regarding the behavior of the "split features" tool
> when it comes
Plugin InaSAFE approval by timlinux.
The plugin version "[183] InaSAFE 4.1.0" is now unapproved
Link: http://plugins.qgis.org/plugins/inasafe/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listi
Hi Magnus,
As I understand you are writing a script that should perform a 25m
buffer on any user layer?
I think you should never buffer unprojected layers. So blocking the
process and telling the user to transform the data to an appropriate
projection would be best in my opinion.
If you re
Hi,
There is a long-standing but elusive crash issue
https://issues.qgis.org/issues/14752
I've now narrowed it down to enabling "Discourage labels from covering
features" for a particular point layer in the provided test project. I've
also attached a recent crash dump from 2.14.15 to the ticket
For QGIS3, adding support for other basic Field-Types in class
QgsField, such as DATE / DATETIME and BLOBs should be taken into
consideration.
Also adding a field (SQLITE stored as 'cid') which would represent the
Field number inside the TABLE could simplify the use inside a Provider.
At the mome
On 29 May 2017 at 13:55, Mark Johnson wrote:
> For QGIS3, adding support for other basic Field-Types in class QgsField,
> such as DATE / DATETIME and BLOBs should be taken into consideration.
>
> Also adding a field (SQLITE stored as 'cid') which would represent the Field
> number inside the TABLE
>> What makes you think that?
Based on the implementation of the QgsSpatiaLiteProvider (which only
supports TEXT, INTEGER and DOUBLE) and the documentation of QgsField.
>> Constructor. Constructs a new QgsField object.
* \param type Field variant type, currently supported: String / Int /
Doub
I would say it's a case of bad docs as it's just a QVariant::Type and other
providers use it already.
On Mon, May 29, 2017 at 2:25 PM, Mark Johnson
wrote:
> >> What makes you think that?
> Based on the implementation of the QgsSpatiaLiteProvider (which only
> supports TEXT, INTEGER and DOUBLE)
On 29 May 2017 at 14:25, Mark Johnson wrote:
>>> What makes you think that?
> Based on the implementation of the QgsSpatiaLiteProvider (which only
> supports TEXT, INTEGER and DOUBLE) and the documentation of QgsField.
>
>>> Constructor. Constructs a new QgsField object.
> * \param type Field
Good, then I will work those samples into QgsSpatiaLiteProvider.
For Spatialite 4.5.0 QgsSpatiaLiteProvider needs to be worked on, which I
am doing now.
Mark
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.or
On 29 May 2017 at 14:36, Mark Johnson wrote:
> Good, then I will work those samples into QgsSpatiaLiteProvider.
> For Spatialite 4.5.0 QgsSpatiaLiteProvider needs to be worked on, which I am
> doing now.
Mark - what are your thoughts on
http://osgeo-org.1560.x6.nabble.com/Future-of-spatialite-pro
Hi,
As I asked previously on twitter, added new feature to PostGIS
versioning, that writes down postgresql user role, that was used for
insert or update of row.
But my github knowledge is not so good, for doing pull request, as my
commits are in two branches.
https://github.com/merkato/QGI
Hi Giovanni
Yes, confirm that it is working well now
https://www.youtube.com/watch?v=qBh0pzI2A5c
from over 2 min to 4 seconds to load the same table.
BIG thanks for everyone behind the scene. I believe the fix is done by
Nyall, so a spacial thanks to him.
read over and understand that this issu
On 29 May 2017 at 15:30, Ted wrote:
> Hi Giovanni
>
> Yes, confirm that it is working well now
> https://www.youtube.com/watch?v=qBh0pzI2A5c
>
> from over 2 min to 4 seconds to load the same table.
>
> BIG thanks for everyone behind the scene. I believe the fix is done by
> Nyall, so a spacial tha
>> what are your thoughts on
http://osgeo-org.1560.x6.nabble.com/Future-of-spatialite-provider-td5311979.
html
?
For gpkg: should remain solely with OGR.
For VectorLayers (SpatialTables and SpatialViews) is more problematic,
since OGR does not support writable SpatialViews, which I use heavily.
16 matches
Mail list logo
