October 2012 Archives by author

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

Starting: Mon Oct 1 00:50:41 PDT 2012
Ending: Wed Oct 31 23:21:52 PDT 2012
Messages: 441

• [postgis-devel] Fwd: ST_DumpPoints in C   David William Bitner
• [postgis-devel] Can we stop using .c prefix for SQL files ?   Mark Cave-Ayland
• [postgis-devel] pgRouting Windows campaign   Paragon Corporation
• [postgis-devel] 2.1 To Do   Paragon Corporation
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   Paragon Corporation
• [postgis-devel] Can we stop using .c prefix for SQL files ?   Paragon Corporation
• [postgis-devel] Transifex translation   Paolo Corti
• [postgis-devel] Transifex translation   Paolo Corti
• [postgis-devel] linkage against libpq.so   Jeff Janes
• [postgis-devel] linkage against libpq.so (Sandro Santilli)   Jeff Janes
• [postgis-devel] linkage against libpq.so (Sandro Santilli)   Jeff Janes
• [postgis-devel] Another devel test   Mateusz Loskot
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   Bborie Park
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   Bborie Park
• [postgis-devel] [PostGIS] #2006: st_area returns NaN   PostGIS
• [postgis-devel] [PostGIS] #2006: st_area returns NaN   PostGIS
• [postgis-devel] [PostGIS] #2006: st_area returns NaN   PostGIS
• [postgis-devel] [PostGIS] #1912: ST_Estimated_Extent() does not handle table name with blank   PostGIS
• [postgis-devel] [PostGIS] #1877: windows stack builder handle passwords with special characters   PostGIS
• [postgis-devel] [PostGIS] #510: ST_Estimated_Extent doesn't work with views   PostGIS
• [postgis-devel] [PostGIS] #1745: [postgis-users] make generates incorrect PERL variable value on v1.5.2 from Bill Teluk March 9, 2011   PostGIS
• [postgis-devel] [PostGIS] #1990: Inconsistent X/Y coordinates swapping in GML   PostGIS
• [postgis-devel] [PostGIS] #1928: st_geomfromgml multipoint issue   PostGIS
• [postgis-devel] [PostGIS] #1984: geography_btree.c: array subscript is above array bounds [-Warray-bounds]   PostGIS
• [postgis-devel] [PostGIS] #1928: st_geomfromgml multipoint issue   PostGIS
• [postgis-devel] [PostGIS] #1928: st_geomfromgml multipoint issue   PostGIS
• [postgis-devel] [PostGIS] #1928: st_geomfromgml multipoint issue   PostGIS
• [postgis-devel] [PostGIS] #1364: [raster] Make ST_Union a c-implementation   PostGIS
• [postgis-devel] [PostGIS] #1364: [raster] Make ST_Union a c-implementation   PostGIS
• [postgis-devel] [PostGIS] #1364: [raster] Make ST_Union a c-implementation   PostGIS
• [postgis-devel] [PostGIS] #1364: [raster] Make ST_Union a c-implementation   PostGIS
• [postgis-devel] [PostGIS] #1364: [raster] Make ST_Union a c-implementation   PostGIS
• [postgis-devel] [PostGIS] #1364: [raster] Make ST_Union a c-implementation   PostGIS
• [postgis-devel] [PostGIS] #1364: [raster] Make ST_Union a c-implementation   PostGIS
• [postgis-devel] [PostGIS] #2024: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy (was: ST_Union is buggy)   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2021: [raster] Multi-band support for ST_Union   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2026: [raster] Add missing ST_Union(raster) variant   PostGIS
• [postgis-devel] [PostGIS] #2026: [raster] Add missing ST_Union(raster) variant   PostGIS
• [postgis-devel] [PostGIS] #2017: Assign Winnie or Debbie to build doxygen docs   PostGIS
• [postgis-devel] [PostGIS] #2027: can't softupgrade from old 2.1 to latest 2.1   PostGIS
• [postgis-devel] [PostGIS] #2027: can't softupgrade from old 2.1 to latest 2.1   PostGIS
• [postgis-devel] [PostGIS] #2027: can't softupgrade from old 2.1 to latest 2.1   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2025: side location conflict at topogeo_AddLineString() of separate edges   PostGIS
• [postgis-devel] [PostGIS] #2028: ST_Multi(<triangle>) does not make a TIN   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2029: PostgreSQL geometric to PostGIS type casts missing in upgrade script   PostGIS
• [postgis-devel] [PostGIS] #2026: [raster] Add missing ST_Union(raster) variant   PostGIS
• [postgis-devel] [PostGIS] #2026: [raster] Add missing ST_Union(raster) variant   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2031: ST_AsSVG spurios space before tag close   PostGIS
• [postgis-devel] [PostGIS] #1659: [raster] ST_Union raster out of memory then kicks the bucket on windows 64bit   PostGIS
• [postgis-devel] [PostGIS] #2031: ST_AsSVG spurios space before tag close   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #1956: ERROR: syntax error at or near "DO"   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #1841: ST_Distance on PostGIS 2.0 is prohibitively slow   PostGIS
• [postgis-devel] [PostGIS] #1393: Evaluate use of GUC for postgis   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2029: PostgreSQL geometric to PostGIS type casts missing in extension upgrade script (was: PostgreSQL geometric to PostGIS type casts missing in upgrade script)   PostGIS
• [postgis-devel] [PostGIS] #310: port ST_DumpPoints() to C   PostGIS
• [postgis-devel] [PostGIS] #1898: ST_DelaunayTriangles option to output as TIN   PostGIS
• [postgis-devel] [PostGIS] #1896: Make create postgis and postgis_topology unpackaged script automated   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2032: Higher dimension support for ST_ClosestPoint   PostGIS
• [postgis-devel] [PostGIS] #2033: 2.5D topology: Column has Z dimension but geometry does not   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2024: raster: ST_Union is buggy   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2032: Higher dimension support for ST_ClosestPoint   PostGIS
• [postgis-devel] [PostGIS] #2033: 2.5D topology: Column has Z dimension but geometry does not   PostGIS
• [postgis-devel] [PostGIS] #2032: Higher dimension support for ST_ClosestPoint   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2032: Higher dimension support for ST_ClosestPoint   PostGIS
• [postgis-devel] [PostGIS] #2033: 2.5D topology: Column has Z dimension but geometry does not   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2017: Assign Winnie or Debbie to build doxygen docs   PostGIS
• [postgis-devel] [PostGIS] #1833: full record json output in 9.2 with valid geojson output   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2035: Strange behavior when using left (<<) and right (>>) operators.   PostGIS
• [postgis-devel] [PostGIS] #2035: Strange behavior when using left (<<) and right (>>) operators.   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   PostGIS
• [postgis-devel] [PostGIS] #1627: package tiger_geocoder as a PostgreSQL extension   PostGIS
• [postgis-devel] [PostGIS] #2018: Distance calculation support for arc features (circstring, compoundcurve, curvepolygon)   PostGIS
• [postgis-devel] [PostGIS] #2036: Windows installer stop creating template_postgis for 9.1+   PostGIS
• [postgis-devel] [PostGIS] #2036: Windows installer stop creating template_postgis for 9.1+   PostGIS
• [postgis-devel] [PostGIS] #1228: [raster] Add a ST_SetValues(raster, ARRAY[values], index DEFAULT 1) variant   PostGIS
• [postgis-devel] [PostGIS] #2037: raster: Seem to be a lot of new raster functions not flagged as such   PostGIS
• [postgis-devel] [PostGIS] #2037: raster: Seem to be a lot of new raster functions not flagged as such   PostGIS
• [postgis-devel] [PostGIS] #2037: raster: Seem to be a lot of new raster functions not flagged as such   PostGIS
• [postgis-devel] [PostGIS] #2030: [raster] n-raster ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #2037: raster: Seem to be a lot of new raster functions not flagged as such   PostGIS
• [postgis-devel] [PostGIS] #2037: raster: Seem to be a lot of new raster functions not flagged as such   PostGIS
• [postgis-devel] [PostGIS] #2037: raster: Seem to be a lot of new raster functions not flagged as such   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #1998: Crash of topogeo_AddPolygon() with "ERROR: query string argument of EXECUTE is null"   PostGIS
• [postgis-devel] [PostGIS] #1998: Crash of topogeo_AddPolygon() with "ERROR: query string argument of EXECUTE is null"   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2039: ST_Area(geography) returning wrong answer   PostGIS
• [postgis-devel] [PostGIS] #2006: st_area returns NaN   PostGIS
• [postgis-devel] [PostGIS] #2039: ST_Area(geography) returning wrong answer   PostGIS
• [postgis-devel] [PostGIS] #2006: st_area returns NaN   PostGIS
• [postgis-devel] [PostGIS] #2040: 2.1 doc build appears to be broken   PostGIS
• [postgis-devel] [PostGIS] #2040: 2.1 doc build appears to be broken   PostGIS
• [postgis-devel] [PostGIS] #2040: 2.1 doc build appears to be broken   PostGIS
• [postgis-devel] [PostGIS] #2041: installation.xml does not follow the DTD   PostGIS
• [postgis-devel] [PostGIS] #2041: installation.xml does not follow the DTD   PostGIS
• [postgis-devel] [PostGIS] #2041: installation.xml does not follow the DTD   PostGIS
• [postgis-devel] [PostGIS] #2041: installation.xml does not follow the DTD   PostGIS
• [postgis-devel] [PostGIS] #2042: measures.c: 'pt_in_arc_A' may be used uninitialized   PostGIS
• [postgis-devel] [PostGIS] #2042: measures.c: 'pt_in_arc_A' may be used uninitialized   PostGIS
• [postgis-devel] [PostGIS] #2040: lwgeodetic.c:1821:1: error: conflicting types for 'ptarray_area_sphere' (was: 2.1 doc build appears to be broken)   PostGIS
• [postgis-devel] [PostGIS] #2043: test_spheroid_area fails   PostGIS
• [postgis-devel] [PostGIS] #2040: lwgeodetic.c:1821:1: error: conflicting types for 'ptarray_area_sphere'   PostGIS
• [postgis-devel] [PostGIS] #2044: lw_arc_length: warning: variable 'a2' set but not used   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2043: test_spheroid_area fails   PostGIS
• [postgis-devel] [PostGIS] #2040: lwgeodetic.c:1821:1: error: conflicting types for 'ptarray_area_sphere'   PostGIS
• [postgis-devel] [PostGIS] #2040: lwgeodetic.c:1821:1: error: conflicting types for 'ptarray_area_sphere'   PostGIS
• [postgis-devel] [PostGIS] #2045: pgsql2shp should not require temp table creation privs when dumping a query   PostGIS
• [postgis-devel] [PostGIS] #2039: ST_Area(geography) returning wrong answer   PostGIS
• [postgis-devel] [PostGIS] #2043: test_spheroid_area fails   PostGIS
• [postgis-devel] [PostGIS] #2043: test_spheroid_area fails   PostGIS
• [postgis-devel] [PostGIS] #2038: Exception of topogeo_AddLineString() of a line string with a part colinear with an existing one.   PostGIS
• [postgis-devel] [PostGIS] #2046: raster: Getting compile errors on postgresql 9.0 build caused by raster   PostGIS
• [postgis-devel] [PostGIS] #2046: raster: Getting compile errors on postgresql 9.0 build caused by raster   PostGIS
• [postgis-devel] [PostGIS] #2043: test_spheroid_area fails   PostGIS
• [postgis-devel] [PostGIS] #2047: debbie not registering error on regress compile failure   PostGIS
• [postgis-devel] [PostGIS] #2047: debbie not registering error on regress compile failure   PostGIS
• [postgis-devel] [PostGIS] #2046: raster: Getting compile errors on postgresql 9.0 build caused by raster   PostGIS
• [postgis-devel] [PostGIS] #2046: raster: Getting compile errors on postgresql 9.0 build caused by raster   PostGIS
• [postgis-devel] [PostGIS] #2048: Regress failure for 9.0   PostGIS
• [postgis-devel] [PostGIS] #2048: Regress failure for 9.0   PostGIS
• [postgis-devel] [PostGIS] #2046: raster: Getting compile errors on postgresql 9.0 build caused by raster   PostGIS
• [postgis-devel] [PostGIS] #2048: Regress failure for 9.0   PostGIS
• [postgis-devel] [PostGIS] #2048: Regress failure for 9.0   PostGIS
• [postgis-devel] [PostGIS] #2048: Regress failure for 9.0   PostGIS
• [postgis-devel] [PostGIS] #2049: populate_geometry_columns: ERROR: cannot alter type of a column used in a trigger definition   PostGIS
• [postgis-devel] [PostGIS] #2049: populate_geometry_columns: ERROR: cannot alter type of a column used in a trigger definition   PostGIS
• [postgis-devel] [PostGIS] #2049: populate_geometry_columns: ERROR: cannot alter type of a column used in a trigger definition   PostGIS
• [postgis-devel] [PostGIS] #2049: populate_geometry_columns: ERROR: cannot alter type of a column used in a trigger definition   PostGIS
• [postgis-devel] [PostGIS] #2049: populate_geometry_columns: ERROR: cannot alter type of a column used in a trigger definition   PostGIS
• [postgis-devel] [PostGIS] #2049: populate_geometry_columns: ERROR: cannot alter type of a column used in a trigger definition   PostGIS
• [postgis-devel] [PostGIS] #2049: populate_geometry_columns: ERROR: cannot alter type of a column used in a trigger definition   PostGIS
• [postgis-devel] [PostGIS] #2048: Regress failure for 9.0   PostGIS
• [postgis-devel] [PostGIS] #2011: [raster] ST_Values (was: [raster] ST_DumpValues)   PostGIS
• [postgis-devel] [PostGIS] #1980: Allow overriding mathml location (was: Winnie hiccuping on mathml doc html)   PostGIS
• [postgis-devel] [PostGIS] #2050: Unable to add constraint: 'extent'. Skipping   PostGIS
• [postgis-devel] [PostGIS] #2050: Unable to add constraint: 'extent'. Skipping   PostGIS
• [postgis-devel] [PostGIS] #2050: Unable to add constraint: 'extent'. Skipping   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2052: buffer overflow in lwgeom_to_geojson when passing high precision   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2054: move trim_trailing_zeros out of liblwgeom.h   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2051: ST_AsGeoJSON printing too many digits   PostGIS
• [postgis-devel] [PostGIS] #2050: Unable to add constraint: 'extent'. Skipping   PostGIS
• [postgis-devel] [PostGIS] #2054: move trim_trailing_zeros out of liblwgeom.h   PostGIS
• [postgis-devel] [PostGIS] #2054: move trim_trailing_zeros out of liblwgeom.h   PostGIS
• [postgis-devel] [PostGIS] #2050: Unable to add constraint: 'extent'. Skipping   PostGIS
• [postgis-devel] [PostGIS] #2050: Unable to add constraint: 'extent'. Skipping   PostGIS
• [postgis-devel] [PostGIS] #2011: [raster] ST_DumpValues (was: [raster] ST_Values)   PostGIS
• [postgis-devel] [PostGIS] #2055: Intersection with a result from Intersection fails   PostGIS
• [postgis-devel] [PostGIS] #2056: [raster] ST_SetValue() for point does NOT check SRID   PostGIS
• [postgis-devel] [PostGIS] #2056: [raster] ST_SetValue() for point does NOT check SRID   PostGIS
• [postgis-devel] [PostGIS] #2056: [raster] ST_SetValue() for point does NOT check SRID   PostGIS
• [postgis-devel] [PostGIS] #595: [raster] Add a series of ST_SetValues functions   PostGIS
• [postgis-devel] [PostGIS] #595: [raster] Add a series of ST_SetValues functions   PostGIS
• [postgis-devel] [PostGIS] #1678: [raster] GDAL_DATA dependency   PostGIS
• [postgis-devel] [PostGIS] #1216: [raster] Make raster_columns a view (was: [raster] Make raster_column a view)   PostGIS
• [postgis-devel] [PostGIS] #1319: [raster] Make raster_columns a constraint-based view, replace AddRasterColumn with AddRasterConstraints and expand # of constraints on raster columns   PostGIS
• [postgis-devel] [PostGIS] #1216: [raster] Make raster_columns a view   PostGIS
• [postgis-devel] [PostGIS] #2057: Raster build ignores pg_config info   PostGIS
• [postgis-devel] [PostGIS] #2057: Raster build ignores pg_config info   PostGIS
• [postgis-devel] [PostGIS] #2057: Raster build ignores pg_config info   PostGIS
• [postgis-devel] [PostGIS] #595: [raster] Add a series of ST_SetValues functions   PostGIS
• [postgis-devel] [PostGIS] #595: [raster] Add a series of ST_SetValues functions   PostGIS
• [postgis-devel] [PostGIS] #2057: Raster build ignores pg_config info   PostGIS
• [postgis-devel] [PostGIS] #2057: Raster build ignores pg_config info   PostGIS
• [postgis-devel] [PostGIS] #2057: Raster build ignores pg_config info   PostGIS
• [postgis-devel] [PostGIS] #2058: [raster] Add a ST_SetValues variant copying values from another raster band   PostGIS
• [postgis-devel] [PostGIS] #2059: Hallie the PostGIS expert bot   PostGIS
• [postgis-devel] [PostGIS] #1614: More normalizer tricks   PostGIS
• [postgis-devel] [PostGIS] #1669: Missing street type w/ Internal component makes geocode() so SLOOOW   PostGIS
• [postgis-devel] [PostGIS] #1930: Missing fields from tabblock table in tiger2011 census loader   PostGIS
• [postgis-devel] [PostGIS] #1846: change missing_indexes_generate_script to use spgist if available   PostGIS
• [postgis-devel] [PostGIS] #1622: Geocoder gets different result when using limit parameter   PostGIS
• [postgis-devel] [PostGIS] #1604: normalize_address() confused by internal component   PostGIS
• [postgis-devel] [PostGIS] #1384: Issue with geocoding addresses where place name doesn't match   PostGIS
• [postgis-devel] [PostGIS] #1354: Problems geocoding addresses containing "ST STE"   PostGIS
• [postgis-devel] [PostGIS] #1111: Add matching status to geocode output   PostGIS
• [postgis-devel] [PostGIS] #1110: Saint Paul vs. St. Paul   PostGIS
• [postgis-devel] [PostGIS] #1110: Saint Paul vs. St. Paul   PostGIS
• [postgis-devel] [PostGIS] #1108: normalize_address: Internal address prefix sometimes get caught in post dir   PostGIS
• [postgis-devel] [PostGIS] #1075: Too much info in address breaks geocoder   PostGIS
• [postgis-devel] [PostGIS] #1074: Matching on different street spelling?   PostGIS
• [postgis-devel] [PostGIS] #2060: GetTopoGeomElementArray: ERROR: value for domain topoelementarray violates check constraint "dimensions"   PostGIS
• [postgis-devel] [PostGIS] #2060: GetTopoGeomElementArray: ERROR: value for domain topoelementarray violates check constraint "dimensions"   PostGIS
• [postgis-devel] [PostGIS] #2060: GetTopoGeomElementArray: ERROR: value for domain topoelementarray violates check constraint "dimensions"   PostGIS
• [postgis-devel] [PostGIS] #2060: GetTopoGeomElementArray: ERROR: value for domain topoelementarray violates check constraint "dimensions"   PostGIS
• [postgis-devel] [PostGIS] #2060: GetTopoGeomElementArray: ERROR: value for domain topoelementarray violates check constraint "dimensions"   PostGIS
• [postgis-devel] [PostGIS] #2060: GetTopoGeomElementArray: ERROR: value for domain topoelementarray violates check constraint "dimensions"   PostGIS
• [postgis-devel] [PostGIS] #1976: ST_Intersects() returns false while ST_Intersection returns a geography   PostGIS
• [postgis-devel] [PostGIS] #1976: ST_Intersects() returns false while ST_Intersection returns a geography   PostGIS
• [postgis-devel] [PostGIS] #1976: ST_Intersects() returns false while ST_Intersection returns a geography   PostGIS
• [postgis-devel] [PostGIS] #1976: ST_Intersects() returns false while ST_Intersection returns a geography   PostGIS
• [postgis-devel] [PostGIS] #2061: [raster] Clarified overview tables naming convention   PostGIS
• [postgis-devel] [PostGIS] #2061: [raster] Clarified overview tables naming convention   PostGIS
• [postgis-devel] [PostGIS] #1664: [raster] (Add|Drop) OverviewConstraints is not documented (was: (Add|Drop) OverviewConstraints is not documented)   PostGIS
• [postgis-devel] [PostGIS] #1664: [raster] (Add|Drop) OverviewConstraints is not documented   PostGIS
• [postgis-devel] [PostGIS] #2062: Performance Drop in ST_Distance(geog)   PostGIS
• [postgis-devel] [PostGIS] #2062: Performance Drop in ST_Distance(geog)   PostGIS
• [postgis-devel] [PostGIS] #1976: ST_Intersects() returns false while ST_Intersection returns a geography   PostGIS
• [postgis-devel] [PostGIS] #2063: lwgeodetic_tree vertex crossing case wrong   PostGIS
• [postgis-devel] [PostGIS] #2062: Performance Drop in ST_Distance(geog)   PostGIS
• [postgis-devel] [PostGIS] #2063: lwgeodetic_tree vertex crossing case wrong   PostGIS
• [postgis-devel] [PostGIS] #2063: lwgeodetic_tree vertex crossing case wrong   PostGIS
• [postgis-devel] [PostGIS] #2017: Assign Winnie or Debbie to build doxygen docs   PostGIS
• [postgis-devel] [PostGIS] #2064: Setup Debbie to build and test 1.5 branch   PostGIS
• [postgis-devel] [PostGIS] #2065: [raster] ST_Clip in C   PostGIS
• [postgis-devel] [PostGIS] #2065: [raster] ST_Clip in C   PostGIS
• [postgis-devel] [PostGIS] #2065: [raster] ST_Clip in C   PostGIS
• [postgis-devel] [PostGIS] #2065: [raster] ST_Clip in C   PostGIS
• [postgis-devel] [PostGIS] #1989: [raster] ST_Clip() does not clip properly in some cases   PostGIS
• [postgis-devel] [PostGIS] #2066: ST_DumpPoints may return latitude just over 90 depending on execution order   PostGIS
• [postgis-devel] [PostGIS] #2067: Invalid polygons give empty centroids   PostGIS
• [postgis-devel] [PostGIS] #2067: Invalid polygons give empty centroids   PostGIS
• [postgis-devel] [PostGIS] #2065: [raster] ST_Clip in C   PostGIS
• [postgis-devel] [PostGIS] #1581: [raster] ST_Clip should not impose a nodata value when the source raster do not have one   PostGIS
• [postgis-devel] [PostGIS] #1581: [raster] ST_Clip should not impose a nodata value when the source raster do not have one   PostGIS
• [postgis-devel] [PostGIS] #2068: [raster] Make out_db column of raster_columns view behave correctly   PostGIS
• [postgis-devel] [PostGIS] #2068: [raster] Make out_db column of raster_columns view behave correctly   PostGIS
• [postgis-devel] [PostGIS] #2068: [raster] Make out_db column of raster_columns view behave correctly   PostGIS
• [postgis-devel] [PostGIS] #2069: [raster] Add a padwithnodata and a nodatavalue parameter to ST_Clip()   PostGIS
• [postgis-devel] [PostGIS] #2069: [raster] Add a padwithnodata and a nodatavalue parameter to ST_Tile() (was: [raster] Add a padwithnodata and a nodatavalue parameter to ST_Clip())   PostGIS
• [postgis-devel] [PostGIS] #2069: [raster] Add a padwithnodata and a nodatavalue parameter to ST_Tile()   PostGIS
• [postgis-devel] [PostGIS] #2069: [raster] Add a padwithnodata and a nodatavalue parameter to ST_Tile()   PostGIS
• [postgis-devel] [PostGIS] #739: [raster] UpdateRasterSRID   PostGIS
• [postgis-devel] [PostGIS] #593: [raster] Add a ST_BandIsNoData function   PostGIS
• [postgis-devel] [PostGIS] #1983: [raster] x and y or columnx and rowy   PostGIS
• [postgis-devel] [PostGIS] #739: [raster] UpdateRasterSRID   PostGIS
• [postgis-devel] [PostGIS] #2070: Move mailing list   PostGIS
• [postgis-devel] [PostGIS] #739: [raster] UpdateRasterSRID   PostGIS
• [postgis-devel] [PostGIS] #739: [raster] UpdateRasterSRID   PostGIS
• [postgis-devel] [PostGIS] #2064: Setup Debbie to build and test 1.5 branch   PostGIS
• [postgis-devel] [PostGIS] #739: [raster] UpdateRasterSRID   PostGIS
• [postgis-devel] [PostGIS] #1686: [raster] mingw64 PostgreSQL 9.0 64-bit windows failure rt_io, rt_bytea, uninstall   PostGIS
• [postgis-devel] [PostGIS] #2068: [raster] Make out_db column of raster_columns view behave correctly   PostGIS
• [postgis-devel] [PostGIS] #2071: Support PgSQL 9.2   PostGIS
• [postgis-devel] [PostGIS] #2071: Support PgSQL 9.2   PostGIS
• [postgis-devel] [PostGIS] #739: [raster] UpdateRasterSRID   PostGIS
• [postgis-devel] [PostGIS] #1655: [raster] ST_Slope should have default parameters   PostGIS
• [postgis-devel] [PostGIS] #883: [raster] Make every rtpostgis.sql function immutable strict when possible   PostGIS
• [postgis-devel] [PostGIS] #594: [raster] Better handling for NULL, ST_IsEmpty, ST_HasNoBand and ST_BandIsNodata rasters   PostGIS
• [postgis-devel] [PostGIS] #594: [raster] Better handling for NULL, ST_IsEmpty, ST_HasNoBand and ST_BandIsNodata rasters   PostGIS
• [postgis-devel] [PostGIS] #1995: Build errors for 1.5 with PostgreSQL 9.2.0   PostGIS
• [postgis-devel] [PostGIS] #594: [raster] Better handling for NULL, ST_IsEmpty, ST_HasNoBand and ST_BandIsNodata rasters   PostGIS
• [postgis-devel] [PostGIS] #594: [raster] Better handling for NULL, ST_IsEmpty, ST_HasNoBand and ST_BandIsNodata rasters   PostGIS
• [postgis-devel] [PostGIS] #2072: [raster] ST_Intersects should work with out-of-db bands   PostGIS
• [postgis-devel] [PostGIS] #2072: [raster] ST_Intersects should work with out-of-db bands   PostGIS
• [postgis-devel] [PostGIS] #2064: Setup Debbie to build and test 1.5 branch   PostGIS
• [postgis-devel] [PostGIS] #2068: [raster] Make out_db column of raster_columns view behave correctly   PostGIS
• [postgis-devel] [PostGIS] #310: port ST_DumpPoints() to C   PostGIS
• [postgis-devel] [PostGIS] #1287: Drop of "gist_geometry_ops" broke a few clients   PostGIS
• [postgis-devel] [PostGIS] #2064: Setup Debbie to build and test 1.5 branch   PostGIS
• [postgis-devel] [PostGIS] #1287: Drop of "gist_geometry_ops" broke a few clients   PostGIS
• [postgis-devel] [PostGIS] #1287: Drop of "gist_geometry_ops" broke a few clients   PostGIS
• [postgis-devel] [PostGIS] #2055: Intersection with a result from Intersection fails   PostGIS
• [postgis-devel] [PostGIS] #1287: Drop of "gist_geometry_ops" broke a few clients   PostGIS
• [postgis-devel] [PostGIS] #2006: st_area returns NaN   PostGIS
• [postgis-devel] [PostGIS] #1940: epsg:2065 projection is incorrect   PostGIS
• [postgis-devel] [PostGIS] #2073: Extension UPDATE: ERROR: cannot change name of input parameter "band"   PostGIS
• [postgis-devel] [PostGIS] #2073: Extension UPDATE: ERROR: cannot change name of input parameter "band"   PostGIS
• [postgis-devel] [PostGIS] #1019: ST_Densify(geography|geometry)   PostGIS
• [postgis-devel] [PostGIS] #2071: Support PgSQL 9.2   PostGIS
• [postgis-devel] [PostGIS] #1940: epsg:2065 projection is incorrect   PostGIS
• [postgis-devel] [PostGIS] #2070: Move mailing list   PostGIS
• [postgis-devel] [PostGIS] #2059: Hallie the PostGIS expert bot   PostGIS
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   Pierre Racine
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   Pierre Racine
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   Pierre Racine
• [postgis-devel] 2.1 To Do   Paul Ramsey
• [postgis-devel] Fwd: ST_DumpPoints in C   Paul Ramsey
• [postgis-devel] Fwd: ST_DumpPoints in C   Paul Ramsey
• [postgis-devel] Fwd: ST_DumpPoints in C   Paul Ramsey
• [postgis-devel] Fwd: ST_DumpPoints in C   Paul Ramsey
• [postgis-devel] [even.rouault at mines-paris.org: [gdal-dev] Travis CI continuous integration service for GDAL]   Paul Ramsey
• [postgis-devel] [even.rouault at mines-paris.org: [gdal-dev] Travis CI continuous integration service for GDAL]   Paul Ramsey
• [postgis-devel] PostGIS Day   Paul Ramsey
• [postgis-devel] [postgis-users] PostGIS 1.5.5 and PostgreSQL 9.2   Paul Ramsey
• [postgis-devel] [postgis-users] PostGIS 1.5.5 and PostgreSQL 9.2   Paul Ramsey
• [postgis-devel] Testing postgis-devel at lists.osgeo.org   Paul Ramsey
• [postgis-devel] Testing postgis-devel at rri gating into osgeo   Paul Ramsey
• [postgis-devel] Do I get this E-Mail?   Paul Ramsey
• [postgis-devel] postgis-users at lists.osgeo.org, postgis-devel at lists.osgeo.org   Paul Ramsey
• [postgis-devel] Another devel test   Paul Ramsey
• [postgis-devel] mail archives   Paul Ramsey
• [postgis-devel] mail archives   Paul Ramsey
• [postgis-devel] linkage against libpq.so   Sandro Santilli
• [postgis-devel] linkage against libpq.so (Sandro Santilli)   Sandro Santilli
• [postgis-devel] linkage against libpq.so (Sandro Santilli)   Sandro Santilli
• [postgis-devel] Topology Postgis 2.0   Sandro Santilli
• [postgis-devel] [PostGIS] #2034: ST_3DClosestPoint with mixed dimensionality in input values   Sandro Santilli
• [postgis-devel] 2.1 To Do   Sandro Santilli
• [postgis-devel] pt_br docs   Sandro Santilli
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   Sandro Santilli
• [postgis-devel] pt_br docs   Sandro Santilli
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   Sandro Santilli
• [postgis-devel] pt_br docs   Sandro Santilli
• [postgis-devel] pt_br docs   Sandro Santilli
• [postgis-devel] pt_br docs   Sandro Santilli
• [postgis-devel] Can we stop using .c prefix for SQL files ?   Sandro Santilli
• [postgis-devel] Can we stop using .c prefix for SQL files ?   Sandro Santilli
• [postgis-devel] Transifex translation   Sandro Santilli
• [postgis-devel] Transifex translation   Sandro Santilli
• [postgis-devel] Transifex translation   Sandro Santilli
• [postgis-devel] temporary table and dumper   Sandro Santilli
• [postgis-devel] Fwd: ST_DumpPoints in C   Sandro Santilli
• [postgis-devel] Fwd: ST_DumpPoints in C   Sandro Santilli
• [postgis-devel] Fwd: ST_DumpPoints in C   Sandro Santilli
• [postgis-devel] [even.rouault at mines-paris.org: [gdal-dev] Travis CI continuous integration service for GDAL]   Sandro Santilli
• [postgis-devel] [even.rouault at mines-paris.org: [gdal-dev] Travis CI continuous integration service for GDAL]   Sandro Santilli
• [postgis-devel] [postgis-users] PostGIS 1.5.5 and PostgreSQL 9.2   Sandro Santilli
• [postgis-devel] mail archives   Sandro Santilli
• [postgis-devel] mail archives   Sandro Santilli
• [postgis-devel] postgis-commits list   Sandro Santilli
• [postgis-devel] pt_br docs   George Silva
• [postgis-devel] pt_br docs   George Silva
• [postgis-devel] pt_br docs   George Silva
• [postgis-devel] pt_br docs   George Silva
• [postgis-devel] pt_br docs   George Silva
• [postgis-devel] pt_br docs   George Silva
• [postgis-devel] Transifex translation   George Silva
• [postgis-devel] Transifex translation   George Silva
• [postgis-devel] Transifex translation   George Silva
• [postgis-devel] Transifex translation   George Silva
• [postgis-devel] Transifex translation   George Silva
• [postgis-devel] [postgis-users] PostGIS 1.5.5 and PostgreSQL 9.2   J Smith
• [postgis-devel] [postgis-users] PostGIS 1.5.5 and PostgreSQL 9.2   J Smith
• [postgis-devel] [postgis-users] PostGIS 1.5.5 and PostgreSQL 9.2   J Smith
• [postgis-devel] [postgis-users] PostGIS 1.5.5 and PostgreSQL 9.2   J Smith
• [postgis-devel] [postgis-users] PostGIS 1.5.5 and PostgreSQL 9.2   J Smith
• [postgis-devel] Question about SUSE Geo repository & Postgres/postgis   Angelos Tzotsos
• [postgis-devel] Question about SUSE Geo repository & Postgres/postgis   Angelos Tzotsos
• [postgis-devel] Question about SUSE Geo repository & Postgres/postgis   Angelos Tzotsos
• [postgis-devel] Question about SUSE Geo repository & Postgres/postgis   Angelos Tzotsos
• [postgis-devel] [PostGIS] #310: port ST_DumpPoints() to C   Nathan Wagner
• [postgis-devel] Fwd: ST_DumpPoints in C   Nathan Wagner
• [postgis-devel] Fwd: ST_DumpPoints in C   Nathan Wagner
• [postgis-devel] Fwd: ST_DumpPoints in C   Nathan Wagner
• [postgis-devel] Fwd: ST_DumpPoints in C   Nathan Wagner
• [postgis-devel] Testing postgis-devel at lists.osgeo.org   David Zwarg
• [postgis-devel] Do I get this E-Mail?   David Zwarg
• [postgis-devel] 2.1 To Do   dustymugs
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   dustymugs
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   dustymugs
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   dustymugs
• [postgis-devel] Deprecate ST_MapAlgebraExpr and ST_MapAlgebraFct   dustymugs
• [postgis-devel] API for uploading raster   dustymugs
• [postgis-devel] Testing postgis-devel at rri gating into osgeo   dustymugs
• [postgis-devel] Question about SUSE Geo repository & Postgres/postgis   pcreso at pcreso.com
• [postgis-devel] Question about SUSE Geo repository & Postgres/postgis   pcreso at pcreso.com
• [postgis-devel] Question about SUSE Geo repository & Postgres/postgis   pcreso at pcreso.com
• [postgis-devel] API for uploading raster   ryagz
• [postgis-devel] API for uploading raster   ryagz

Last message date: Wed Oct 31 23:21:52 PDT 2012
Archived on: Fri Nov 10 09:26:17 PST 2017

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