| 02:37:14 | Yancho: | I need an advice on how to do a query please : I need to check what is the minimum extent i can use for a hospital point to cover all points in a map please? |
| 04:35:59 | martijn_: | hi, anyone experience with the isvalid functionality of postgis |
| 04:36:00 | martijn_: | ? |
| 04:36:31 | martijn_: | I have a linestring with duplicated coordinates, which is found valid by the isvalid function |
| 04:38:31 | martijn_: | in my opinion this should not be the case... am I correct? |
| 04:42:08 | martijn_: | this: "select isvalid( 'LINESTRING( 0 0, 1 1, 1 1, 1 1, 0 0 )' )" returns valid == true |
| 09:23:50 | racicot: | If I want to take an arbitrary shapefile ( not knowing all the attributes it contains ) and just load into postgis the geometry ( stripping out all the attributes or maybe just selecting a subset of the attributes ) into a pre-existing table... is that possible using shp2pgsql or ogr2ogr? |
| 09:27:48 | bitner: | don't think so with shp2pgsql, but using -sql flag with ogr2ogr I think you could |
| 09:29:12 | : | * racicot goes to look... thanks |
| 09:30:24 | racicot: | I thought that all you could do with the sql flag are "where" clause stuff... not selecting subsets of attributes... but I will check |
| 09:32:13 | bitner: | I *think* that is the key dif between -sql and -where |
| 09:32:46 | bitner: | I know someone on a nearby channel who could say for sure :- ) |
| 09:33:17 | racicot: | roger... always hate to bug that certain someone ;- ) |
| 09:36:47 | racicot: | hmmm, there is a -select flag on ogr2ogr, just not sure it will work on shapefiles... |
| 09:36:51 | : | * racicot goes to test |
| 09:36:57 | racicot: | thanks bitner |
| 09:37:20 | bitner: | now that I've saved the day, it's time to go fall asleep at a meeting |
| 09:37:37 | racicot: | happy dreams |
| 09:37:47 | bitner: | cheers |
| 09:51:58 | racicot: | way cool... -select does a fine job. |
| 09:52:41 | mloskot: | : ) |
| 09:53:10 | : | * racicot waves to mloskot |
| 09:53:29 | mloskot: | yoyo fellows |
| 09:53:48 | nhv: | oyoy |
| 09:54:04 | racicot: | mloskot: hows the thesis going? |
| 09:54:18 | : | * racicot thought he remembers mloskot working hard on that... |
| 09:54:21 | mloskot: | racicot: don't ask :- ) |
| 09:54:43 | racicot: | been there... done that... I know what you are going through ;- ) |
| 09:54:46 | mloskot: | it's been too long since I dropped regular studying |
| 10:08:01 | racicot: | hmmm, I take it back, the -select does not seem to work when importing shapefile ( atleast for me ), but ogr2ogr is pretty logical about adding attributes that match and leaving blank those that dont. |
| 10:08:26 | racicot: | probably good enough for what I need to do... |
| 13:59:42 | pimpaa: | does any1 ever have problems wiht loading psotgis layers in gvsig? |
| 13:59:53 | pimpaa: | i ahve a perfectly good layer |
| 13:59:59 | pimpaa: | that wont load in gvsig but will in qgis |
| 14:02:09 | mloskot: | pimpaa: perhaps gvsig issue |
| 14:02:37 | pimpaa: | it does have all the proper constraints |
| 14:02:40 | pimpaa: | works fine in qgis |
| 14:02:56 | mloskot: | I'd suggest to as on gvsig list |
| 14:03:01 | mloskot: | perhaps there is also #gvsig channel |
| 14:03:12 | mloskot: | It sounds like gvsig issue |
| 14:03:13 | mloskot: | to me |
| 14:03:25 | pimpaa: | thx mloskot |
| 14:03:28 | pimpaa: | tried the list already |
| 14:03:33 | pimpaa: | waiting for an answer :P |
| 14:03:38 | mloskot: | : ) |
| 14:03:44 | pimpaa: | no gvsig channel |
| 14:06:57 | pimpaa: | humn |
| 14:06:59 | pimpaa: | bizarre |
| 14:07:03 | pimpaa: | i have 2 versions of it |
| 14:07:11 | pimpaa: | one in each db |
| 14:07:15 | pimpaa: | the other one loads fine |
| 14:07:22 | pimpaa: | not sure why doesnt load in the other |
| 14:08:32 | mloskot: | check if in both tables/databses geometries have SRID set |
| 14:08:37 | mloskot: | not -1 but valid SRID |
| 14:08:41 | mloskot: | perhaps that's the case |
| 14:09:08 | mloskot: | Another issue may be with missing index or may be gvsig requires estimated spatial extent |
| 14:09:13 | mloskot: | and other statistics |
| 14:09:16 | mloskot: | so run VACCUUM |
| 14:09:21 | mloskot: | command |
| 14:09:34 | mloskot: | but IMO best is to ask gvsig folks |
| 14:10:43 | pimpaa: | got it |
| 15:01:02 | unlord: | hi |
| 15:06:45 | mloskot: | hi |
| 15:27:03 | unlord: | I'm just now trying out postgis |
| 15:27:13 | unlord: | I run gentoo linux, I saw there was a package for this |
| 15:27:33 | pimpaa: | g2g bye |
| 15:27:44 | unlord: | there is a geos USE flag |
| 15:28:02 | unlord: | is that something I want? |
| 15:35:51 | mloskot: | unlord: yes, you want geos |
| 15:37:10 | mloskot: | unlord: go to http://postgis.refractions.net -> documentation |
| 15:37:11 | sigq: | Title: PostGIS : Home ( at postgis.refractions.net ) |
| 15:37:29 | mloskot: | and check chapter 2.1 where you will see all postgis requirements |
| 15:37:38 | mloskot: | plus, compilation procedure |
| 15:37:42 | mloskot: | g'night |
| 16:12:56 | unlord: | okay |
| 16:20:11 | unlord: | Error #1: org.postgresql.util.PSQLException: ERROR: type "geometry" does not exist |
| 16:48:58 | unlord: | okay, that is fixed |