[Qgis-user] Crowdfunding campaign for a Point Cluster Renderer
Hi all, I've just launched a new crowdfunding campaign to implement a web-mapping style cluster renderer for QGIS: http://north-road.com/qgis-cluster-renderer-crowdfunding/ Any assistance you can offer in spreading the word about this would be greatly appreciated, and help make this cool new feature a reality! So please reshare via twitter/facebook/etc, and if you've got any contacts in the local user groups who might be interested please let them know too... Cheers, Nyall ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
[QGIS-it-user] QGis 2.14 LTR - Errore nella creazione di Cataloghi
QGis 2.14 LTR, 64bit, installazione stand alone, MSWindows 7 e 8. Segnalo il malfunzionamento della funzione Raster -> Miscellanea --> Crea raster virtuale (Catalogo). Il malfunzionamento si manifesta nella perdita di dati o nella perdita di risoluzione del raster virtuale (ossia, il programma carica perfettamente tutti i raster del mosaico ma alla fine del processo, a seconda dei raster che carico,o ottengo un raster virtuale illeggibile, ossia una moltitudine caotica di pixel varicolori o ottengo un raster con perdita di risoluzione e di dettagli grafaici rispetto all'originale (??? ..lo so che questa è difficile da spiegarsi, ma tant'è). Se invece carico uno ad uno i vari raster del mosaico nella maniera classica, tutto funziona alla perfezione. ___ QGIS-it-user mailing list QGIS-it-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-it-user
[Qgis-user] Clip tool regression
Dear list members, There appears to be a regression in the clip tool accessible from the Vector > Geoprocessing Tools menu. In the past, the ftools version of the clip tool applied the clip operation to selected features only (if features were selected). This is no longer the case and the clip operation is now applied to all features, ignoring any selections. This applies to both the Input and Clip layers. Does anyone confirm? I'm using QGIS Master on Ubuntu 16.04. Regards, Frank. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] GDAL warp not functional in 2.16
Hi On 07/25/2016 04:16 PM, Bernd Vogelgesang wrote: Hi, just realized that warp does not work anymore in my upgraded 2.16 on Linux Mint. Neither in a model that worked before, nor through the raster menu. The error shown there is ERROR 5: MINUSERPIXELVALUE must be specified. No idea what this means. Was not able to pick settings that would allow warp to run. This worked for me: micha@mint-18-work ~/GIS/DEM/SRTM-1arc_v3 $ gdalwarp --version GDAL 2.1.0, released 2016/04/25 micha@mint-18-work ~/GIS/DEM/SRTM-1arc_v3 $ gdalwarp -s_srs EPSG:4326 -t_srs EPSG:2039 n30_e035_1arc_v3.tif n30_e035_epsg2039.tif Creating output file that is 3351P x 3859L. Processing input file n30_e035_1arc_v3.tif. Using internal nodata values (e.g. -32767) for image n30_e035_1arc_v3.tif. Copying nodata values from source n30_e035_1arc_v3.tif to destination n30_e035_epsg2039.tif. 0...10...20...30...40...50...60...70...80...90...100 - done. micha@mint-18-work ~/GIS/DEM/SRTM-1arc_v3 $ gdalinfo n30_e035_epsg2039.tif Driver: GTiff/GeoTIFF Files: n30_e035_epsg2039.tif Size is 3351, 3859 Coordinate System is: PROJCS["Israel 1993 / Israeli TM Grid", GEOGCS["Israel 1993", . Perhaps try on the CLI to be sure it's a QGIS issue. Local issue? Any alternatives for warp (preferably working in a model)? Cheers Bernd ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] GDAL warp not functional in 2.16
Hi, just realized that warp does not work anymore in my upgraded 2.16 on Linux Mint. Neither in a model that worked before, nor through the raster menu. The error shown there is ERROR 5: MINUSERPIXELVALUE must be specified. No idea what this means. Was not able to pick settings that would allow warp to run. Local issue? Any alternatives for warp (preferably working in a model)? Cheers Bernd -- Bernd Vogelgesang Siedlerstraße 2 91083 Baiersdorf/Igelsdorf Tel: 09133-825374 ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] Handling of PostGIS TopoGeometry layers
Hello everyone,
I am currently tinkering with the PostGIS topology capabilities and therefore
having QGIS as an "frontend" for editing the TopoGeometries. That works really
well so far, as long as we are talking about really minor counts of polygons in
the layer to be edited.
That is because there is no spatial indexing available for the columns of type
TopoGeometry.
I was examining the SQL-statements which QGIS uses to deal with TopoGeometry
layers. It essentialy looks somewhat like this:
---
SELECT st_asbinary("topo",'NDR'),"gid"
FROM "public"."topo_test"
WHERE "topo" &&
st_makeenvelope(138.48618410228871767,-35.03610634074148322,138.71434043049001161,-34.78702094367417885,4326)
---
Those kind of statements run really slow because the column "topo" of type
TopoGeometry does not have any spatial index.
In my case the table has a "normal" Geometry column AND a TopoGeometry column,
which are pretty much in sync.
If the statement above is altered to get the overlapping features based on the
Geometry column instead of the TopoGeometry column one can benefit from a
spatial index on the Geometry column.
So I am asking for your opinion if a possibly small addition to a TopoGeometry
layer properties in form of e.g. a checkbox is thinkable/reasonable which
enables the alteration of the statement to something like that (given the hint,
that both geometry columns have to be more or less in sync):
---
SELECT st_asbinary("topo",'NDR'),"gid"
FROM "public"."topo_test"
WHERE "geom" &&
st_makeenvelope(138.48618410228871767,-35.03610634074148322,138.71434043049001161,-34.78702094367417885,4326)
---
Would that be a way to tackle this well known performance issue?
Thanks
Andreas___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Bug in Map Composer?
Hi Benjamin, No - you need to submit it at http://hub.qgis.org/ - see also https://www.qgis.org/en/site/getinvolved/development/bugreporting.html Thanks for the efforts and greetings, Andreas On 2016-07-25 09:36, fuenfer-koenigstein.benja...@swm.de wrote: > Hi Andreas, > > I'm using EPSG:31468 (DHDN GK zone 4). The extend in composer is smaller than > the extend on project canvas as I use two map boxes in a DIN A4 layout, but > the extend which is visible in the composer is fully visible on the project > canvas. As the data sources are not public and only available within our > company network, I will have to create another test project with public wms > and local sources, try to reproduce the issues and send this project and data > to your email. Is that all right with you? > > Regards, > > Benjamin Fünfer-Königstein > > S-IP-AN-TG Techn. Geschäftsfelder > > VON: Neumann, Andreas [mailto:a.neum...@carto.net] > GESENDET: Montag, 25. Juli 2016 09:23 > AN: Fuenfer-Koenigstein.Benjamin S-IP-AN-TG > CC: qgis-user@lists.osgeo.org > BETREFF: Re: [Qgis-user] Bug in Map Composer? > > Hi Benjamin, > > What projection are you using? Is the map extent on canvas and composer > exactly the same? > > There are projections where scale varies according to the latitude of the > extent - but I rather assume it is a bug in QGIS and should be reported in > our issue tracker. > > We would need sample data/project and steps to reproduce. > > Thanks, > > Andreas > > On 2016-07-25 08:58, Benni wrote: > >> David, thanks for your answer! The scale in map composer is definitely at >> 10,000 as I set it in the map-box item properties (numeric scale bar also >> prints 1:10,000). So the scale in composer is within the threshold of layer >> visibility. Besides that, as I said, the layer with "scale dependent >> visibility" set to min 1:10,001 and max 1:9,938 IS visible in map composer >> but IS NOT in the created pdf. Meanwhile I also found out that with WMS >> sources displayed in the map, there is a similar issue. The WMS is delivered >> with different styling at different scale levels. In map composer the style >> Looks the same as in the project canvas. But in a PDF printed from map >> composer, the styling looks different (like the one for smaller scales). So >> all together it still seems to be a bug. Anyone up to test it on your >> system? I can send the project and files I created for testing. >> >> Regards >> Benjamin >> >> -- >> View this message in context: >> http://osgeo-org.1560.x6.nabble.com/Bug-in-Map-Composer-tp5277723p5277953.html >> [1] >> Sent from the Quantum GIS - User mailing list archive at Nabble.com. >> ___ >> Qgis-user mailing list >> Qgis-user@lists.osgeo.org >> List info: http://lists.osgeo.org/mailman/listinfo/qgis-user >> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user Links: -- [1] http://osgeo-org.1560.x6.nabble.com/Bug-in-Map-Composer-tp5277723p5277953.html___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Bug in Map Composer?
Hi Benjamin, What projection are you using? Is the map extent on canvas and composer exactly the same? There are projections where scale varies according to the latitude of the extent - but I rather assume it is a bug in QGIS and should be reported in our issue tracker. We would need sample data/project and steps to reproduce. Thanks, Andreas On 2016-07-25 08:58, Benni wrote: > David, thanks for your answer! The scale in map composer is definitely at > 10,000 as I set it in the map-box item properties (numeric scale bar also > prints 1:10,000). So the scale in composer is within the threshold of layer > visibility. Besides that, as I said, the layer with "scale dependent > visibility" set to min 1:10,001 and max 1:9,938 IS visible in map composer > but IS NOT in the created pdf. Meanwhile I also found out that with WMS > sources displayed in the map, there is a similar issue. The WMS is delivered > with different styling at different scale levels. In map composer the style > Looks the same as in the project canvas. But in a PDF printed from map > composer, the styling looks different (like the one for smaller scales). So > all together it still seems to be a bug. Anyone up to test it on your > system? I can send the project and files I created for testing. > > Regards > Benjamin > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/Bug-in-Map-Composer-tp5277723p5277953.html > Sent from the Quantum GIS - User mailing list archive at Nabble.com. > ___ > Qgis-user mailing list > Qgis-user@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-user > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Bug in Map Composer?
David, thanks for your answer! The scale in map composer is definitely at 10,000 as I set it in the map-box item properties (numeric scale bar also prints 1:10,000). So the scale in composer is within the threshold of layer visibility. Besides that, as I said, the layer with “scale dependent visibility” set to min 1:10,001 and max 1:9,938 IS visible in map composer but IS NOT in the created pdf. Meanwhile I also found out that with WMS sources displayed in the map, there is a similar issue. The WMS is delivered with different styling at different scale levels. In map composer the style Looks the same as in the project canvas. But in a PDF printed from map composer, the styling looks different (like the one for smaller scales). So all together it still seems to be a bug. Anyone up to test it on your system? I can send the project and files I created for testing. Regards Benjamin -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Bug-in-Map-Composer-tp5277723p5277953.html Sent from the Quantum GIS - User mailing list archive at Nabble.com. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user
