<p dir="ltr">Bob,</p>
<p dir="ltr">In general this is a very hard problem (impossible) to solve on the GeoMoose side. This is really a question of data organization. </p>
<p dir="ltr">In general, there is a one to many relationship between a GeoMoose catalog layer and GeoMoose MapSources (a WMS/WFS/other thing OpenLayers can read service). </p>
<p dir="ltr">There is also a one to (zero or many) relationship between a WMS layer and data files/tables. It could be an inline feature, could be a group name that pulls in many (MapServer) layers, it could be data generated on the fly (DB View or MapServer GeoProcessing).</p>
<p dir="ltr">If assumptions can be made about how the data is organized on the server or organized via WMS/WFS layer pairs via MapServer or the source data is otherwise documented then you could have a service (possibly WFS) generate a file and send it to the client to download/save.</p>
<p dir="ltr">Brent,</p>
<p dir="ltr">Assuming you are looking to solve this for a particular dataset and not every possible GeoMoose datasource, I'd look at building a URL that returns the data as (Geo)JSON (either via a MapServer query/template, WFS outputformat, or custom script) and feeding that to D3.js to make the chart.</p>
<div class="gmail_quote">On Apr 26, 2016 11:27 AM, "Brent Fraser" <<a href="mailto:bfraser@geoanalytic.com">bfraser@geoanalytic.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
bobb,<br>
<br>
I was just looking into a similar problem. But the target would
be a chart (e.g. bar/pie chart) in a browser window.<br>
<pre cols="72">Best Regards,
Brent Fraser</pre>
<div>On 4/26/2016 9:48 AM, Basques, Bob
(CI-StPaul) wrote:<br>
</div>
<blockquote type="cite">
All,
<div><br>
</div>
<div>This is an on again, off again wishlist item for me.</div>
<div><br>
</div>
<div>Came up again this week here in the office. I was
wondering about adding a tool config to the mapbook for setting
up a download link for data on a particular layer. I understand
that not all data sources are the same, and that some might be
easier to setup than others, but in general, anyone else
interested in this type of capability?</div>
<div><br>
</div>
<div>I initially thought about trying this with SHP
files, of which we have about 260 different ones in our install.
Note: some layers are composed of more than one SHP file.
While thinking on it some more, another thought was to
investigate whether some sort of standard output might be washed
through Mapserver as a generic method of data output. This
would allow for a clip and ship approach too vs downloading an
entire dataset, it also seems like it would help with data
originating in Databases. Maybe this is two different tools, or
at least download options. Some of the layers could easily be
downloaded in their entirety. Would GeoPackage be a possible
output format to target for something like this, something else?
I’m also interested in any thoughts on how to manage/organize
things on the backend. I suspect that we have a good system
already, but all ideas welcome.</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div><br>
</div>
<div>bobb</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>
<div style="color:rgb(0,0,0);font-family:'Comic Sans MS';font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
<div><br>
<br>
</div>
<div>“There is nothing quite so useless as doing
with great efficiency something that should not be done
at all.” </div>
<div> - Peter Drucker</div>
<div><br>
</div>
</div>
<br>
</div>
<br style="color:rgb(0,0,0);font-family:'Comic Sans MS';font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<br>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Geomoose-users mailing list
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br></blockquote></div>