Geographic Information Systems Extensions to PostgreSQL
https://www.postgis.net/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".
-
19
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout Application:Geo/postgis && cd $_
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _multibuild | 0000000163 163 Bytes | 3 months |
| patch-tests-results.patch | 0000040587 39.6 KB | 5 months |
| postgis-3.1.4.tar.gz | 0017269391 16.5 MB | about 1 month |
| postgis-rpmlintrc | 0000000201 201 Bytes | almost 5 years |
| postgis.changes | 0000090196 88.1 KB | about 1 month |
| postgis.spec | 0000007890 7.71 KB | about 1 month |
Comments 3
rmax wrote 23 days ago
Is there a reason besides "wasn't needed so far" why PostGIS is not (yet) on Factory? I would like to have it on PackageHub, but AFAICS for that it first needs to be on Factory.
bruno_friedmann wrote 23 days ago
Since years I'm looking for a co-maintainer which didn't occurs, except complains ;-) Alone I will not be able to maintain the pace of Factory, and constant breakage in postgresql-packaging (see the mess with missing target, llvm and so on). Those are my reasons to have not push it. I don't know how to move forward.
rmax wrote 12 days ago
I see, thanks for the info. I hope we can get PostgreSQL packaging more stable for extensions in the future, e.g. by having macros for stuff like LLVM, so that extensions don't have to be touched each time such a feature gets switched on or off on the PostgreSQL core side (and I hope there will also be less need for such switchings).