New answers tagged

3

I have done a similar stuff, mine does work. Check it out. It is for 2.14 qgis. If you are locked you should probably check http://docs.qgis.org/2.2/en/docs/pyqgis_developer_cookbook/raster.html (see the version number on the link) from PyQt4.QtCore import QSize from PyQt4.QtGui import QPainter, QImage, QColor from PyQt4.QtCore import QFileInfo from ...


3

I got it to work on my GNU/Linux machine by replacing this code block from your script: QgsApplication.setPrefixPath('/usr', True) QgsApplication.initQgis() by this one: qgisApp = QgsApplication([], True) QgsApplication.setPrefixPath('/usr', True) QgsApplication.initQgis() The first line of this code block initializes the QgsApplication class, making ...


0

Your error has nothing to do with JSON, there is a problem with the PostGIS datastore jar on your path. The most likely cause of this issue is that you have combined jars from different GeoTools releases. Check your pom.xml file - the usual practice is to use a property geotools.version set to the version you plan to use: <properties> ...


3

A similar idea to Underdark's, but doesn't require a unique field Adding a unique id is easy with attribute editor and $rownumber, but it can be slow if you're using shapefiles and have lots of points. Use Rule Based Rendering, and have two rules randf(0.0,1.0)>.9 [default rule] Unselect the default rule so it doesn't appear, and symbolise the first ...


2

Other way, if no field suitable for modulo filter, is create a cluster layer. There is a plugin: https://plugins.qgis.org/plugins/QgisMarkerCluster/ Then use Scale Dependent Rendering...


4

Your dataset needs some kind of feature ID, like in this example: Then you can use a rule using the modulo operator % to fhe features, e.g. every 10th feature only: <theID> % 10 = 0 This is the corresponding rule-based renderer. You can add scales to the rules as well.


1

Thanks to MappaGnosis, I finally found the answer. The problematic dataset was in EPSG:4326 (whereas the rest of the project is in EPSG:3031, but that doesn't really matter). This CRS causes rendering issues near the poles, which seems logical when you think about it. Reprojecting the dataset in EPSG:3031 (Polar Stereographic) ultimately solved the issue.


1

The problem is, that the orientation switches for every part of the network (like in the red circle). Why? The orientation of your offset changes from one side to the other for some parts because these parts were drawn into your GIS in the opposite direction. Lines are drawn from a From/Start point to a To/End point, and if you offset a line the ...



Top 50 recent answers are included