[ESIP-all] The Web Services Cluster

George Percivall gpercivall at opengeospatial.org
Fri Feb 3 09:46:59 EST 2017


Thanks for organizing this.  It is very timely.   Not sure how widely you want to consider this topic, but here are some ideas.

- OPeNDAP is a useful protocol as demonstrated by Ed’s stats from PODAAC as well as at other locations.  Where to next with OPeNDAP?  There has been good progress in aligning OPeNDAP with similar activities such as the Geographic Coverages information type and the OGC Web Coverage Service (WCS).  Based on your results in working with others in the recently completed OGC Testbed 12 there is good progress on reaching common semantics allowing interoperability on a broader scale.  In a similar way is the advancements of OPeNDAP and WCS regarding uniform and non-uniform grids; as well as spatial-temporal indexing.

- APIs.  The explosion of public APIs is an effective software development technique.  But the proliferation of APIs has degraded interoperability previously established by open web protocols.  Public but proprietary APIs define structures with similar names but different meanings; an structures with similar meaning but different names.  What actions can be taken by ESIP to promote the interoperability of APIs?  Perhaps ESIP would consider use of the Open API Specification (formerly Swagger) to increase the interoperability of public but proprietary APIs by defining open conventions for Earth Observation APIs.  Later this month, based on requirements from USGS, OGC will be releasing a Request for Information about these and similar API topics.

- OGC Web Services evolution after 10+ years of operational experience is a current theme that this ESIP discussion could inform.  Many ESIP members and beyond use OGC Web Services (OWS) on an operational basis to access large services [1].  What refinements, extensions, changes are needed to OWS specs to meet current and future ESIP member needs?  Current discussions include how to make OWS interfaces more resource oriented.  WMTS is a good example of resource orientation and is considered a basis for this OWS evolution.  Additional topics are being addressed over the course of this year in OGC Testbed 13 - see below.

Thanks again for raising this discussion.  As a member of ESIP, OGC looks forward to the discussion.


[1]   Global-Scale Resource Survey and Performance Monitoring of Public OGC Web Map Services  <https://portal.opengeospatial.org/%3Ca%20href='http://www.mdpi.com/2220-9964/5/6/88'%3Ehttp://www.mdpi.com/2220-9964/5/6/88%3C/a%3E>  This paper explicates a distributed monitoring framework that was used to monitor 46,296 WMSs continuously for over one year and a crawling method to discover these WMSs. We analyzed server locations, provider types, themes, the spatiotemporal coverage of map layers and the service versions for 41,703 valid WMSs. Furthermore, we appraised the stability and performance of basic operations for 1210 selected WMSs  


During the ESIP meeting last month, Luis Bermudez presented about the OGC Testbed 13.

The Call for Participation has now been announced for TB13.
Of particular interest to ESIP may be these work items:

B.5. Cloud Computing Environment for Earth Observation Data - WPS for access to processing services.
B.13. Climate Data Accessibility for Adaptation Planning - NASA sponsored topic.
B.23. Workflows

B.6. DCAT/SRIM - semantic enable catalogues 

B.11. Map Markup Language & Web-Map HTML Element 
B.15. Vector Tiling
B.17. 3DTiles and i3s: Interoperability & Performance

The CFP is available at www.opengeospatial.org/standards/requests/154  
Responses for the CFP are due by 17 February 2017.

George Percivall
CTO, Chief Engineer
Open Geospatial Consortium
gpercivall at opengeospatial.org

> On Feb 2, 2017, at 12:19 PM, Armstrong, Edward M (398G) via ESIP-all <esip-all at lists.esipfed.org> wrote:
> Here is one data center that shows steady uptick of services usage (mostly OPeNDAP) with perhaps some leveling off in 2016
> http://podaac.jpl.nasa.gov/metrics <http://podaac.jpl.nasa.gov/metrics>
> From: ESIP-all <esip-all-bounces at lists.esipfed.org <mailto:esip-all-bounces at lists.esipfed.org>> on behalf of James Gallagher via ESIP-all <esip-all at lists.esipfed.org <mailto:esip-all at lists.esipfed.org>>
> Reply-To: James Gallagher <jgallagher at opendap.org <mailto:jgallagher at opendap.org>>
> Date: Wednesday, February 1, 2017 at 8:52 PM
> To: "esip-all at lists.esipfed.org <mailto:esip-all at lists.esipfed.org>" <esip-all at lists.esipfed.org <mailto:esip-all at lists.esipfed.org>>
> Subject: [ESIP-all] The Web Services Cluster
> Hello ESIP,
> Soren Scott and I would like to restart the web services cluster along the following lines:
> We
>  propose that the cluster look at measuring web services patterns of use at sites where large servers are run (e.g., NASA and NOAA). A casual observation is that subsetting services for data access are underused relative to simple file-access, but  to qualify
>  and quantify this more data about access patterns are needed. OPeNDAP has some experience with analysis of access data for web services (e.g., server logs) and often has found very telling patterns that can be used to improve server performance, so even if
>  the perception regarding under-utilization it false, there will be significant benefit to the analysis of use.
> If
>  it is the case that web services are underused, we should ask why. Is it because users lack knowledge about them? Or do these services underperform users' expectations?
>  represents an excellent forum for this investigation since it is unique in having people representing all three groups of users (implicitly) mentioned above (end-users, system developers and data center managers).
> If
>  you’re interested in this, or if you have a different idea for the cluster, please join us for a meeting next week. This
>  is a busy time for many, so to simplify finding a time, I’ve started a doodle poll:
> http://doodle.com/poll/r6hivdtygcw543g2 <http://doodle.com/poll/r6hivdtygcw543g2>
> If none of those times work for you, email me or contact me on the new ESIP #web-services slack channel.
> Thanks,
> James
> --
> James Gallagher
> jgallagher at opendap.org <mailto:jgallagher at opendap.org>_______________________________________________
> ESIP-all mailing list
> ESIP-all at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-all

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-all/attachments/20170203/4c3db74f/attachment-0001.html>

More information about the ESIP-all mailing list