am I missing something or can this already be done online with arbitrary data? without an angleitem and startangleitem and some "not so easy" postgis processing for the start angles, I don't get it.<br>The advantage here is using arbitrary data, and in this context can be easily extended to bar graphs for example.
<br>I couldn't find any reference to the expressions bindings you talk about, any pointers?<br><br>tb<br><br><div><span class="gmail_quote">On 6/13/06, <b class="gmail_sendername">Steve Lime</b> <<a href="mailto:Steve.Lime@dnr.state.mn.us">
Steve.Lime@dnr.state.mn.us</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">That is very similar to the chart hack I've done precviously. With postgis I would imagine computing angles (from percentages) would be easy. I now see a use for Steve W. expression bindings...
<br><br>Please file a bug to track your additions and we can talk about integration.<br><br>Steve<br><br>>>> thomas bonfort <<a href="mailto:thomas.bonfort@GMAIL.COM">thomas.bonfort@GMAIL.COM</a>> 06/12/06 2:25 PM >>>
<br>hi there,<br>I quickly hacked up something, finally leaving out gdchart mainly because I<br>was too lazy to modify it so it accepts a gdhandle rather than file<br>pointers, but also because the sizes of the output charts were'nt consistent
<br>with one another.<br>I've attached a jpeg image of the output.<br>basically so as to keep the "class" parts semantically correct, I use a new<br>layer type "CHART", in which each class corresponds to a slice of the pie
<br>chart, and the sizeitem to the value. the example shown here is therefore:<br><br>LAYER<br> NAME "ages"<br> TYPE CHART<br> CONNECTIONTYPE postgis<br> CONNECTION "blabla"<br> DATA "the_geom from demo"
<br> STATUS ON<br> CLASS<br> NAME "population age 0-19"<br> STYLE<br> SIZEITEM "v1006"<br> COLOR 255 244 237<br> END<br> END
<br> CLASS<br> NAME "population age 20-39"<br> STYLE<br> SIZEITEM "v1007"<br> COLOR 255 217 191<br> END<br> END<br> CLASS<br> NAME "population age 40-59"
<br> STYLE<br> SIZEITEM "v1008"<br> COLOR 255 186 140<br> END<br> END<br> END<br><br>I'd hope this could be integrated/expanded in a future version, keep in
<br>touch if you're interested.<br>cheers,<br>tb<br><br><br>On 6/9/06, Daniel Morissette <<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>> wrote:<br>><br>> thomas bonfort wrote:<br>> >
<br>> > Steve and Daniel: the url type symbol does seem promising feature-wise.<br>> > but once again the overhead of network request and probably two<br>> > intermediate files (one for owt, one for MS) seems quite important.
<br>> ><br>><br>> True, there can be a performance hit for large numbers of symbols, but<br>> using an external service via a URL to produce the chart or dynamic<br>> symbol gives maximum flexibility to the users to return whatever they
<br>> like and not just charts.<br>><br>> Anyway, if you insist on direct integration inside MapServer, then I'd<br>> recommend that you look at gdchart which is used by OWTChart<br>> (<a href="http://maptools.org/owtchart/).">
http://maptools.org/owtchart/).</a>.. the original version of gdchart was<br>> messy with a bunch of global variables and static stuff that didn't<br>> build well on all platforms, and for owtchart I reworked it to replace
<br>> the global vars with a struct and make it more multi-platform. You'll<br>> find that version in directory "gdchart2" in the owtchart source<br>> package. The only other dependency of gdchart is GD (and its own
<br>> dependencies), that would be fairly easy to integrate.<br>><br>> Daniel<br>> --<br>> Daniel Morissette<br>> <a href="http://www.mapgears.com/">http://www.mapgears.com/</a><br>><br><br></blockquote>
</div><br>