July 2012 Archives by thread

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

Starting: Sun Jul 1 05:32:43 PDT 2012
Ending: Tue Jul 31 16:46:27 PDT 2012
Messages: 257

• [postgis-devel] New node splitting algorithm for GiST   Alexander Korotkov
  • [postgis-devel] New node splitting algorithm for GiST   Paragon Corporation
    • [postgis-devel] New node splitting algorithm for GiST   Alexander Korotkov
• [postgis-devel] [PostGIS] #1796: Improve ST_DWithin performance, especially for geography   PostGIS
  • [postgis-devel] [PostGIS] #1796: Improve ST_DWithin performance, especially for geography   PostGIS
• [postgis-devel] [PostGIS] #1895: New node splitting algorithm for GiST   PostGIS
  • [postgis-devel] [PostGIS] #1895: New node splitting algorithm for GiST   PostGIS
  • [postgis-devel] [PostGIS] #1895: New node splitting algorithm for GiST   PostGIS
  • [postgis-devel] [PostGIS] #1895: New node splitting algorithm for GiST   PostGIS
• [postgis-devel] [PostGIS] #1894: Documentation test failure   PostGIS
  • [postgis-devel] [PostGIS] #1894: Documentation test failure   PostGIS
  • [postgis-devel] [PostGIS] #1894: Documentation test failure   PostGIS
  • [postgis-devel] [PostGIS] #1894: Documentation test failure   PostGIS
• [postgis-devel] [PostGIS] #1896: Make create postgis and postgis_topology unpackaged script automated   PostGIS
  • [postgis-devel] [PostGIS] #1896: Make create postgis and postgis_topology unpackaged script automated   PostGIS
• [postgis-devel] [PostGIS] #1897: extension missing migration path from 2.0.1 to 2.1..   PostGIS
• [postgis-devel] [PostGIS] #1898: ST_DelaunayTriangles option to output as TIN   PostGIS
  • [postgis-devel] [PostGIS] #1898: ST_DelaunayTriangles option to output as TIN   PostGIS
