Why I am moving from Google Earth Pro to QGIS

I’ve spent a lot of time developing an open source workflow for permaculture design. While, initially, I thought that Google Earth Pro was my ticket to professional level work, I slowly began to realize the limits that the platform has. I’ll admit, I spent all this time working on learning one type of GIS that I wanted it to be the one I could use until the end of time. But there are some pretty compelling reasons to use QGIS over Google Earth Pro if your goal is to do professional design work, and that is the subject of my article.

Updates and support

I’m fairly certain that Google has been developing their Google Earth Engine¬†while GEP has been left on version 7.1 for years. QGIS on the other hand just came out with version 2.16, and is continuously developing their platform. It’s simply a matter of goals. I don’t think Google really ever wanted to create an ArcGIS alternative, and after using both GEP and QGIS I understand the vast differences in their user interface and capabilities.

File Type Support

This is a pretty straight forward benefit to using QGIS. It supports many more file types that you are going to encounter while doing geospatial analysis. Many data types on websites like CTECO (Connecticuts repository of GIS data) can be used in QGIS, while GEP cannot handle any of it. Take the shapefile, or SHP. Here is a file that needs to be converted to either one of the file types that GEP can support, KML or KMZ.

QGIS is meant to be an open source, high end software and thus understands the need to be able to open and use file types used by the dominant company in GIS: ESRI.


QGIS is adept in handling databases, something I am learning more about everyday. The beauty of databases is that when I create a shape to represent some data on site, for example a riparian buffer, I can create a table with information about that buffer such as seasonal flow, water quality tests, and what kind of species composition is contained within the buffer. I’ll be honest though, I haven’t quite figured out how to do what I just said, but I think it is within the realm of possibility.

Datums & Geolocation for everything

Everything you do on this platform will need to be marked geospatially. Because of this, the workflow that all stems from the master GIS file will be better streamlined. Also, due to the large numbers of plugins available and file types supported, you can export data from QGIS to the next step such as LibreCAD for some CAD work, all while maintaining GPS locations which will become helpful in the field.

Datums are quite possibly one of the primary reasons to switch over. A Datum is essentially a way of orientating the GPS coordinates, there are many, and to keep everything smooth you need to be aware or which datum you are working. The orthoimagery that I use works on the EPSG:2234 datum for example, while GEP only works on WGS84.

It all comes down to workflow, conversion, and goals

QGIS makes the professional open source workflow all that much better. There are many municipalities and governments investing in this technology and doing real world projects on the ground. To me, that signals that QGIS is the better choice for having the workflow be smoother and save time. It is just too much of a hassle to rely on third party apps to convert data from GEP to anything else that will be useful.

Though my one caveat is to not throw out the baby with the bathwater. GEP is a wonderful software and I have had happy clients who end up with the GEP file and can do what they need to do at their level. Most clients need to visualize and play with their data on the fly, GEP is perfect for that. For us other designers, who want to be taken seriously but don’t want to fork up the cash for the proprietary software, QGIS is a great option.

Leave a Reply

Your email address will not be published. Required fields are marked *