#POSTGIS IRC Log - 2008-07-14

For logs after Feb 3, 2007, all times are GMT-8. Prior logs are GMT-9.
Back to Logs
02:05:43 CIA-6: mcayland * r2844 /trunk/ ( configure.ac doc/Makefile.in ):
02:05:43 CIA-6: Apply some autoconf / Makefile changes from Olivier Courtin. XSLBASE should not
02:05:43 CIA-6: be checked for validity unless it has been explicitly specified using the
02:05:43 CIA-6: --with-xsldir option, and we also add some friendlier messages in the
02:05:43 CIA-6: documentation Makefile in case the DocBook stylesheets and/or xsltproc cannot be
02:05:46 CIA-6: found. Additionally, the configure --help output has been tidied up using the
02:05:48 CIA-6: AS_HELP_STRING macro.
02:42:50 CIA-6: mcayland * r2845 /trunk/configure.ac:
02:42:50 CIA-6: Change autoconf iconv-detection code so that ICONV_LDFLAGS is explicitly set in
02:42:50 CIA-6: the AC_CHECK_LIB( ) action-if-found section ( LIBS does not get automatically set
02:42:50 CIA-6: when action-if-found is set ). Thanks to Olivier Courtin for the bug report.
04:17:55 CIA-6: mcayland * r2846 /trunk/configure.ac: Modify autoconf stylesheet logic ( again ) to correctly distinguish between the case where a valid docbook stylesheet is found automatically and where it is explicitly specified using the --with-xsldir option.
13:52:50 CIA-6: pramsey * r2848 /branches/1.3/doc/html/style.css: Updated CSS from Dane Springmeyer
13:53:05 CIA-6: pramsey * r2849 /trunk/doc/html/style.css: Updated CSS from Dane Springmeyer
14:26:06 landonf: Dunno if anyone else has run into this, but it has been aborting our transactions and making me sad: http://code.google.com/p/postgis/issues/detail?id=43
14:26:07 sigq: Title: Issue 43 - postgis - Google Code ( at code.google.com )
15:08:13 pramsey: no, landof, I have not
15:08:25 pramsey: and I just loaded all of TIGER too... landonf
15:08:44 pramsey: however, you were gracious enough to submit a patch : )
15:09:27 landonf: You have to get lucky to hit it during a vacuum, but a big dataset provides lots of chances for luck = )
15:28:11 landonf: pramsey: Did you look into table inheritance, et al, for the tiger data?
15:28:37 pramsey: nope. you mean a partition?
15:29:35 landonf: Would be in effect a partition, but I'm looking at setting up all the county/state data to inherit from a single table so I can run queries across the entire set.
15:30:03 pramsey: right. should work fine, use statefp as your constraint key
15:30:52 pramsey: if you're truly running them over the entire set, it won't be any faster, but if you're always constraining on state, it could be better in good ways
15:31:39 landonf: *nod*
15:31:53 pramsey: unless you go whole hog, and pgpool it http://pgpool.projects.postgresql.org/
15:31:54 landonf: Not truly using the whole set, and wanted to use constraint exclusion to avoid even touching most of the tables.
15:31:55 sigq: Title: pgpool-II README ( at pgpool.projects.postgresql.org )
19:53:44 ahughes: can anyone suggest how I can store a node/graph ( route ) network?
19:54:44 mleslie: Do you need to preserve/enforce the network topology?
19:57:31 ahughes: ummmmm, depends what you mean by preserve/enforce.... *ideally* we can edit the 'node network' with qgis or uDig
19:58:30 ahughes: i.e. the data will not be static
19:59:25 mleslie: Right. You can simply store it as linestrings in PostGIS, but that makes editing difficult. I'm not aware of networked editing functionality in uDig of QGIS.
19:59:48 mleslie: ie. if you move the node of one linestring, you must manually move all other nodes.
20:00:18 ahughes: yes - plus networks normally have rules :'(
20:01:26 ahughes: I'm sure it's possible to put some postgres function to 'snap' points on linestrings to a point on another linestring to form a network.
20:02:20 mleslie: PostGIS does support basic topology, it might be up to the task: http://postgis.refractions.net/support/wiki/index.php?PostgisTopology
20:02:21 sigq: Title: PostGIS Wiki : Postgis Topology ( at postgis.refractions.net )
20:06:10 ahughes: cheers mleslie
22:58:01 CIA-6: kneufeld * r2850 /trunk/doc/ ( 13 files in 2 dirs ):
22:58:01 CIA-6: Started migration of the functions in reference.xml using the <variablelist>
22:58:01 CIA-6: concept to a new "reference_new.xml" using DocBook's <refentry> concept. Once
22:58:01 CIA-6: migration is complete, reference.xml will be removed and reference_new.xml will
22:58:01 CIA-6: be renamed to reference.xml. The included template.xml file is not used, except
22:58:01 CIA-6: to provide example usage of DocBook's refentry tag.