./databases/postgresql-postgis2, Spatial database capabilities for PostgreSQL

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 3.5.2nb2, Package name: postgresql13-postgis-3.5.2nb2, Maintainer: gdt

PostGIS adds support for geographic objects to the PostgreSQL object-relational
database. In effect, PostGIS "spatially enables" the PostgreSQL server,
allowing it to be used as a backend spatial database for geographic information
systems (GIS), much like ESRI's SDE or Oracle's Spatial extension. PostGIS
follows the OpenGIS "Simple Features Specification for SQL" and has been
certified as compliant with the "Types and Functions" profile.

PostGIS/PostgreSQL includes the following functionality:
* Simple Features as defined by the OpenGIS Consortium (OGC)
* Support for Well-Known Text and Well-Known Binary representations of GIS
objects
* Fast spatial indexing using GiST
* Geospatial analysis functions
* PostgreSQL JDBC extension objects corresponding to the geometries
* Support for OGC access functions as defined by the Simple Features
Specification

The package is postgis2 for historical reasons; this is currently
PostGIS 3 and intends to track the most recent stable release.


Required to run:
[textproc/libxml2] [textproc/libxslt] [graphics/ImageMagick] [geography/gdal-lib] [geography/geos] [devel/cunit] [geography/proj] [textproc/json-c] [devel/pcre2] [devel/protobuf-c] [databases/postgresql14-client] [databases/postgresql14-server]

Required to build:
[textproc/docbook-xsl] [pkgtools/x11-links]

Master sites:

Filesize: 14692.923 KB

Version history: (Expand)

CVS history: (Expand)


   2025-03-04 10:37:39 by Nia Alarie | Files touched by this commit (31) 
Log message:
*: Assume that the user has a C99-capable compiler.

A compiler that supports -std=c99 is required for
bootstrap, so it doesn't make sense to specify a c99
compiler everywhere in package makefiles.

At any rate, I would bet my entire life's savings that
this is a small fraction of the total number of packages
requiring c99.

Note that compilers that default to c89 but support c99
are still supported...
   2025-02-18 11:33:23 by Thomas Klausner | Files touched by this commit (38) 
Log message:
*: recursive bump for openh264
   2025-02-09 15:44:09 by Thomas Klausner | Files touched by this commit (62) 
Log message:
*: recursive bump for abseil 20250127.0
   2025-01-19 16:02:05 by Greg Troxel | Files touched by this commit (3) 
Log message:
databases/postgresql-postgis2: Update to 3.5.2

Upstream NEWS: micro release / bugfixes
   2024-12-27 00:57:23 by Adam Ciarcinski | Files touched by this commit (46) | Package updated
Log message:
revbump after devel/protobuf update
   2024-12-26 15:33:31 by Thomas Klausner | Files touched by this commit (1) | Package updated
Log message:
postgresql-postgis2: reset PKGREVISION after update
   2024-12-26 13:55:46 by Greg Troxel | Files touched by this commit (3) 
Log message:
databases/postgresql-postgis2: Update to 3.5.1

Upstream NEWS, less bugfixes and minor improvements.

PostGIS 3.5.1
2024/12/22

* Bug fixes *

- #5823, Build support for Pg18 (Paul Ramsey)

* Enhancements *

  - #5782, Improve robustness of min distance calculation (Sandro Santilli)
  - [topology] Speedup topology building when closing large rings with many
    holes (Björn Harrtell)
  - #5810, [tiger_geocoder] Update tiger geocoder to handle TIGER 2024 data \ 
(Regina Obe)

* Breaking Changes *

  - #5799, make ST_TileEnvelope clip envelopes to tile plane
           extent (Paul Ramsey)
   2024-11-30 17:17:48 by Greg Troxel | Files touched by this commit (1) 
Log message:
databases/postgresql-postgis2: Alow pg17

The README does not say, but the release announcement for 3.5.0 says
"best served with PostgreSQL 17 RC1".  While it's ridiculous for a
release to recommend using a non-release, it's a clue that 17 should
be ok.