Try running a batch file with the following:
call "C:\Program Files\QGIS 3.0\bin\o4w_env.bat"
call "C:\Program Files\QGIS 3.0\bin\qt5_env.bat"
call "C:\Program Files\QGIS 3.0\bin\py3_env.bat"
pyrcc5 -o resources.py resources.qrc
either place the batch file in your directory with resources.py or type in an absolute path.
I ran ArcGIS Desktop 10.3 on the Windows 10 Technical Preview for a couple months, over several different builds of Windows, and everything worked fine (I was on the "Fast" ring). I wasn't using it intensively but I didn't encounter any problems. However, I stopped using the Windows 10 Tech Preview around July 1 and went back to Windows 7, so I have not run ...
I do not see a direct question here and I am little late in answering this. Yet, I have had a hard time setting up a similar environment recently and could not find a simple solution that did not involve hacking source files... So, here is what worked for me:
Install Python 3.6 (32 bit)
Create a virtual environment and activate it
pip install django
Could be wrong but you should reinstall QGIS 3.18 with the new installer. QGIS standalone installers on Windows are all based on OSGEO4W. At the moment, 2 OSGEO4W installers and only the new one allows for point cloud support.
See announcement at https://lists.osgeo.org/pipermail/qgis-user/2021-February/048137.html
You may try the new standalone installer ...
Both QGIS and GRASS GIS are standalone applications which can be used on their own. QGIS is using some of the functionality from GRASS GIS through QGIS GRASS Plugin and through QGIS Processing. Each of these can support some of the tools available in GRASS GIS or somehow modifies their usage. In this context, the functions or tools in GRASS GIS are called ...
I think I discovered the problem. Is a kind of conflict with AVG Protection. If you use AVG antivirus (AVG Protection 2016.71.797 in my case), try to uninstall it, reboot and try ArcMAP again. It worked for me.
On my machine which is a Windows 10 computer the normal template that I would delete to restore ArcCatalog to its default settings is here:
You have really two options.
Create a file with needed scales and share the file with your end users. They, with your guidance, will update the scales in the map document they are working. This is something they will need to do for every map document they will create.
Create a new empty map document. Add any layer and then remove it. Now the Map Scale list ...
I have been able to replicate your problem on a Windows 7 system using QGIS 2.14 LTR.
Similar to your batch file, the QGIS install includes a python-qgis batch file which you can use to run scripts with the environment pre-configured. As I've tested on 2.14 LTR my batch file is %OSGEO4W_ROOT%\bin\python-qgis-ltr.bat ( depending on your version your file may ...
Below are some resources related to AppEEARS that should help with some of the things you are trying to accomplish with MODIS data. Using the AppEEARS API, you can determine product availability, and submit requests for a host of geospatial datasets from a variety of federal data archives (including MODIS version 6 data). When submitting an AppEEARS Area ...
Try to upgrade to the latest version.My suggestion is that you remove version 3.4.x and install the latest version 3.10.
From my experience QGIS loads slowly when we have too many plug-ins installed. Try removing those that you do not need.
Just to make sure that the issue is not related to your PC, try to install QGIS on another machine and see if the ...
I've also had my share of QGIS slowness troubleshooting. Here are things I try; some probably don't apply directly in your situation but summarizing for when others have the same question.
Look at the Log messages (bottom right) in case there is some meaningful error message that provides a clue what to fix.
Try with new, empty user profile, in case ...
Use an IT Asset Manager
I would advice to use a management tool, which would enable you to handle not only the installation of QGIS, but also all current and future deployment/update needs.
About fifteen years ago, I used a similar software to manage a number of windows PCs, but it seems it has not been developed for a while.
A tool like
The Open Endpoint ...
You need to download QGIS 2.14.3 from OSGEO4W in order to be able to open ECW file format. The QGIS help stated that clearly. Also, here is a good source on ADDING ECW SUPPORT IN QGIS. The help provides good information on how to open ECW file format using different operating system.
Your PYTHONHOME should be:
Your PATH should include (in the beggining):
PYTHONPATH should have:
ArcGIS Survey Analyst was an extension product for ArcGIS Desktop 9.3.1, and earlier, that was deprecated at ArcGIS 9.3.1 and did not ship with ArcGIS 10.
The ArcGIS 9.3.1 System Requirements included Windows 7 (with some limitations) but no later OS versions.
ArcGIS 9.3.1 was retired for support on 31 Dec 2013.
With such a new operating system (Windows ...
Firstly, I see you have a standalone install of QGIS; my answer is based on an OSGeo4W install (it's been a while since I used the standalone installers) but I think the approach should be much the same.
If you just want to use a python shell, you can make a copy of your osgeo4w.bat file in the same location and rename it (like osgeo4w_pyqgis.bat) or ...
So this worked for me but no promises because I don't really know what I did I just followed some stuff I found else where. Now I'm on win 10 installing PostgreSQL 11.5 and postgis 2.5 (installed through the native application stack builder) all 64bit and I just did a new install of them all.
Then I followed the instructions here and copped the dll files "...
The GUI is a different exe than the command line one.
The command line tool is at C:\Program Files\PostgreSQL\12\bin\shp2pgsql.exe
while the GUI is at C:\Program Files\PostgreSQL\12\bin\postgisgui\shp2pgsql-gui.exe
I had a very similar issue and eventually resolved it by accident when I finally disconnected a hard drive that had failed, but was still being recognized by Windows 10 as present. QGIS was trying to scan the drive during startup. Disconnecting the drive led directly to a resolution of the issue.
GeoPandas development team does not have control over the version which comes from conda defaults channel, but it does have control over conda-forge channel. GeoPandas installed from conda-forge will be always the most recent release, unless there are some other dependency constraints.
If using conda, ideally install GeoPandas using conda install -c conda-...
You set the path one step too deep.
The example path in the error message set JAVA_HOME=C:\Program Files\Java\jdk8 gives a hint and if you open the startup.bat file with a text editor you will see a line
if not exist "%JAVA_HOME%\bin\java.exe" goto badJava.
Remove \bin from your JAVA_HOME and GeoServer will start.
It's too late I imagine but for someone esle with the same problem.
It worked for me in W7