

It used to be the case that Homebrew was the better option if you needed support for other PostgreSql extensions, like PgRouting or Mapbox Vector Tiles (MVT) support.

The official PostGIS documentation summarizes the options better if you want a dead simple way to get started, use Postgres.app. That can be a barrier for users just getting started with Postgres.
POSTGRES APP SETTING PATH WINDOWS
The official documentation for Postgres lists 2 options for Windows installation. From here on, I will also refer to this combination just as “Postgres”.
POSTGRES APP SETTING PATH MAC
In this post, I’ll cover the basics of getting PostgreSql with the PostGIS extension installed on both Mac and Windows for development purposes (in production, we use Ubuntu Linux, which is another post), and look at ways you can also manage your database, import spatial data and see the results of a spatial query. So, whether you need local spatial processing for data science or GIS, or you plan to support spatial queries in an application backend, PostgreSql/PostGIS is a worthy tool. If you’re still not convinced, check out this great article all about PostGIS: Layers are also easily organized in schemas or distinct databases, and every table can store metadata (comments) about itself and every column it contains. Organization – Have you ever opened your own GIS project, and started crying when you look at the mess of temporary layers that were created in the pursuit of that one perfect map? I can often run a set of several steps with either a single SQL query or SQL script. This saves me time, helps keep me organized and makes it easier to re-run tasks.Less limitations – But what if your data doesn’t fit into the 2GB limit of a shapefile, or the the process is too slow or never finishes in your GIS? Modern databases like Postgres are designed to deal with large datasets, and process millions of records much faster than a traditional GIS, or even scripts with Python or R.Freedom – speaking of buttons, what if you need to accomplish something across several different layers that isn’t supported by a GUI option? With SQL you get freedom to stitch together the analysis you need.This can also help automate repetitive tasks and skips laborious menus and forms.
POSTGRES APP SETTING PATH UPDATE
Need to redo the analysis and tweak a few things? Update the code and run it again.
