| | 1 | == Features Of PostGIS == |
| | 2 | |
| | 3 | PostGIS is not your standard spatial extension to a relational database... or is it? |
| | 4 | |
| | 5 | == PostGIS supports many standards: == |
| | 6 | |
| | 7 | * The '''Open GIS Consortium (OGC)''' standards for "Simple Features" (2D Geometries) |
| | 8 | * [http://www.opengeospatial.org/standards/sfa Simple Features at OGC] |
| | 9 | * [http://portal.opengeospatial.org/files/index.php?artifact_id=6211&version=2&format=htm What does OGC mean by Openness and Open Standards?] |
| | 10 | * [http://www.jump-project.org/project.php?PID=JTS&SID=OVER#spatialdatatypes Graphic of OGC Spatial Data Types implemented in JTS/GEOS code at JUMP site] |
| | 11 | * [http://en.wikipedia.org/wiki/Simple_Features Simple Features on Wikipedia] |
| | 12 | |
| | 13 | * The '''Open GIS Consortium (OGC)''' markup language for "Simple Features" known as Well Known Text (WKT) and Well Known Binary (WKB) representations of data. |
| | 14 | * [http://postgis.refractions.net/docs/ch04.html#id3008383 WKT and WKB in PostGIS manual] |
| | 15 | * [http://en.wikipedia.org/wiki/Well-known_text WKT on Wikipedia] |
| | 16 | * [http://www.opengeospatial.org/standards/sfa Download the PDF's on Simple Features at OGC] |
| | 17 | |
| | 18 | * '''OGC SQL functions:''' standards for managing spatial tables using SQL language |
| | 19 | * [http://www.opengeospatial.org/standards/sfs SQL for Simple Features at OGC] |
| | 20 | * [http://postgis.refractions.net/docs/ch04.html#id3008736 Discussion of Compliance in PostGIS manual] |
| | 21 | * [http://postgis.refractions.net/docs/ch06.html#id3011852 Direct Link to Functions in PostGIS manual] |
| | 22 | |
| | 23 | == PostGIS extends support for geometry types: == |
| | 24 | * '''EWKB, EWKT and Canonical Forms''' |
| | 25 | * PostGIS adds support for embedding the SRID (projection information) and for 3 and 4D geometries with Z and M values, respectively. |
| | 26 | * [http://postgis.refractions.net/docs/ch04.html#id3008491 EWKT and EWKT in PostGIS manual] |
| | 27 | * [http://en.wikipedia.org/wiki/Extended_Well-known_text EWKT on Wikipedia] |
| | 28 | * '''Other Types''' |
| | 29 | * [wiki:UsersWikiRasterNotes Progress on Raster Support] |
| | 30 | * [http://www.foss4g2007.org/presentations/view.php?abstract_id=224 Proposed X3D types: TIN and COLLADA for Web Output] |
| | 31 | |
| | 32 | == PostGIS enables powerful spatial analysis and editing of geometries == |
| | 33 | * [http://postgis.refractions.net/docs/ch06.html#id3011852 Spatial functions and operators in PostGIS manual] |
| | 34 | * [http://www.jump-project.org/project.php?PID=JTS&SID=OVER#spatialanalysismethods Graphic of Spatial Analysis methods implemented in JTS/GEOS code at JUMP site] |
| | 35 | * [http://www.bostongis.com/postgis_quickguide.bqg Boston GIS PostGIS Functions Cheatsheet] |
| | 36 | * [wiki:UsersWikiplpgsqlfunctions Additional User-contributed Functions] |
| | 37 | |
| | 38 | == PostGIS can be extended by scripting with an array of languages == |
| | 39 | * Client-side extensions exist to access spatial data in PostgreSQL for the following programming languages: |
| | 40 | * Python | [wiki:UsersWikiPostgisAndPython Scripting Examples] |
| | 41 | * [http://www.initd.org/tracker/psycopg Psycopg:] a PostgreSQL database adapter for Python |
| | 42 | * [http://www.initd.org/tracker/psycopg/wiki/GeoTypes GeoTypes:] an extension to Psycopg |
| | 43 | * Java | [wiki:UsersWikiPostGISAndJava Scripting Examples] |
| | 44 | * Included in PostGIS, supports own class model as well as JTS, and read-only support for Java2D |
| | 45 | * PHP | [wiki:UsersWikiPostGISAndPhp Scripting Examples] |
| | 46 | * [http://code.google.com/support/bin/answer.py?answer=69906&topic=11364 PHP example of writing to KML (in MySQL)] |
| | 47 | * Ruby |
| | 48 | * [http://georuby.rubyforge.org/ GeoRuby's Spatial Adapter for Active Record] |
| | 49 | * ''(I heard rumors of a perl interface, please edit)'' |
