March 2011 Archives by date

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...

Starting: Tue Mar 1 02:02:19 PST 2011
Ending: Thu Mar 31 21:34:07 PDT 2011
Messages: 360

• [postgis-devel] ST_Covers AND &&   Sandro Santilli
• [postgis-devel] ST_Covers AND &&   Sandro Santilli
• [postgis-devel] (no subject)   reena at indiamail.com
• [postgis-devel] [PostGIS] #850: Binary IO support for geography type   PostGIS
• [postgis-devel] (no subject)   reena at indiamail.com
• [postgis-devel] [PostGIS] #844: Allow specifying BoundaryNodeRule in ST_Relate*   PostGIS
• [postgis-devel] [PostGIS] #844: Allow specifying BoundaryNodeRule in ST_Relate*   PostGIS
• [postgis-devel] [PostGIS] #770: [topology] AddEdge refuses to add closed edge touching at endpoint   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #852: The use of tolerance in function point_in_ring is not robust.   PostGIS
• [postgis-devel] [PostGIS] #852: The use of tolerance in function point_in_ring is not robust.   PostGIS
• [postgis-devel] [PostGIS] #853: topology.Envelope(TopoGeometry)   PostGIS
• [postgis-devel] [PostGIS] #854: X3D output functions   PostGIS
• [postgis-devel] Copying topologies   Sandro Santilli
• [postgis-devel] [PostGIS] #485: Quick geometry viewer that is integrable in PgAdmin III   PostGIS
• [postgis-devel] [PostGIS] #575: ST_Union fails on a group of linestrings.   PostGIS
• [postgis-devel] [PostGIS] #575: ST_Union fails on a group of linestrings.   PostGIS
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Jeff Adams
• [postgis-devel] PostGIS configuration with raster support   Stephen Chenoweth
• [postgis-devel] PostGIS configuration with raster support   Jorge Arévalo
• [postgis-devel] PostGIS configuration with raster support   Mateusz Loskot
• [postgis-devel] [PostGIS] #844: Allow specifying BoundaryNodeRule in ST_Relate*   PostGIS
• [postgis-devel] [PostGIS] #844: Allow specifying BoundaryNodeRule in ST_Relate*   PostGIS
• [postgis-devel] [PostGIS] #844: Allow specifying BoundaryNodeRule in ST_Relate*   PostGIS
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Jeff Adams
• [postgis-devel] [PostGIS] #855: topology.TopologySummary(<name>)   PostGIS
• [postgis-devel] [PostGIS] #357: Update function names in loader to ST_   PostGIS
• [postgis-devel] [PostGIS] #844: Allow specifying BoundaryNodeRule in ST_Relate*   PostGIS
• [postgis-devel] [PostGIS] #855: topology.TopologySummary(<name>)   PostGIS
• [postgis-devel] [PostGIS] #855: topology.TopologySummary(<name>)   PostGIS
• [postgis-devel] [PostGIS] #856: topology.CopyTopology(<name>, <newname>)   PostGIS
• [postgis-devel] [PostGIS] #856: topology.CopyTopology(<name>, <newname>)   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Mark Cave-Ayland
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Pierre Racine
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Sandro Santilli
• [postgis-devel] [PostGIS] #857: shp2pgsql with single argument   PostGIS
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Sandro Santilli
• [postgis-devel] [PostGIS] #856: topology.CopyTopology(<name>, <newname>)   PostGIS
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Paul Ramsey
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #854: X3D output functions   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #849: Topology: function GetFaceByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #849: Topology: function GetFaceByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Jeff Adams
• [postgis-devel] Postgis issue suggestions for OSGeo sprint?   Jeff Adams
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] Montreal Task Items   Paragon Corporation
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #590: [raster] Implement the two rasters version of ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #858: [raster] Two ST_AddBand PL/pgSQL variants are missing   PostGIS
• [postgis-devel] [PostGIS] #849: Topology: function GetFaceByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #591: [raster] Add a ST_IsEmpty function   PostGIS
• [postgis-devel] (no subject)   reena at indiamail.com
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #591: [raster] Add a ST_IsEmpty function   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #854: X3D output functions   PostGIS
• [postgis-devel] [PostGIS] #854: X3D output functions   PostGIS
• [postgis-devel] [PostGIS] #67: new tablespace parameter for shp2pgsql   PostGIS
• [postgis-devel] [PostGIS] #859: shp2pgsql new option to do something with bad geometries.   PostGIS
• [postgis-devel] [PostGIS] #651: [raster] ST_makeemptyraster inconsistent with documentation   PostGIS
• [postgis-devel] [PostGIS] #650: [raster] st_dumpaspolygon create int values   PostGIS
• [postgis-devel] [PostGIS] #650: [raster] st_dumpaspolygon create int values   PostGIS
• [postgis-devel] [PostGIS] #792: [raster] Addband regresssion test fail on some systems.   PostGIS
• [postgis-devel] [PostGIS] #651: [raster] ST_makeemptyraster inconsistent with documentation   PostGIS
• [postgis-devel] [PostGIS] #110: shp2pgsql new option to not batch commit   PostGIS
• [postgis-devel] [PostGIS] #859: shp2pgsql new option to do something with bad geometries.   PostGIS
• [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
• [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
• [postgis-devel] DropGeometryTable should not raise exception   aperi2007
• [postgis-devel] [PostGIS] #123: SQLite output format support for shp2pgsql   PostGIS
• [postgis-devel] DropGeometryTable should not raise exception   Sandro Santilli
• [postgis-devel] DropGeometryTable should not raise exception   Mark Cave-Ayland
• [postgis-devel] DropGeometryTable should not raise exception   Sandro Santilli
• [postgis-devel] [PostGIS] #769: [raster] Regression test fails when debug option is active   PostGIS
• [postgis-devel] [PostGIS] #861: DropGeometryTable should not raise exception if no geometry column   PostGIS
• [postgis-devel] DropGeometryTable should not raise exception   aperi2007
• [postgis-devel] [PostGIS] #862: Topology: the topology.DropTopology() drop any type of schemas   PostGIS
• [postgis-devel] 3D Index / 2D Index concerns   Paragon Corporation
• [postgis-devel] 3D Index / 2D Index concerns   Nicklas Avén
• [postgis-devel] 3D Index / 2D Index concerns   Paul Ramsey
• [postgis-devel] [PostGIS] #863: shp2pgsql -S doesn't work with MULTIPOINTs   PostGIS
• [postgis-devel] [PostGIS] #864: shp2pgsql fails to import MULTIPOINTs with only one vertice.   PostGIS
• [postgis-devel] [PostGIS] #229: shp2pgsql ability to transform from one spatial ref to another   PostGIS
• [postgis-devel] [PostGIS] #863: shp2pgsql -S doesn't work with MULTIPOINTs   PostGIS
• [postgis-devel] [PostGIS] #779: shp2pgsql -S option seems to fail, and is missing in doc   PostGIS
• [postgis-devel] 3D Index / 2D Index concerns   Paragon Corporation
• [postgis-devel] [PostGIS] #779: shp2pgsql -S option seems to fail, and is missing in doc   PostGIS
• [postgis-devel] 3D Index / 2D Index concerns   Paragon Corporation
• [postgis-devel] 3D Index / 2D Index concerns   Paul Ramsey
• [postgis-devel] 3D Index / 2D Index concerns   Nicklas Avén
• [postgis-devel] [PostGIS] #779: shp2pgsql -S option seems to fail, and is missing in doc   PostGIS
• [postgis-devel] 3D Index / 2D Index concerns   Paul Ramsey
• [postgis-devel] 3D Index / 2D Index concerns   Olivier Courtin
• [postgis-devel] [PostGIS] #865: shp2pgsql crashes when both -g and -G are used.   PostGIS
• [postgis-devel] 3D Index / 2D Index concerns   Nicklas Avén
• [postgis-devel] [PostGIS] #779: shp2pgsql -S option seems to fail, and is missing in doc   PostGIS
• [postgis-devel] [PostGIS] #865: shp2pgsql crashes when both -g and -G are used.   PostGIS
• [postgis-devel] [PostGIS] #650: [raster] st_dumpaspolygon create int values   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #643: [raster] ST_DeleteBand in raster/scripts/plpgsql function is broken   PostGIS
• [postgis-devel] [PostGIS] #644: [raster] ST_MapAlgebra raster/scripts/plpgsql some broken   PostGIS
• [postgis-devel] [PostGIS] #645: [raster] more raster/scripts/plpgsql st_setarray.sql, st_sevalues, st_union   PostGIS
• [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #792: [raster] Addband regresssion test fail on some systems.   PostGIS
• [postgis-devel] [PostGIS] #825: [raster] raster overview -- trying to insert into wrong table (if schema qualify), and not creating rast column   PostGIS
• [postgis-devel] [PostGIS] #858: [raster] Two ST_AddBand PL/pgSQL variants are missing   PostGIS
• [postgis-devel] [PostGIS] #590: [raster] Implement the two rasters version of ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #792: [raster] Addband regresssion test fail on some systems.   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #792: [raster] Addband regresssion test fail on some systems.   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #866: [raster] Change the ST_MapAlgebra nodatavalueexpr text parameter for nadatavaluerepl   PostGIS
• [postgis-devel] [PostGIS] #229: shp2pgsql ability to transform from one spatial ref to another   PostGIS
• [postgis-devel] [PostGIS] #659: shp2pgsql crashing when trying to load into geography order sensitive   PostGIS
• [postgis-devel] [PostGIS] #779: shp2pgsql -S option seems to fail, and is missing in doc   PostGIS
• [postgis-devel] [PostGIS] #864: shp2pgsql fails to import MULTIPOINTs with only one vertice.   PostGIS
• [postgis-devel] [PostGIS] #865: shp2pgsql crashes when both -g and -G are used.   Jeff Adams
• [postgis-devel] shp2pgsql documentation.   Jeff Adams
• [postgis-devel] [PostGIS] #857: shp2pgsql with single argument   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #857: shp2pgsql with single argument   PostGIS
• [postgis-devel] [PostGIS] #866: [raster] Change the ST_MapAlgebra nodatavalueexpr text parameter for nadatavaluerepl   PostGIS
• [postgis-devel] [PostGIS] #867: [raster] Implement a version of rt_raster_deserialize for the raster header only   PostGIS
• [postgis-devel] [PostGIS] #867: [raster] Implement a version of rt_raster_deserialize for the raster header only   PostGIS
• [postgis-devel] [PostGIS] #868: Error in check of circularstring   PostGIS
• [postgis-devel] [PostGIS] #868: Error in check of circularstring   PostGIS
• [postgis-devel] [PostGIS] #857: shp2pgsql with single argument   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #358: Add regression tests for shp2pgsql loading in -G mode   PostGIS
• [postgis-devel] [PostGIS] #358: Add regression tests for shp2pgsql loading in -G mode   PostGIS
• [postgis-devel] [PostGIS] #358: Add regression tests for shp2pgsql loading in -G mode   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #869: gml export error failure under MingW   PostGIS
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #663: shp2pgsql uses the wrong return type for pgis_getopt   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #868: Error in check of circularstring   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #808: shp2pgsql and encoding, something must be wrong   PostGIS
• [postgis-devel] [PostGIS] #864: shp2pgsql fails to import MULTIPOINTs with only one vertice.   PostGIS
• [postgis-devel] [PostGIS] #779: shp2pgsql -S option seems to fail, and is missing in doc   PostGIS
• [postgis-devel] [PostGIS] #229: shp2pgsql ability to transform from one spatial ref to another   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #871: [raster] ST_AddBand documentation is inconsistent with function definitions and spec   PostGIS
• [postgis-devel] [PostGIS] #872: ST_GeomFromX3D   PostGIS
• [postgis-devel] [PostGIS] #873: ST_AsCollada / ST_GeomFromCollada   PostGIS
• [postgis-devel] [PostGIS] #617: uninstall script get rid of drop cascade   PostGIS
• [postgis-devel] what version of geos ?   aperi2007
• [postgis-devel] what version of geos ?   Paragon Corporation
• [postgis-devel] what version of geos ?   aperi2007
• [postgis-devel] [PostGIS] #701: Support for 9.1 KNN GIST enhancements   PostGIS
• [postgis-devel] [PostGIS] #874: AddFace gets left_face/right_face of edge crossing startPoint wrong   PostGIS
• [postgis-devel] [PostGIS] #874: AddFace gets left_face/right_face of edge crossing startPoint wrong   PostGIS
• [postgis-devel] [PostGIS] #874: AddFace gets left_face/right_face of edge crossing startPoint wrong   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #876: Better document ST_Azimuth   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #873: ST_AsCollada / ST_GeomFromCollada   PostGIS
• [postgis-devel] [PostGIS] #858: [raster] Two ST_AddBand PL/pgSQL variants are missing   PostGIS
• [postgis-devel] [PostGIS] #792: [raster] Addband regresssion test fail on some systems.   PostGIS
• [postgis-devel] [PostGIS] #873: ST_AsCollada / ST_GeomFromCollada   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] lwgeom_calculate_bbox   Sandro Santilli
• [postgis-devel] lwgeom_calculate_bbox   Sandro Santilli
• [postgis-devel] [PostGIS] #853: topology.Envelope(TopoGeometry)   PostGIS
• [postgis-devel] lwgeom_calculate_bbox   Sandro Santilli
• [postgis-devel] lwgeom_calculate_bbox   Paul Ramsey
• [postgis-devel] Update postgis windows experimental version   aperi2007
• [postgis-devel] Windows Experimental Builds   Paragon Corporation
• [postgis-devel] Windows Experimental Builds   Sandro Santilli
• [postgis-devel] lwgeom_calculate_bbox   Sandro Santilli
• [postgis-devel] [PostGIS] #855: topology.TopologySummary [misses documentation] (was: topology.TopologySummary(<name>))   PostGIS
• [postgis-devel] [PostGIS] #855: topology.TopologySummary [misses documentation]   PostGIS
• [postgis-devel] [PostGIS] #819: topology: error on regress of createtopogeom   PostGIS
• [postgis-devel] [PostGIS] #794: Rename function ST_ModEdgesSplit to ST_ModEdgeSplit   PostGIS
• [postgis-devel] [PostGIS] #798: ST_RemoveIsoNode: iso name is ST_RemIsoNode   PostGIS
• [postgis-devel] [PostGIS] #797: ST_RemoveIsoNode does not throw an exception when passed a non-existent node   PostGIS
• [postgis-devel] [PostGIS] #752: Add to topology readme the grants to do   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #714: topology is using outdated sql syntax   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #877: st_estimated_extent returns error on empty table   PostGIS
• [postgis-devel] [PostGIS] #878: ST_LineMerge with collection   PostGIS
• [postgis-devel] [PostGIS] #878: ST_LineMerge with collection   PostGIS
• [postgis-devel] [PostGIS] #877: st_estimated_extent returns error on empty table   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #871: [raster] ST_AddBand documentation is inconsistent with function definitions and spec   PostGIS
• [postgis-devel] [PostGIS] #879: ST_ModEdgeSplit using deprecated function   PostGIS
• [postgis-devel] [PostGIS] #879: ST_ModEdgeSplit using deprecated function   PostGIS
• [postgis-devel] [PostGIS] #877: st_estimated_extent returns error on empty table   PostGIS
• [postgis-devel] [PostGIS] #877: st_estimated_extent returns error on empty table   PostGIS
• [postgis-devel] [PostGIS] #877: st_estimated_extent returns error on empty table   PostGIS
• [postgis-devel] [PostGIS] #880: topology.AddFace speed up using prepared geometries   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #881: ST_ExtrudePolygons   PostGIS
• [postgis-devel] [PostGIS] #882: ST_UnionAsTIN, ST_UnionAsPolyghedralSurface   PostGIS
• [postgis-devel] Contributing code to PostGIS Raster   Bborie Park
• [postgis-devel] Contributing code to PostGIS Raster   Pierre Racine
• [postgis-devel] Contributing code to PostGIS Raster   Bborie Park
• [postgis-devel] Contributing code to PostGIS Raster   Jorge Arévalo
• [postgis-devel] Possible bug with ST_Within in an island of a multipolygon?   Larry Reeder
• [postgis-devel] Contributing code to PostGIS Raster   Pierre Racine
• [postgis-devel] Contributing code to PostGIS Raster   Jorge Arévalo
• [postgis-devel] Contributing code to PostGIS Raster   Bborie Park
• [postgis-devel] Contributing code to PostGIS Raster   Pierre Racine
• [postgis-devel] Contributing code to PostGIS Raster   Jorge Arévalo
• [postgis-devel] Contributing code to PostGIS Raster   Pierre Racine
• [postgis-devel] Contributing code to PostGIS Raster   Bborie Park
• [postgis-devel] Contributing code to PostGIS Raster   Jorge Arévalo
• [postgis-devel] Contributing code to PostGIS Raster   Pierre Racine
• [postgis-devel] Contributing code to PostGIS Raster   Sandro Santilli
• [postgis-devel] [PostGIS] #871: [raster] ST_AddBand documentation is inconsistent with function definitions and spec   PostGIS
• [postgis-devel] Contributing code to PostGIS Raster   Jorge Arévalo
• [postgis-devel] Contributing code to PostGIS Raster   Pierre Racine
• [postgis-devel] Contributing code to PostGIS Raster   Bborie Park
• [postgis-devel] [PostGIS] #883: [raster] Make every rtpostgis.sql function immutable strict when possible   PostGIS
• [postgis-devel] [PostGIS] #883: [raster] Make every rtpostgis.sql function immutable strict when possible   PostGIS
• [postgis-devel] [PostGIS] #871: [raster] ST_AddBand documentation is inconsistent with function definitions and spec   PostGIS
• [postgis-devel] [PostGIS] #883: [raster] Make every rtpostgis.sql function immutable strict when possible   PostGIS
• [postgis-devel] [PostGIS] #883: [raster] Make every rtpostgis.sql function immutable strict when possible   PostGIS
• [postgis-devel] Contributing code to PostGIS Raster   David Zwarg
• [postgis-devel] Contributing code to PostGIS Raster   Jorge Arévalo
• [postgis-devel] Contributing code to PostGIS Raster   Bborie Park
• [postgis-devel] Contributing code to PostGIS Raster   Jorge Arévalo
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] What to return when refering to an invalid band number   Pierre Racine
• [postgis-devel] What to return when refering to an invalid band number   Mateusz Loskot
• [postgis-devel] What to return when refering to an invalid band number   Pierre Racine
• [postgis-devel] What to return when refering to an invalid band number   Mateusz Loskot
• [postgis-devel] What to return when refering to an invalid band number   Jorge Arévalo
• [postgis-devel] What to return when refering to an invalid band number   Sandro Santilli
• [postgis-devel] What to return when refering to an invalid band number   Pierre Racine
• [postgis-devel] What to return when refering to an invalid band number   Mateusz Loskot
• [postgis-devel] What to return when refering to an invalid band number   Paragon Corporation
• [postgis-devel] What to return when refering to an invalid bandnumber   Paragon Corporation
• [postgis-devel] [postgis-users] Problems with ST_Within in an island of a multipolygon   Sandro Santilli
• [postgis-devel] [PostGIS] #884: Unstable results from ST_Within   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results from ST_Within   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results from ST_Within   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results from ST_Within   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results from ST_Within   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with Prepared Geometry (ST_Within, ST_Intersects) (was: Unstable results from ST_Within)   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects (was: Unstable results with Prepared Geometry (ST_Within, ST_Intersects))   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] [PostGIS] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] [PostGIS] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] [PostGIS] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] [PostGIS] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] [PostGIS] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] [PostGIS] #886: Fix normalizing of multi street number range addresses   PostGIS
• [postgis-devel] [PostGIS] #887: Tiger geocoder fails when address contains name of street sometimes   PostGIS
• [postgis-devel] [PostGIS] #887: Tiger geocoder fails when address contains name of state sometimes (was: Tiger geocoder fails when address contains name of street sometimes)   PostGIS
• [postgis-devel] [PostGIS] #888: add cunit tests for pgsql2shp   PostGIS
• [postgis-devel] patch: cunit tests for pgsql2shp   Loic Dachary
• [postgis-devel] [PostGIS] #889: shp2pgsql fail load localized character   PostGIS
• [postgis-devel] [PostGIS] #889: shp2pgsql fail load localized character   PostGIS
• [postgis-devel] [PostGIS] #889: shp2pgsql fail load localized character   PostGIS
• [postgis-devel] [PostGIS] #889: shp2pgsql fail load localized character   PostGIS
• [postgis-devel] [PostGIS] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] [PostGIS] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] patch: pgsql2shp fields conversion from predefined list   Loic Dachary
• [postgis-devel] [PostGIS] #817: Renaming old 3D functions to the convention ST_3D..........   PostGIS
• [postgis-devel] [PostGIS] #817: Renaming old 3D functions to the convention ST_3D..........   PostGIS
• [postgis-devel] [PostGIS] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] [PostGIS] #702: ticket #183 test fails on 32bit system (was: tickets test failure)   PostGIS
• [postgis-devel] [PostGIS] #890: ticket #304 tests fail on 64bit system   PostGIS
• [postgis-devel] [PostGIS] #890: ticket #304 tests fail on 64bit system (ST_DWithin false negatives?) (was: ticket #304 tests fail on 64bit system)   PostGIS
• [postgis-devel] [PostGIS] #890: ticket #304 tests fail on 64bit system (ST_DWithin false negatives?)   PostGIS
• [postgis-devel] [PostGIS] #869: ticket #304 regress is failing (was: gml export error failure under MingW)   PostGIS
• [postgis-devel] [PostGIS] #869: ticket #304 regress is failing   PostGIS
• [postgis-devel] [PostGIS] #869: ticket #304 regress is failing   PostGIS
• [postgis-devel] [PostGIS] #817: Renaming old 3D functions to the convention ST_3D..........   PostGIS
• [postgis-devel] [PostGIS] #817: Renaming old 3D functions to the convention ST_3D..........   PostGIS
• [postgis-devel] [PostGIS] #884: Unstable results with ST_Within, ST_Intersects   PostGIS
• [postgis-devel] Fwd: Build failed in Hudson: PostGIS-trunk-regression #568   Paul Ramsey
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] Fwd: Build failed in Hudson:PostGIS-trunk-regression #568   Paragon Corporation
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #817: Renaming old 3D functions to the convention ST_3D..........   PostGIS
• [postgis-devel] (no subject)   reena at indiamail.com
• [postgis-devel] (no subject)   reena at indiamail.com
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #875: Regress errors: ReprojectPts, ReprojectPtsGeog, tickets   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #869: ticket #304 regress is failing   PostGIS
• [postgis-devel] [PostGIS] #829: st_addedgenewfaces looks incomplete   PostGIS
• [postgis-devel] [PostGIS] #891: Allow 2.5D topologies   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #174: Point Clustering Utility Trigger   PostGIS
• [postgis-devel] [PostGIS] #870: [raster] Optimize ST_DumpAsWKTPolygons   PostGIS
• [postgis-devel] [PostGIS] #892: Smarter linear location (for ST_Line_Interpolate_Point, ST_Line_Substring, ST_Line_Locate_Point)   PostGIS
• [postgis-devel] [PostGIS] #893: Error loading (shp2pgsql or bad geometry)   PostGIS
• [postgis-devel] [PostGIS] #893: Error loading (shp2pgsql or bad geometry)   PostGIS
• [postgis-devel] [PostGIS] #893: Error loading (shp2pgsql or bad geometry)   PostGIS
• [postgis-devel] [PostGIS] #893: Error loading (shp2pgsql or bad geometry)   PostGIS
• [postgis-devel] [PostGIS] #894: _ST_Expand for geography is broken   PostGIS
• [postgis-devel] [PostGIS] #894: _ST_Expand for geography is broken   PostGIS
• [postgis-devel] [PostGIS] #895: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions (was: FV.01 functions)   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS

Last message date: Thu Mar 31 21:34:07 PDT 2011
Archived on: Fri Nov 10 09:26:06 PST 2017

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...