| 07:08:14 | darkblue_B: | I have a data set that is not supposed to have any Z data, 2d |
| 07:08:31 | darkblue_B: | can I check for rougue 3d somehow ? |
| 07:08:43 | darkblue_B: | MULTIPOLYGON |
| 07:15:09 | darkblueB_: | select ST_CoordDim( the_geom ), gid, name from zips00 where ST_CoordDim( the_geom ) > 2; |
| 07:15:13 | darkblueB_: | I tried that |
| 07:23:32 | CIA-34: | mloskot * r2311 /trunk/nmake.opt: Added _NMAKE_VER 9.00.21022.08 to nmake.opt. Fixed bug with using BUILD_DEBUG instead of BUILD_BATCH in nmake.opt. |
| 07:41:07 | bitner: | darkblueB_: if you just want to make sure your data is all 2d just update zips00 set the_geom=st_force2d( the_geom ); |
| 07:49:23 | darkblueB_: | ok, I'll try that bitner |
| 07:49:40 | darkblueB_: | I wanted to know if there was any z data though |
| 07:49:58 | darkblueB_: | I have a new geoserver, and its balking |
| 07:50:04 | darkblueB_: | on a parcticular table |
| 07:50:37 | darkblueB_: | aaime is suggesting that it is z data |
| 07:50:41 | darkblueB_: | but I dont think there is any |
| 07:50:54 | darkblueB_: | so actually is important to prove if there is any or not |
| 07:51:33 | darkblueB_: | I could create a new table.. create table new as select blah, st_force2d( the_geom ) from zips00; |
| 07:51:43 | darkblueB_: | and try the new table |
| 07:52:40 | darkblueB_: | adding the geom cols entry by hand then |
| 08:19:20 | darkblueB_: | oh yeah when I do that the new geom column ends up being named st_force_2d |
| 08:19:29 | darkblueB_: | bother.. I just changed that name afterwards |
| 08:19:44 | darkblueB_: | some syntax to avoid that no doubt |
| 08:42:52 | bitner: | st_force2d( the_geom ) as whatevernameyouwant |
| 08:53:01 | darkblueB_: | ohhhh yeah |