October 2011 Archives by thread

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

Starting: Sat Oct 1 06:25:49 PDT 2011
Ending: Mon Oct 31 16:01:50 PDT 2011
Messages: 347

• [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] Why doesn't knn work on table1.geom <#>table2.geom   Nicklas Avén
    • [postgis-devel] Why doesn't knn work on table1.geom <#>table2.geom   Paul Ramsey
      • [postgis-devel] Why doesn't knn work on table1.geom <#>table2.geom   Nicklas Avén
      • [postgis-devel] Why doesn't knn work on table1.geom <#>table2.geom   Paragon Corporation
      • [postgis-devel] Why doesn't knn work on table1.geom <#>table2.geom   Nicklas Avén
      • [postgis-devel] Why doesn't knn work on table1.geom <#>table2.geom   Paul Ramsey
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
  • [postgis-devel] [PostGIS] #860: [raster] Modify ST_MapAlgebra to handle expressions and user-functions   PostGIS
• [postgis-devel] [PostGIS] #866: [raster] Change the ST_MapAlgebra nodatavalueexpr text parameter for nodatavaluerepl   PostGIS
  • [postgis-devel] [PostGIS] #866: [raster] Change the ST_MapAlgebra nodatavalueexpr text parameter for nodatavaluerepl   PostGIS
• [postgis-devel] [PostGIS] #615: [raster] rtpostgis.sql installed in wrong folder   PostGIS
• [postgis-devel] [PostGIS] #1217: add a raster_upgrade_20_minor script   PostGIS
• [postgis-devel] ST_UnaryUnion vs ST_Dump + ST_Union   Jose Carlos Martinez Llario
  • [postgis-devel] ST_UnaryUnion vs ST_Dump + ST_Union   Sandro Santilli
    • [postgis-devel] ST_UnaryUnion vs ST_Dump + ST_Union   Sandro Santilli
    • [postgis-devel] ST_UnaryUnion vs ST_Dump + ST_Union   Paul Ramsey
      • [postgis-devel] ST_UnaryUnion vs ST_Dump + ST_Union   Sandro Santilli
