November 2008 Archives by thread

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

Starting: Mon Nov 3 05:55:57 PST 2008
Ending: Fri Nov 28 09:36:11 PST 2008
Messages: 167

• [postgis-devel] postgis.refractions.net / svn.refractions.net currently unavailable   Mark Cave-Ayland
  • [postgis-devel] postgis.refractions.net / svn.refractions.netcurrently unavailable   Obe, Regina
    • [postgis-devel] postgis.refractions.net / svn.refractions.netcurrently unavailable   Kevin Neufeld
• [postgis-devel] Impatient on 1.3.4   Mark Cave-Ayland
  • [postgis-devel] Impatient on 1.3.4   Mark Cave-Ayland
  • [postgis-devel] Impatient on 1.3.4   Obe, Regina
    • [postgis-devel] Impatient on 1.3.4   Mark Cave-Ayland
      • [postgis-devel] Impatient on 1.3.4   Obe, Regina
      • [postgis-devel] Impatient on 1.3.4   Obe, Regina
• [postgis-devel] Trunk - Mac OSX - libiconv   Mark Cave-Ayland
• [postgis-devel] Issue 65 in postgis: ST_AsGML kills the backend when fed a CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 65 in postgis: ST_AsGML kills the backend when fed a CIRCULAR STRING   codesite-noreply at google.com
    • [postgis-devel] Issue 65 in postgis: ST_AsGML kills the backend when fed a CIRCULAR STRING   Courtin Olivier
      • [postgis-devel] Issue 65 in postgis: ST_AsGML kills the backend when fed a CIRCULAR STRING   Mark Cave-Ayland
      • [postgis-devel] Issue 65 in postgis: ST_AsGML kills the backend when fed a CIRCULAR STRING   Courtin Olivier
  • [postgis-devel] Issue 65 in postgis: ST_AsGML kills the backend when fed a CIRCULAR STRING   codesite-noreply at google.com
