OGC blogs

  • GeoPackage guidance
    Contributed by: 
    OGC Architecture Board (OAB)

    The OGC Architecture Board (OAB) – comprised of elected OGC member experts – is tasked to ensure that candidate standards 1) align with the OGC Standards Baseline, 2) are compliant with the OGC Modular Specification policy (where appropriate), and 3) have considered the intersection with and dependencies related to other OGC standards and with partner international standards organizations such as ISO/TC 211.

    In a recent OAB meeting, the GeoPackage 1.2 candidate standard was reviewed against the criteria above. The OAB reached a consensus that the candidate base standard is ready to be released to proceed to an approval vote in the OGC, but that the Elevation Extension does not yet meet the criteria. The OAB requested that the Elevation Extension include normative and informative references to one or more standard methods of encoding elevation, specifically methods that are consistent with coverages as defined in the OGC Coverages standard (also published as ISO 19123) and the ongoing harmonization of OGC and ISO coverage standards. This is not a repudiation of the work done to date. Rather, the OAB recognizes that elevation content is of general interest to OGC and ISO standards and thus the work should be as broadly applicable as possible. The expectation is that an updated Elevation Extension will be based on the work already drafted as part of GeoPackage 1.2 and will proceed in a rapid fashion through the OGC process. OGC encourages the participation of the developer community in finalizing this extension. Meanwhile, separation into two documents will allow the core standard to move forward without further delay while providing opportunity for the issues identified above to be addressed.

    The GeoPackage Standards Working Group (SWG) began its first work in an environment that was somewhat unique in the OGC in that the implementer community was deeply involved in the development of the standard from the very beginning and the standard evolved in parallel with software testing. Now other OGC standards are following a similar model, much to the benefit of the geospatial community. While separation of the GeoPackage core from the Elevation Extension and revision of the latter specification is inconvenient for early implementers of the draft extension, the longer-term benefits of additional work on the extension will benefit not only the GeoPackage software community in terms of improved modularity, but also the OGC standards community as a whole by leading to a more consistent model for “elevation” across different formats and encodings.

  • Leveraging the OGC Innovation Program to Advance Big Data Spokes
    Contributed by: 
    Luis Bermudez

    The National Science Foundation (NSF) currently has an open program solicitation that seeks to establish more ‘Big Data Spokes’ to advance Big Data Applications. Like the BD Hubs, the BD Spokes will provide a regional coordinating role but they will focus on narrower topic areas, such as applications concerning the acquisition and use of health data, or data science in agriculture, among others. In addition to its topic area, spokes will be driven by three themes: 1) advance solutions towards a grand challenge, 2) automate the Big Data lifecycle, and 3) improve and incentivise access to critical data.

    Using the Open Geospatial Consortium’s (OGC) Innovation Process could help Big Data Spokes advance a solution to better integrate and run analytics on data sets using technologies that are not only freely available and ‘open’, but that are also maintained by an established Standards Development Organization (SDO). OGC also has various domain working groups currently advancing solutions that would complement the work done in Big Data Hubs.

    The OGC is an international voluntary SDO that provides a broad interface with over 500 industry, government, academia, and research organizations engaged in advancing standards to improve geospatial interoperability. OGC’s standards are implemented in hundreds of products to improve the discovery, sharing, access, fusion, and application of location-based information. In addition to its proven consensus process for advancing open standards, OGC - via its Innovation Program - provides a venue in which to prototype in an agile, collaborative environment. It has developed more than 90 initiatives in the last 17 years.

    OGC’s Innovation Program Initiatives have helped advance technology solutions that deal with important challenges, such as those rising from continued population increase. Most recently, OGC’s Future City Pilot Initiative created technologies that aid in the provision of adult health services using multi-source data analytics (you can learn more in this 5 minute video on OGC’s Future City Pilot).

    An OGC initiative could help prototype and design a solution for Big Data Spokes, based on open standards, that could be further implemented in a Data Hub. An OGC initiative has five phases:

    • Phase 1 - Concept Development: OGC gathers requirements and proposes an initial systems architecture.
    • Phase 2 - Call for Participation (CFP): OGC publicly invites industry and non-industry organizations worldwide to participate in the Initiative to develop the components of the architecture.
    • Phase 3 - Team Formation and Kick-off: The OGC evaluation team selects participants. Selected participants meet face to face at the initiative kick-off meeting to coordinate on the development, testing, and demonstration process.
    • Phase 4 - Execution: Participants engage virtually through frequent teleconferences, net meetings, and email exchanges to discuss progress and to identify and resolve issues.
    • Phase 5 - Reporting, Demonstration and Outreach: Technology demonstrations occur at the end of the Initiative to showcase the major accomplishments. Engineering reports and other artifacts are written that identify and summarize the resulting technologies.

    The completion of such an initiative would result in a proven solution that can be implemented in a Big Data Hub to help automate Big Data lifecycles, and support, for example, Smart Cities or Health related challenges.

    If you want to learn more about how to partner with OGC for the NSF Big Data Spokes, or other solicitations, please contact Luis Bermudez, Executive Director of the OGC Innovation Program (lbermudez at opengeosptial.org).

  • Our newest OGC staff member: Marie-Françoise Voidrot
    Contributed by: 
    Marie-Françoise Voidrot

    Today I am honored to join the staff of OGC Europe as Europe Director of the Innovation Program, and to contribute more intensively to the development of OGC activities.

    Prior to joining OGCE staff I worked with Meteo-France, the French national weather service. While working there, I was a project manager of weather information systems for meteorological forecasters, with major customers like the CNES, the French Armed Forces, Air France, etc., and, more recently, for mass market consumption via the Internet and mobile apps.

    As an OGC member, I have contributed to the definition of the MetOcean Domain Working Group that I have co-chaired with Chris Little since 2009. Together, we have helped the definition of common terms of reference for a relationship with the World Meteorological Organization that supports both hydrological and meteorological standards development.

    I have been involved in the organisation of several annual workshops within the Met Community to gather the issues identified by the developers, while providing Met Ocean data with OGC standards to several spatial data infrastructures, including INSPIRE and SESAR. Met Ocean data is complex, inherently spatial, temporal, and constantly changing. It is big, heterogeneous, and multi dimensional - including multiple time attributes. Another source of complexity is the very demanding level of service, as these data are used for critical safety purposes, and are essential for major business activities.

    The MetOcean DWG provides an open forum to work on meteorological data interoperability, and a route to publication through OGC's standards ladder (Discussion paper -> Best Practice -> Standard -> [and if appropriate] ISO status), and giving a route for submission to WMO CBS for adoption. Since 2009, the DWG has produced several Best Practice documents (available on the MetOcean DWG wiki) and multiple presentations to further knowledge and understanding of the complexity of these environmental data.

    As further background, I have a Master’s Degree in Computer Sciences from Ecole Centrale Paris, and a Master’s Degree in meteorology from the Ecole Nationale de la Meteorologie (French National School of Meteorology). I am trilingual (French, Spanish, and English), and am located in Toulouse, France.

    As a new OGCE staff member, my first focus will be on the NextGEOSS, which fits perfectly with my experience. NextGEOSS aims to develop GEOSS into a next-generation data hub, and increase the use of Earth Observation data to better support decision making.

    If you would like to get in contact with Marie-Françoise to offer congratulations or discuss the MetOcean DWG, NextGEOSS, or other OGC activities, she can be reached at mvoidrot [at] opengeospatial.org, or on Twitter @twitt_mfv.

