QGIS 2.14 standalone GRASS provider missing Msys folder, can't execute tools

QGIS 2.14 standalone GRASS provider missing Msys folder, can't execute tools

In QGIS 2.12 and down, when one went about manually setting the GRASS provider folder paths, this was the way to do it In GIS 2.14 there is no Msys folder in the same path ...appsmsys or any other folder in the QGIS installation. So even though QGIS standalone needs to have it set correctly in order for GRASS tools to work, it cant be done. So how do you make GRASS tools work in QGIS 2.14

I got the same problem using the Osgeo installer, but I just managed to solve it. First download this https:sourceforge.netprojectsmingwsourcetyp_redirect Install it, look for msys-base package and install it. Set the path to msys in QGIS to C:MinGWmsys or what ever local drive it was installed on and the Grass algorithms should work fine.

So heres the deal: QGIS 2.14 standalone doesnt come with msys installation, but comes with grass 7 folders. QGIS 2.12 standalone comes with msys and grass 6.4 folders, yet no grass 7. The solution is as simple as copying the folders from one registry to the other. I worked with both 2.12 and 2.14 to verify that this works, and it does. In order to have all the grass functionality working in 2.14, I copied the msys and grass 6.4 from QGIS 2.12 apps folder to the C:Program FilesQGIS Essenapps folder, and set the correct path in the providers setting.

Im on OSX 10.11.3 and Ive got the same bug with my 2.12 version downloaded from Kynchaos. I just download this file, unpack it in the msys folder that I created in the path indicated in processing options box. It seems working fine. Ive got 160 Algorithms, I dont remember if it is the expected number, can someone confirm me

Unfortunately, Grass did not work for me. directly it gives me error and hangs up.

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository … doesn't support architecture 'i386'

Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository … doesn't support architecture 'i386' I installed Ubuntu 18.04 and then while installing Virtualbox i get the i386 error message after I did: sudo apt-get update Get:1 http:nl.archive.ubuntu.comubuntu bionic InRelease 242 kB Hit:2 http:security.ubuntu.comubuntu bionic-security InRelease Hit:3 http:ppa.launchpad.netdanielrichter2007grub-customizerubuntu bionic InRelease Hit:4 http:nl.archive.ubuntu.comubuntu bionic-updates InRelease Hit:5 http:nl.archive.ubuntu.comubuntu bionic-backports InRelease Get:6 http:download.virtualbox.orgvirtualboxdebian bionic InRelease 4429 B Get:7 http:download.virtualbox.orgvirtualboxdebian bioniccontrib amd64 Packages 1426 B Fetched 248 kB in 1s 209 kBs Reading package lists... Done N: Skipping acquire of configured file contribbinary-i386Packages as repository http:download.virtualbox.orgvirtualboxdebian bionic InRelease doesnt support architecture i386 ...
Далее...

Connection string for MariaDB using ODBC

Connection string for MariaDB using ODBC What is the connection string for using MariaDB with ODBC Im guessing its something like DRIVERMariaDB ODBC 5.1 Driver; SERVERLOCALHOST; PORT3306; DATABASEDatabaseName; UIDroot; PASSWORDpassword;OPTION3; Connection strings seems to show strings for MySQL but not MariaDB. MariaDB seems to have a lot of connection strings for Access, SQL Lite, excel, etc ... What have I missed Although this is late answer, but MariaDB have that documented here SQLWCHAR ConnStr LDriverMariaDB ODBC 2.0 Driver;Serverlocalhost;UIDodbc_user;PWDodbc_pw;DBodbc_test;Port3306;
Далее...

Celery like system based on django channels

Celery like system based on django channels According to the docs of django channels: http:channels.readthedocs.ioenlatestconcepts.htmlhighlightcelerynext-steps One thing channels do not do, however, is guarantee delivery. If you need certainty that tasks will complete, use a system designed for this with retries and persistence e.g. Celery, or alternatively make a management command that checks for completion and re-submits a message to the channel if nothing is completed rolling your own retry logic, essentially. I worked with celery some years ago. Yes, it is great, it is big, it is too much. I would like to avoid it. I am searching a simple tasks queue with guarantee delivery and a re-submission on failure. An other alternative would be python-rq. But this has other disadvantages like using pickle data format instead of json. A friend gave me an advice: https:github.comfurious-lukedjango-cq Looks good. From the docs An attempt to implement a distributed task queue ...
Далее...