February 2011 Archives by author

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

Starting: Tue Feb 1 01:02:06 PST 2011
Ending: Mon Feb 28 03:50:15 PST 2011
Messages: 277

• [postgis-devel] Status of raster mapalgebra?   Jorge Arévalo
• [postgis-devel] [PostGIS] #588: [raster] Implement the one raster version of ST_MapAlgebra   Jorge Arévalo
• [postgis-devel] configure on HP-UX   Scott Brunza
• [postgis-devel] Could patch in #810 be applied?   Mark Cave-Ayland
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   Mark Cave-Ayland
• [postgis-devel] GML3 output signatures   Mark Cave-Ayland
• [postgis-devel] [PATCH] Binary IO support for geography type   Mark Cave-Ayland
• [postgis-devel] Raster: Raster2pgsql -V option why do we need it?   Paragon Corporation
• [postgis-devel] MULTIPOINT() WKT   Paragon Corporation
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   Paragon Corporation
• [postgis-devel] [PostGIS] #827: Hudson has fallen againand can't get up   Paragon Corporation
• [postgis-devel] GML3 output signatures   Olivier Courtin
• [postgis-devel] GML3 output signatures   Olivier Courtin
• [postgis-devel] GML3 output signatures   Olivier Courtin
• [postgis-devel] Faster option to get an image   Emilio de Torres Fernández
• [postgis-devel] Faster option to get an image   Emilio de Torres Fernández
• [postgis-devel] [raster] Is wktraster-0.1.6d.tar.gz last snapshot?   Chris Hodgson
• [postgis-devel] configure on HP-UX   Chris Hodgson
• [postgis-devel] Could patch in #810 be applied?   Peter Hopfgartner
• [postgis-devel] Could patch in #810 be applied?   Peter Hopfgartner
• [postgis-devel] functions for building linestring grids and clipping polygons by a linestring   David Kaplan
• [postgis-devel] Raster: Raster2pgsql -V option why do we need it?   Mateusz Loskot
• [postgis-devel] Faster option to get an image   Mateusz Loskot
• [postgis-devel] [raster] Is wktraster-0.1.6d.tar.gz last snapshot?   Mateusz Loskot
• [postgis-devel] [raster] Is wktraster-0.1.6d.tar.gz last snapshot?   Mateusz Loskot
• [postgis-devel] ST_CollectionExtract with empy collection   Andrea Peri
• [postgis-devel] ST_CollectionExtract with empy collection   Andrea Peri
• [postgis-devel] [PostGIS] #809: errors building the documentation   PostGIS
• [postgis-devel] [PostGIS] #818: ANALYZE does not override statistics on empty table   PostGIS
• [postgis-devel] [PostGIS] #818: ANALYZE does not override statistics on empty table   PostGIS
• [postgis-devel] [PostGIS] #818: ANALYZE does not override statistics on empty table   PostGIS
• [postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList   PostGIS
• [postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList   PostGIS
• [postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList   PostGIS
• [postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList   PostGIS
• [postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList   PostGIS
• [postgis-devel] [PostGIS] #818: ANALYZE does not override statistics on empty table   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] #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] #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] #819: topology: error on regress of createtopogeom   PostGIS
• [postgis-devel] [PostGIS] #819: topology: error on regress of createtopogeom   PostGIS
• [postgis-devel] [PostGIS] #343: History Table Enhancements   PostGIS
• [postgis-devel] [PostGIS] #343: History Table Enhancements   PostGIS
• [postgis-devel] [PostGIS] #820: ST_Within fails at walls (upright polygons)   PostGIS
• [postgis-devel] [PostGIS] #820: ST_Within fails at walls (upright polygons)   PostGIS
• [postgis-devel] [PostGIS] #607: 1 regression tests failed with PostGIS SVN version (was: 6 regression tests failed with PostGIS SVN version)   PostGIS
• [postgis-devel] [PostGIS] #557: ST_Within fails at walls (upright polygons)   PostGIS
• [postgis-devel] [PostGIS] #821: doc typos   PostGIS
• [postgis-devel] [PostGIS] #821: doc typos   PostGIS
• [postgis-devel] [PostGIS] #821: doc typos   PostGIS
• [postgis-devel] [PostGIS] #821: doc typos   PostGIS
• [postgis-devel] [PostGIS] #821: doc typos   PostGIS
• [postgis-devel] [PostGIS] #135: Upgrade geocoder to use the new tiger 2010 files   PostGIS
• [postgis-devel] [PostGIS] #822: Add a reverse_geocode function to tiger geocoder   PostGIS
• [postgis-devel] [PostGIS] #822: Add a reverse_geocode function to tiger geocoder   PostGIS
• [postgis-devel] [PostGIS] #823: tiger geocoder: Make loader_generate_script download portion less greedyy   PostGIS
• [postgis-devel] [PostGIS] #824: Another doc patch   PostGIS
• [postgis-devel] [PostGIS] #822: Add a reverse_geocode function to tiger geocoder   PostGIS
• [postgis-devel] [PostGIS] #824: Another doc patch   PostGIS
• [postgis-devel] [PostGIS] #825: 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] #826: [raster] There should be an option in raster2pgsql.py to prevent completing tiles with nodata   PostGIS
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   PostGIS
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   PostGIS
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   PostGIS
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   PostGIS
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   PostGIS
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   PostGIS
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   PostGIS
• [postgis-devel] [PostGIS] #827: Hudson has fallen again and can't get up   PostGIS
• [postgis-devel] [PostGIS] #828: [raster] Loader generates wrong SQL when NODATA for a band is NaN   PostGIS
• [postgis-devel] [PostGIS] #763: Topology_comments - createtopogeom(..) is missing   PostGIS
• [postgis-devel] [PostGIS] #829: st_addedgenewfaces looks incomplete   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #828: [raster] Loader generates wrong SQL when NODATA for a band is NaN   PostGIS
• [postgis-devel] [PostGIS] #101: ST_Union on one-row table doesn't union   PostGIS
• [postgis-devel] [PostGIS] #575: ST_Union fails on a group of linestrings.   PostGIS
• [postgis-devel] [PostGIS] #830: ST_UnaryUnion   PostGIS
• [postgis-devel] [PostGIS] #830: ST_UnaryUnion   PostGIS
• [postgis-devel] [PostGIS] #830: ST_UnaryUnion   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #822: Add a reverse_geocode function to tiger geocoder   PostGIS
• [postgis-devel] [PostGIS] #806: Optimize Geometry(TopoGeometry) for polygons   PostGIS
• [postgis-devel] [PostGIS] #830: ST_UnaryUnion   PostGIS
• [postgis-devel] [PostGIS] #828: [raster] Loader generates wrong SQL when NODATA for a band is NaN   PostGIS
• [postgis-devel] [PostGIS] #831: Flags for ST_IsValid*   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #310: port ST_DumpPoints() to C   PostGIS
• [postgis-devel] [PostGIS] #832: Wrong line from ST_Difference   PostGIS
• [postgis-devel] [PostGIS] #825: [raster] raster overview -- trying to insert into wrong table (if schema qualify), and not creating rast column (was: raster overview -- trying to insert into wrong table (if schema qualify), and not creating rast column)   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] #833: PostGIS 2.0 Testing on various desktops   PostGIS
• [postgis-devel] [PostGIS] #833: PostGIS 2.0 Testing on various desktops   PostGIS
• [postgis-devel] [PostGIS] #833: PostGIS 2.0 Testing on various desktops   PostGIS
• [postgis-devel] [PostGIS] #832: Wrong line from ST_Difference   PostGIS
• [postgis-devel] [PostGIS] #831: Flags for ST_IsValid*   PostGIS
• [postgis-devel] [PostGIS] #832: Wrong line from ST_Difference   PostGIS
• [postgis-devel] [PostGIS] #831: Flags for ST_IsValid*   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   PostGIS
• [postgis-devel] [PostGIS] #831: Flags for ST_IsValid*   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   PostGIS
• [postgis-devel] [PostGIS] #830: ST_UnaryUnion   PostGIS
• [postgis-devel] [PostGIS] #835: ST_CollectionExtract returns EMPTY or NULL inconsistently   PostGIS
• [postgis-devel] [PostGIS] #588: [raster] Implement the one raster version of ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #836: PostGIS raster in 2.0 is not being output in Trunk Doxygen   PostGIS
• [postgis-devel] [PostGIS] #836: PostGIS raster in 2.0 is not being output in Trunk Doxygen   PostGIS
• [postgis-devel] [PostGIS] #588: [raster] Implement the one raster version of ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #835: ST_CollectionExtract returns EMPTY or NULL inconsistently   PostGIS
• [postgis-devel] [PostGIS] #588: [raster] Implement the one raster version of ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #588: [raster] Implement the one raster version of ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #837: ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #837: ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #837: ST_MapAlgebra -- I think we have a memory leak   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #837: [raster] ST_MapAlgebra -- I think we have a memory leak (was: ST_MapAlgebra -- I think we have a memory leak)   PostGIS
• [postgis-devel] [PostGIS] #701: Support for 9.1 KNN GIST enhancements   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #834: lw_collection_construct error   PostGIS
• [postgis-devel] [PostGIS] #701: Support for 9.1 KNN GIST enhancements   PostGIS
• [postgis-devel] [PostGIS] #838: Check GDAL Python bindings with NumPy support   PostGIS
• [postgis-devel] [PostGIS] #497: [raster] Start testing displaying PostGIS raster with Mapserver   PostGIS
• [postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList   PostGIS
• [postgis-devel] [PostGIS] #839: error: too many arguments to function GEOSisValidDetail   PostGIS
• [postgis-devel] [PostGIS] #839: error: too many arguments to function GEOSisValidDetail   PostGIS
• [postgis-devel] [PostGIS] #839: error: too many arguments to function GEOSisValidDetail   PostGIS
• [postgis-devel] [PostGIS] #838: [raster] Check GDAL Python bindings with NumPy support (was: Check GDAL Python bindings with NumPy support)   PostGIS
• [postgis-devel] [PostGIS] #611: [raster] gdal2wktraster.py crashes on Windows 7   PostGIS
• [postgis-devel] [PostGIS] #838: [raster] Check GDAL Python bindings with NumPy support   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #762: [raster] Raster some check fails   PostGIS
• [postgis-devel] [PostGIS] #792: [raster] Addband regresssion test fail on some systems.   PostGIS
• [postgis-devel] [PostGIS] #611: [raster] gdal2wktraster.py crashes on Windows 7   PostGIS
• [postgis-devel] [PostGIS] #792: [raster] Addband regresssion test fail on some systems.   PostGIS
• [postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #842: OSGEO Web branding   PostGIS
• [postgis-devel] [PostGIS] #843: Reflect membership in foundation   PostGIS
• [postgis-devel] [PostGIS] #843: Reflect membership in foundation   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #842: OSGEO Web branding   PostGIS
• [postgis-devel] [PostGIS] #842: OSGeo Web branding (was: OSGEO Web branding)   PostGIS
• [postgis-devel] [PostGIS] #842: OSGeo Web branding   PostGIS
• [postgis-devel] [PostGIS] #844: Allow specifying BoundaryNodeRule in ST_Relate*   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #843: Reflect membership in foundation   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #841: Commiter Responsibilities Guidelines   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #846: Cleaning up around and enhance point in polygon tests around the code   PostGIS
• [postgis-devel] [PostGIS] #846: Cleaning up around and enhance point in polygon tests around the code   PostGIS
• [postgis-devel] [PostGIS] #846: Cleaning up around and enhance point in polygon tests around the code   PostGIS
• [postgis-devel] [PostGIS] #846: Cleaning up around and enhance point in polygon tests around the code   PostGIS
• [postgis-devel] [PostGIS] #312: ST_ConcaveHull   PostGIS
• [postgis-devel] [PostGIS] #822: Add a reverse_geocode function to tiger geocoder   PostGIS
• [postgis-devel] [PostGIS] #846: Cleaning up around and enhance point in polygon tests around the code   PostGIS
• [postgis-devel] [PostGIS] #830: ST_UnaryUnion   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #153: [raster] gdal2wktraster.py: check for same pixelsize when loading using wildcard   PostGIS
• [postgis-devel] [PostGIS] #840: Code Provenance Review   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #845: ST_Intersects() precision error - returns false instead of true   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #793: Topology: function GetNodeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #846: Cleaning up around and enhance point in polygon tests around the code   PostGIS
• [postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList   PostGIS
• [postgis-devel] [PostGIS] #846: Cleaning up around and enhance point in polygon tests around the code   PostGIS
• [postgis-devel] [PostGIS] #793: Topology: function GetNodeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #833: PostGIS 2.0 Testing on various desktops   PostGIS
• [postgis-devel] [PostGIS] #833: PostGIS 2.0 Testing on various desktops   PostGIS
• [postgis-devel] [PostGIS] #847: Internationalization of documentation   PostGIS
• [postgis-devel] [PostGIS] #791: Topology: function GetEdgeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #793: Topology: function GetNodeByPoint($1, $2, $3)   PostGIS
• [postgis-devel] [PostGIS] #848: Fix eror message for GetNodeByPoint, GetNodeByEdge   PostGIS
• [postgis-devel] [PostGIS] #848: Fix eror message for GetNodeByPoint, GetNodeByEdge   PostGIS
• [postgis-devel] [PostGIS] #847: Internationalization of documentation   PostGIS
• [postgis-devel] [PostGIS] #847: Internationalization of documentation   PostGIS
• [postgis-devel] [PostGIS] #848: Fix eror message for GetNodeByPoint, GetNodeByEdge   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] #846: Cleaning up around and enhance point in polygon tests around the code   PostGIS
• [postgis-devel] [PostGIS] #784: topology: add some functions to retrieve the id of node, edge and face   PostGIS
• [postgis-devel] [PATCH] Binary IO support for geography type   Elvis Pranskevichus
• [postgis-devel] Status of raster mapalgebra?   Pierre Racine
• [postgis-devel] Raster: Raster2pgsql -V option why do we need it?   Pierre Racine
• [postgis-devel] [PostGIS] #588: [raster] Implement the one raster version of ST_MapAlgebra   Pierre Racine
• [postgis-devel] MULTIPOINT() WKT   Paul Ramsey
• [postgis-devel] Fwd: [TOSprint] Montreal Code Sprint Reminders   Paul Ramsey
• [postgis-devel] X3D Export   Leonardo Rafael Fernandez Ruiz
• [postgis-devel] GML3 output signatures   Sandro Santilli
• [postgis-devel] GML3 output signatures   Sandro Santilli
• [postgis-devel] GML3 output signatures   Sandro Santilli
• [postgis-devel] GML3 output signatures   Sandro Santilli
• [postgis-devel] GML3 output signatures   Sandro Santilli
• [postgis-devel] Boundary of closed linestrings, part 2   Sandro Santilli
• [postgis-devel] [postgis-users] st_intersects() returns false with point and polygon that obviously intersect   Sandro Santilli
• [postgis-devel] [postgis-users] st_intersects() returns false with point and polygon that obviously intersect   Craig de Stigter
• [postgis-devel] Faster option to get an image   cesius
• [postgis-devel] Nightly build performance   James.Sewell at lisasoft.com
• [postgis-devel] MULTIPOINT() WKT   strk
• [postgis-devel] ST_IsValidDetail   strk
• [postgis-devel] ST_CollectionExtract with empy collection   strk
• [postgis-devel] ST_CollectionExtract with empy collection   strk

Last message date: Mon Feb 28 03:50:15 PST 2011
Archived on: Fri Nov 10 09:26:06 PST 2017

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