From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Kased, Razy (Chemistry and Geosciences)" <rkased(at)monroecc(dot)edu> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: What is the purpose of PostGIS on PostgreSQL? |
Date: | 2017-01-23 23:46:48 |
Message-ID: | CAHyXU0xUX=Aw1okJkydn222CSUi6SxsK0cgJGJYTZej3OT6SaQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 23, 2017 at 11:08 AM, Kased, Razy (Chemistry and
Geosciences) <rkased(at)monroecc(dot)edu> wrote:
> I recently came across this question: "What is the purpose of PostGIS on
> PostgreSQL?" and wanted to know what this mailing list had to respond with.
PostGIS is a SQL wrapper to the GEOS library which lets you do a large
number of really complex things that relate to coordinate systems on a
precise level.
Postgres geo types are useful for a very small set of uses cases with
a small but important overlap with PostGIS: indexed bounded box
lookups which is a fairly common requirement.
All else being equal, less dependencies are good so if that's all you
need work off the built in types. If you need PostGIS though you
really need it. For example, I heavily use the ST_UNION aggregate
function to build large market boundaries from smaller zip code
boundaries and it works beautifully. There is no analog to that in
the built in stuff.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-01-24 00:02:33 | Re: recovery dump on database with different timezone |
Previous Message | Edmundo Robles | 2017-01-23 23:45:33 | recovery dump on database with different timezone |