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