<div dir="ltr">Dear all,<div>very nice tool, it looks promising and quite useful too.</div><div><br></div><div>It would be possible to have some more details on its implementation and how it interacts with GeoServer?</div><div><br></div><div>In the past <a href="http://www.geo-solutions.it">we</a> had some headaches building a complete and reliable download plugin for GeoServer.</div><div>In the end we implemented it as a WPS process capable of subsetting through several strategies (intersect or crop) all kind of datasets (both raster and vectorial). It is also capable of reprojecting the outcome, estimate the download size before starting the process, prepare the outcome ZIP archive (along with associated layer styles) asynchrounsly also and provide back a progress and/or a download link. It is also able to send an email to the requester when the file is ready. It was thought to allow GeoServer subsetting and downloading reliably also big datadsets and manage different download requests without overloading the server.</div><div><br></div><div>The plugin is available as a community plugin here <a href="http://docs.geoserver.org/stable/en/user/community/wps-download/index.html">http://docs.geoserver.org/stable/en/user/community/wps-download/index.html</a></div><div>code available here <a href="https://github.com/geoserver/geoserver/tree/master/src/community/wps-download">https://github.com/geoserver/geoserver/tree/master/src/community/wps-download</a></div><div><br></div><div>Maybe you want to consider the use of such plugin to extend the capabilities of your query plugin instead of relying only on CQL filters (if I understood correctly how the tool currently works).</div><div><br></div><div>If so we can envisage the inclusion of the WPS Download process into the official distribution of the GeoNode-GeoServer-ext package.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div style="font-size:12.8px">Best Regards,</div><div style="font-size:12.8px">Alessio Fabiani.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><div>==</div><div>GeoServer Professional Services from the experts!</div><div>Visit <a href="http://goo.gl/it488V" target="_blank">http://goo.gl/it488V</a> for more information.</div><div>==</div></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Ing. Alessio Fabiani</div><div style="font-size:12.8px">@alfa7691</div><div style="font-size:12.8px">Founder/Technical Lead</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><div>GeoSolutions S.A.S.</div><div>Via di Montramito 3/A</div><div>55054 Massarosa (LU)</div><div>Italy</div><div>phone: +39 0584 962313</div><div>fax: +39 0584 1660272</div><div>mob: +39 331 6233686</div><div><br></div><div><a href="http://www.geo-solutions.it" target="_blank">http://www.geo-solutions.it</a></div><div><a href="http://twitter.com/geosolutions_it" target="_blank">http://twitter.com/geosolutions_it</a></div></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">-------------------------------------------------------</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><p><span lang="IT"><font size="1"><b>AVVERTENZE AI SENSI DEL D.Lgs. 196/2003</b></font></span></p><p><span lang="IT"><font size="1">Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.</font></span></p><p><span lang="IT"><font size="1"> </font></span></p><p><font size="1">The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.</font></p><p><font size="1">---------------------------------------------------------------------</font></p></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, May 24, 2016 at 10:33 AM, Eugenio Trumpy <span dir="ltr"><<a href="mailto:frippe12573@hotmail.com" target="_blank">frippe12573@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">Ho Dimitris and all,<br><br>the tool you developed it' really fantastic as well as useful from my point of view.<br>Your work made me think about a possible tool: it could be nice to have a query builder for the layer to insert in the map composer, just a sort of a layer pre-filter. Moreover I wonder even if having a combo box, including possible values, in the query builder is easy to implement.<br><br>This my 2 cents.<br>Best<br><br>Eugenio<br><br><hr>Date: Mon, 23 May 2016 17:14:49 +0200<br>From: <a href="mailto:karakostis.dimitris@gmail.com" target="_blank">karakostis.dimitris@gmail.com</a><br>To: <a href="mailto:pjdufour.dev@gmail.com" target="_blank">pjdufour.dev@gmail.com</a><br>Subject: Re: [GeoNode-devel] QueryBuilder for Download Layer functionality<br>CC: <a href="mailto:geonode-devel@lists.osgeo.org" target="_blank">geonode-devel@lists.osgeo.org</a><div><div class="h5"><br><br><div dir="ltr"><br><div>Hi guys, </div><div><br></div><div>I have deployed the newly developed 'Query Builder and Map Filter' tool in our staging server for WFP Geonode: <a href="http://staging.geonode.wfp.org/layers/" target="_blank">http://staging.geonode.wfp.org/layers/</a> There are still several features to be added but you can have a look and give some recommendations, improvement ideas etc.</div><div>To use the tool, select a layer, click the Download button and then the Layer Filtering.</div><div><br></div><div>Cheers</div><div>Dimitris</div><div><br></div><div><br></div></div><div><br><div>On Mon, May 16, 2016 at 9:09 PM, Patrick Dufour <span dir="ltr"><<a href="mailto:pjdufour.dev@gmail.com" target="_blank">pjdufour.dev@gmail.com</a>></span> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Yes, I can help with the GNIP when ready.</p>
<p dir="ltr">The implementation will leverage the cql_filter GeoServer WFS querystring parameter, as such no changes to GeoServer or django DB models are needed.</p>
<p dir="ltr">Regards,<br>
Patrick Dufour</p><div><div>
<div>On May 16, 2016 6:11 PM, "Jeffrey Johnson" <<a href="mailto:ortelius@gmail.com" target="_blank">ortelius@gmail.com</a>> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex">This is really awesome!<br>
<br>
Can you file a GNIP for this so we can discuss the implementation as a<br>
group? If you need help with that, let us know. You will need a core<br>
committer to actually file the GNIP. Perhaps Patrick can help?<br>
<br>
Looking forward to seeing/using this!<br>
<br>
Jeff<br>
<br>
On Mon, May 16, 2016 at 2:34 AM, Dimitris Karakostis<br>
<<a href="mailto:karakostis.dimitris@gmail.com" target="_blank">karakostis.dimitris@gmail.com</a>> wrote:<br>
><br>
><br>
> Hello guys,<br>
><br>
> How are you doing? I wanted to share with you our current development<br>
> plans/progress for WFPGeonode. During the last week I have been working on<br>
> the implementation of a 'Query Builder' functionality in order to be able to<br>
> download specific parts of layers in the provided formats (kml, xls, csv,<br>
> zipped shape, geojson).<br>
><br>
> The user can build the query by :<br>
> 1. selecting from a dropdown menu the available attributes,<br>
> 2. selecting an operator,<br>
> 3. enter a valid value<br>
><br>
> The different statements of the query can be combined either with AND or OR<br>
> operator. I have also used the OWSLib (0.11.0; thanks Tom) in order to get<br>
> the type of attributes and apply some sort of validation (e.g. if you try to<br>
> put a string, while number is expected then you get an error message).<br>
><br>
> For the above process I have used JQuery for the JS functionality and<br>
> BootstrapCSS for the gui. The tool is part of the 'Download Layer' modal and<br>
> is currently being tested and making small fixes.<br>
><br>
> The next step will be to build a map tool, which you will select the area of<br>
> interest (rectangle tool; bounding box etc.) and download it.<br>
><br>
> I attach some screenshots of the two tools. If you have any<br>
> ideas/advice/comments please let me know. They are most welcome!<br>
><br>
> Cheers<br>
> Dimitris<br>
><br>
> _______________________________________________<br>
> geonode-devel mailing list<br>
> <a href="mailto:geonode-devel@lists.osgeo.org" target="_blank">geonode-devel@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
><br>
_______________________________________________<br>
geonode-devel mailing list<br>
<a href="mailto:geonode-devel@lists.osgeo.org" target="_blank">geonode-devel@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
</blockquote></div>
</div></div></blockquote></div><br></div>
<br>_______________________________________________
geonode-devel mailing list
<a href="mailto:geonode-devel@lists.osgeo.org" target="_blank">geonode-devel@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a> </div></div></div></div>
<br>_______________________________________________<br>
geonode-devel mailing list<br>
<a href="mailto:geonode-devel@lists.osgeo.org">geonode-devel@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geonode-devel" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geonode-devel</a><br>
<br></blockquote></div><br></div>