Markus Schneider blog

Simple Features

On INSPIRE, rich application schemas, GML and deegree in general
  • INSPIRE Download Services with deegree 3.2: Part Three
    The second part of this series focussed on harmonized INSPIRE datasets and their GML encoding. It also lined out why the technical features of the deegree WFS make it an excellent choice for serving valid, harmonized, GML-encoded INSPIRE datasets. Why … Continue reading
  • Writing processes for deegree WPS
    Finally, there’s an updated documentation for writing processes for the deegree WPS. It’s part of the new deegree webservices documentation, which has been released together with deegree 3.2. deegree WPS is an implementation of the OGC Processing Service specification. Notable … Continue reading
  • deegree webservices 3.2.1 released
    Today, the first maintenance release for deegree webservices 3.2 has been released. Get it here: http://www.deegree.org/Download Changelog: Pull request #85: WMS: Fixed outputting of layers if the corresponding theme has no layers and subthemes Pull request #86: WFS: Fixed default … Continue reading
  • INSPIRE Download Services with deegree 3.2: Part Two
    The first part of this series described the different classes of INSPIRE Download Services and why a Direct Access Download Service is most versatile. It also lined out that a Download Service may be interoperable or non-interoperable and that data … Continue reading
  • INSPIRE Download Services with deegree 3.2: Part One
    Why has deegree webservices 3.2 been dubbed “INSPIRE release”? This blog post series explains why it is an excellent choice for providing compliant INSPIRE Download Services, especially if you want the full monty: Interoperable Direct Access Download Services that serve … Continue reading

feed-image Feed Entries