Personal tools
Home » Members » scw » testing folder » PostGIS presentation
Document Actions

PostGIS presentation

PostGIS: future developments


What is PostGIS

  • GPL PostgreSQL extension for Geographic Objects

  • Types

  • Operators

  • Functions

  • Indexes

  • Standard interfaces

  • Extension API


Current features

  •  OpenGIS “Simple Features for SQL” standard

  •  Spatial analisys and predicates (GEOS/JTS)

  •  Up to 4 dimensions coordinates (Shapefile-like)

  •  2d spatial indexing (rtree/GiST)

  •  SRS reprojections (PROJ4)

  •  About 200 spatial functions

  •  Lossless shapefile import / export

current features
OGC types

  1.  Points

  1.  Lines

  1.  Polygons

  1.  MultiPoints

  1.  MultiLines

  1.  MultiPolygons

  1.  Collections


current features
Spatial analisys

  • Union

  • Intersection

  • Difference

  • Symmetric difference

  • Convex Hull

  • Buffer


current features
Spatial predicates

  • Equals

  • Disjoint

  • Intersects

  • Touches

  • Crosses

  • Within

  • Contains

  • Overlaps


current features
Coordinate dimensions

  • 2D  ( X, Y )

  • 2.5D  ( X, Y, Z )

  • Measured  ( X, Y, M )

  • Measured 2.5D  ( X, Y, Z, M )

Lossless

Shapfile

import / export


Community

  • MapServer

  • GeoServer

  • UDIG

  • Qgis

  • Jump

  • OpenEV

  • GRASS

  • OGR

  • GeoTypes

  • GeoTools

  • MezoGIS

  • Thuban

  • phpPgGis

  • PrimaGIS

  • OrbisCAD

  • ...

Ongoing and future developments

  • Long transactions

  • Topology

  • Networks

  • Rasters

  • ISO SQL/MM

  • ...

ongoing development
Long transactions

  • Features locking

  • Implemented in 1.1.3

  • OGC standard (WFS)


long transactions
What for ?

  • OGC Web Features Service

  • Generic web-based architectures

  • Data integrity

  • Concurrent access

long transactions
How does it work

  • Lock any database row (not only features)

  • The lock is bound to an authentication token

  • Add auth tokens to your session

  • Do your things

  • Unlock the row(s)

ongoing development
Topology

  • Space partitioning

  • Drafted since 1.1.0

  • ISO standard (SQL/MM)


topology
Why ?

  • Topological integrity

  • Reduced storage size

  • Spatial analisys


why topology ?
Topological integrity

  • Every intersection is a node


why topology ?
Topological integrity

  • Every intersection is a node


why topology ?
Topological integrity

  • Edges are shared ...


why topology ?
Topological integrity

  • ... not separate entities.


why topology ?
Reduced storage size

  • Every edge is stored only once


why topology ?
Spatial analisys

  • Spatial relationships are part of the model

  • Predicates and overlays using standard SQL

  • Do they touch ? YES ! (no starvation)


topology
What do we have

  • Draft included in PostGIS 1.1.0

  • Conceptual schema

  • Phisical schema (ISO SQL/MM)

  • Functions (ISO SQL/MM)

topology
Conceptual model

  • Faces, Edges and Nodes


topology
Conceptual model


  • Topo-geometries

topology
Conceptual model

  • Layers



topology
Conceptual model

topology
Phisical model

  • PostgreSQL 7.3 or up required

  • All routines, types and other management objects are stored in the "topology" schema

  • Topologies are stored in schemas

  • TopoGeometry type

  • Layers metadata

topology
Metadata tables

  • topology.topology

  • topology.layer

topology
Topology schemas

  • <name>.edge

  • <name>.face

  • <name>.node

  • <name>.relation (TopoGeometry comp.)

topology
Functions

  • Create/destroy topologies

  • Edit topologies

  • Validate topologies

  • Define layers (simple and hierachical)

  • Define TopoGeometries (simple and hierarchical)

  • Cast TopoGeometries to Geometries

topology
Missing features

  • ISO SQL/MM topology editing functions are incomplete (can still use standard SQL)

  • TIGER/Line loader dumper (possible at this stage)

  • Geometry => TopoGeometry

future developments
Network

  • Shortest path

  • Cartoweb

  • ISO standard (SQL/MM)


network
Why ?

  • Communication networks modeling

  • Standardized interface

  • Common algorithms

network
What would it be ?

  • A schema and a set of functions

  • Like Topology model

  • Nodes, Links (vs. edges), No faces

network
Current status

  • Unimplemented :)

future developments
Rasters

  • DBMS vs. filesystem

  • Imagery or analisys ?

  • Standards ?


rasters
Why ?

  • Unified access

  • SQL interface

  • ....

  • ....

rasters
Why not ?

  • File formats already indexed

  • Easier disaster recovery

rasters
What do we have

  • The CHIP type

  • PgCHIP gdal driver

  • ...

  • ...

rasters
Possible design

  • GEORASTER-like

  • ...

  • ...

  • ...

by Shaun Walbridge last modified 03-10-2006 11:39

Built with Plone