• [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
  • [postgis-devel] Issue 66 in postgis: ST_Dump kills backend when fed CIRCULAR STRING   codesite-noreply at google.com
• [postgis-devel] Issue 67 in postgis: new tablespace parameter for shp2pgsql   codesite-noreply at google.com
  • [postgis-devel] Issue 67 in postgis: new tablespace parameter for shp2pgsql   codesite-noreply at google.com
    • [postgis-devel] Issue 67 in postgis: new tablespace parameter for shp2pgsql   Kevin Neufeld
• [postgis-devel] Issue 68 in postgis: ST_Shift_Longitude doesn't work with MULTIPOINT   codesite-noreply at google.com
  • [postgis-devel] Issue 68 in postgis: ST_Shift_Longitude doesn't work with MULTIPOINT   codesite-noreply at google.com
  • [postgis-devel] Issue 68 in postgis: ST_Shift_Longitude doesn't work with MULTIPOINT   codesite-noreply at google.com
  • [postgis-devel] Issue 68 in postgis: ST_Shift_Longitude doesn't work with MULTIPOINT   codesite-noreply at google.com
  • [postgis-devel] Issue 68 in postgis: ST_Shift_Longitude doesn't work with MULTIPOINT   codesite-noreply at google.com
• [postgis-devel] Issue 69 in postgis: ST_Translate crashes when fed circular string   codesite-noreply at google.com
  • [postgis-devel] Issue 69 in postgis: ST_Translate crashes when fed circular string   codesite-noreply at google.com
  • [postgis-devel] Issue 69 in postgis: ST_Translate crashes when fed circular string   codesite-noreply at google.com
  • [postgis-devel] Issue 69 in postgis: ST_Translate crashes when fed circular string   codesite-noreply at google.com
  • [postgis-devel] Issue 69 in postgis: ST_Translate crashes when fed circular string   codesite-noreply at google.com
  • [postgis-devel] Issue 69 in postgis: ST_Translate crashes when fed circular string   codesite-noreply at google.com
• [postgis-devel] AsGML & AsGeoJson patches   Courtin Olivier
  • [postgis-devel] AsGML & AsGeoJson patches   Paul Ramsey
    • [postgis-devel] AsGML & AsGeoJson patches   Mark Cave-Ayland
      • [postgis-devel] AsGML & AsGeoJson patches   Courtin Olivier
    • [postgis-devel] AsGML & AsGeoJson patches   Obe, Regina
      • [postgis-devel] AsGML & AsGeoJson patches   Kevin Neufeld
      • [postgis-devel] AsGML & AsGeoJson patches   Paul Ramsey
      • [postgis-devel] AsGML & AsGeoJson patches   Kevin Neufeld
      • [postgis-devel] AsGML & AsGeoJson patches   Courtin Olivier
• [postgis-devel] Fwd: [postgis-users] 1.3.4rc2 Released   Paul Ramsey
  • [postgis-devel] Re: [postgis-users] 1.3.4rc2 Released   Paul Ramsey
    • [postgis-devel] Re: [postgis-users] 1.3.4rc2 Released   Obe, Regina
      • [postgis-devel] Re: [postgis-users] 1.3.4rc2 Released   Mark Cave-Ayland
      • [postgis-devel] Re: [postgis-users] 1.3.4rc2 Released   Obe, Regina
      • [postgis-devel] Re: [postgis-users] 1.3.4rc2 Released   Mark Cave-Ayland
      • [postgis-devel] Re: [postgis-users] 1.3.4rc2 Released   Paul Ramsey
• [postgis-devel] Issue 70 in postgis: ST_NPoints Crashes with Curves   codesite-noreply at google.com
  • [postgis-devel] Issue 70 in postgis: ST_NPoints Crashes with Curves   codesite-noreply at google.com
  • [postgis-devel] Issue 70 in postgis: ST_NPoints Crashes with Curves   codesite-noreply at google.com
• [postgis-devel] Missing commits in PostGIS trunk compared to 1.3 branch   Mark Cave-Ayland
  • [postgis-devel] Missing commits in PostGIS trunk compared to 1.3 branch   Paul Ramsey
• [postgis-devel] Issue 48 in postgis: Broken scroll cursors with gist index   codesite-noreply at google.com
• [postgis-devel] Issue 58 in postgis: bounding box of circular string is incorrect   codesite-noreply at google.com
• [postgis-devel] Issue 47 in postgis: Avoiding notices upon import of lwpostgis.sql   codesite-noreply at google.com
• [postgis-devel] 8.4+1.3   Paul Ramsey
  • [postgis-devel] 8.4+1.3   Mark Cave-Ayland
    • [postgis-devel] 8.4+1.3   Paul Ramsey
• [postgis-devel] Issue 62 in postgis: PgSQL 8.4 Support in PostGIS 1.3   codesite-noreply at google.com
• [postgis-devel] Issue 35 in postgis: Comments on Postgis Functions   codesite-noreply at google.com
  • [postgis-devel] Issue 35 in postgis: Comments on Postgis Functions   codesite-noreply at google.com
  • [postgis-devel] Issue 35 in postgis: Comments on Postgis Functions   codesite-noreply at google.com
• [postgis-devel] Proposal for 1.3.4 RC2   Mark Cave-Ayland
  • [postgis-devel] Proposal for 1.3.4 RC2   Obe, Regina
    • [postgis-devel] Proposal for 1.3.4 RC2   Mark Cave-Ayland
  • [postgis-devel] Proposal for 1.3.4 RC2 (don't we mean RC3)   Obe, Regina
    • [postgis-devel] Proposal for 1.3.4 RC2 (don't we mean RC3)   Mark Cave-Ayland
• [postgis-devel] Association for Geographic Information Technical SIG event   Cooper, Alexander P R
• [postgis-devel] 1.3.4 RC3   Obe, Regina
  • [postgis-devel] 1.3.4 RC3   Mark Cave-Ayland
• [postgis-devel] Issue 31 in postgis: Negative distance buffer   codesite-noreply at google.com
  • [postgis-devel] Issue 31 in postgis: Negative distance buffer   codesite-noreply at google.com
• [postgis-devel] Issue 71 in postgis: Update section 4.2 of docs to describe manual adding to geometry columns   codesite-noreply at google.com
  • [postgis-devel] Issue 71 in postgis: Update section 4.2 of docs to describe manual adding to geometry columns   codesite-noreply at google.com
• [postgis-devel] RE: [postgis-users] PostGIS 1.3.4 RC3 released   Obe, Regina
• [postgis-devel] Release notes for 1.3.4   Mark Cave-Ayland
  • [postgis-devel] Release notes for 1.3.4   Obe, Regina
    • [postgis-devel] Release notes for 1.3.4   Mark Cave-Ayland
      • [postgis-devel] Release notes for 1.3.4   Paul Ramsey
      • [postgis-devel] Release notes for 1.3.4   Kevin Neufeld
      • [postgis-devel] Release notes for 1.3.4   Obe, Regina
      • [postgis-devel] Release notes for 1.3.4   Obe, Regina
      • [postgis-devel] Release notes for 1.3.4   Mark Cave-Ayland
      • [postgis-devel] Release notes for 1.3.4   Mark Cave-Ayland
      • [postgis-devel] Release notes for 1.3.4   Obe, Regina
      • [postgis-devel] Release notes for 1.3.4   Mark Cave-Ayland
      • [postgis-devel] Release notes for 1.3.4   Obe, Regina
      • [postgis-devel] Release notes for 1.3.4   Paul Ramsey
• [postgis-devel] ST_Transform doesn't need Proj support?   Obe, Regina
  • [postgis-devel] ST_Transform doesn't need Proj support?   Mark Cave-Ayland
    • [postgis-devel] ST_Transform doesn't need Proj support?   Obe, Regina
    • [postgis-devel] ST_Transform doesn't need Proj support?   Obe, Regina
• [postgis-devel] Toronto Code Sprint 2009   Paul Ramsey
• [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
  • [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
  • [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
  • [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
  • [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
  • [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
  • [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
  • [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
  • [postgis-devel] Issue 72 in postgis: ST_Estimated_Extent sometimes returns null if table exists but not in current schema   codesite-noreply at google.com
• [postgis-devel] Issue 73 in postgis: ST_Force_Collection crashes with CIRCULARSTRING   codesite-noreply at google.com
  • [postgis-devel] Issue 73 in postgis: ST_Force_Collection crashes with CIRCULARSTRING   codesite-noreply at google.com
  • [postgis-devel] Issue 73 in postgis: ST_Force_Collection crashes with CIRCULARSTRING   codesite-noreply at google.com
• [postgis-devel] PGRaster branch   strk
  • [postgis-devel] PGRaster branch   Mark Cave-Ayland
• [postgis-devel] Issue 74 in postgis: AddGeometryColumn does not detect search_path properly   codesite-noreply at google.com
  • [postgis-devel] Issue 74 in postgis: AddGeometryColumn does not detect search_path properly   codesite-noreply at google.com
• [postgis-devel] PostGIS 1.3.4 Released   Paul Ramsey
  • [postgis-devel] RE: [postgis-users] PostGIS 1.3.4 Released   Obe, Regina
• [postgis-devel] Now that we have moved on - getting regression failure on 1.4   Obe, Regina
  • [postgis-devel] Now that we have moved on - getting regression failure on 1.4   Mark Cave-Ayland
• [postgis-devel] What feeds this Change Log and Release date is wrong   Obe, Regina
  • [postgis-devel] What feeds this Change Log and Release date is wrong   Mark Cave-Ayland
    • [postgis-devel] What feeds this Change Log and Release date is wrong   Paul Ramsey
      • [postgis-devel] What feeds this Change Log and Release date iswrong   Obe, Regina
      • [postgis-devel] What feeds this Change Log and Release date iswrong   Paul Ramsey
• [postgis-devel] README patch and \set ON_ERROR_STOP   strk
  • [postgis-devel] README patch and \set ON_ERROR_STOP   Mark Cave-Ayland
    • [postgis-devel] README patch and \set ON_ERROR_STOP   strk
• [postgis-devel] trunk: ERROR on spatially-enabling a database   strk
  • [postgis-devel] Re: trunk: ERROR on spatially-enabling a database   strk
    • [postgis-devel] Re: trunk: ERROR on spatially-enabling a database   strk
      • [postgis-devel] Re: trunk: ERROR on spatially-enabling a database   Mark Cave-Ayland
      • [postgis-devel] Re: trunk: ERROR on spatially-enabling a database   strk
      • [postgis-devel] Re: trunk: ERROR on spatially-enabling a database   Mark Cave-Ayland
    • [postgis-devel] Re: trunk: ERROR on spatially-enabling a database   Mark Cave-Ayland
      • [postgis-devel] Re: trunk: ERROR on spatially-enabling a database   strk
      • [postgis-devel] Re: trunk: ERROR on spatially-enabling a database   Mark Cave-Ayland
• [postgis-devel] regress_bdpoly failed   strk
  • [postgis-devel] regress_bdpoly failed   Mark Cave-Ayland
    • [postgis-devel] regress_bdpoly failed   strk
      • [postgis-devel] regress_bdpoly failed   Cooper, Alexander P R
• [postgis-devel] Issue 51 in postgis: Enhancement to ST_Summary to include info about invalid geometries   codesite-noreply at google.com
  • [postgis-devel] Issue 51 in postgis: Enhancement to ST_Summary to include info about invalid geometries   codesite-noreply at google.com
    • [postgis-devel] Compilation problems on OpenSUSE 11   Obe, Regina
      • [postgis-devel] Compilation problems on OpenSUSE 11   Mark Cave-Ayland
      • [postgis-devel] Compilation problems on OpenSUSE 11   Obe, Regina
  • [postgis-devel] Issue 51 in postgis: Enhancement to ST_Summary to include info about invalid geometries   codesite-noreply at google.com
  • [postgis-devel] Issue 51 in postgis: Enhancement to ST_Summary to include info about invalid geometries   codesite-noreply at google.com
  • [postgis-devel] Issue 51 in postgis: Enhancement to ST_Summary to include info about invalid geometries   codesite-noreply at google.com
  • [postgis-devel] Issue 51 in postgis: Enhancement to ST_Summary to include info about invalid geometries   codesite-noreply at google.com
    • [postgis-devel] Issue 51 in postgis: Enhancement to ST_Summary toinclude info about invalid geometries   Obe, Regina
  • [postgis-devel] Issue 51 in postgis: Enhancement to ST_Summary to include info about invalid geometries   codesite-noreply at google.com
• [postgis-devel] PIP short circuits   Kevin Neufeld
  • [postgis-devel] PIP short circuits   Paul Ramsey
• [postgis-devel] Issue 75 in postgis: Enhancement to PIP short circuit   codesite-noreply at google.com
• [postgis-devel] Issue 76 in postgis: ST_DumpPoints - I think we said we would add to TODO   codesite-noreply at google.com
• [postgis-devel] Toronto Code Sprint   Paul Ramsey
• [postgis-devel] Issue 77 in postgis: make check - is there anyway for us to delete postgis_reg db when load fails   codesite-noreply at google.com
  • [postgis-devel] Issue 77 in postgis: make check - is there anyway for us to delete postgis_reg db when load fails   strk
    • [postgis-devel] Issue 77 in postgis: make check - is there anywayfor us to delete postgis_reg db when load fails   Obe, Regina
      • [postgis-devel] Issue 77 in postgis: make check - is thereanywayfor us to delete postgis_reg db when load fails   Obe, Regina
      • [postgis-devel] Issue 77 in postgis: make check - is thereanywayfor us to delete postgis_reg db when load fails   strk
      • [postgis-devel] Issue 77 in postgis: make check - is there anywayfor us to delete postgis_reg db when load fails   strk
  • [postgis-devel] Issue 77 in postgis: make check - is there anyway for us to delete postgis_reg db when load fails   codesite-noreply at google.com

Last message date: Fri Nov 28 09:36:11 PST 2008
Archived on: Fri Nov 10 09:25:58 PST 2017

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