| 06:23:48 | vdeparday: | hello |
| 06:24:12 | vdeparday: | I'd like to use graduated point symbol |
| 06:24:44 | vdeparday: | points with a size proportionnal to an attribute |
| 06:25:20 | vdeparday: | I've seen that I could do SIZE [attributeName] |
| 06:25:26 | vdeparday: | but I can use a formula? |
| 06:26:12 | vdeparday: | Has this improvement been implemented ( http://mapserver.org/development/rfc/ms-rfc-49.html ) ? |
| 06:26:13 | sigabrt: | Title: MS RFC 49: Symbology, Labeling, and Cartography Improvements MapServer 5.4.2 documentation ( at mapserver.org ) |
| 06:26:28 | vdeparday: | same moment : ) |
| 06:26:32 | vdeparday: | yes I've seen that |
| 06:26:42 | vdeparday: | but I didn't find a roadmap for it |
| 06:30:03 | ue: | well you can precompute the size in your GIS editor and just use the prepared "size" as a column value |
| 06:30:17 | ue: | http://mapserver.org/development/rfc/ms-rfc-49.html, yes but only for AGG renderer |
| 06:32:02 | ue: | vdeparday, if you want to compute the size on the fly based on some criteria ... using a spatial database is an option |
| 06:33:09 | ue: | vdeparday, open your layers with http://mapserver.org/input/vector/ogr.html , you can do some SQL logic with it |
| 06:33:11 | sigabrt: | Title: OGR MapServer 5.4.2 documentation ( at mapserver.org ) |
| 06:33:49 | vdeparday: | I'm having a look |
| 06:35:15 | vdeparday: | ok I see what you mean, I would do my calculation in my SQLquery in the DATA definition? |
| 06:35:35 | vdeparday: | and then use the result of the query directly with SIZE |
| 06:35:55 | ue: | yes |
| 06:37:00 | vdeparday: | ok, it sounds like a good alternative, I just to load my data in PostGIS |
| 06:37:16 | ue: | you can open a shape file with OGR |
| 06:37:36 | ue: | if you are using shapefiles at the moment |
| 06:38:04 | vdeparday: | I am |
| 06:38:16 | vdeparday: | so I can do SQL query directly on my shapefile |
| 06:38:24 | vdeparday: | in the DATA parameter |
| 06:38:49 | ue: | yes |
| 06:39:12 | vdeparday: | ok I will try that |
| 06:39:14 | vdeparday: | thanks |
| 06:39:21 | ue: | CONNECTIONTYPE OGR |
| 06:39:21 | ue: | CONNECTION "data/shppoly" |
| 06:39:50 | vdeparday: | thanks, I've just found it example 4 on the page |
| 06:40:08 | vdeparday: | I'll give it a try |
| 06:40:09 | vdeparday: | thanks |
| 06:54:19 | vdeparday: | ue, how do I have to write my sql request if I have just one straight shapefile with .shp and .dbf |
| 06:54:38 | vdeparday: | I don't have to do a join between the dbf and shp |
| 06:55:49 | vdeparday: | I tried just SELECT attribute FROM shapefilename |
| 06:56:00 | vdeparday: | and then use the attribute |
| 06:56:07 | vdeparday: | in the SIZE |
| 06:56:44 | ue: | and ? |
| 06:56:58 | vdeparday: | it didn't work |
| 06:57:24 | vdeparday: | I realize that I may have to take the bracket off from my attribute name |
| 07:02:15 | vdeparday: | I must do something wrong |
| 07:03:49 | vdeparday: | I hae |
| 07:03:56 | vdeparday: | CONNECTIONTYPE OGR |
| 07:04:11 | vdeparday: | CONNECTION "shapefilename" |
| 07:05:18 | vdeparday: | DATA 'select attribute from shapefilename' |
| 07:05:31 | vdeparday: | CLASSITEM 'attribute' |
| 07:06:02 | vdeparday: | other stuff |
| 07:06:07 | vdeparday: | and |
| 07:06:16 | vdeparday: | SIZE attribute |
| 07:06:37 | vdeparday: | is that supposed to work like that? |
| 07:06:43 | vdeparday: | I may have a typo somewhere |
| 07:09:55 | vdeparday: | ue, is it supposed to work like that? |
| 07:10:07 | vdeparday: | if it is I will look for an error somewhere |
| 07:10:24 | vdeparday: | but I can't see any so far |
| 07:16:06 | vdeparday: | I guess I have to add some geometry column in my query |
| 08:20:47 | FrankW: | vdeparday: in the data statement, you should just have the basename of the shapefile. |
| 08:20:57 | FrankW: | So not /data/abc.shp - just abc. |
| 08:21:04 | vdeparday: | right |
| 08:21:06 | vdeparday: | it's what I have |
| 08:21:13 | FrankW: | ok |
| 08:21:20 | vdeparday: | in the select |
| 08:21:22 | FrankW: | and do you get an error message? |
| 08:21:40 | vdeparday: | the thing is that it's embedded in an application |
| 08:21:52 | vdeparday: | and I would have to test them with shp2img |
| 08:21:57 | FrankW: | then you need to find a way of testing it in isolation. |
| 08:22:06 | vdeparday: | but I don't have it install here |
| 08:22:23 | vdeparday: | I wanted to grab the packaged but I got an error and I didn't have time to look into it |
| 08:22:50 | vdeparday: | on ubuntu karmic |
| 08:23:02 | FrankW: | oh - well, us making wild assed guesses as to the problem does not seem very productive. |
| 08:23:09 | vdeparday: | right |
| 08:23:16 | vdeparday: | it was just to make sure |
| 08:23:23 | vdeparday: | that I was not missing something obvious |
| 08:23:37 | vdeparday: | because the example in the doc is with a JOIN |
| 08:23:54 | vdeparday: | so it's normal that I put only the attribute in the select |
| 08:24:00 | vdeparday: | no geometry column |
| 08:25:53 | vdeparday: | I will install mapserver locally and test it with shp2img |
| 08:25:57 | vdeparday: | see if I get something |
| 08:26:20 | vdeparday: | thanks FrankW |
| 08:40:16 | FrankW: | vdeparday: in OGR joins the geometry is carried along without explicitly referencing it. |
| 08:40:36 | vdeparday: | ok |
| 09:56:43 | vdeparday: | FrankW, I have some better things for you from running shp2img |
| 09:57:19 | vdeparday: | msOGRFileOpen( ): OGR error. Open failed for OGR connection in layer `csd_prev_low_inco_centroid_SDG'. File not found or unsupported format. |
| 09:57:37 | vdeparday: | the thing is that I had DATA "shapefilename" |
| 09:58:09 | vdeparday: | and I replaced by CONNECTIONTYPE OGR |
| 09:58:23 | vdeparday: | CONNECTION 'shapefilename' |
| 09:58:56 | vdeparday: | DATA 'Select attribute From shapefilename' |
| 09:59:03 | vdeparday: | to test |
| 09:59:32 | vdeparday: | and it worked when use straight shapefile and not OGR |
| 10:09:38 | vdeparday: | if I put a .shp in the CONNECTION parameter then it can read but doesn't find the attribute |