• [postgis-devel] [PostGIS] #1899: TIN to topology : ERROR: Unexpected feature dimension 2   PostGIS
• [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
  • [postgis-devel] [PostGIS] #1828: Estimate returned by geography_gist_selectivity results in slow query plan for ST_DWithin   PostGIS
• [postgis-devel] [PostGIS] #1900: Fix pgsql2shp for big-endian systems   PostGIS
  • [postgis-devel] [PostGIS] #1900: Fix pgsql2shp for big-endian systems   PostGIS
  • [postgis-devel] [PostGIS] #1900: Fix pgsql2shp for big-endian systems   PostGIS
  • [postgis-devel] [PostGIS] #1900: Fix pgsql2shp for big-endian systems   PostGIS
• [postgis-devel] [PostGIS] #1901: PostGIS 2.0.0 - Errors during "make check"   PostGIS
  • [postgis-devel] [PostGIS] #1901: PostGIS 2.0.0 - Errors during "make check"   PostGIS
  • [postgis-devel] [PostGIS] #1901: PostGIS 2.0.0 - Errors during "make check"   PostGIS
  • [postgis-devel] [PostGIS] #1901: PostGIS 2.0.0 - Errors during "make check"   PostGIS
  • [postgis-devel] [PostGIS] #1901: PostGIS 2.0.0 - Errors during "make check"   PostGIS
  • [postgis-devel] [PostGIS] #1901: PostGIS 2.0.0 - Errors during "make check"   PostGIS
  • [postgis-devel] [PostGIS] #1901: PostGIS 2.0.0 - Errors during "make check"   PostGIS
• [postgis-devel] [PostGIS] #1864: ST_Intersection returns wrong values with high latitudes   PostGIS
• [postgis-devel] [PostGIS] #1610: Support for larger objects in ST_Intersection(geography)   PostGIS
  • [postgis-devel] [PostGIS] #1610: Support for larger objects in ST_Intersection(geography)   PostGIS
  • [postgis-devel] [PostGIS] #1610: Support for larger objects in ST_Intersection(geography)   PostGIS
• [postgis-devel] [PostGIS] #1808: [raster] Raster importation creates gaps and corrupted data   PostGIS
  • [postgis-devel] [PostGIS] #1808: [raster] Raster importation creates gaps and corrupted data   PostGIS
• [postgis-devel] [PostGIS] #1902: [raster] GDAL Surfer export creates files with minY and maxY swapped in header.   PostGIS
  • [postgis-devel] [PostGIS] #1902: [raster] GDAL Surfer export creates files with minY and maxY swapped in header.   PostGIS
  • [postgis-devel] [PostGIS] #1902: [raster] GDAL Surfer export creates files with minY and maxY swapped in header.   PostGIS
  • [postgis-devel] [PostGIS] #1902: [raster] GDAL Surfer export creates files with minY and maxY swapped in header.   PostGIS
  • [postgis-devel] [PostGIS] #1902: [raster] GDAL Surfer export creates files with minY and maxY swapped in header.   PostGIS
  • [postgis-devel] [PostGIS] #1902: [raster] GDAL Surfer export creates files with minY and maxY swapped in header.   PostGIS
  • [postgis-devel] [PostGIS] #1902: [raster] GDAL Surfer export creates files with minY and maxY swapped in header.   PostGIS
  • [postgis-devel] [PostGIS] #1902: [raster] GDAL Surfer export creates files with minY and maxY swapped in header.   PostGIS
• [postgis-devel] [PostGIS] #1903: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1903: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1903: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1903: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1903: Crash when inserting ~280 GEOGRAPHY POINTs (and NULLs) into a GIST indexed table (was: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index)   PostGIS
  • [postgis-devel] [PostGIS] #1903: Crash when inserting ~280 GEOGRAPHY POINTs (and NULLs) into a GIST indexed table   PostGIS
  • [postgis-devel] [PostGIS] #1903: Crash when inserting ~280 GEOGRAPHY POINTs (and NULLs) into a GIST indexed table   PostGIS
  • [postgis-devel] [PostGIS] #1903: Crash when inserting ~280 GEOGRAPHY POINTs (and NULLs) into a GIST indexed table   PostGIS
• [postgis-devel] [PostGIS] #1904: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1904: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1904: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1904: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
• [postgis-devel] [PostGIS] #1905: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1905: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1905: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
• [postgis-devel] [PostGIS] #1906: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1906: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
  • [postgis-devel] [PostGIS] #1906: PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index   PostGIS
• [postgis-devel] [PostGIS] #1888: Planet PostGIS blog aggregator   PostGIS
  • [postgis-devel] [PostGIS] #1888: Planet PostGIS blog aggregator   PostGIS
  • [postgis-devel] [PostGIS] #1888: Planet PostGIS blog aggregator   PostGIS
  • [postgis-devel] [PostGIS] #1888: Planet PostGIS blog aggregator   PostGIS
  • [postgis-devel] [PostGIS] #1888: Planet PostGIS blog aggregator   PostGIS
• [postgis-devel] [wiki] Moved content of Code Sprint in Paris   Mateusz Loskot
• [postgis-devel] New PostGIS Planet   Paragon Corporation
• [postgis-devel] [PostGIS] #1907: Autobuild windows experimental builds   PostGIS
• [postgis-devel] [PostGIS] #1887: New Buildbot   PostGIS
  • [postgis-devel] [PostGIS] #1887: New Buildbot   PostGIS
• [postgis-devel] [PostGIS] #1678: [raster] GDAL_DATA dependency   PostGIS
• [postgis-devel] [PostGIS] #485: Quick geometry viewer that is integrable in PgAdmin III   PostGIS
  • [postgis-devel] [PostGIS] #485: Quick geometry viewer that is integrable in PgAdmin III   PostGIS
• [postgis-devel] [PostGIS] #1908: crasher with 2 geography columns in view used in query   PostGIS
  • [postgis-devel] [PostGIS] #1908: crasher with 2 geography columns in view used in query   PostGIS
  • [postgis-devel] [PostGIS] #1908: crasher with 2 geography columns in view used in query   PostGIS
  • [postgis-devel] [PostGIS] #1908: crasher with 2 geography columns in view used in query   PostGIS
• [postgis-devel] [PostGIS] #1909: intersection problem   PostGIS
  • [postgis-devel] [PostGIS] #1909: intersection problem   PostGIS
  • [postgis-devel] [PostGIS] #1909: intersection problem   PostGIS
• [postgis-devel] [PostGIS] #1215: ST_DelaunayTriangles   PostGIS
  • [postgis-devel] [PostGIS] #1215: ST_DelaunayTriangles   PostGIS
• [postgis-devel] [PostGIS] #1910: Node size in circ trees is fixed at 2   PostGIS
  • [postgis-devel] [PostGIS] #1910: Node size in circ trees is fixed at 2   PostGIS
  • [postgis-devel] [PostGIS] #1910: Node size in circ trees is fixed at 2   PostGIS
  • [postgis-devel] [PostGIS] #1910: Node size in circ trees is fixed at 2   PostGIS
• [postgis-devel] CMake Progress?   Mateusz Loskot
  • [postgis-devel] CMake Progress?   Sandro Santilli
    • [postgis-devel] CMake Progress?   Mateusz Loskot
• [postgis-devel] How to make a 3D table   José María Amuedo
• [postgis-devel] Prueba de la lista de correos   José María Amuedo
• [postgis-devel] [PostGIS] #1825: containsproperly: Conditional jump or move depends on uninitialised value(s)   PostGIS
• [postgis-devel] [PostGIS] #510: ST_Estimated_Extent doesn't work with views   PostGIS
• [postgis-devel] [PostGIS] #1865: Data loss in postgis_restore.pl when data rows have leading dashes   PostGIS
  • [postgis-devel] [PostGIS] #1865: Data loss in postgis_restore.pl when data rows have leading dashes   PostGIS
  • [postgis-devel] [PostGIS] #1865: Data loss in postgis_restore.pl when data rows have leading dashes   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] #1832: Crash when updating GIST index on geography column   PostGIS
• [postgis-devel] [PostGIS] #1911: [raster] ST_Surface returning a multipolygon of a band   PostGIS
  • [postgis-devel] [PostGIS] #1911: [raster] ST_Surface returning a multipolygon of a band   PostGIS
  • [postgis-devel] [PostGIS] #1911: [raster] ST_Surface returning a multipolygon of a band   PostGIS
  • [postgis-devel] [PostGIS] #1911: [raster] ST_BandSurface returning a multipolygon of a band (was: [raster] ST_Surface returning a multipolygon of a band)   PostGIS
• [postgis-devel] [postgis-users] Super weird problem: Cannot insert more than ~300 rows (or ~100 kb) into a table   Paul Ramsey
• [postgis-devel] [PostGIS] #1912: ST_Estimated_Extent() does not handle table name with blank   PostGIS
• [postgis-devel] [PostGIS] #1913: reverse geocoder overwrites best street answer with worst street answer   PostGIS
• [postgis-devel] [PostGIS] #1914: [raster] ST_Contains() in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1914: [raster] ST_Contains() in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1914: [raster] ST_Contains() in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1914: [raster] ST_Contains() in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1914: [raster] ST_Contains() in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1915: [raster] ST_ContainsProperly() in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1915: [raster] ST_ContainsProperly() in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1915: [raster] ST_ContainsProperly() in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1915: [raster] ST_ContainsProperly() in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1916: [raster] ST_Covers in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1916: [raster] ST_Covers in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1916: [raster] ST_Covers in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1916: [raster] ST_Covers in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1916: [raster] ST_Covers in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1917: [raster] ST_CoveredBy in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1917: [raster] ST_CoveredBy in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1917: [raster] ST_CoveredBy in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1917: [raster] ST_CoveredBy in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1918: [raster] ST_Crosses in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1918: [raster] ST_Crosses in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1918: [raster] ST_Crosses in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1918: [raster] ST_Crosses in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1919: [raster] ST_Disjoint in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1919: [raster] ST_Disjoint in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1919: [raster] ST_Disjoint in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1919: [raster] ST_Disjoint in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1919: [raster] ST_Disjoint in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1920: [raster] ST_DFullyWithin in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1920: [raster] ST_DFullyWithin in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1920: [raster] ST_DFullyWithin in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1921: [raster] ST_Touches in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1921: [raster] ST_Touches in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1921: [raster] ST_Touches in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1921: [raster] ST_Touches in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1921: [raster] ST_Touches in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1922: [raster] ST_DWithin in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1922: [raster] ST_DWithin in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1923: [raster] ST_Within in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1923: [raster] ST_Within in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1923: [raster] ST_Within in raster and vector space   PostGIS
• [postgis-devel] [PostGIS] #1924: [raster] ST_Overlaps in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1924: [raster] ST_Overlaps in raster and vector space   PostGIS
  • [postgis-devel] [PostGIS] #1924: [raster] ST_Overlaps in raster and vector space   PostGIS
• [postgis-devel] How can to make a 3D table   josamulai
  • [postgis-devel] How can to make a 3D table   Mateusz Loskot
• [postgis-devel] [PostGIS] #1925: lwgeom_estimate.c: In function 'LWGEOM_gist_joinsel'   PostGIS
  • [postgis-devel] [PostGIS] #1925: lwgeom_estimate.c: In function 'LWGEOM_gist_joinsel'   PostGIS
  • [postgis-devel] [PostGIS] #1925: lwgeom_estimate.c: In function 'LWGEOM_gist_joinsel'   PostGIS
  • [postgis-devel] [PostGIS] #1925: lwgeom_estimate.c: In function 'LWGEOM_gist_joinsel'   PostGIS
  • [postgis-devel] [PostGIS] #1925: lwgeom_estimate.c: In function 'LWGEOM_gist_joinsel'   PostGIS
  • [postgis-devel] [PostGIS] #1925: lwgeom_estimate.c: In function 'LWGEOM_gist_joinsel'   PostGIS
  • [postgis-devel] [PostGIS] #1925: lwgeom_estimate.c: In function 'LWGEOM_gist_joinsel'   PostGIS
• [postgis-devel] PostGIS 1.5.5 Release   Paul Ramsey
  • [postgis-devel] PostGIS 1.5.5 Release   Paragon Corporation
  • [postgis-devel] PostGIS 1.5.5 Release   Sandro Santilli
• [postgis-devel] [PostGIS] #1668: ST_AsText, ST_AsEWKT under Windows 64-bit PostGIS 64-bit is all screwy   PostGIS
• [postgis-devel] [PostGIS] #1926: ST_Linecurve creates a strange multi-linestring   PostGIS
  • [postgis-devel] [PostGIS] #1926: ST_OffsetCurve creates a strange multi-linestring (was: ST_Linecurve creates a strange multi-linestring)   PostGIS
  • [postgis-devel] [PostGIS] #1926: ST_OffsetCurve creates a strange multi-linestring   PostGIS
• [postgis-devel] [PostGIS] #1927: Announce 1.5.5 on website   PostGIS
  • [postgis-devel] [PostGIS] #1927: Announce 1.5.5 on website   PostGIS
• [postgis-devel] Spatial relationship functions   Bborie Park
  • [postgis-devel] Spatial relationship functions   Pierre Racine
    • [postgis-devel] Spatial relationship functions   Bborie Park
  • [postgis-devel] Spatial relationship functions   Bborie Park
    • [postgis-devel] Spatial relationship functions   Bborie Park
  • [postgis-devel] Spatial relationship functions   Paul Ramsey
• [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] #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] #1928: st_geomfromgml multipoint issue   PostGIS
  • [postgis-devel] [PostGIS] #1928: st_geomfromgml multipoint issue   PostGIS
• [postgis-devel] [PostGIS] #1929: regression issue: ST_Polygon used to return simplest polygon   PostGIS
  • [postgis-devel] [PostGIS] #1929: regression issue: ST_Polygon used to return simplest polygon   PostGIS
  • [postgis-devel] [PostGIS] #1929: regression issue: ST_Polygon used to return simplest polygon   PostGIS
  • [postgis-devel] [PostGIS] #1929: regression issue: ST_Polygon used to return simplest polygon   PostGIS
• [postgis-devel] [PostGIS] #1930: Missing fields from tabblock table in tiger2011 census loader   PostGIS
• [postgis-devel] ST_Disjoint doesn't use an index   dustymugs
  • [postgis-devel] ST_Disjoint doesn't use an index   Paragon Corporation
    • [postgis-devel] ST_Disjoint doesn't use an index   Bborie Park
• [postgis-devel] [PostGIS] #1931: [raster] Some raster2pgsql options are still undocumented   PostGIS
  • [postgis-devel] [PostGIS] #1931: [raster] Some raster2pgsql options are still undocumented   PostGIS
  • [postgis-devel] [PostGIS] #1931: [raster] Some raster2pgsql options are still undocumented   PostGIS
• [postgis-devel] [PostGIS] #1932: index tablespace handing in raster2psql broken   PostGIS
  • [postgis-devel] [PostGIS] #1932: [raster] Index tablespace handing in raster2psql broken (was: index tablespace handing in raster2psql broken)   PostGIS
  • [postgis-devel] [PostGIS] #1932: [raster] Index tablespace handing in raster2psql broken   PostGIS
  • [postgis-devel] [PostGIS] #1932: [raster] Index tablespace handing in raster2psql broken   PostGIS
• [postgis-devel] [PostGIS] #1933: raster2psql command installed into /usr   PostGIS
  • [postgis-devel] [PostGIS] #1933: raster2psql command installed into /usr   PostGIS
  • [postgis-devel] [PostGIS] #1933: [raster] raster2psql command installed into /usr (was: raster2psql command installed into /usr)   PostGIS
  • [postgis-devel] [PostGIS] #1933: [raster] raster2psql command installed into /usr   PostGIS
  • [postgis-devel] [PostGIS] #1933: [raster] raster2psql command installed into /usr   PostGIS
  • [postgis-devel] [PostGIS] #1933: [raster] raster2psql command installed into /usr   PostGIS
  • [postgis-devel] [PostGIS] #1933: [raster] raster2psql command installed into /usr   PostGIS
  • [postgis-devel] [PostGIS] #1933: [raster] raster2psql command installed into /usr   PostGIS
  • [postgis-devel] [PostGIS] #1933: [raster] raster2psql command installed into /usr   PostGIS
  • [postgis-devel] [PostGIS] #1933: [raster] raster2psql command installed into /usr   PostGIS
• [postgis-devel] [PostGIS] #1934: Documentation of geometry() type modifier   PostGIS
  • [postgis-devel] [PostGIS] #1934: Documentation of geometry() type modifier   PostGIS
  • [postgis-devel] [PostGIS] #1934: Documentation of geometry() type modifier   PostGIS
• [postgis-devel] [PostGIS] #1935: Signal 11: Segmentation fault   PostGIS
• [postgis-devel] [PostGIS] #1936: gml xml string crashes postgresql server   PostGIS
  • [postgis-devel] [PostGIS] #1936: gml xml string crashes postgresql server   PostGIS
• [postgis-devel] [PostGIS] #1937: must specify "true" to st_length when casting to geography   PostGIS
  • [postgis-devel] [PostGIS] #1937: must specify "true" to st_length when casting to geography   PostGIS
• [postgis-devel] [PostGIS] #1858: [raster] Raster dataset functionality (was: Raster dataset functionality)   PostGIS
• [postgis-devel] [PostGIS] #1228: [raster] Add a ST_SetValues(raster, ARRAY[values], index DEFAULT 1) variant (was: [raster] Add a ST_AddBand(raster, ARRAY[values], index DEFAULT 1) variant)   PostGIS
• [postgis-devel] [PostGIS] #1938: [raster] Refactor ST_AddBand to add multiple new bands in one call   PostGIS
  • [postgis-devel] [PostGIS] #1938: [raster] Refactor ST_AddBand to add multiple new bands in one call   PostGIS
  • [postgis-devel] [PostGIS] #1938: [raster] Refactor ST_AddBand to add multiple new bands in one call   PostGIS
  • [postgis-devel] [PostGIS] #1938: [raster] Refactor ST_AddBand to add multiple new bands in one call   PostGIS
• [postgis-devel] [PostGIS] #1363: [raster] convert ST_AddBand array version to C   PostGIS
• [postgis-devel] [PostGIS] #1939: [raster] Remove custom data types that are only used for output.   PostGIS
  • [postgis-devel] [PostGIS] #1939: [raster] Remove custom data types that are only used for output.   PostGIS
  • [postgis-devel] [PostGIS] #1939: [raster] Remove custom data types that are only used for output.   PostGIS
• [postgis-devel] Regarding ticket #1939   Bborie Park
  • [postgis-devel] Regarding ticket #1939   Sandro Santilli
    • [postgis-devel] Regarding ticket #1939   Paragon Corporation
• [postgis-devel] Ticket #1363 ST_AddBand(raster, raster[], integer)   Bborie Park
• [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] #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] #1940: epsg:2065 projection is incorrect   PostGIS
• [postgis-devel] [PostGIS] #1941: supporting lwgeom_grid() in liblwgeom   PostGIS
• [postgis-devel] [PostGIS] #1942: Hudson and jenkins scripts move to PostGIS repo   PostGIS
  • [postgis-devel] [PostGIS] #1942: Hudson and jenkins scripts move to PostGIS repo   PostGIS
  • [postgis-devel] [PostGIS] #1942: Hudson and jenkins scripts move to PostGIS repo   PostGIS
  • [postgis-devel] [PostGIS] #1942: Hudson and jenkins scripts move to PostGIS repo   PostGIS
• [postgis-devel] [PostGIS] #1943: regress script doesn't work for 2.0 and trunk branch   PostGIS
  • [postgis-devel] [PostGIS] #1943: regress script doesn't work for 2.0 and trunk branch   PostGIS
  • [postgis-devel] [PostGIS] #1943: regress script doesn't work for 2.0 and trunk branch   PostGIS
• [postgis-devel] [PostGIS] #1800: Doxygen need some help to understand the new directory structure in trunk   PostGIS
• [postgis-devel] type agg_samealignment does not exist   Salvatore Larosa
  • [postgis-devel] type agg_samealignment does not exist   Bborie Park
    • [postgis-devel] type agg_samealignment does not exist   Salvatore Larosa

Last message date: Tue Jul 31 16:46:27 PDT 2012
Archived on: Fri Nov 10 09:26:16 PST 2017

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