• [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
  • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
  • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
  • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
  • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
  • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
    • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   Sandro Santilli
      • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   Bborie Park
      • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   Sandro Santilli
  • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
  • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
  • [postgis-devel] [PostGIS] #1213: [raster] RT_Intersects test fails   PostGIS
• [postgis-devel] [PostGIS] #1225: postgis_gdal_version   PostGIS
  • [postgis-devel] [PostGIS] #1225: postgis_gdal_version   PostGIS
  • [postgis-devel] [PostGIS] #1225: postgis_gdal_version   PostGIS
  • [postgis-devel] [PostGIS] #1225: postgis_gdal_version   PostGIS
  • [postgis-devel] [PostGIS] #1225: postgis_gdal_version   PostGIS
• [postgis-devel] David Zwarg as Committer in Raster   Paul Ramsey
  • [postgis-devel] David Zwarg as Committer in Raster   Sandro Santilli
    • [postgis-devel] David Zwarg as Committer in Raster   Paragon Corporation
      • [postgis-devel] David Zwarg as Committer in Raster   Jorge Arévalo
  • [postgis-devel] David Zwarg as Committer in Raster   David Zwarg
  • [postgis-devel] David Zwarg as Committer in Raster   Mark Cave-Ayland
• [postgis-devel] [mtnclimb at gmail.com: Re: Fwd: ST_UnaryUnion vs ST_Dump + ST_Union]   Sandro Santilli
• [postgis-devel] [PostGIS] #1226: ST_RemEdgeNewFace: Spatial exception non-existent edge - typo error   PostGIS
  • [postgis-devel] [PostGIS] #1226: ST_RemEdgeNewFace: Spatial exception non-existent edge - typo error   PostGIS
  • [postgis-devel] [PostGIS] #1226: ST_RemEdgeNewFace: Spatial exception non-existent edge - typo error   PostGIS
  • [postgis-devel] [PostGIS] #1226: ST_RemEdgeNewFace: Spatial exception non-existent edge - typo error   PostGIS
• [postgis-devel] [PostGIS] #286: Change "no SRID" SRID to 0   PostGIS
  • [postgis-devel] [PostGIS] #286: Change "no SRID" SRID to 0   PostGIS
  • [postgis-devel] [PostGIS] #286: Change "no SRID" SRID to 0   PostGIS
  • [postgis-devel] [PostGIS] #286: Change "no SRID" SRID to 0   PostGIS
• [postgis-devel] [PostGIS] #1222: After the switch to SRID=0 topology tests fail   PostGIS
  • [postgis-devel] [PostGIS] #1222: After the switch to SRID=0 topology tests fail   PostGIS
  • [postgis-devel] [PostGIS] #1222: After the switch to SRID=0 topology tests fail   PostGIS
• [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
  • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Mark Cave-Ayland
    • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Howard Butler
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
    • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Chris Hodgson
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Paul Ramsey
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Paul Ramsey
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Paul Ramsey
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Chris Hodgson
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Paragon Corporation
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Paul Ramsey
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
  • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   aperi2007
    • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Paul Ramsey
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   aperi2007
      • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Sandro Santilli
  • [postgis-devel] Motion: vote for considering SRID <= 0 as "unknown"   Mark Cave-Ayland
    • [postgis-devel] Motion approved: SRID <= 0 as UNKNOWN (+ thoughts)   Sandro Santilli
• [postgis-devel] Unknown SRID (Was: #1223: Unknown SRID to NULL)   Mark Cave-Ayland
• [postgis-devel] Adding postgis_gdal_version function   dustymugs
  • [postgis-devel] Adding postgis_gdal_version function   Sandro Santilli
• [postgis-devel] GDAL Python bindings with NumPy array support   Sandro Santilli
  • [postgis-devel] GDAL Python bindings with NumPy array support   Mateusz Loskot
    • [postgis-devel] GDAL Python bindings with NumPy array support   Sandro Santilli
• [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
  • [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
  • [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
  • [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
  • [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
  • [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
  • [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
  • [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
  • [postgis-devel] [PostGIS] #1227: server crash on invalid gml in st_geomfromgml   PostGIS
• [postgis-devel] [PostGIS] #1228: [raster] Add a ST_AddBand(raster, ARRAY[values], index DEFAULT 1) variant   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] #766: [raster] The raster2pgsql.py -M option should just do an ANALYSE   PostGIS
  • [postgis-devel] [PostGIS] #766: [raster] The raster2pgsql.py -M option should just do an ANALYSE   PostGIS
• [postgis-devel] [PostGIS] #165: [raster] missing uninstall target   PostGIS
• [postgis-devel] [PostGIS] #633: [raster] st_above, st_below, st_right whatever make raster_above, raster_left whatever   PostGIS
• [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra (was: [raster] Implement the two rasters version of ST_MapAlgebra)   PostGIS
• [postgis-devel] [PostGIS] #1066: [raster] raster crashes server with arbitrary tests   PostGIS
• [postgis-devel] [PostGIS] #1168: [raster] ST_AsRaster ability to render more complex types   PostGIS
  • [postgis-devel] [PostGIS] #1168: [raster] ST_AsRaster ability to render more complex types   PostGIS
• [postgis-devel] [PostGIS] #1174: [raster] C-level index-to-geocoordinate functions   PostGIS
• [postgis-devel] [PostGIS] #1167: gdal-config unrecognized option   PostGIS
• [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
  • [postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra   PostGIS
• [postgis-devel] [PostGIS] #589: [raster] Implement ST_SameAlignment   PostGIS
  • [postgis-devel] [PostGIS] #589: [raster] Implement ST_SameAlignment   PostGIS
  • [postgis-devel] [PostGIS] #589: [raster] Implement ST_SameAlignment   PostGIS
  • [postgis-devel] [PostGIS] #589: [raster] Implement ST_SameAlignment   PostGIS
• [postgis-devel] [PostGIS] #1229: ST_SRID mutator function (sql/mm)   PostGIS
• [postgis-devel] [PostGIS] #1182: GetSRID function for topology   PostGIS
  • [postgis-devel] [PostGIS] #1182: GetSRID function for topology   PostGIS
• [postgis-devel] [PostGIS] #679: shp2pgsql-gui should warn when SRID is not specified   PostGIS
• [postgis-devel] [PostGIS] #738: AddGeometryColumn allow to accept srid = 0 and other unkonwn srid issues   PostGIS
• [postgis-devel] [PostGIS] #1221: Update Java components to support SRID<=0 as unknown SRID (was: Update Java components to support SRID=0 as unknown SRID)   PostGIS
• [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
  • [postgis-devel] [PostGIS] #1230: _ST_BestSRID should not return negative SRID values   PostGIS
• [postgis-devel] [PostGIS] #1231: Expose clamp_srid function for external use   PostGIS
  • [postgis-devel] [PostGIS] #1231: Expose clamp_srid function for external use   PostGIS
• [postgis-devel] SRID discovery   maplabs at light42.com
• [postgis-devel] [PostGIS] #810: Increare accuracy of area calculation   PostGIS
  • [postgis-devel] [PostGIS] #810: Increare accuracy of area calculation   PostGIS
  • [postgis-devel] [PostGIS] #810: Increare accuracy of area calculation   PostGIS
  • [postgis-devel] [PostGIS] #810: Increare accuracy of area calculation   PostGIS
• [postgis-devel] [PostGIS] #1232: Exception when calling isValid on multilinestring with only 1 point   PostGIS
  • [postgis-devel] [PostGIS] #1232: Exception when calling isValid on multilinestring with only 1 point   PostGIS
  • [postgis-devel] [PostGIS] #1232: Exception when calling isValid on multilinestring with only 1 point   PostGIS
  • [postgis-devel] [PostGIS] #1232: Exception when calling isValid on multilinestring with only 1 point   PostGIS
  • [postgis-devel] [PostGIS] #1232: Exception when calling isValid on multilinestring with only 1 point   PostGIS
  • [postgis-devel] [PostGIS] #1232: Exception when calling isValid on multilinestring with only 1 point   PostGIS
  • [postgis-devel] [PostGIS] #1232: Exception when calling isValid on multilinestring with only 1 point   PostGIS
• [postgis-devel] [PostGIS] #1233: Forbid SRID <= 0 or SRID >= 999000 in spatial_ref_sys   PostGIS
  • [postgis-devel] [PostGIS] #1233: Forbid SRID <= 0 or SRID >= 999000 in spatial_ref_sys   PostGIS
  • [postgis-devel] [PostGIS] #1233: Forbid SRID <= 0 or SRID >= 999000 in spatial_ref_sys   PostGIS
• [postgis-devel] [PostGIS] #1234: _ST_BestSRID making up utm zone 61   PostGIS
  • [postgis-devel] [PostGIS] #1234: _ST_BestSRID making up utm zone 61   PostGIS
• [postgis-devel] Unknown SRID <= 0 status report   Sandro Santilli
• [postgis-devel] [PostGIS] #1235: cast to different-srid typmod   PostGIS
• [postgis-devel] [PostGIS] #1195: CopyTopologyLayer   PostGIS
• [postgis-devel] [PostGIS] #956: SELECT (SRF()).* -> SELECT * FROM SRF()   PostGIS
• [postgis-devel] [PostGIS] #1185: Need DropTopoGeometryTable function   PostGIS
• [postgis-devel] [PostGIS] #1236: ST_IsValid*(TopoGeometry)   PostGIS
  • [postgis-devel] [PostGIS] #1236: topology.IsValid*(TopoGeometry) (was: ST_IsValid*(TopoGeometry))   PostGIS
• [postgis-devel] [PostGIS] #982: ST_ChangeEdgeGeom doesn't let you change geometry of a closed edge   PostGIS
• [postgis-devel] [PostGIS] #1237: ST_SpatialRefSys data type (sql/mm)   PostGIS
  • [postgis-devel] [PostGIS] #1237: ST_SpatialRefSys data type (sql/mm)   PostGIS
  • [postgis-devel] [PostGIS] #1237: ST_SpatialRefSys data type (sql/mm)   PostGIS
• [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
  • [postgis-devel] [PostGIS] #1150: Prevent people from inserting entries in spatial_ref_sys with no proj4text   PostGIS
• [postgis-devel] [PostGIS] #1238: Resample and upperleftx , upperlefty   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty (was: Resample and upperleftx , upperlefty)   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty   PostGIS
  • [postgis-devel] [PostGIS] #1238: [raster] Resample and upperleftx , upperlefty   PostGIS
• [postgis-devel] [PostGIS] #1239: [raster] A warning message makes psql to hang   PostGIS
  • [postgis-devel] [PostGIS] #1239: [raster] A warning message makes psql to hang   PostGIS
• [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
  • [postgis-devel] [PostGIS] #1240: [raster] ST_Addband() should be in the "Raster Constructors" part of the documentation   PostGIS
• [postgis-devel] [postgis-users] ST_Intersection Raster error   Sandro Santilli
• [postgis-devel] [PostGIS] #1241: Typos in documentation: VACUUM ANALYZE, I None   PostGIS
  • [postgis-devel] [PostGIS] #1241: Typos in documentation: VACUUM ANALYZE, I None   PostGIS
• [postgis-devel] New node splitting algorithm for GiST   Alexander Korotkov
  • [postgis-devel] New node splitting algorithm for GiST   Paul Ramsey
    • [postgis-devel] New node splitting algorithm for GiST   Paul Ramsey
      • [postgis-devel] New node splitting algorithm for GiST   Alexander Korotkov
      • [postgis-devel] New node splitting algorithm for GiST   Paul Ramsey
      • [postgis-devel] New node splitting algorithm for GiST   Alexander Korotkov
      • [postgis-devel] New node splitting algorithm for GiST   Paul Ramsey
• [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block (was: Tiger Geocoder 2010 Geocode() to even/odd side of street)   PostGIS
• [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
  • [postgis-devel] [PostGIS] #1052: Tiger Geocoder 2010 Geocode() "squishing" toward end of block   PostGIS
• [postgis-devel] [PostGIS] #1215: ST_DelaunayTriangles   PostGIS
  • [postgis-devel] [PostGIS] #1215: ST_DelaunayTriangles   PostGIS
• [postgis-devel] [PostGIS] #1242: Document bug or regression bug - ST_Line_Locate_Point for multilinestring   PostGIS
• [postgis-devel] [PostGIS] #1243: ST_Distance_Sphere regress failure   PostGIS
  • [postgis-devel] [PostGIS] #1243: ST_Distance_Sphere regress failure   PostGIS
• [postgis-devel] [PostGIS] #1244: rev7982 link against GEOS 3.2.3 fails   PostGIS
• [postgis-devel] [PostGIS] #375: Add lwcollection_homogenize and ST_Homogenize   PostGIS
  • [postgis-devel] [PostGIS] #375: Add lwcollection_homogenize and ST_Homogenize   PostGIS
• [postgis-devel] [PostGIS] #1017: Implement topology.ToTopoGeom(Geometry, topology_name, layer_id)   PostGIS
• [postgis-devel] [PostGIS] #1245: ST_AddMultiBand that can add multiple bands to an existing raster   PostGIS
  • [postgis-devel] [PostGIS] #1245: [raster] ST_AddMultiBand that can add multiple bands to an existing raster (was: ST_AddMultiBand that can add multiple bands to an existing raster)   PostGIS
  • [postgis-devel] [PostGIS] #1245: [raster] ST_AddMultiBand that can add multiple bands to an existing raster   PostGIS
  • [postgis-devel] [PostGIS] #1245: [raster] ST_AddMultiBand that can add multiple bands to an existing raster   PostGIS
  • [postgis-devel] [PostGIS] #1245: [raster] ST_AddMultiBand that can add multiple bands to an existing raster   PostGIS
• [postgis-devel] [PostGIS] #1212: [raster]: st_intersects signature change - documentation out of synch   PostGIS
• [postgis-devel] [PostGIS] #1246: Can't make check under mingw   PostGIS
  • [postgis-devel] [PostGIS] #1246: Can't make check under mingw   PostGIS
  • [postgis-devel] [PostGIS] #1246: Can't make check under mingw   PostGIS
• [postgis-devel] Geometry Columns View   maplabs at light42.com
  • [postgis-devel] Geometry Columns View   Sandro Santilli
  • [postgis-devel] Geometry Columns View   maplabs at light42.com
    • [postgis-devel] Geometry Columns View   Paragon Corporation
• [postgis-devel] PostGIS 2 Docs   maplabs at light42.com
• [postgis-devel] KNN c r d   maplabs at light42.com
• [postgis-devel] [PostGIS] #1247: ST_AsRaster aggregate function   PostGIS
  • [postgis-devel] [PostGIS] #1247: ST_AsRaster aggregate function   PostGIS
  • [postgis-devel] [PostGIS] #1247: ST_AsRaster aggregate function   PostGIS
  • [postgis-devel] [PostGIS] #1247: ST_AsRaster aggregate function   PostGIS
• [postgis-devel] [PostGIS] #1248: Increasing cost of spatial functions.   PostGIS
  • [postgis-devel] [PostGIS] #1248: Increasing cost of spatial functions.   PostGIS
  • [postgis-devel] [PostGIS] #1248: Increasing cost of spatial functions.   PostGIS
• [postgis-devel] PostGIS Raster problem   David B�langer
  • [postgis-devel] PostGIS Raster problem   dustymugs
    • [postgis-devel] PostGIS Raster problem   David B�langer
      • [postgis-devel] PostGIS Raster problem   Jorge Arévalo
      • [postgis-devel] PostGIS Raster problem   David B�langer
      • [postgis-devel] PostGIS Raster problem   Jorge Arévalo
• [postgis-devel] [PostGIS] #754: [raster] Standardize the index nomenclature for rt_core functions   PostGIS
• [postgis-devel] Expected behavior of rt_raster_has_no_band function   Bborie Park
  • [postgis-devel] Expected behavior of rt_raster_has_no_band function   Pierre Racine
• [postgis-devel] [PostGIS] #1249: Cut part of the raster   PostGIS
  • [postgis-devel] [PostGIS] #1249: Cut part of the raster   PostGIS
• [postgis-devel] [PostGIS] #1250: ST_LocateBetweenElevations should return NULL and not fail if intersection is void   PostGIS
• [postgis-devel] [PostGIS] #754: [raster] Band index in rt_core functions must be 0-based (was: [raster] Standardize the index nomenclature for rt_core functions)   PostGIS
• [postgis-devel] [PostGIS] #754: [raster] Band index in rt_core functions must be 0-based   PostGIS
• [postgis-devel] Uses of PostGIS 2.0 Topology?   maplabs at light42.com
  • [postgis-devel] Uses of PostGIS 2.0 Topology?   Sandro Santilli
• [postgis-devel] [PostGIS] #1251: Enhance ST_Rotate by adding offset origin parameters   PostGIS
  • [postgis-devel] [PostGIS] #1251: Enhance ST_Rotate by adding offset origin parameters   PostGIS
  • [postgis-devel] [PostGIS] #1251: Enhance ST_Rotate by adding offset origin parameters   PostGIS
• [postgis-devel] [PostGIS] #376: Add ST_GeomFromGeoJSON   PostGIS
• [postgis-devel] [PostGIS] #701: Support for 9.1 KNN GIST enhancements   PostGIS
  • [postgis-devel] [PostGIS] #701: Support for 9.1 KNN GIST enhancements   PostGIS
  • [postgis-devel] [PostGIS] #701: Support for 9.1 KNN GIST enhancements   PostGIS
  • [postgis-devel] [PostGIS] #701: Support for 9.1 KNN GIST enhancements   PostGIS
• [postgis-devel] KNN <#> Operator - odd results   maplabs at light42.com
  • [postgis-devel] KNN <#> Operator - odd results   Paul Ramsey
  • [postgis-devel] KNN <#> Operator - odd results   maplabs at light42.com
• [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
  • [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
  • [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
  • [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
  • [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
  • [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
  • [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
  • [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
  • [postgis-devel] [PostGIS] #1252: SRID appearing in ST_AsText for particular multipolygon   PostGIS
• [postgis-devel] [PostGIS] #648: ST_Summary starts and ends with a newline   PostGIS
• [postgis-devel] [PostGIS] #1253: ST_Summary never reports an "S" flag (for SRID)   PostGIS
• [postgis-devel] [PostGIS] #1254: Composite geometries end up with nested BBOX caches   PostGIS
• [postgis-devel] [PostGIS] #1255: ST_Union Returns NULL on valid geometries   PostGIS
  • [postgis-devel] [PostGIS] #1255: ST_Union Returns NULL on valid geometries   PostGIS
• [postgis-devel] "make check" failure   David Zwarg
  • [postgis-devel] "make check" failure   Bborie Park
    • [postgis-devel] "make check" failure   David Zwarg
      • [postgis-devel] "make check" failure   Bborie Park
• [postgis-devel] How define a view that use a case operator for geometry field   aperi2007
  • [postgis-devel] How define a view that use a case operator for geometry field   Sandro Santilli
    • [postgis-devel] How define a view that use a case operator for geometry field   aperi2007
      • [postgis-devel] How define a view that use a case operator for geometry field   Sandro Santilli
      • [postgis-devel] How define a view that use a case operator for geometry field   aperi2007
      • [postgis-devel] CASE w/out ELSE hides typmod (was: How define a view that use a case operator for geometry field)   Sandro Santilli
      • [postgis-devel] How define a view that use a case operator for geometry field   Paragon Corporation
      • [postgis-devel] How define a view that use a case operator for geometry field   Sandro Santilli
• [postgis-devel] [PostGIS] #1256: uninstall_legacy.sql fails dropping geomunion(geometry, geometry)   PostGIS
• [postgis-devel] [PostGIS] #1257: mem_size not dropped by uninstall_legacy.sql   PostGIS
• [postgis-devel] lwgeom->bbox   Paul Ramsey
  • [postgis-devel] lwgeom->bbox   Sandro Santilli
    • [postgis-devel] lwgeom->bbox   Paul Ramsey
• [postgis-devel] [PostGIS] #1258: ST_CreateTopoGeo drops lineal input boundaries   PostGIS
  • [postgis-devel] [PostGIS] #1258: ST_CreateTopoGeo drops lineal input boundaries   PostGIS
• [postgis-devel] [PostGIS] #1259: xsl scripts to generate programmer cheat sheets   PostGIS
  • [postgis-devel] [PostGIS] #1259: xsl scripts to generate programmer cheat sheets   PostGIS
• [postgis-devel] [PostGIS] #1260: Topology: Support security access to tables   PostGIS
• [postgis-devel] [PostGIS] #1261: ST_CreateTopoGeo drops lineal input components sharing the same bounding box   PostGIS
  • [postgis-devel] [PostGIS] #1261: ST_CreateTopoGeo drops lineal input components sharing the same bounding box   PostGIS
• [postgis-devel] [PostGIS] #1262: FAQ about licensing   PostGIS
• [postgis-devel] [PostGIS] #1206: ST_Node or ST_NodeLines   PostGIS
• [postgis-devel] 1.5 Regression?   Paul Ramsey
  • [postgis-devel] 1.5 Regression?   Paul Ramsey
    • [postgis-devel] 1.5 Regression?   Sandro Santilli
      • [postgis-devel] 1.5 Regression?   Paul Ramsey
  • [postgis-devel] 1.5 Regression?   Sandro Santilli
    • [postgis-devel] 1.5 Regression?   Paul Ramsey
      • [postgis-devel] 1.5 Regression?   Sandro Santilli

Last message date: Mon Oct 31 16:01:50 PDT 2011
Archived on: Fri Nov 10 09:26:10 PST 2017

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