Tag Info

Hot answers tagged

4

The only plugins I know that involve databases in QGIS are: DB Manager SQL Anywhere plugin eVis You can also import MySQL layers directly via: Layer > Add Vector Layer... > select Database and your type.


3

Let us imagine your UI file name is MyDialogFile.py. Then, from PyQt4.QtGui import QFileDialog from MyDialogFile import MyDialog def InitGui(self): #other stuff.... self.dialog = MyDialog() def OpenBrowse(self): filename1 = QFileDialog.getOpenFileName() self.dialog.Input_TB.setText(filename1)


3

As indicated in the error message you have to install 'python-gdal' bindings. Also you may check out similar questions: Missing QGIS raster menu tools - '“osgeo python-gdal” module is missing', QGIS says “osgeo python-gdal” isn't installed on Mac


3

You can use QSettings to read and write settings. It takes care of storing the settings on all platforms without you having to find a place to write a file. I used this functionality in the Google Maps Engine Connector plugin to store UI settings https://github.com/googlemaps/mapsengine-qgis-connector/blob/master/plugin/settings.py


2

There is nothing the algorithm could simplify. In the test data you provided, one road/curve is modeled using multiple very short links which - by themselves - are mostly just short straight lines.


2

There was a bunch of bugs in the heatmap code which I've now fixed. You can either download an updated development snapshot to get these fixes, or for QGIS < 2.6 there's some workarounds: make sure your layer isn't a "multipoint" layer there's a bug which causes the layer choice from the dialog not to apply the first time in a session. Rerunning the ...


2

The openlayers plugin requires the project CRS to be set to EPSG:3857. If OL is the first layer, it sets the project CRS successfully. In your case, setting the CRS seems to fail. So set the project CRS manually to EPSG:3857 before adding an Openlayers plugin background.


2

Here is a good tutorial that helped me a lot: http://pythongisbook.com/blog/2013/04/11/creating-a-postgresql-connection-from-a-qgis-layer-datasource/


1

Modifications need to be made in 3 different files in the folder generated by Plugin Builder... QtCore.QObject.connect(self.Input, QtCore.SIGNAL("clicked()"), self.OpenBrowse) To be added in the UI File under the main Class... def OpenBrowse(self): filename1 = QFileDialog.getOpenFileName() self.dialog.Input_TB.setText(filename1) ...


1

You're making your updates feature by feature. I've found that making changes in bulk is orders of magnitude faster. prepare your changes in the loop by making a dictionary of fids to change and the desired attribute changes. Then run the update outside the loop in a single step as per the Modify Features section of the pyQGIS cookbook Documentation QGIS ...


1

download the latest version from here: http://plugins.qgis.org/plugins/openlayers_plugin/ unzip to your qgis python plugins directory on linux: ~/.qgis2/python/plugins on windows: %USERPROFILE%\.qgis2\python\plugins restart qgis now you can enable it


1

I found it! I haven't update the version attribute in pyqgis_plugin tag: <pyqgis_plugin name="my plugin" version="1.0.1" plugin_id="148">


1

Yes, you can store settings in separate files/ways with QSettings, and within the same Q(Core)Application. This makes it ideal for what you are looking to do. When initializing your PyQGIS plugin's QSettings, you will want to do something like this for a standard settings setup: my_settings = QtCore.QSettings(QtCore.QSettings.IniFormat, ...


1

I'm the author of the plugin and uploaded a new version to the plugin repository (version 2.0.1 to be precise). It was actually an old bug, but nobody used that apparently... All QGIS plugins are written by different authors. Either via plugins.qgis.org or via the info in the plugin manager you can reach the author, of find the place to create issues for ...


1

The problems with 'Polygonize' appear to have gone away in recent builds of QGIS (in later builds of 2.4 and in 2.5). Perhaps it's time for this topic to disappear too, rather than being bumped by 'Community' every so often.



Only top voted, non community-wiki answers of a minimum length are eligible