Hackpads are smart collaborative documents. Join Hackpad Now.
7 days ago
0 / 10
Unfiled. Edited by nhoebel@kmotifs.com , brandon whitehead 7 days ago
nhoebel@kmotifs.com 22 August 2016
 
Attending:
Beth, Brandon, Nancy Hoebelheinrich
Apologies:  Soren
 
Agenda:
  • Brainstorm next steps
  • When to invite Bhaskar or ESRI person?
 
Notes:
 
 
Action items;
From last time:
  • Beth - draft project plan by next week in preparation for ADL Quad Chart, due by September 1st;  will discuss on the call next week
  • Brandon, Nancy to look for information on the ADL's Technical Learning Architecture to see if ToolMatch might fit in
  • Nancy to do the same as above
  •  Chris:  look at API for CMR to see in what the form the tags making the assertions should be, whether tags could be added back to the CMR; also see if Tags could then be exported for consumption to demonstrate the end - end capabilities of a ToolMatch. 
  • Nancy to find spreadsheet with the datasets that work with Giovanni that Chris generated many months ago.  See if this info could be re-used or adapted
  • Contact people to attend future meetings to create more assertions:
  • Bhaskar - Nancy to ask
  • Christine or someone from ESRI - Nancy to ask
  • The Tisdales - Beth to ask
From this meeting:
brandon w
  • Sky Bristol and/or USGS CDI funding
 
 
 
14 days ago
0 / 9
Unfiled. Edited by nhoebel@kmotifs.com , brandon whitehead , soren scott 14 days ago
nhoebel@kmotifs.com 15 August 2016
 
Attending:
Beth, Soren, Brandon, Chris, Nancy
 
Agenda:
  • What's next
  • ADL grant
  • Is a DOD agency request for proposals
  • Specifically asking for semantic ontologies & how the ontology can be used for interoperability
  • Improve the interoperability of tools for learning
  • Need to map learning tools, primarily for soldiers
  • ESRI partnership possibilities?
Notes:
  • Is not completely obvious how the ADL grant might serve our purposes;  the idea is to test / assess how the Technical Learning Architecture (TLA) that ADL is developing could incorporate something like ToolMatch into the learning tools they already have.  Will need to explore more;  a draft plan for what we want to do could be useful for this opportunity as well as other opportunities that might arise, e.g., 
  • EarthCube Building Block call -- will there be one?
  • The March call funded proposals have not yet been announced
soren s
  • Building blocks are usually two years (spring), Integrative Activities (IAs) (same and fall?)
nhoebel@kmotifs.com
  • AIST proposals - probably September 9th announcement
  • USGS CDI grant proposal out in October
  • Would probably be best to focus on assertions that we can make for a given tool, and then expand from there, e.g., datasets that work with ArcGIS.  For that purposes, we'll ask people to attend future calls to see if they would be willing to help us make these assertions:
  • Guests at future calls to get information - focus on assertions: Bhaskar, Christine White or someone from ESRI, The Tisdales
  • Chris & Beth suggested that we go back to the concept we've discussed earlier to just make declarations or assertions on relationships between tools and datasets as a way to prove the end to end efficacy of a matching service.  
  • The assertions could take the form of some simple tags that could be added to the datasets in the CMR (Common Metadata Repository) which has an API that should facilitate this.  
  • By script, it should be possible to make the assertions for these tags for a small number of tools such as Panoply, Ferret, HDFView, ArcGIS, Giovanni (we already have this, more or less).
  • The (python) script might be used that would pull a dataset name and CMR Entry ID from the CMR, put the tags back into the MD entry for a dataset, and then pull the information as a demonstration of a tool match capability
  • It's a low level (semantic) technology, but could prove the concept, and then would be more persuasive to be able to build upon it to do the more complicated, interesting rules creation & inferencing. 
  • Testing of the assertions could be done as part of a hackathon any gotchas to the assertions could be recorded as a possible basis for needed rules / inferencing.
  • Possible tags could be:
  •  mapped by
  •  reads
  •  subsets 
  • plots
 
Action Items:
  • Beth - draft project plan by next week in preparation for ADL Quad Chart, due by September 1st;  will discuss on the call next week
  • Brandon, Nancy to look for information on the ADL's Technical Learning Architecture to see if ToolMatch might fit in
  • Nancy to do the same as above
  •  Chris:  look at API for CMR to see in what the form the tags making the assertions should be, whether tags could be added back to the CMR; also see if Tags could then be exported for consumption to demonstrate the end - end capabilities of a ToolMatch. 
  • Nancy to find spreadsheet with the datasets that work with Giovanni that Chris generated many months ago.  See if this info could be re-used or adapted
  • Contact people to attend future meetings to create more assertions:
  • Bhaskar - Nancy to ask
  • Christine or someone from ESRI - Nancy to ask
  • The Tisdales - Beth to ask
 
 
 
 
28 days ago
Unfiled. Edited by soren scott , brandon whitehead 28 days ago
  • AIST grant?
soren s
  • should be out Sept 9
 
