#POSTGIS IRC Log - 2009-06-05

For logs after Feb 3, 2007, all times are GMT-8. Prior logs are GMT-9.
Back to Logs
00:21:00 theuns: hi all
00:21:41 theuns: in what format is the dbf file that is created by postgis when you create shapefile from postgis?
00:22:17 theuns: more correct what version dbf , DBASE III or DBASE IV
00:23:21 theuns: I could always read the dbf files with the borland database engine , but files created by postgis , i cant read the data
00:51:17 simplexio: no idea, but maybe file commands tells you that
00:51:37 simplexio: or specs from postgis homepage
01:11:35 CIA-34: strk * r2539 /trunk/ ( ChangeLog.svn Makefile.am ): Allow generating ChangeLog from external build tree
01:14:12 theuns: ok thanks
01:23:42 CIA-34: strk * r2540 /trunk/source/ ( 4 files in 3 dirs ): Fix deletion of void pointer in IntervalRTreeLeafNode, document ownership, fix callers tracking allocations to avoid leaks. Fixes bug #227.
01:26:41 sigq: geosfeed: Ticket #227 ( defect closed ): Deleting 'void*' is undefined in IntervalRTreeLeafNode class. <http://trac.osgeo.org/geos/ticket/227#comment:5>
01:31:22 CIA-34: strk * r2541 /trunk/source/headers/geos/geom.h: Fix doxygen link
01:31:44 CIA-34: strk * r2542 /trunk/source/headers/geos/geom.h: typo in doxygen index page
01:36:42 sigq: geosfeed: Ticket #184 ( defect updated ): Some parts of documented C++ API do not available for public usage <http://trac.osgeo.org/geos/ticket/184#comment:5>
01:48:46 sigq: geosfeed: Ticket #86 ( defect updated ): Possible memory leaks caused by LineString constructor <http://trac.osgeo.org/geos/ticket/86#comment:43>
02:19:02 CIA-34: strk * r2543 /trunk/source/ ( 16 files in 2 dirs ): Add port info and introduce header exposion info. Relate op results partially in JTS-1.7 still.
02:59:31 CIA-34: strk * r2544 /trunk/source/ ( 15 files in 2 dirs ): Port info in the geomgraph package ( unfinished ); fix compiler warning in GeometryGraph and make code more readable;
03:38:34 sigq: geosfeed: Ticket #86 ( defect updated ): Possible memory leaks caused by LineString constructor <http://trac.osgeo.org/geos/ticket/86#comment:44>
03:57:26 sigq: geosfeed: Ticket #86 ( defect updated ): Possible memory leaks caused by LineString constructor <http://trac.osgeo.org/geos/ticket/86#comment:45>
04:03:30 CIA-34: strk * r2545 /trunk/source/ ( 21 files in 2 dirs ): Complete port info in geomgraph package
04:37:52 CIA-34: strk * r2546 /trunk/source/ ( 3 files in 2 dirs ): Add support for custom BoundaryNodeRule bringing GeometryGraph to JTS-1.10
04:59:42 sigq: geosfeed: Ticket #86 ( defect updated ): Possible memory leaks caused by LineString constructor <http://trac.osgeo.org/geos/ticket/86#comment:46>
05:37:29 CIA-34: strk * r2547 /trunk/source/ ( 8 files in 6 dirs ): added BoundaryNodeRule capability to EdgeEnds
05:40:25 CIA-34: strk * r2548 /trunk/source/ ( 3 files in 2 dirs ): geomgraph package fully sync'ed to JTS-1.10 now
06:48:41 heizpilz: hello everybody
06:49:16 heizpilz: has anyone an idea, why the following loop stops with the error 'invalid geometry'?
06:49:19 heizpilz: for newWay in ( select * from ways where x1 = ( select x from waypoints where num = 1 ) and y1 = ( select y from waypoints where num = 1 ) ) loop
06:49:22 heizpilz: raise notice 'result : %', newWay;
06:49:42 heizpilz: end loop;
08:06:25 CIA-34: mloskot * r4137 /spike/wktraster/scripts/rtreader.py: [wktraster] Added query_pixel_types( ) function to rtreader.RasterReader class.
08:06:54 CIA-34: mloskot * r4138 /spike/wktraster/scripts/rtpixdump.py: [wktraster] tidy up
08:11:14 CIA-34: mloskot * r4139 /spike/wktraster/scripts/rtrowdump.py:
08:11:14 CIA-34: [wktraster] Added rtrowdump.py tool that reads single tile/block/raster stored
08:11:15 CIA-34: as single row/field in WKT Raster table to GeoTIFF file using GDAL Python
08:11:19 CIA-34: bindings and rtreader.RasterReader class. It is helpful to debug gdal2wktraster
08:11:21 CIA-34: jobs, check it does not break rasters while loading as well as check if pixels
08:11:23 CIA-34: of padding are appended correctly.
08:25:06 CIA-34: mloskot * r4140 /spike/wktraster/scripts/rtrowdump.py: [wktraster] in rtrowdump.py added pt2numpy( ) to translate WKT Raster pixel type to NumPy data type.
08:28:00 CIA-34: mloskot * r4141 /spike/wktraster/scripts/rtrowdump.py: [wktraster] update usage message for rtrowdump.py
08:45:30 CIA-34: mloskot * r4142 /spike/wktraster/scripts/rtrowdump.py: [wktraster] rtrowdump.py: enabled --where option to pass WHERE condition.
09:02:26 CIA-34: mloskot * r4143 /spike/wktraster/scripts/ ( rtreader.py rtrowdump.py ): [wktraster] Added logging property to rtreader.RasterReader class.
09:08:32 CIA-34: mloskot * r4144 /spike/wktraster/scripts/ ( rtreader.py rtrowdump.py ): [wktraster] rtreader.RasterReader: simplified handling class properties
09:30:41 CIA-34: mloskot * r4145 /spike/wktraster/scripts/rtrowdump.py: [wktraster] rtrowdump.py: use tuple for raster dim
09:46:11 CIA-34: strk * r2549 /trunk/source/ ( 4 files in 4 dirs ): Boundary Node Rule support in relateOp. JTS-1.10.
09:58:36 CIA-34: strk * r2550 /trunk/source/ ( 2 files in 2 dirs ): JTS-1.10 sync
10:08:08 CIA-34: strk * r2551 /trunk/source/headers/geos/geomgraph/EdgeNodingValidator.h: Add missing static function
10:14:13 CIA-34: strk * r2552 /trunk/source/ ( 2 files in 2 dirs ): JTS-1.10 OverlayOp
10:39:00 CIA-34: pracine * r4146 /spike/wktraster/rt_pg/rtpostgis.sql.in.c: [wktraster] Renamed st_lib_version( ) to postgis_raster_lib_version( ) & rt_lib_build_date( ) to postgis_raster_lib_build_date( )
10:51:28 vauxia_: Is there any way to do something like this?
10:51:42 vauxia_: CREATE TABLE foo ( bar geometry );
10:52:13 vauxia_: DoWhatAddGeometryColumn( )WasGoingToDo;
10:52:15 vauxia_: ?
10:52:18 vauxia_: ?
11:12:18 vauxia_: I'm writing support for the Drupal CMS ( http://drupal.org/project/geo )
11:12:21 sigq: Title: Geo | drupal.org ( at drupal.org )
11:12:50 vauxia_: It allows you to define db columns in an array, and its schema api will create them for you.
11:13:08 bitner: AddGeometryColumn does two main things
11:13:19 vauxia_: It would be a big win if I could just tell it "type" => geometry
11:13:31 vauxia_: ... and then post-process to fix things up.
11:13:36 bitner: 1: adds constraints on table for geometry type ( ie POLYGON ) and srid
11:13:46 bitner: 2: adds a record to the geometry_columns table
11:14:04 bitner: neither of which are necessary for PostGIS
11:14:15 bitner: #1 can be useful though just to keep the data consistent
11:14:36 bitner: #2 follows the specs for spatial features for SQL and is used by some clients
11:15:14 bitner: for the record, I have been a heavy user of PostGIS for several years and most of my tables have neither #1 or #2
11:15:34 vauxia_: really?!
11:15:40 bitner: and for my use case that is just fine
11:16:09 vauxia_: do you simply do what I described? "CREATE TABLE foo ( bar geometry );"
11:16:16 bitner: yep
11:18:00 bitner: I believe there are some new management functions in 1.4 that can help you add #1 / #2 after the fact
11:18:13 bitner: probe_geometry_columns( ) or something like that
11:20:44 vauxia_: sweet! this helps tremendously!
11:21:15 vauxia_: I was having to manage a lot of CRUD by myself, and this will make things like, a million times easier : )
16:51:33 CIA-34: strk * r2553 /trunk/source/ ( 7 files in 2 dirs ): Complete port info and headers exposion for operation::distance package
22:17:51 mdance: hey everyone! i have some pipeline buffers in a postgis database and i was wondering what is the best approach to displaying them dynamically with openlayers? for example user 1 logs in and has access to certain buffers, i would like to overlay them onto openlayers
23:46:28 ue: mdance, mapscript