<div dir="ltr">Dear Jeff<div><br></div><div>The wiki page has been updated. I am sorry for missing the content. </div><div><br></div><div><br></div><div>Best </div><div>Niroshan <br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 31, 2017 at 4:00 AM, <span dir="ltr"><<a href="mailto:soc-request@lists.osgeo.org" target="_blank">soc-request@lists.osgeo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send SoC mailing list submissions to<br>
<a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.osgeo.org/mailman/listinfo/soc" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/soc</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:soc-request@lists.osgeo.org">soc-request@lists.osgeo.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:soc-owner@lists.osgeo.org">soc-owner@lists.osgeo.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SoC digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [IMPORTANT] About URLs provided by students and subsequent<br>
evaluation (Margherita Di Leo)<br>
2. Re: Integrating istSOS as a data store in MapMint (Jeff McKenna)<br>
3. Re: GSoC 2017 Weekly Report 12 - SOS tools in GRASS GIS<br>
(Jeff McKenna)<br>
4. Re: Week 12 Final Report: GRASS GIS Locations from Public<br>
Data (Jeff McKenna)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Wed, 30 Aug 2017 09:58:37 +0200<br>
From: Margherita Di Leo <<a href="mailto:diregola@gmail.com">diregola@gmail.com</a>><br>
To: OSGeo-SoC <<a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a>><br>
Cc: <a href="mailto:gsoc-admin@osgeo.org">gsoc-admin@osgeo.org</a><br>
Subject: [SoC] [IMPORTANT] About URLs provided by students and<br>
subsequent evaluation<br>
Message-ID:<br>
<CABa=<a href="mailto:8QoYGVqeBV_oNZrsFgLNxunVXLZQeuoAxLVEq2d6YbTeZw@mail.gmail.com">8QoYGVqeBV_<wbr>oNZrsFgLNxunVXLZQeuoAxLVEq2d6Y<wbr>bTeZw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear All,<br>
<br>
unfortunately only few students followed our indications [1] about URL<br>
submission. Our indication was that students would use the URL of last<br>
report published in soc mailing list. Every other link should have been<br>
prior discussed with us to make sure they are compliant to Google's<br>
rules[2].<br>
*@Students*: We make rules because if you follow them you and your mentors<br>
don't have to make the extra work of checking compliance on yourselves.<br>
Now it's too late to change the submission, and the extra work is required:<br>
*@mentors*, please check the URLs provided by your students against the<br>
requirements given by Google at: [2]. Remember that you are required to<br>
FAIL students that provided a link that doesn't meet these requirements. We<br>
admins are double checking that this is respected.<br>
Lesson learned: in case of doubts, ASK US before.<br>
<br>
<br>
[1] <a href="https://lists.osgeo.org/pipermail/soc/2017-August/003827.html" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>pipermail/soc/2017-August/<wbr>003827.html</a><br>
[2] <a href="https://developers.google.com/open-source/gsoc/help/work-product" rel="noreferrer" target="_blank">https://developers.google.com/<wbr>open-source/gsoc/help/work-<wbr>product</a><br>
<br>
--<br>
Margherita Di Leo<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.osgeo.org/pipermail/soc/attachments/20170830/f9d23df7/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>pipermail/soc/attachments/<wbr>20170830/f9d23df7/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 30 Aug 2017 11:52:47 -0300<br>
From: Jeff McKenna <<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a><wbr>><br>
To: <a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a><br>
Subject: Re: [SoC] Integrating istSOS as a data store in MapMint<br>
Message-ID:<br>
<<a href="mailto:a16c571c-4a75-3ea2-8299-b63065289e24@gatewaygeomatics.com">a16c571c-4a75-3ea2-8299-<wbr>b63065289e24@gatewaygeomatics.<wbr>com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Hi Niroshan,<br>
<br>
Could you please make sure that all of these weekly reports are<br>
documented on your wiki page at:<br>
<a href="https://wiki.osgeo.org/wiki/Integrating_istSOS_as_a_data_store_in_MapMint" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/<wbr>Integrating_istSOS_as_a_data_<wbr>store_in_MapMint</a><br>
Your weekly reports only go until Week 6 there. This is very important<br>
to document, please do this as soon as possible.<br>
<br>
Thanks!<br>
<br>
-GSoC Admins<br>
<br>
<br>
<br>
On 2017-08-13 8:24 PM, Niroshan Sanjaya wrote:<br>
> Hi all,<br>
><br>
> What did you get done this week?<br>
><br>
> This week I was working on building the module of istSOS in mapmint.<br>
> - visualize the data in mapmimt<br>
> - adding parameters<br>
><br>
><br>
> What do you plan on doing next week?<br>
><br>
> This week I will finish the module.<br>
> Implement an example service.<br>
><br>
><br>
> Are you blocked on anything?<br>
><br>
> No<br>
><br>
><br>
> Wiki<br>
> <a href="https://wiki.osgeo.org/wiki/Integrating_istSOS_as_a_data_store_in_MapMint" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/<wbr>Integrating_istSOS_as_a_data_<wbr>store_in_MapMint</a> <<a href="https://wiki.osgeo.org/wiki/Integrating_istSOS_as_a_data_store_in_MapMint" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/<wbr>Integrating_istSOS_as_a_data_<wbr>store_in_MapMint</a>><br>
><br>
> Repository<br>
><br>
> <a href="https://github.com/niroshansb/gsoc2017" rel="noreferrer" target="_blank">https://github.com/niroshansb/<wbr>gsoc2017</a><br>
> <<a href="https://github.com/niroshansb/gsoc2017" rel="noreferrer" target="_blank">https://github.com/<wbr>niroshansb/gsoc2017</a>><br>
><br>
> Best<br>
><br>
><br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 30 Aug 2017 13:25:55 -0300<br>
From: Jeff McKenna <<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a><wbr>><br>
To: <a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a><br>
Subject: Re: [SoC] GSoC 2017 Weekly Report 12 - SOS tools in GRASS GIS<br>
Message-ID:<br>
<<a href="mailto:73be819b-0f76-8bfe-d49c-105e3a807088@gatewaygeomatics.com">73be819b-0f76-8bfe-d49c-<wbr>105e3a807088@gatewaygeomatics.<wbr>com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Hello Ondřej,<br>
<br>
Can you please record this final report on your wiki page in the weekly<br>
timeline at <a href="https://trac.osgeo.org/grass/wiki/GSoC/2017/SOSInGRASS" rel="noreferrer" target="_blank">https://trac.osgeo.org/grass/<wbr>wiki/GSoC/2017/SOSInGRASS</a> as<br>
soon as possible? thanks,<br>
<br>
-GSoC admins<br>
<br>
<br>
<br>
On 2017-08-22 6:11 PM, Ondřej Pešek wrote:<br>
> Hi Madi,<br>
><br>
> oh, I'm sorry. I have read that manual, but I have thought that the<br>
> final report will be the next one. My fault. So here it is reelaborated.<br>
><br>
> *Project Title:*<br>
> SOS tools in GRASS GIS<br>
><br>
> *Organization:*<br>
> Google Summer of Code 2017<br>
> Open Source Geospatial Foundation (OSGeo)<br>
> GRASS GIS<br>
><br>
> *Abstract:*<br>
> Intended modules would enable the user to create a vector, a raster<br>
> based on some aggregations and create a space time vector or raster<br>
> dataset, everything directly from user's access to the SOS server.<br>
> t.vect.to.rast would also allow the user to convert a space time vector<br>
> dataset into a raster dataset. The user should be also allowed to get<br>
> the capabilities to get info about sensors from these modules and filter<br>
> the results.<br>
><br>
> *Pre-GSoC:*<br>
> GRASS GIS didn't have any module to work with Sensor Observation Service<br>
> (SOS). When the user wanted to use data from his SOS server, he had to<br>
> access them through OWSLib, convert them into GRASS GIS or OGR supported<br>
> format ad then import it somehow to GRASS GIS as one huge file.<br>
><br>
> *Added value:*<br>
> v.in.sos imports data from SOS server as a vector map to GRASS GIS. It<br>
> creates one layer for each offering and observed property.<br>
> r.in.sos imports data from SOS server as a raster maps to GRASS GIS. It<br>
> creates new raster map for each timestamp. User is allowed to use some<br>
> aggregations and granularity to filter data.<br>
> t.vect.in.sos imports data from SOS server to GRASS GIS as a<br>
> spatio-temporal vector dataset. It creates new stvds for each offering<br>
> and observed property (created from one vector map as an intermediate).<br>
> t.rast.in.sos imports data from SOS server to GRASS GIS as a<br>
> spatio-temporal raster dataset. It creates new strds for each property<br>
> and each procedure (registered from raster maps created as intermediates).<br>
> t.vect.to.rast doesn't import data from SOS server to GRASS GIS. It<br>
> converts a space time vector dataset into a space time raster dataset.<br>
><br>
> *Continued Work:*<br>
> There are some issues or possible enhancements in the modules.<br>
> v.in.sos uses timestamps as column names for each layer. The problem is<br>
> that it is not possible to have more than 3000 columns in SQLite table<br>
> (GRASS GIS attribute table) without SQLite recompilation. It will be<br>
> little bit solved by granularity and this module isn't so necessary when<br>
> there is t.vect.in.sos, but it is still useful for some purposes and<br>
> this is really lack.<br>
> t.vect.to.rast is working, but if you take look at t.rast.to.vect, you<br>
> can see much more options. It would be great to involve them also into<br>
> this module.<br>
> It would be also great to have a flag for ignoring empty procedures in<br>
> all the modules.<br>
><br>
> *Link:<br>
> *<br>
> The modules github repository:<br>
> <a href="https://github.com/pesekon2/GRASS-GIS-SOS-tools" rel="noreferrer" target="_blank">https://github.com/pesekon2/<wbr>GRASS-GIS-SOS-tools</a><br>
> (they should be moved into the official GRASS GIS add-ons repository in<br>
> the future)<br>
><br>
> *One image to show how can visualized sensors look on the OSM map:*<br>
> <a href="https://raw.githubusercontent.com/pesekon2/GRASS-GIS-SOS-tools/d566c868a50f12ba6fc4e1d6b953e9708e4b0061/image_vector_import.png" rel="noreferrer" target="_blank">https://raw.githubusercontent.<wbr>com/pesekon2/GRASS-GIS-SOS-<wbr>tools/<wbr>d566c868a50f12ba6fc4e1d6b953e9<wbr>708e4b0061/image_vector_<wbr>import.png</a><br>
><br>
><br>
> 2017-08-18 22:22 GMT+02:00 Margherita Di Leo <<a href="mailto:diregola@gmail.com">diregola@gmail.com</a><br>
> <mailto:<a href="mailto:diregola@gmail.com">diregola@gmail.com</a>>>:<br>
><br>
> Hi Ondrej,<br>
><br>
> Thank you for your report.<br>
> Note that this is your final report and was supposed to be a summary<br>
> of your work. Please, read<br>
> <a href="https://lists.osgeo.org/pipermail/soc/2017-August/003827.html" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>pipermail/soc/2017-August/<wbr>003827.html</a><br>
> <<a href="https://lists.osgeo.org/pipermail/soc/2017-August/003827.html" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>pipermail/soc/2017-August/<wbr>003827.html</a>> and<br>
> re-elaborate your report to meet the given template<br>
><br>
> --<br>
> Margherita Di Leo<br>
><br>
><br>
><br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 30 Aug 2017 13:29:57 -0300<br>
From: Jeff McKenna <<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a><wbr>><br>
To: <a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a><br>
Subject: Re: [SoC] Week 12 Final Report: GRASS GIS Locations from<br>
Public Data<br>
Message-ID:<br>
<<a href="mailto:8773ee77-7d3d-853b-9846-1ecfabbc0fcb@gatewaygeomatics.com">8773ee77-7d3d-853b-9846-<wbr>1ecfabbc0fcb@gatewaygeomatics.<wbr>com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Hello Zechariah,<br>
<br>
Can you please record this final report on your wiki page in the weekly<br>
timeline as soon possible<br>
<a href="https://trac.osgeo.org/grass/wiki/GSoC/2017/GRASSGISLocationsfromPublicData" rel="noreferrer" target="_blank">https://trac.osgeo.org/grass/<wbr>wiki/GSoC/2017/<wbr>GRASSGISLocationsfromPublicDat<wbr>a</a><br>
<br>
thanks,<br>
<br>
-GSoC Admins<br>
<br>
<br>
<br>
On 2017-08-21 2:03 AM, Zechariah Krautwurst wrote:<br>
> *Project Title:*<br>
> GRASS GIS Locations from Public Data<br>
><br>
> *Organization:*<br>
> Google Summer of Code 2017<br>
> Open Source Geospatial Foundation (OSGeo)<br>
> GRASS GIS<br>
><br>
> *Abstract:*<br>
> r.in.usgs is an add-on module for GRASS GIS that greatly simplifies the<br>
> process of downloading and using USGS raster datasets.<br>
><br>
> *Pre-GSoC:*<br>
> Before r.in.usgs was created, USGS raster imagery was selected through a<br>
> web-based interface, manually downloaded, and manually imported into<br>
> GRASS GIS through a multi-step process. The process requires prior<br>
> knowledge of USGS dataset parameters, spatial reference systems,<br>
> coordinate reprojection, computational regions, and the appropriate<br>
> GRASS GIS tools and methods.<br>
><br>
> *Added value:*<br>
> r.in.usgs provides a GRASS GIS GUI that suggests appropriate default<br>
> parameters, as well as provides advanced options for downloading<br>
> available USGS datasets. The module assembles user-input information<br>
> with the required GRASS GIS parameters and tools to automatically<br>
> download, import, reproject, and patch complex USGS raster data in a<br>
> single process.<br>
><br>
> *Continued Work:*<br>
> r.in.usgs currently handles all three products from the USGS National<br>
> Elevation Dataset (NED) as well as all three products from the National<br>
> Land Cover Dataset (NLCD). Several other USGS datasets are made<br>
> available for download but each requires custom formatting and further<br>
> modifications to the r.in.usgs script processes.<br>
><br>
> Further development of the module should include continued incorporation<br>
> of USGS datasets, as well as creating accessible tools for sources of<br>
> international data. Ultimately, creating a module that allows GRASS GIS<br>
> users to contribute to a centralized, automated repository of properly<br>
> formatted publicly available datasets would provide a huge service to<br>
> the open source GIS community.<br>
><br>
> r.in.usgs will be moved into the official GRASS GIS add-ons repository<br>
> in the coming week.<br>
><br>
> *Links and Documentation:*<br>
> OSGeo project wiki:<br>
> <a href="https://trac.osgeo.org/grass/wiki/GSoC/2017/GRASSGISLocationsfromPublicData" rel="noreferrer" target="_blank">https://trac.osgeo.org/grass/<wbr>wiki/GSoC/2017/<wbr>GRASSGISLocationsfromPublicDat<wbr>a</a><br>
><br>
> Git repository:<br>
> <a href="https://github.com/zkwurst/GSoC2017-GRASS-GIS" rel="noreferrer" target="_blank">https://github.com/zkwurst/<wbr>GSoC2017-GRASS-GIS</a><br>
><br>
> Raw code:<br>
> <a href="https://raw.githubusercontent.com/zkwurst/GSoC2017-GRASS-GIS/master/r.in.usgs/r.in.usgs.py" rel="noreferrer" target="_blank">https://raw.githubusercontent.<wbr>com/zkwurst/GSoC2017-GRASS-<wbr>GIS/master/r.in.usgs/r.in.<wbr>usgs.py</a><br>
><br>
> Raw html documentation:<br>
> <a href="https://raw.githubusercontent.com/zkwurst/GSoC2017-GRASS-GIS/master/r.in.usgs/r.in.usgs.html" rel="noreferrer" target="_blank">https://raw.githubusercontent.<wbr>com/zkwurst/GSoC2017-GRASS-<wbr>GIS/master/r.in.usgs/r.in.<wbr>usgs.html</a><br>
><br>
> Google Docs version of html documentation:<br>
> <a href="https://docs.google.com/document/d/1jarl2X05A020_dv8YAcXjdPAONHrWpGnWigHWyzb3ys/edit#heading=h.gu5m0ou06qhs" rel="noreferrer" target="_blank">https://docs.google.com/<wbr>document/d/1jarl2X05A020_<wbr>dv8YAcXjdPAONHrWpGnWigHWyzb3ys<wbr>/edit#heading=h.gu5m0ou06qhs</a><br>
><br>
><br>
><br>
> Zechariah F. Krautwurst<br>
><br>
> NCSU College of Natural Resources<br>
><br>
> MGIST Candidate 2017<br>
><br>
> <a href="mailto:zfkrautw@ncsu.edu">zfkrautw@ncsu.edu</a> <mailto:<a href="mailto:zfkrautw@ncsu.edu">zfkrautw@ncsu.edu</a>><br>
><br>
> <a href="http://www.zekefrank.com" rel="noreferrer" target="_blank">www.zekefrank.com</a> <<a href="http://www.zekefrank.com" rel="noreferrer" target="_blank">http://www.zekefrank.com</a>><br>
><br>
><br>
><br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
SoC mailing list<br>
<a href="mailto:SoC@lists.osgeo.org">SoC@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/soc" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/soc</a><br>
<br>
------------------------------<br>
<br>
End of SoC Digest, Vol 97, Issue 27<br>
******************************<wbr>*****<br>
</blockquote></div><br></div></div></div>