29 days ago
0 / 2
Unfiled. Edited by nhoebel@kmotifs.com 29 days ago
Thursday, July 21st, 2016 at Durham Convention Center, Durham NC
nhoebel@kmotifs.com From Nancy's notes:
  • Sky Bristol mentioned a Rangeland Fire tool that uses a landscape view app called GeoCortex built on ArcGIS that does not fully support WMS (Web Map Service), but only uses ArcGIS REST services.  He considered that a limitation in the flexibility of the tool.   For our purposes, we would probably be most interested in describing the GeoCortex tool since the Rangeland Fire tool shows up in "Oregon Explorer" and is more of a decision support tool with pre-figured datasets as part of it.
  • Sky also noted that ArcGIS for Desktop 2.0  works with WLS (Oracle's WebLogic Service(??) 1.0, but not 2.0.  This should be verified from Beth's and Soren's notes as mine are not clear.  (Also, current WLS seems to be a much later version now, so don't know if this makes sense.
  • Other tools worth including:
  • Leaflet -- an OGC client tool
  • Cesium is a webGL virtual globe and map engine mentioned taht is an open source Java script library for creating 3D globes and maps.  See https://cesiumjs.org/ 
  • TerraGS -- an Australian Map GIS
  • GeoServer -- open source 
  • Bhaskar from NASA described tools that work with MODIS data, but have some limitations:
  • MRT doesn't work with Level 3 Swath data, but does work with Level 1B & Level 2 data
  • MRT also works with HDF4 to mosaic and stitch images (?) together
  • There is a tool called HEG (pronounced "haig" that turns an HDF file into GIS;  we could ask the EED (?) program people about this for more detail
  • GDAL tools were mentioned as being useful ones to include (Geospatial Data Abstraction Library)
  • MINX was mentioned
  • ENVI -- tools for spectral libraries & MODIS data as well
  • Imagine -- another tool for MODIS & ASTER data that is CF compliant
  • ArcGIS tools seemed to be another productive avenue to pursue in order to get more info.  Christine can help identify people at ESRI who can help with that
  • Christine was also interested in meeting with us to talk about possible collaborative funding to move the project forward.  Nancy & Beth to followup.
  • CIRIUS tools for HDF were mentioned;  
  • followup with Pam Mlynczk at SSAI, NASA Langley
 
Chris's notes:
(1) Got some excellent input on some tools, like the MRT family. 
(2) Formed an idea for a more foolproof telecon:
Provision a bunch of tools in the cloud (IDV, McIDAS-V, Panoply, Ferret, ArcGIS, qgis, ...)
Provision a bunch of datasets
Have everyone in the room start trying datasets in tools and updating, say, a Google Sheet with their compatibility.
 
Beth's Notes:
 
49 days ago
Unfiled. Edited by nhoebel@kmotifs.com 49 days ago
  • Start with what's on github
nhoebel@kmotifs.com
  • Add ToolMatch ontology to one of ESIP's Semantic portals?
 
  • Funding opportunities for any of the above?
  • USGS CDI proposals are a possibility;  talk with Leslie Hsu at ESIP Summer;  next call is September 2016.
  • How important would ToolMatch be to your community?
  • Identify organizations (& personal contacts) of those who might be interested in supporting by submitting a letter of support for a grant and/or partnering to develop the tool further (to move from incubation into prototyping at least).
  • Any ideas for funding opportunities?
 
112 days ago
Unfiled. Edited by nhoebel@kmotifs.com , soren scott 112 days ago
NEW CALL-IN Information at:
 
nhoebel@kmotifs.com You can also dial in using your phone. United States: +1 (872) 240-3212 Access Code: 156-154-397 
 
Background Information:
  • Includes ideas for other places to use to collect both data collections & tools
 
Agenda:
  • Progress / issues with comparison of ToolMatch to ODISEES ontologies
  • Questions re:  Glossary of Terms
  • Planning for ToolMatch sprint.
 
Anything else?
Notes:
  • Beth was able to import ToolMatch into ODISEES using TopBraid
soren s
  • Soren: still banned from the coastwatch ERDDAP proper, the link is in the notes for HTMLTable and information may also be with Live Action Server.
 
Members (41)
brandon whitehead soren scott Anne Basham anirudh prabhu Sophie Hou jgoldstein@usgcrp.gov Amanda L Whitmire Ruth Duerr steven.j.kempler@nasa.gov annieburgess@esipfed.org beth@lingualogica.net max7@rpi.edu b.whitehead@auckland.ac.nz prabha2@rpi.edu jgoldstein@usgrcp.gov rduerr@nsidc.org dhills@gsa.state.al.us jgoldstein@usgcrip.gov tnarock@marymount.edu West, Patrick

Create a New Collection

Cancel

Move XXX to XXX


XXX will be invited to the XXX on XXX.

Cancel

Contact Support



Please check out our How-to Guide and FAQ first to see if your question is already answered! :)

If you have a feature request, please add it to this pad. Thanks!


Log in / Sign up