April 2011 Archives by subject

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

Starting: Fri Apr 1 01:19:39 PDT 2011
Ending: Sat Apr 30 15:27:01 PDT 2011
Messages: 349

• [postgis-devel] (no subject)   Randy Horner
• [postgis-devel] (no subject)   Jeff Adams
• [postgis-devel] (no subject)   RANDYHORNER
• [postgis-devel] (no subject)   Paul Ramsey
• [postgis-devel] (no subject)   Paragon Corporation
• [postgis-devel] 8BUI JPEG and PNG raster export   Bborie Park
• [postgis-devel] 8BUI JPEG and PNG raster export   Pierre Racine
• [postgis-devel] 8BUI JPEG and PNG raster export   Bborie Park
• [postgis-devel] 8BUI JPEG and PNG raster export   Pierre Racine
• [postgis-devel] 8BUI JPEG and PNG raster export   Bborie Park
• [postgis-devel] 8BUI JPEG and PNG raster export   Pierre Racine
• [postgis-devel] 8BUI JPEG and PNG raster export   Bborie Park
• [postgis-devel] [postgis-users] PSC Vote to officially drop support for PostgreSQL 8.3 in PostGIS 2.0   Magnus Hagander
• [postgis-devel] [PostGIS] #103: Box3D always gets cast to 2D geometry   PostGIS
• [postgis-devel] [PostGIS] #103: Box3D always gets cast to 2D geometry   PostGIS
• [postgis-devel] [PostGIS] #103: Box3D always gets cast to 2D geometry   PostGIS
• [postgis-devel] [PostGIS] #103: Box3D always gets cast to 2D geometry   PostGIS
• [postgis-devel] [PostGIS] #103: Box3D always gets cast to 2D geometry   PostGIS
• [postgis-devel] [PostGIS] #287: ST_AsText should return SQL/MM WKT   PostGIS
• [postgis-devel] [PostGIS] #312: ST_ConcaveHull   PostGIS
• [postgis-devel] [PostGIS] #339: [raster] Implement ST_Band function for raster   PostGIS
• [postgis-devel] [PostGIS] #339: [raster] Implement ST_Band function for raster   PostGIS
• [postgis-devel] [PostGIS] #339: [raster] Implement ST_Band function for raster   PostGIS
• [postgis-devel] [PostGIS] #339: [raster] ST_Band   PostGIS
• [postgis-devel] [PostGIS] #339: [raster] ST_Band   PostGIS
• [postgis-devel] [PostGIS] #339: [raster] ST_Band (was: [raster] Implement ST_Band function for raster)   PostGIS
• [postgis-devel] [PostGIS] #340: [raster] Implement ST_AsJPEG function for raster   PostGIS
• [postgis-devel] [PostGIS] #340: [raster] Implement ST_AsJPEG function for raster   PostGIS
• [postgis-devel] [PostGIS] #340: [raster] Implement ST_AsJPEG function for raster   PostGIS
• [postgis-devel] [PostGIS] #340: [raster] Implement ST_AsJPEG function for raster   PostGIS
• [postgis-devel] [PostGIS] #340: [raster] Implement ST_AsJPEG function for raster   PostGIS
• [postgis-devel] [PostGIS] #340: [raster] ST_AsJPEG (was: [raster] Implement ST_AsJPEG function for raster)   PostGIS
• [postgis-devel] [PostGIS] #341: [raster] Implement ST_AsTIFF function for raster   PostGIS
• [postgis-devel] [PostGIS] #341: [raster] Implement ST_AsTIFF function for raster   PostGIS
• [postgis-devel] [PostGIS] #341: [raster] Implement ST_AsTIFF function for raster   PostGIS
• [postgis-devel] [PostGIS] #341: [raster] Implement ST_AsTIFF function for raster   PostGIS
• [postgis-devel] [PostGIS] #341: [raster] Implement ST_AsTIFF function for raster   PostGIS
• [postgis-devel] [PostGIS] #341: [raster] ST_AsTIFF (was: [raster] Implement ST_AsTIFF function for raster)   PostGIS
• [postgis-devel] [PostGIS] #342: [raster] Implement ST_AsPNG function for raster   PostGIS
• [postgis-devel] [PostGIS] #342: [raster] Implement ST_AsPNG function for raster   PostGIS
• [postgis-devel] [PostGIS] #342: [raster] Implement ST_AsPNG function for raster   PostGIS
• [postgis-devel] [PostGIS] #342: [raster] ST_AsPNG (was: [raster] Implement ST_AsPNG function for raster)   PostGIS
• [postgis-devel] [PostGIS] #353: Reduce the dependency footprint of shp2pgsql-gui   PostGIS
• [postgis-devel] [PostGIS] #372: shp2pgsql-gui Move About button to menu   PostGIS
• [postgis-devel] [PostGIS] #376: Add ST_GeomFromGeoJSON   PostGIS
• [postgis-devel] [PostGIS] #393: shp2pgsql returns "fseek(-xxx) failed on DBF file." for large (>2GB) DBF files   PostGIS
• [postgis-devel] [PostGIS] #396: GCC warning - shp2pgsql   PostGIS
• [postgis-devel] [PostGIS] #398: pgsql2shp should prompt for password if not supplied in command args   PostGIS
• [postgis-devel] [PostGIS] #413: ST_OffsetCurve   PostGIS
• [postgis-devel] [PostGIS] #459: GML Envelope   PostGIS
• [postgis-devel] [PostGIS] #482: [raster] Implement ST_SetRotation   PostGIS
• [postgis-devel] [PostGIS] #484: [raster] rtpostgis.sql.in.c using old style 1.3 syntax and other arcane stuff   PostGIS
• [postgis-devel] [PostGIS] #486: pgsql2shp-gui similar to shp2pgsql-gui   PostGIS
• [postgis-devel] [PostGIS] #502: [raster] Optimize ST_Intersection to return ST_Value when intersecting with points   PostGIS
• [postgis-devel] [PostGIS] #528: Command line options for shp2pgsql-gui in the About box   PostGIS
• [postgis-devel] [PostGIS] #542: [raster] raster2pgsql.py should not set regular_blocking to true when wildcard are used to load many rasters (was: [raster] gdal2wktraster.py should not set regular_blocking to true when wildcard are used to load many rasters)   PostGIS
• [postgis-devel] [PostGIS] #551: Upgrade script still seems to be generating junk from 1.5   PostGIS
• [postgis-devel] [PostGIS] #551: Upgrade script still seems to be generating junk from 1.5   PostGIS
• [postgis-devel] [PostGIS] #565: shp2pgsql-gui crashes when selecting second file   PostGIS
• [postgis-devel] [PostGIS] #565: shp2pgsql-gui crashes when selecting second file   PostGIS
• [postgis-devel] [PostGIS] #582: [raster] Create functions returning correct pixel size calculations   PostGIS
• [postgis-devel] [PostGIS] #582: [raster] Create functions returning correct pixel size calculations   PostGIS
• [postgis-devel] [PostGIS] #582: [raster] Create functions returning correct pixel size calculations (was: [raster] Correct pixel size calculations)   PostGIS
• [postgis-devel] [PostGIS] #589: [raster] Implement ST_SameAlignment   PostGIS
• [postgis-devel] [PostGIS] #593: [raster] Add a ST_BandIsNoData function   PostGIS
• [postgis-devel] [PostGIS] #597: [raster] Add a ST_Clip function   PostGIS
• [postgis-devel] [PostGIS] #607: 1 regression tests failed with PostGIS SVN version   PostGIS
• [postgis-devel] [PostGIS] #608: Add dbf filter to shp2pgsql-gui   PostGIS
• [postgis-devel] [PostGIS] #608: Add dbf filter to shp2pgsql-gui   PostGIS
• [postgis-devel] [PostGIS] #616: change with-gdal to with-gdalconfig   PostGIS
• [postgis-devel] [PostGIS] #625: make clean does not clean raster   PostGIS
• [postgis-devel] [PostGIS] #625: make clean does not clean raster   PostGIS
• [postgis-devel] [PostGIS] #637: [raster] Modify raster dump function to produce real geometries   PostGIS
• [postgis-devel] [PostGIS] #637: [raster] Modify raster dump function to produce real geometries   PostGIS
• [postgis-devel] [PostGIS] #637: [raster] Modify raster dump function to produce real geometries   PostGIS
• [postgis-devel] [PostGIS] #650: [raster] st_dumpaspolygon create int values   PostGIS
• [postgis-devel] [PostGIS] #651: [raster] ST_makeemptyraster inconsistent with documentation   PostGIS
• [postgis-devel] [PostGIS] #660: shp2pgsql-gui support of -S switch Simple geometries   PostGIS
• [postgis-devel] [PostGIS] #663: shp2pgsql uses the wrong return type for pgis_getopt   PostGIS
• [postgis-devel] [PostGIS] #671: ST_IsEmpty('GEOMETRYCOLLECTION(GEOMETRYCOLLECTION EMPTY)') (was: ST_isempty( GEOMETRYCOLLECTION(GEOMETRYCOLLECTION(EMPTY)) ) returns false)   PostGIS
• [postgis-devel] [PostGIS] #679: shp2pgsql-gui should warn when SRID is not specified   PostGIS
• [postgis-devel] [PostGIS] #702: ticket #183 test fails on 32bit system   PostGIS
• [postgis-devel] [PostGIS] #702: ticket #183 test fails on 32bit system   PostGIS
• [postgis-devel] [PostGIS] #702: ticket #183 test fails on 32bit system   PostGIS
• [postgis-devel] [PostGIS] #707: loading postgis.sql returns an error   PostGIS
• [postgis-devel] [PostGIS] #707: loading postgis.sql returns an error   PostGIS
• [postgis-devel] [PostGIS] #707: loading postgis.sql returns an error   PostGIS
• [postgis-devel] [PostGIS] #735: regress failed   PostGIS
• [postgis-devel] [PostGIS] #735: regress failed   PostGIS
• [postgis-devel] [PostGIS] #735: regress failed   PostGIS
• [postgis-devel] [PostGIS] #748: shp2pgsql use wrong schema name   PostGIS
• [postgis-devel] [PostGIS] #751: Error making check in regress directory   PostGIS
• [postgis-devel] [PostGIS] #753: [raster] Error in make comments   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #796: [raster] Error in tickets core test   PostGIS
• [postgis-devel] [PostGIS] #817: Renaming old 3D functions to the convention ST_3D..........   PostGIS
• [postgis-devel] [PostGIS] #819: topology: error on regress of createtopogeom   PostGIS
• [postgis-devel] [PostGIS] #819: topology: error on regress of createtopogeom   PostGIS
• [postgis-devel] [PostGIS] #819: topology: error on regress of createtopogeom   PostGIS
• [postgis-devel] [PostGIS] #823: tiger geocoder: Make loader_generate_script download portion less greedyy   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] #826: [raster] There should be an option in raster2pgsql.py to prevent completing tiles with nodata   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   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] #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] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   Sandro Santilli
• [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] #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] #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] #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] #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] #851: [raster] Numerous ST_Value query cause the memory to grow indefinitely   PostGIS
• [postgis-devel] [PostGIS] #854: X3D output functions   PostGIS
• [postgis-devel] [PostGIS] #854: X3D output functions   PostGIS
• [postgis-devel] [PostGIS] #854: X3D output functions   PostGIS
• [postgis-devel] [PostGIS] #855: topology.TopologySummary [misses documentation]   PostGIS
• [postgis-devel] [PostGIS] #859: shp2pgsql new option to do something with bad geometries.   PostGIS
• [postgis-devel] [PostGIS] #861: DropGeometryTable should not raise exception if no geometry column   PostGIS
• [postgis-devel] [PostGIS] #861: DropGeometryTable should not raise exception if no geometry column   PostGIS
• [postgis-devel] [PostGIS] #861: DropGeometryTable should not raise exception if no geometry column   PostGIS
• [postgis-devel] [PostGIS] #861: DropGeometryTable should not raise exception if no geometry column   PostGIS
• [postgis-devel] [PostGIS] #862: Topology: the topology.DropTopology() drop any type of schemas   PostGIS
• [postgis-devel] [PostGIS] #862: Topology: the topology.DropTopology() drop any type of schemas   PostGIS
• [postgis-devel] [PostGIS] #862: Topology: the topology.DropTopology() drop any type of schemas   PostGIS
• [postgis-devel] [PostGIS] #869: ticket #304 regress is failing   PostGIS
• [postgis-devel] [PostGIS] #869: ticket #304 regress is failing   PostGIS
• [postgis-devel] [PostGIS] #869: ticket #304 regress is failing   PostGIS
• [postgis-devel] [PostGIS] #871: [raster] ST_AddBand documentation is inconsistent with function definitions and spec   PostGIS
• [postgis-devel] [PostGIS] #876: Better document ST_Azimuth   PostGIS
• [postgis-devel] [PostGIS] #880: topology.AddFace speed up using prepared geometries   PostGIS
• [postgis-devel] [PostGIS] #883: [raster] Make every rtpostgis.sql function immutable strict when possible   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] #885: pgsql2shp fields conversion from predefined list   PostGIS
• [postgis-devel] [PostGIS] #887: Tiger geocoder fails when address contains name of state sometimes   PostGIS
• [postgis-devel] [PostGIS] #887: Tiger geocoder fails when address contains name of state sometimes   PostGIS
• [postgis-devel] [PostGIS] #888: add cunit tests for pgsql2shp   PostGIS
• [postgis-devel] [PostGIS] #891: Allow 2.5D topologies   PostGIS
• [postgis-devel] [PostGIS] #891: Allow 2.5D topologies   PostGIS
• [postgis-devel] [PostGIS] #893: Error loading (shp2pgsql or bad geometry)   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #895: [raster]: FV.01 functions   PostGIS
• [postgis-devel] [PostGIS] #896: WARNING: transaction left non-empty SPI stack   PostGIS
• [postgis-devel] [PostGIS] #896: WARNING: transaction left non-empty SPI stack   PostGIS
• [postgis-devel] [PostGIS] #896: WARNING: transaction left non-empty SPI stack   PostGIS
• [postgis-devel] [PostGIS] #896: WARNING: transaction left non-empty SPI stack   PostGIS
• [postgis-devel] [PostGIS] #896: WARNING: transaction left non-empty SPI stack   PostGIS
• [postgis-devel] [PostGIS] #897: Ability to output X3D using GeoCoordinates   PostGIS
• [postgis-devel] [PostGIS] #898: Generate legacy.sql script   PostGIS
• [postgis-devel] [PostGIS] #898: Generate legacy.sql script   PostGIS
• [postgis-devel] [PostGIS] #899: shp2pgsql attribute names mapping   PostGIS
• [postgis-devel] [PostGIS] #899: shp2pgsql attribute names mapping   PostGIS
• [postgis-devel] [PostGIS] #900: shp2pgsql: a switch to drop M from 4d imports   PostGIS
• [postgis-devel] [PostGIS] #900: shp2pgsql: a switch to drop M from 4d imports   PostGIS
• [postgis-devel] [PostGIS] #901: [raster] ST_AsGDALRaster and the helper functions ST_getGDALDrivers and ST_srtext   PostGIS
• [postgis-devel] [PostGIS] #901: [raster] ST_AsGDALRaster and the helper functions ST_getGDALDrivers and ST_srtext   PostGIS
• [postgis-devel] [PostGIS] #901: [raster] ST_AsGDALRaster and the helper functions ST_getGDALDrivers and ST_srtext   PostGIS
• [postgis-devel] [PostGIS] #901: [raster] ST_AsGDALRaster and the helper functions ST_getGDALDrivers and ST_srtext   PostGIS
• [postgis-devel] [PostGIS] #901: [raster] ST_AsGDALRaster and the helper functions ST_getGDALDrivers and ST_srtext   PostGIS
• [postgis-devel] [PostGIS] #901: [raster] ST_AsGDALRaster and the helper functions ST_getGDALDrivers and ST_srtext   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #902: [raster] ST_MinMax   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #903: [raster] ST_Reclass   PostGIS
• [postgis-devel] [PostGIS] #904: PostGIS 2.0.0 stop testing on 8.3 and make 8.4 minimum   PostGIS
• [postgis-devel] [PostGIS] #904: PostGIS 2.0.0 stop testing on 8.3 and make 8.4 minimum   PostGIS
• [postgis-devel] [PostGIS] #904: PostGIS 2.0.0 stop testing on 8.3 and make 8.4 minimum   PostGIS
• [postgis-devel] [PostGIS] #904: PostGIS 2.0.0 stop testing on 8.3 and make 8.4 minimum   PostGIS
• [postgis-devel] [PostGIS] #904: PostGIS 2.0.0 stop testing on 8.3 and make 8.4 minimum   PostGIS
• [postgis-devel] [PostGIS] #904: PostGIS 2.0.0 stop testing on 8.3 and make 8.4 minimum   PostGIS
• [postgis-devel] [PostGIS] #905: GML LinearRing is not supported in ST_GeomFromGML   PostGIS
• [postgis-devel] [PostGIS] #905: GML LinearRing is not supported in ST_GeomFromGML   PostGIS
• [postgis-devel] [PostGIS] #906: ST_GeomFromGML add SRID option   PostGIS
• [postgis-devel] [PostGIS] #906: ST_GeomFromGML add SRID option   PostGIS
• [postgis-devel] [PostGIS] #907: Test tiger geocoder loader script on linux/unix and remove issues   PostGIS
• [postgis-devel] [PostGIS] #907: Test tiger geocoder loader script on linux/unix and remove issues   PostGIS
• [postgis-devel] [PostGIS] #908: linux version of tiger2010 geocoder does not work   PostGIS
• [postgis-devel] [PostGIS] #908: linux version of tiger2010 geocoder does not work   PostGIS
• [postgis-devel] [PostGIS] #908: linux version of tiger2010 geocoder does not work   PostGIS
• [postgis-devel] [PostGIS] #908: linux version of tiger2010 geocoder does not work   PostGIS
• [postgis-devel] [PostGIS] #909: cu_tester segfaults on 64bit system   PostGIS
• [postgis-devel] [PostGIS] #909: cu_tester segfaults on 64bit system   PostGIS
• [postgis-devel] [PostGIS] #910: Raster not listed under the "Extensions" configure output block   PostGIS
• [postgis-devel] [PostGIS] #910: Raster not listed under the "Extensions" configure output block   PostGIS
• [postgis-devel] [PostGIS] #910: Raster not listed under the "Extensions" configure output block   PostGIS
• [postgis-devel] [PostGIS] #910: Raster not listed under the "Extensions" configure output block   PostGIS
• [postgis-devel] [PostGIS] #910: Raster not listed under the "Extensions" configure output block   PostGIS
• [postgis-devel] [PostGIS] #910: Raster not listed under the "Extensions" configure output block   PostGIS
• [postgis-devel] [PostGIS] #911: regress_managment ticket failing on 9.1 alpha5 and hudson   PostGIS
• [postgis-devel] [PostGIS] #911: regress_managment ticket failing on 9.1 alpha5 and hudson   PostGIS
• [postgis-devel] [PostGIS] #912: ST_COLLECT truncates result after null value   PostGIS
• [postgis-devel] [PostGIS] #913: legacy.sql install failing on geometry2box2d not found in postgis-2.0...   PostGIS
• [postgis-devel] [PostGIS] #913: legacy.sql install failing on geometry2box2d not found in postgis-2.0...   PostGIS
• [postgis-devel] [PostGIS] #914: legacy.sql install failing on can't find chip   PostGIS
• [postgis-devel] [PostGIS] #914: legacy.sql install failing on can't find chip   PostGIS
• [postgis-devel] [PostGIS] #915: regress test for legacy.sql   PostGIS
• [postgis-devel] [PostGIS] #916: topology.Polygonize: automatically find faces from edges   PostGIS
• [postgis-devel] [PostGIS] #916: topology.Polygonize: automatically find faces from edges   PostGIS
• [postgis-devel] [PostGIS] #917: Limit topology.Polygonize by extent   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #918: two bugs in Populate_Geometry_Columns(oid)   PostGIS
• [postgis-devel] [PostGIS] #919: Documentation build errors again   PostGIS
• [postgis-devel] [PostGIS] #919: Documentation build errors again   PostGIS
• [postgis-devel] [PostGIS] #919: Documentation build errors again   PostGIS
• [postgis-devel] [PostGIS] #920: CURVEPOLYGON problem when converting to/from text   PostGIS
• [postgis-devel] [PostGIS] #920: CURVEPOLYGON problem when converting to/from text   PostGIS
• [postgis-devel] [PostGIS] #920: CURVEPOLYGON problem when converting to/from text   PostGIS
• [postgis-devel] [PostGIS] #920: ST_LineToCurve generating invalid CURVEPOLYGON (was: CURVEPOLYGON problem when converting to/from text)   PostGIS
• [postgis-devel] [PostGIS] #921: populate_geometry_columns() does not add parent tables   PostGIS
• [postgis-devel] [PostGIS] #921: populate_geometry_columns() does not add parent tables   PostGIS
• [postgis-devel] [PostGIS] #921: populate_geometry_columns() does not add parent tables   PostGIS
• [postgis-devel] [PostGIS] #922: Have ST_Union aggregate use UnaryUnion from GEOS-3.0.0   PostGIS
• [postgis-devel] [PostGIS] #923: Erroneous documentation examples with "GEOMETRYCOLLECTION(EMPTY)"   PostGIS
• [postgis-devel] [PostGIS] #923: Erroneous documentation examples with "GEOMETRYCOLLECTION(EMPTY)"   PostGIS
• [postgis-devel] [PostGIS] #923: Erroneous documentation examples with "GEOMETRYCOLLECTION(EMPTY)"   PostGIS
• [postgis-devel] [PostGIS] #923: Erroneous documentation examples with "GEOMETRYCOLLECTION(EMPTY)"   PostGIS
• [postgis-devel] [PostGIS] #924: GEOMETRYCOLLECTION(EMPTY) breaking change   PostGIS
• [postgis-devel] [PostGIS] #925: [raster] ST_Transform   PostGIS
• [postgis-devel] [PostGIS] #926: ST_GeometryN, ST_PointN (input of array) return set   PostGIS
• [postgis-devel] [PostGIS] #926: ST_GeometryN, ST_PointN (input of array) return set   PostGIS
• [postgis-devel] [PostGIS] #926: ST_GeometryN, ST_PointN (input of array) return set   PostGIS
• [postgis-devel] [PostGIS] #926: ST_GeometryN, ST_PointN (input of array) return set   PostGIS
• [postgis-devel] [PostGIS] #926: ST_GeometryN, ST_PointN (input of array) return set   PostGIS
• [postgis-devel] [PostGIS] #926: ST_GeometryN, ST_PointN (input of array) return set   PostGIS
• [postgis-devel] [PostGIS] #927: reverse_geocode second proto is broken (was: reverse_geocoder second proto is broken)   PostGIS
• [postgis-devel] [PostGIS] #927: reverse_geocoder second proto is broken   PostGIS
• [postgis-devel] [PostGIS] #927: reverse_geocoder second proto is broken   PostGIS
• [postgis-devel] [PostGIS] #928: [raster] Implement ST_PixelWidth   PostGIS
• [postgis-devel] [PostGIS] #928: [raster] Implement ST_PixelWidth   PostGIS
• [postgis-devel] [PostGIS] #929: [raster] Implement ST_PixelHeight   PostGIS
• [postgis-devel] [PostGIS] #930: [raster] ST_SummaryStats   PostGIS
• [postgis-devel] [PostGIS] #930: [raster] ST_SummaryStats   PostGIS
• [postgis-devel] [PostGIS] #930: [raster] ST_SummaryStats   PostGIS
• [postgis-devel] [PostGIS] #931: [raster] ST_Mean   PostGIS
• [postgis-devel] [PostGIS] #931: [raster] ST_Mean   PostGIS
• [postgis-devel] [PostGIS] #931: [raster] ST_Mean   PostGIS
• [postgis-devel] [PostGIS] #931: [raster] ST_Mean   PostGIS
• [postgis-devel] [PostGIS] #931: [raster] ST_Mean   PostGIS
• [postgis-devel] [PostGIS] #932: [raster] ST_StdDev   PostGIS
• [postgis-devel] [PostGIS] #933: Error in GML namespace handle - ST_GeomFromGML   PostGIS
• [postgis-devel] [PostGIS] #933: Error in GML namespace handle - ST_GeomFromGML   PostGIS
• [postgis-devel] Error: GDAL Python bindings required   Emilio de Torres Fernández
• [postgis-devel] Error: GDAL Python bindings required   Pierre Racine
• [postgis-devel] Fwd: Build failed in Hudson: PostGIS-trunk-build #2157   Olivier Courtin
• [postgis-devel] GDAL Trunk   Paragon Corporation
• [postgis-devel] GDAL Trunk   Jorge Arévalo
• [postgis-devel] Hudson: run make check with RUNTESTFLAGS=-v!   Sandro Santilli
• [postgis-devel] lwgeom_calculate_bbox   Sandro Santilli
• [postgis-devel] lwgeom_calculate_bbox   Sandro Santilli
• [postgis-devel] OSGeo Hatching   Chris Hodgson
• [postgis-devel] OSGeo Hatching   Paul Ramsey
• [postgis-devel] OSGeo Hatching   Paragon Corporation
• [postgis-devel] patch: pgsql2shp fields conversion from predefined list   Loic Dachary
• [postgis-devel] Planning of raster work to be integrated in PostGIS 2.0   Olivier Courtin
• [postgis-devel] Planning of raster work to be integrated in PostGIS 2.0   Pierre Racine
• [postgis-devel] Planning of raster work to be integrated in PostGIS 2.0   Paul Ramsey
• [postgis-devel] PostGIS Raster Project for GSoC 2011   Vipul Raheja
• [postgis-devel] Problems compiling GEOS 3.3.0 with MngW-64   Paragon Corporation
• [postgis-devel] Problems compiling GEOS 3.3.0 with MngW-64   Mark Cave-Ayland
• [postgis-devel] PSC Vote to officially drop support for PostgreSQL 8.3 in PostGIS 2.0   Sandro Santilli
• [postgis-devel] PSC Vote to officially drop support for PostgreSQL 8.3 in PostGIS 2.0   Paragon Corporation
• [postgis-devel] PSC Vote to officially drop support for PostgreSQL 8.3 in PostGIS 2.0   Paragon Corporation
• [postgis-devel] PSC Vote to officially drop support for PostgreSQL 8.3 in PostGIS 2.0   Paul Ramsey
• [postgis-devel] PSC Vote to officially drop support for PostgreSQL 8.3 in PostGIS 2.0   Mark Cave-Ayland
• [postgis-devel] PSC Vote to officially drop support for PostgreSQL 8.3 in PostGIS 2.0   Paul Ramsey
• [postgis-devel] PSC Vote to officially drop support for PostgreSQL 8.3 in PostGIS 2.0   Mark Cave-Ayland
• [postgis-devel] Question on memory management on C functions   Jorge Arévalo
• [postgis-devel] Question on memory management on C functions   Sandro Santilli
• [postgis-devel] RFC-1: Project Steering Committee Guidelines   Chris Hodgson
• [postgis-devel] RFC-1: Project Steering Committee Guidelines   Paragon Corporation
• [postgis-devel] RFC-1: Project Steering Committee Guidelines   Chris Hodgson
• [postgis-devel] SnapToGrid support of circular string   Sandro Santilli
• [postgis-devel] SnapToGrid support of circular string   Mark Cave-Ayland
• [postgis-devel] SnapToGrid support of circular string   Sandro Santilli
• [postgis-devel] Where should RFCs live?   Chris Hodgson
• [postgis-devel] Where should RFCs live?   Mike Toews
• [postgis-devel] Where should RFCs live?   Sandro Santilli
• [postgis-devel] Where should RFCs live?   Chris Hodgson
• [postgis-devel] Where should RFCs live?   Paragon Corporation

Last message date: Sat Apr 30 15:27:01 PDT 2011
Archived on: Wed Oct 31 11:53:57 PDT 2012

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