Interoperability and Technology

Welcome to the Information Technology and Interoperability Committee Wiki Committee Chair: Dave Blodgett

Get Involved

The IT&I committee provides a venue for a monthly community webinar on current Information Technology and Interoperability topics. In early years, the webinar series was known as the "IT&I Rants and Raves" a title the committee is bringing back starting in 2023.

Rants and Raves are designed to get smart people to share insightful, provocative views of what's great and what's not about technology and interoperability in modern Earth science. We welcome, high energy talks on personal pet peeves: topics that you can't believe in this day and age we're still dealing with, or solutions that you can't believe that in this day and age more people aren't using.

Upcoming meetings 3pm ET (calendar)

IT&I OGC October 2023

October 26th: Scott Simmons

Improving standards and documentation publishing methods: Why can’t we cross the finish line?

OGC and the rest of the Standards community have been promising for YEARS that our Standards and supporting documentation will be more friendly to the users that need this material the most. Progress has been made on many fronts, but why are we still not finished with a promise made in 2015 that all OGC Standards will be available in implementer-friendly views first, ugly virtual printed paper second?This topic bugs me as much as it bugs our whole community. Some of the problems are institutional (often from our Government members across the globe), others are due to lack of resources, but I think that most are due to a lack of clear reward to motivate people to do things differently.Major progress is being made in some areas. The OGC APIs have landing pages that include focused and relevant content for users/implementers and it takes some effort to find the owning Standard. OGC Developer Resources are growing quickly with sample code, running examples, and multiple views of API resources in OpenAPI, Swagger, and ReDoc.

November 9th: Hannah Ake

Persistent Unique Well Identifiers: Why does California need well IDs?

Groundwater is a critical resource for farms, urban and rural communities, and ecosystems in California, supplying approximately 40 percent of California's total water supply in average water years, and in some regions of the state, up to 60 percent in dry years. Regardless of water year type – some communities rely entirely on groundwater for drinking water supplies year-round. However, California lacks a uniform well identification system, which has real impacts on those who manage and depend upon groundwater. Clearly identifying wells, both existing and newly constructed, is vital to maintaining a statewide well inventory that can be more easily monitored to ensure the wellbeing of people, the environment, and the economy, while supporting the sustainable use of groundwater. A uniform well ID program has not yet been accomplished at a scale like California, but it is achievable, as evidenced by great successes in other states. Learn more about why a well ID program will be so important to tackle in California and offer your thoughts about how to untangle some of the particularly thorny technical challenges.

ESIP Vision

To be a leader in promoting the collection, stewardship and use of Earth science data, information and knowledge that are responsive to societal needs.

Information Technology and Interoperability Committee

The Information Technology and Interoperability Committee of the ESIP Federation is a standing committee created to:

ensure that data, information and services can be readily exchanged and integrated to improve Earth science data, information, products and services; and
encourage the use of standards and protocols relevant to interoperability;
encourage the use of best information technology practices to ensure the quality, usability and breadth of standards and protocols relevant to interoperability.

@@ Line 23: / Line 23: @@
 OGC and the rest of the Standards community have been promising for YEARS that our Standards and supporting documentation will be more friendly to the users that need this material the most. Progress has been made on many fronts, but why are we still not finished with a promise made in 2015 that all OGC Standards will be available in implementer-friendly views first, ugly virtual printed paper second?This topic bugs me as much as it bugs our whole community. Some of the problems are institutional (often from our Government members across the globe), others are due to lack of resources, but I think that most are due to a lack of clear reward to motivate people to do things differently.Major progress is being made in some areas. The OGC APIs have landing pages that include focused and relevant content for users/implementers and it takes some effort to find the owning Standard. OGC Developer Resources are growing quickly with sample code, running examples, and multiple views of API resources in OpenAPI, Swagger, and ReDoc.
-November 9th: [https://cawaterdata.org/teams/hannah-ake/ Hanna Ake]
+November 9th: [https://cawaterdata.org/teams/hannah-ake/ Hannah Ake]
 Persistent Unique Well Identifiers: Why does California need well IDs?

Difference between revisions of "Interoperability and Technology"

Revision as of 14:04, October 17, 2023

Get Involved

ESIP Vision

Information Technology and Interoperability Committee

Archive