March 2009 Archives by author
Starting: Sun Mar 1 14:27:38 PST 2009
Ending: Tue Mar 31 13:40:07 PDT 2009
Messages: 437
- [postgis-devel] RE: 40% faster st_distance and returningmeasurepoints :-)
Nicklas Avén
- [postgis-devel] WKT Raster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mark Cave-Ayland
- [postgis-devel] WKT Raster: Why having tocompilePostgreSQL&PostGIS first?
Mark Cave-Ayland
- [postgis-devel] WKT Raster: Why having tocompilePostgreSQL&PostGISfirst?
Mark Cave-Ayland
- [postgis-devel] configure error while buildingWKTRaster onUbuntu8.10
Mark Cave-Ayland
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mark Cave-Ayland
- [postgis-devel] configure error whilebuildingWKTRaster onUbuntu8.10
Mark Cave-Ayland
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mark Cave-Ayland
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mark Cave-Ayland
- [postgis-devel] More dump comments
Mark Cave-Ayland
- [postgis-devel] Remove PDF from Hudson build?
Mark Cave-Ayland
- [postgis-devel] More dump comments
Mark Cave-Ayland
- [postgis-devel] Coordinate compression for native PostGIS geometry storage?
Mark Cave-Ayland
- [postgis-devel] Remove PDF from Hudson build?
Mark Cave-Ayland
- [postgis-devel] Coordinate compression for native PostGIS geometry storage?
Mark Cave-Ayland
- [postgis-devel] Code sprint notes
Mark Cave-Ayland
- [postgis-devel] New Doco
Mark Cave-Ayland
- [postgis-devel] Compilation using Visual C++ 8.0
Mark Cave-Ayland
- PostGIS infrastructure (was: Re: [postgis-devel] SVN is [temporarily] broken)
Mark Cave-Ayland
- [postgis-devel] Re: PostGIS infrastructure
Mark Cave-Ayland
- [postgis-devel] Re: PostGIS infrastructure
Mark Cave-Ayland
- [postgis-devel] Compilation using Visual C++ 8.0
Mark Cave-Ayland
- [postgis-devel] Re: PostGIS infrastructure
Mark Cave-Ayland
- [postgis-devel] [WKT Raster] Requirement of PostgreSQL
Mark Cave-Ayland
- [postgis-devel] Re: PostGIS infrastructure
Mark Cave-Ayland
- [postgis-devel] SVN trunk libxml2 detection is broken
Mark Cave-Ayland
- [postgis-devel] Re: PostGIS infrastructure
Mark Cave-Ayland
- [postgis-devel] Re: Q3C
Mark Cave-Ayland
- [postgis-devel] gml, geojson, svg
Mark Cave-Ayland
- [postgis-devel] GEOS Warnings
Mark Cave-Ayland
- [postgis-devel] GEOS Warnings
Mark Cave-Ayland
- [postgis-devel] run_test and PostgreSQL user
Mark Cave-Ayland
- [postgis-devel] Slouching Towards 1.4
Mark Cave-Ayland
- [postgis-devel] Compilation using Visual C++ 8.0
Mark Cave-Ayland
- [postgis-devel] Function Sigs
Mark Cave-Ayland
- [postgis-devel] Compilation using Visual C++ 8.0
Mark Cave-Ayland
- [postgis-devel] Function Sigs
Mark Cave-Ayland
- [postgis-devel] Re: User IDs @ OSGeo
Mark Cave-Ayland
- [postgis-devel] Slouching Towards 1.4
Mark Cave-Ayland
- [postgis-devel] Re: Incubation
Mark Cave-Ayland
- [postgis-devel] Does GEOS functiion GEOSGeomFromWKB_buf support Measured collection type?
Chenzhen
- [postgis-devel] Issue 119 in postgis: ST_AsSVGcrashedDBbackendwith large geometries.
Paragon Corporation
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Paragon Corporation
- [postgis-devel] RE: 40% faster st_distance and returningmeasurepoints :-)
Paragon Corporation
- [postgis-devel] [WKT Raster] Type of extent columnofRASTER_COLUMNS
Paragon Corporation
- [postgis-devel] [WKT Raster] Type of extent columnofRASTER_COLUMNS
Paragon Corporation
- [postgis-devel] gml, geojson, svg
Paragon Corporation
- [postgis-devel] gml, geojson, svg
Paragon Corporation
- [postgis-devel] gml, geojson, svg
Paragon Corporation
- [postgis-devel] Function Sigs
Paragon Corporation
- [postgis-devel] Function Sigs
Paragon Corporation
- [postgis-devel] Function Sigs
Paragon Corporation
- [postgis-devel] Function Sigs
Paragon Corporation
- [postgis-devel] Function Sigs
Paragon Corporation
- [postgis-devel] [WKT Raster] Still using old SVN
Paragon Corporation
- [postgis-devel] Coordinate compression for native PostGIS geometry storage?
Martin Davis
- [postgis-devel] Coordinate compression for native PostGIS geometry storage?
Martin Davis
- [postgis-devel] Q3C
Martin Davis
- [postgis-devel] Re: Q3C
Martin Davis
- [postgis-devel] Re: Q3C
Martin Davis
- [postgis-devel] Re: Q3C
Martin Davis
- [postgis-devel] configure error while building WKTRaster on Ubuntu 8.10
Tyler Erickson
- [postgis-devel] configure error while building WKTRaster onUbuntu8.10
Tyler Erickson
- [postgis-devel] WKTRaster news from the Toronto Code Sprint?
Tyler Erickson
- [postgis-devel] RE: WKTRaster news from the Toronto Code Sprint?
Stephen Frost
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
Stephen Frost
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Stephen Frost
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Stephen Frost
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Stephen Frost
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Stephen Frost
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Stephen Frost
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Magnus Hagander
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Chris Hodgson
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Chris Hodgson
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Chris Hodgson
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Chris Hodgson
- [postgis-devel] [WKT Raster] Still using old SVN
Chris Hodgson
- [postgis-devel] Code sprint notes
Mark Leslie
- [postgis-devel] Code sprint notes
Mark Leslie
- [postgis-devel] Re: Incubation
Mark Leslie
- [postgis-devel] [WKT Raster] Still using old SVN
Mark Leslie
- [postgis-devel] WKT Raster: Why having to compile PostgreSQL& PostGIS first?
Mateusz Loskot
- [postgis-devel] WKT Raster: Why having to compilePostgreSQL&PostGIS first?
Mateusz Loskot
- [postgis-devel] [WKTRaster] RT_Value function added
Mateusz Loskot
- [postgis-devel] configure error while building WKTRaster on Ubuntu8.10
Mateusz Loskot
- [postgis-devel] configure error while building WKTRaster onUbuntu8.10
Mateusz Loskot
- [postgis-devel] configure error while buildingWKTRaster onUbuntu8.10
Mateusz Loskot
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mateusz Loskot
- [postgis-devel] configure error whilebuildingWKTRaster onUbuntu8.10
Mateusz Loskot
- [postgis-devel] configureerror whilebuildingWKTRaster onUbuntu8.10
Mateusz Loskot
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mateusz Loskot
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mateusz Loskot
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mateusz Loskot
- [Fwd: [postgis-devel] WKT Raster: GDAL or World file upper left coordinates]
Mateusz Loskot
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Mateusz Loskot
- [postgis-devel] WKT Raster: GDAL or World file upper leftcoordinates
Mateusz Loskot
- [postgis-devel] WKT Raster: GDAL or World fileupper leftcoordinates
Mateusz Loskot
- [postgis-devel] WKT Raster: GDAL orWorld fileupper leftcoordinates
Mateusz Loskot
- [postgis-devel] WKT Raster: Bug tracking
Mateusz Loskot
- [postgis-devel] WKT Raster: Bug tracking
Mateusz Loskot
- [postgis-devel] WKT Raster: Bug tracking
Mateusz Loskot
- [postgis-devel] WKT Raster: Bug tracking
Mateusz Loskot
- [postgis-devel] WKTRaster autobuilds
Mateusz Loskot
- [postgis-devel] Compilation using Visual C++ 8.0
Mateusz Loskot
- [postgis-devel] Compilation using Visual C++ 8.0
Mateusz Loskot
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Mateusz Loskot
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Mateusz Loskot
- [postgis-devel] [WKT Raster] Requirement of PostgreSQL
Mateusz Loskot
- [postgis-devel] [WKT Raster] Requirement of PostgreSQL
Mateusz Loskot
- [postgis-devel] [WKT Raster] Type of extent column of RASTER_COLUMNS
Mateusz Loskot
- [postgis-devel] [WKT Raster] Type of extent column of RASTER_COLUMNS
Mateusz Loskot
- [postgis-devel] [WKT Raster] Type of extent column ofRASTER_COLUMNS
Mateusz Loskot
- [postgis-devel] PostGIS website is down?
Mateusz Loskot
- [postgis-devel] [WKT Raster] Type of extent columnofRASTER_COLUMNS
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking restrictions
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking restrictions
Mateusz Loskot
- [postgis-devel] [WKT Raster] Type of extent columnofRASTER_COLUMNS
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] Does GEOS functiion GEOSGeomFromWKB_buf supportMeasured collection type?
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] Compilation using Visual C++ 8.0
Mateusz Loskot
- [postgis-devel] Compilation using Visual C++ 8.0
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] SVN Location
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Mateusz Loskot
- [postgis-devel] Compilation using Visual C++ 8.0
Mateusz Loskot
- [postgis-devel] [Fwd: [gdal-dev] WKT Raster driver in GSoC 2009]
Mateusz Loskot
- [postgis-devel] [WKT Raster] Still using old SVN
Mateusz Loskot
- [postgis-devel] [WKT Raster] Still using old SVN
Mateusz Loskot
- [postgis-devel] [WKT Raster] Still using old SVN
Mateusz Loskot
- [postgis-devel] [WKT Raster] Still using old SVN
Mateusz Loskot
- [postgis-devel] Re: PostGIS infrastructure
Jeff Lounsbury
- [postgis-devel] Re: PostGIS infrastructure
Jeff Lounsbury
- [postgis-devel] WKTRaster autobuilds
Kevin Neufeld
- [postgis-devel] Remove PDF from Hudson build?
Kevin Neufeld
- [postgis-devel] New Doco
Kevin Neufeld
- [postgis-devel] SVN is [temporarily] broken
Kevin Neufeld
- [postgis-devel] Re: PostGIS infrastructure
Kevin Neufeld
- [postgis-devel] Re: PostGIS infrastructure
Kevin Neufeld
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
Kevin Neufeld
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
Kevin Neufeld
- [postgis-devel] WKT Raster: Why havingtocompilePostgreSQL&PostGIS first?
Obe, Regina
- [postgis-devel] WKT Raster: Why having tocompilePostgreSQL&PostGISfirst?
Obe, Regina
- [postgis-devel] WKT Raster:Why having tocompilePostgreSQL&PostGISfirst?
Obe, Regina
- [postgis-devel] WKTRaster:Why having tocompilePostgreSQL&PostGISfirst?
Obe, Regina
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Obe, Regina
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Obe, Regina
- [postgis-devel] WKT Raster: Bug tracking
Obe, Regina
- [postgis-devel] WKT Raster: Bug tracking
Obe, Regina
- [postgis-devel] WKT Raster: Bug tracking
Obe, Regina
- [postgis-devel] More dump comments
Obe, Regina
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backendwith large geometries.
Obe, Regina
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DBbackendwith large geometries.
Obe, Regina
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashedDBbackendwith large geometries.
Obe, Regina
- [postgis-devel] Code sprint notes
Obe, Regina
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashedDBbackendwith large geometries.
Obe, Regina
- [postgis-devel] WKTRaster autobuilds
Obe, Regina
- [postgis-devel] Issue 119 in postgis: ST_AsSVGcrashedDBbackendwith large geometries.
Obe, Regina
- [postgis-devel] Issue 119 in postgis:ST_AsSVGcrashedDBbackendwith large geometries.
Obe, Regina
- [postgis-devel] More dump comments
Obe, Regina
- [postgis-devel] Remove PDF from Hudson build?
Obe, Regina
- [postgis-devel] Remove PDF from Hudson build?
Obe, Regina
- [postgis-devel] New Doco
Obe, Regina
- [postgis-devel] New Doco
Obe, Regina
- [postgis-devel] Compilation using Visual C++ 8.0
Obe, Regina
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
Courtin Olivier
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
Courtin Olivier
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backendwith large geometries.
Courtin Olivier
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DBbackendwith large geometries.
Courtin Olivier
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashedDBbackendwith large geometries.
Courtin Olivier
- [postgis-devel] Issue 119 in postgis: ST_AsSVGcrashedDBbackendwith large geometries.
Courtin Olivier
- [postgis-devel] gml, geojson, svg
Courtin Olivier
- [postgis-devel] run_test and PostgreSQL user
Courtin Olivier
- [postgis-devel] run_test and PostgreSQL user
Courtin Olivier
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
Courtin Olivier
- [postgis-devel] [PostGIS] #346: PostGIS Site down?
PostGIS
- [postgis-devel] [PostGIS] #346: PostGIS Site down?
PostGIS
- [postgis-devel] [PostGIS] #346: PostGIS Site down?
PostGIS
- [postgis-devel] WKT Raster: Why having to compile PostgreSQL&PostGIS first?
Pierre Racine
- [postgis-devel] WKT Raster: Why having tocompilePostgreSQL&PostGIS first?
Pierre Racine
- [postgis-devel] WKT Raster: Why havingtocompilePostgreSQL&PostGISfirst?
Pierre Racine
- [postgis-devel] WKT Raster: WhyhavingtocompilePostgreSQL&PostGISfirst?
Pierre Racine
- [postgis-devel] WKT Raster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Pierre Racine
- [postgis-devel] WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Pierre Racine
- [postgis-devel]WKTRaster:WhyhavingtocompilePostgreSQL&PostGISfirst?
Pierre Racine
- [postgis-devel] WKT Raster: GDAL or World file upper left coordinates
Pierre Racine
- [postgis-devel] WKT Raster: GDAL or World file upper leftcoordinates
Pierre Racine
- [postgis-devel] WKT Raster: GDAL or World fileupper leftcoordinates
Pierre Racine
- [postgis-devel] WKT Raster: GDAL orWorld fileupper leftcoordinates
Pierre Racine
- [postgis-devel] WKT Raster: Bug tracking
Pierre Racine
- [postgis-devel] WKT Raster: Bug tracking
Pierre Racine
- [postgis-devel] WKTRaster autobuilds
Pierre Racine
- [postgis-devel] RE: WKTRaster news from the Toronto Code Sprint?
Pierre Racine
- [postgis-devel] about get/set wktraster sql funtion name convention
Pierre Racine
- [postgis-devel] Re: PostGIS infrastructure
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking restrictions
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Pierre Racine
- [postgis-devel] New Doco
Paul Ramsey
- [postgis-devel] Re: PostGIS infrastructure
Paul Ramsey
- [postgis-devel] Re: PostGIS infrastructure
Paul Ramsey
- [postgis-devel] SVN trunk libxml2 detection is broken
Paul Ramsey
- [postgis-devel] Re: PostGIS infrastructure
Paul Ramsey
- [postgis-devel] Re: PostGIS infrastructure
Paul Ramsey
- [postgis-devel] Re: PostGIS infrastructure
Paul Ramsey
- [postgis-devel] Re: PostGIS infrastructure
Paul Ramsey
- [postgis-devel] Q3C
Paul Ramsey
- [postgis-devel] Re: Q3C
Paul Ramsey
- [postgis-devel] Re: Q3C
Paul Ramsey
- [postgis-devel] Re: Q3C
Paul Ramsey
- [postgis-devel] gml, geojson, svg
Paul Ramsey
- [postgis-devel] gml, geojson, svg
Paul Ramsey
- [postgis-devel] gml, geojson, svg
Paul Ramsey
- [postgis-devel] GEOS Warnings
Paul Ramsey
- [postgis-devel] Slouching Towards 1.4
Paul Ramsey
- [postgis-devel] Function Sigs
Paul Ramsey
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
Paul Ramsey
- [postgis-devel] SVN Location
Paul Ramsey
- [postgis-devel] User IDs @ OSGeo
Paul Ramsey
- [postgis-devel] Incubation
Paul Ramsey
- [postgis-devel] Re: User IDs @ OSGeo
Paul Ramsey
- [postgis-devel] Re: User IDs @ OSGeo
Paul Ramsey
- [postgis-devel] Slouching Towards 1.4
Paul Ramsey
- [postgis-devel] Re: Incubation
Paul Ramsey
- [postgis-devel] Under the Heat Lamp
Paul Ramsey
- [postgis-devel] Re: PostGIS infrastructure
Christopher Schmidt
- [postgis-devel] WKT Raster: GDAL or World file upper left coordinates
Frank Warmerdam
- [postgis-devel] WKT Raster: Bug tracking
Frank Warmerdam
- [postgis-devel] RASTER_COLUMNS Table Spec
Frank Warmerdam
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Frank Warmerdam
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Frank Warmerdam
- [postgis-devel] RE: WKTRaster news from the Toronto CodeSprint?
Frank Warmerdam
- [postgis-devel] [WKT Raster] Type of extent column of RASTER_COLUMNS
Frank Warmerdam
- [postgis-devel] Re: PostGIS infrastructure
Frank Warmerdam
- [postgis-devel] Re: PostGIS infrastructure
Frank Warmerdam
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Frank Warmerdam
- [postgis-devel] [WKT Raster] Regular blocking in gdal2wktraster.py
Frank Warmerdam
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 122 in postgis: ST_SnapToGrid gives 13 when fed circular string
codesite-noreply at google.com
- [postgis-devel] Issue 86 in postgis: ST_LineToCurve produces invalid curves
codesite-noreply at google.com
- [postgis-devel] Issue 109 in postgis: Some operators not supported for Circular
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 122 in postgis: ST_SnapToGrid gives 13 when fed circular string
codesite-noreply at google.com
- [postgis-devel] Issue 116 in postgis: Hex string representing POLYGON EMPTY crashes postmaster
codesite-noreply at google.com
- [postgis-devel] Issue 112 in postgis: ST_CurveToLine sometimes crashes server
codesite-noreply at google.com
- [postgis-devel] Issue 93 in postgis: ST_Extent() and ST_Estimated_Extent() return BOX2DFLOAT4s
codesite-noreply at google.com
- [postgis-devel] Issue 87 in postgis: Probe_Geometry_Columns does not parse an SRID of -1
codesite-noreply at google.com
- [postgis-devel] Issue 110 in postgis: shp2pgsql new option to not batch commit
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 110 in postgis: shp2pgsql new option to not batch commit
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 123 in postgis: SQLite output format support for shp2pgsql
codesite-noreply at google.com
- [postgis-devel] Issue 123 in postgis: SQLite output format support for shp2pgsql
codesite-noreply at google.com
- [postgis-devel] Issue 91 in postgis: "makefile check" Shows check failed of sql-mm-circularstring in PostGIS
codesite-noreply at google.com
- [postgis-devel] Issue 105 in postgis: pgsql2shp seems to produce incorrect dbase files, problems importing into Gnumeric
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 124 in postgis: Missing CompoundCurve parser test when disjoint segments
codesite-noreply at google.com
- [postgis-devel] Issue 103 in postgis: Box3D always gets cast to 2D geometry
codesite-noreply at google.com
- [postgis-devel] Issue 96 in postgis: ST_Multi on the new SQL-MM curve types should return a MULTICURVE
codesite-noreply at google.com
- [postgis-devel] Issue 87 in postgis: Probe_Geometry_Columns does not parse an SRID of -1
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 112 in postgis: ST_CurveToLine sometimes crashes server
codesite-noreply at google.com
- [postgis-devel] Issue 108 in postgis: ST_LineToCurve Crashing
codesite-noreply at google.com
- [postgis-devel] Issue 125 in postgis: postgres.h header isnot included first
codesite-noreply at google.com
- [postgis-devel] Issue 125 in postgis: postgres.h header isnot included first
codesite-noreply at google.com
- [postgis-devel] Issue 124 in postgis: Missing CompoundCurve parser test when disjoint segments
codesite-noreply at google.com
- [postgis-devel] Issue 126 in postgis: Don't include private PROJ.4 header projects.h
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 87 in postgis: Probe_Geometry_Columns does not parse an SRID of -1
codesite-noreply at google.com
- [postgis-devel] Issue 87 in postgis: Probe_Geometry_Columns does not parse an SRID of -1
codesite-noreply at google.com
- [postgis-devel] Issue 127 in postgis: Finish 1.4 Documentation
codesite-noreply at google.com
- [postgis-devel] Issue 127 in postgis: Finish 1.4 Documentation
codesite-noreply at google.com
- [postgis-devel] Issue 128 in postgis: Test 1.4 on Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 128 in postgis: Test 1.4 on Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 129 in postgis: Test 1.4 against Windows
codesite-noreply at google.com
- [postgis-devel] Issue 130 in postgis: Fix BdPoly Regression Error
codesite-noreply at google.com
- [postgis-devel] Issue 131 in postgis: Remove GEOS 2.2 support and test for GEOS >= 3.0
codesite-noreply at google.com
- [postgis-devel] Issue 132 in postgis: Make check should run CUnit
codesite-noreply at google.com
- [postgis-devel] Issue 133 in postgis: Run astyle on full code base
codesite-noreply at google.com
- [postgis-devel] Issue 124 in postgis: Missing CompoundCurve parser test when disjoint segments
codesite-noreply at google.com
- [postgis-devel] Issue 130 in postgis: Fix BdPoly Regression Error
codesite-noreply at google.com
- [postgis-devel] Issue 116 in postgis: Hex string representing POLYGON EMPTY crashes postmaster
codesite-noreply at google.com
- [postgis-devel] Issue 105 in postgis: pgsql2shp seems to produce incorrect dbase files, problems importing into Gnumeric
codesite-noreply at google.com
- [postgis-devel] Issue 96 in postgis: ST_Multi on the new SQL-MM curve types should return a MULTICURVE
codesite-noreply at google.com
- [postgis-devel] Issue 99 in postgis: shp2pgsql 'Only import DBF' error.
codesite-noreply at google.com
- [postgis-devel] Issue 112 in postgis: ST_CurveToLine sometimes crashes server
codesite-noreply at google.com
- [postgis-devel] Issue 109 in postgis: Some operators not supported for Circular
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 89 in postgis: transform() grid-shift 2nd chance logic defective
codesite-noreply at google.com
- [postgis-devel] Issue 89 in postgis: transform() grid-shift 2nd chance logic defective
codesite-noreply at google.com
- [postgis-devel] Issue 134 in postgis: Release Notes
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 89 in postgis: transform() grid-shift 2nd chance logic defective
codesite-noreply at google.com
- [postgis-devel] Issue 126 in postgis: Don't include private PROJ.4 header projects.h
codesite-noreply at google.com
- [postgis-devel] Issue 87 in postgis: Probe_Geometry_Columns does not parse an SRID of -1
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 125 in postgis: postgres.h header isnot included first
codesite-noreply at google.com
- [postgis-devel] Issue 131 in postgis: Remove GEOS 2.2 support and test for GEOS >= 3.0
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 132 in postgis: Make check should run CUnit
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 76 in postgis: ST_DumpPoints - I think we said we would add to TODO
codesite-noreply at google.com
- [postgis-devel] Issue 125 in postgis: postgres.h header isnot included first
codesite-noreply at google.com
- [postgis-devel] Issue 126 in postgis: Don't include private PROJ.4 header projects.h
codesite-noreply at google.com
- [postgis-devel] Issue 126 in postgis: Don't include private PROJ.4 header projects.h
codesite-noreply at google.com
- [postgis-devel] Issue 123 in postgis: SQLite output format support for shp2pgsql
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 135 in postgis: Upgrade geocoder to use the new tiger 2008 files
codesite-noreply at google.com
- [postgis-devel] Issue 135 in postgis: Upgrade geocoder to use the new tiger 2008 files
codesite-noreply at google.com
- [postgis-devel] Issue 136 in postgis: Remove deprecated definitions from postgis.sql
codesite-noreply at google.com
- [postgis-devel] Issue 136 in postgis: Remove deprecated definitions from postgis.sql
codesite-noreply at google.com
- [postgis-devel] Issue 136 in postgis: Remove deprecated definitions from postgis.sql
codesite-noreply at google.com
- [postgis-devel] Issue 136 in postgis: Remove deprecated definitions from postgis.sql
codesite-noreply at google.com
- [postgis-devel] Issue 137 in postgis: st_distance, shortestline (, st_maxdistance)
codesite-noreply at google.com
- [postgis-devel] Issue 128 in postgis: Test 1.4 on Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 128 in postgis: Test 1.4 on Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 128 in postgis: Test 1.4 on Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 128 in postgis: Test 1.4 on Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 138 in postgis: Build against 8.1 fails in Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 138 in postgis: Build against 8.1 fails in Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 128 in postgis: Test 1.4 on Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 139 in postgis: Default selectivity returned when geometry used for restricted join comes from another table, but accurate when from WKT
codesite-noreply at google.com
- [postgis-devel] Issue 139 in postgis: Default selectivity returned when geometry used for restricted join comes from another table, but accurate when from WKT
codesite-noreply at google.com
- [postgis-devel] Issue 128 in postgis: Test 1.4 on Solaris
codesite-noreply at google.com
- [postgis-devel] Issue 140 in postgis: Patch for geometry_column without S at the end typo
codesite-noreply at google.com
- [postgis-devel] Issue 140 in postgis: Patch for geometry_column without S at the end typo
codesite-noreply at google.com
- [postgis-devel] Issue 127 in postgis: Finish 1.4 Documentation
codesite-noreply at google.com
- [postgis-devel] Issue 87 in postgis: Probe_Geometry_Columns does not parse an SRID of -1
codesite-noreply at google.com
- [postgis-devel] Issue 95 in postgis: PostGIS 1.4 documentation update
codesite-noreply at google.com
- [postgis-devel] Issue 111 in postgis: Enhancement request - Minimum Bounding Circle for PostGIS
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 121 in postgis: update tiger_geocoder to run in PostgreSQL 8.3 (patch attached)
codesite-noreply at google.com
- [postgis-devel] Issue 82 in postgis: Bug in bug tracker
codesite-noreply at google.com
- [postgis-devel] Issue 63 in postgis: ST_Max_Distance is not yet implemented?
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 141 in postgis: AsGML multipoint issue on MacOS X
codesite-noreply at google.com
- [postgis-devel] Issue 141 in postgis: AsGML multipoint issue on MacOS X
codesite-noreply at google.com
- [postgis-devel] Issue 141 in postgis: AsGML multipoint issue on MacOS X
codesite-noreply at google.com
- [postgis-devel] Issue 112 in postgis: ST_CurveToLine sometimes crashes server
codesite-noreply at google.com
- [postgis-devel] Issue 95 in postgis: PostGIS 1.4 documentation update
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 95 in postgis: PostGIS 1.4 documentation update
codesite-noreply at google.com
- [postgis-devel] Issue 95 in postgis: PostGIS 1.4 documentation update
codesite-noreply at google.com
- [postgis-devel] Issue 95 in postgis: PostGIS 1.4 documentation update
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 141 in postgis: AsGML multipoint issue on MacOS X
codesite-noreply at google.com
- [postgis-devel] Issue 119 in postgis: ST_AsSVG crashed DB backend with large geometries.
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 137 in postgis: st_distance, shortestline (, st_maxdistance)
codesite-noreply at google.com
- [postgis-devel] Issue 63 in postgis: ST_Max_Distance is not yet implemented?
codesite-noreply at google.com
- [postgis-devel] Issue 137 in postgis: st_distance, shortestline (, st_maxdistance)
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 143 in postgis: regress_ogc failed for trunk on Linux
codesite-noreply at google.com
- [postgis-devel] Issue 142 in postgis: 1.4 snapshot build is broken
codesite-noreply at google.com
- [postgis-devel] Issue 143 in postgis: regress_ogc failed for trunk on Linux
codesite-noreply at google.com
- [postgis-devel] Issue 137 in postgis: st_distance, shortestline (, st_maxdistance)
codesite-noreply at google.com
- [postgis-devel] Issue 137 in postgis: st_distance, shortestline (, st_maxdistance)
codesite-noreply at google.com
- [postgis-devel] Issue 137 in postgis: st_distance, shortestline (, st_maxdistance)
codesite-noreply at google.com
- [postgis-devel] Issue 144 in postgis: Hard/soft upgrade need to be tested
codesite-noreply at google.com
- [postgis-devel] Issue 144 in postgis: Hard/soft upgrade need to be tested
codesite-noreply at google.com
- [postgis-devel] Issue 137 in postgis: st_distance, shortestline (, st_maxdistance)
codesite-noreply at google.com
- [postgis-devel] Issue 137 in postgis: st_distance, shortestline (, st_maxdistance)
codesite-noreply at google.com
- [postgis-devel] Issue 145 in postgis: POLYGON( EMPTY) is unparseable
codesite-noreply at google.com
- [postgis-devel] Issue 93 in postgis: ST_Extent() and ST_Estimated_Extent() return BOX2DFLOAT4s
codesite-noreply at google.com
- [postgis-devel] Issue 93 in postgis: ST_Extent() and ST_Estimated_Extent() return BOX2DFLOAT4s
codesite-noreply at google.com
- [postgis-devel] Issue 129 in postgis: Test 1.4 against Windows
codesite-noreply at google.com
- [postgis-devel] Issue 93 in postgis: ST_Extent() and ST_Estimated_Extent() return BOX2DFLOAT4s
codesite-noreply at google.com
- [postgis-devel] Issue 93 in postgis: ST_Extent() and ST_Estimated_Extent() return BOX2DFLOAT4s
codesite-noreply at google.com
- [postgis-devel] Issue 93 in postgis: ST_Extent() and ST_Estimated_Extent() return BOX2DFLOAT4s
codesite-noreply at google.com
- [postgis-devel] 40% faster st_distance and returning measurepoints :-)
nicklas.aven at jordogskog.no
- [postgis-devel] RE: 40% faster st_distance and returning measurepoints :-)
nicklas.aven at jordogskog.no
- [postgis-devel] RE: 40% faster st_distance and returning measurepoints :-)
nicklas.aven at jordogskog.no
- [postgis-devel] RE: 40% faster st_distance and returning measurepoints :-)
nicklas.aven at jordogskog.no
- [postgis-devel] questions about wktraster
strk
- [postgis-devel] questions about wktraster
strk
- [postgis-devel] WKTRaster: errors building WKTRaster on Ubuntu 8.10
strk
- [postgis-devel] configure error while building WKTRaster on Ubuntu8.10
strk
- [postgis-devel] WKT Raster: Why havingtocompilePostgreSQL&PostGISfirst?
strk
- [postgis-devel] WKTRaster autobuilds
strk
- PostGIS infrastructure (was: Re: [postgis-devel] SVN is [temporarily] broken)
strk
- [postgis-devel] [WKT Raster] Requirement of PostgreSQL
strk
- [postgis-devel] questions about wktraster
xie_jiong
- [postgis-devel] questions about wktraster
xie_jiong
- [postgis-devel] a question about wktraster
xie_jiong
- [postgis-devel] about get/set wktraster sql funtion name convention
xie_jiong
Last message date:
Tue Mar 31 13:40:07 PDT 2009
Archived on: Fri Nov 10 09:25:59 PST 2017
This archive was generated by
Pipermail 0.09 (Mailman edition).