We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

OGC Overview: programs, processes, standards baseline and new developments relevant for the OSGeo community

00:00

Formal Metadata

Title
OGC Overview: programs, processes, standards baseline and new developments relevant for the OSGeo community
Title of Series
Number of Parts
295
Author
Contributors
License
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
The coordination of increasingly faster development of geospatial Free and Open Source Software and more longer term oriented standards presents some challenges which have been identified and taken up by key organizations of the domain. OGC and OSGeo have a long history of cooperation, since many years we work together through a Memorandum of Understanding, which amongst other aspects provides OSGeo to a certain extend access to the OGC standards development process. The cooperation is meant to bring in requirements, ideas and expertise from the OSGeo community to the OGC programs and processes and provides the OSGeo community with an insight into the current developments of open standards. The Overview presentation will provide a short insight into the OGC programs and processes and will explain the idea and development approaches for the OGC baseline. It will also talk about the results of various hackathons (OGC API hackathon) and Innovation Program initiatives (e.g. EO Big Data Architecture) that will happen in June and July. It will furthermore give an update on the Future Directions technology trends mapping of OGC and how the OSGeo community can be part of it.
Keywords
129
131
137
139
Thumbnail
28:17
Service (economics)Field (computer science)SoftwareDialectService (economics)Centralizer and normalizerComputer animation
Source codeOpen setGrass (card game)RootDemosceneStandard deviationSelf-organizationProcess (computing)InformationSystem programmingRootBitSlide ruleStandard deviationOpen setWikiNumeral (linguistics)Link (knot theory)CollaborationismAreaMereologyFeedbackSelf-organizationNumberImplementationHand fanMultiplication signProcess (computing)WordTraffic reportingLecture/ConferenceComputer animation
Traffic reportingProcess (computing)WebsiteMetropolitan area networkLecture/Conference
Multiplication signMultiplication signStatistical dispersionComputer animation
TwitterInternet der DingeTablet computerInternetworkingLaptopTemplate (C++)SmartphoneNeuroinformatikComputer animation
EmailSource codeMaxima and minimaInformation securityMIDIWechselseitige InformationInformationInformation securitySound effectEvent horizonExtreme programmingComputer animation
Uniform resource locatorPhysicalismSound effectInternationalization and localizationEvent horizonPhysical systemInformationStandard deviationOpen setLecture/Conference
Representation (politics)Visualization (computer graphics)Maschinenbau KielCountingProduct (business)Process (computing)Standard deviationPhysical systemBitProduct (business)
Web browserService (economics)Scalable Coherent InterfaceOntologyInformation securityVirtual memoryInformation systemsDesign by contractMoving averagePlastikkarteInformationAnalytic setDecimalCommon Language InfrastructurePublic domainStandard deviationProcess (computing)Computer programIntegrated development environmentOpen setTelecommunicationImplementationGroup actionRevision controlComputing platformData managementStandard deviationProcess (computing)SoftwareComputer programmingService (economics)Shared memoryInformation securityWeb browserDifferent (Kate Ryan album)OntologyUniform resource locatorCartesian coordinate systemDesign by contractCircleOpen setPhysical systemComplex (psychology)Electric generatorDecision theoryMachine learningInformation managementExploit (computer security)Electronic mailing listGroup actionRevision controlDomain nameComputing platformWeb 2.0TelecommunicationAddress spaceState observerIntegrated development environmentInformationProduct (business)PlastikkartePoint (geometry)Sign (mathematics)EmailSoftware testingAnalytic setEvent horizonBitWindows RegistryImplementationVirtual machineXML
Standard deviationComputer programmingSoftwarePresentation of a groupCollaborationismProcess (computing)Software developerBitImplementationLecture/Conference
Standard deviationProduct (business)Self-organizationServer (computing)Computer programCodierung <Programmierung>Interface (computing)PrototypeOpen setIntegrated development environmentBuildingProcess (computing)Condition numberPersonal digital assistantCollaborationismInternet forumSoftware testingInformationTelecommunicationStandard deviationSoftware developerComputer programmingIntegrated development environmentTelecommunicationSoftwareResultantGoodness of fitCASE <Informatik>Internet service providerSelf-organizationEvent horizonPrototypeImplementationSoftware testingSlide rulePresentation of a groupProcess (computing)Metropolitan area networkBlock (periodic table)MathematicsForcing (mathematics)Real numberValidity (statistics)Computer animation
Computer programStandard deviationComputer programmingLecture/ConferenceComputer animation
Computer programOpen setStandard deviationIntegrated development environmentPublic domainGroup actionSlide ruleOperations researchComputing platformStatisticsNeuroinformatikArtificial intelligenceChainBlock (periodic table)Local GroupObservational studyLibrary catalogSoftware developerService (economics)NeuroinformatikSelf-organizationComputer programmingState observerSoftware developerArtificial neural networkAreaDomain nameBus (computing)Group actionWeb serviceMappingSpacetime19 (number)Traffic reportingMultiplication signInteractive televisionComputing platformElectric generatorGauge theoryWeb 2.0Exploit (computer security)Focus (optics)ResultantLink (knot theory)Standard deviationBoundary value problemSoftware testingObservational studyLimit (category theory)Network topologyComputer architecturePoint (geometry)Goodness of fitSlide ruleLevel (video gaming)Open setIntegrated development environmentMultilaterationWorld Wide Web ConsortiumDialectComputer animation
Software developerSoftware testingOrder (biology)Lecture/Conference
Utility softwareLibrary catalogOpen setService (economics)Standard deviationBlogMultilaterationElectronic mailing listLattice (order)SoftwareInformationGroup actionBlock (periodic table)Event horizonDialectWebsiteProcess (computing)BlogOpen setComputer animation
Standard deviationStandard deviationKey (cryptography)Right angleMusical ensemblePhysical systemOpen setComputer animation
TwitterService (economics)Goodness of fitLevel (video gaming)Computer programmingStaff (military)Scheduling (computing)Presentation of a groupLecture/Conference
ResultantProcess (computing)Software testingSoftwareComputer fileWebsiteElectronic mailing listType theoryStandard deviationLecture/Conference
Computer programmingSoftwareUniverse (mathematics)Self-organizationTestbedElectronic mailing listElement (mathematics)Type theoryShared memoryGoodness of fitSystem callEndliche ModelltheorieSoftware testingBitPower (physics)Point (geometry)Metropolitan area networkLecture/Conference
Transcript: English(auto-generated)
So, who am I? I ask myself every morning. Who am I? I'm I'm Athena, some of you know me, some of you have not seen me before. I work since a couple of years for OTC and
I work in the field of GIS since over 20 years. Yeah, I've been 10 years working for in the private industry and since 2009, I'm OTC's director for regional services for Europe, Central Asia, and Africa. This means I'm
connecting with people. I'm bringing people together. It's a lot about networking. It's about a lot about informing what we are doing in OTC. I reach out to stakeholders and we have alliance partners, so I also work partly with alliance partners and and yeah, I'm here also because I'm a charter member for OSGIO since 2008 and
to give you a little bit of an idea why, you know, why OGC and OSGIO has a cooperation. We have a memorandum of understanding. Here are
in one slide the roots of OGC and who of you has seen Judy Garnett's presentation? Yeah, excellent, so I think he presented very, very well the history and the story about both organizations. So in 2008,
OGC and OSGIO decided that they need to or there there is a need and the wish from the community to collaborate and we identified a lot of common areas of work between the two organizations. So this is changing over time.
Of course, OGC standards are an important role because the OSGIO community are implementing that so we get a lot of feedback from from the OSGIO community, the Phosphor G community. Open API is a topic of common interest and team engine and Dirk Stenger, are you here?
Yeah, so we have one of the guys behind team engine sitting here and Stefan as well as Angela and Tom, they will also talk about in more detail about those topics of collaboration. So the Phosphor G community
developed and contributed to numerous reference implementations, and you will also hear about that later. So all these led in 2008 to a memorandum of understanding and there is a link where you can find the memorandum of understanding. It's in the OSGIO Wiki and just to give you an idea, one part of the MOU is that we from OGC provide
six slots for individuals from the OSGIO community to participate in the OGC process and report back to the OSGIO community. So it's really a process that is behind that and if you're interested to
learn more about that either talk to me or Bruce Bannerman on the OSGIO site because he's leading the process there. Good, we're all living in exciting times. There's new technology, new gadgets to play around with,
you know, drones, just to name a few, variables, variable devices and many more things. So I think it's a nice playground for adults that never really grew up. So there's also abundance of data
not only from the EO community, but all the sensors that are out there, they're collecting a lot of data. So and you see the trend is really going up and the abundance of devices that comes with the new technology, I just say Internet of Things, so there's more and more out there.
Before also, you know, we had just one computer with us, if at all a laptop. Now you have your mobile phone, you have your smartphone, you have a tablet and what else. So there's a lot of technology going out. Available and
the question is how do we use all these devices and the information we are gathering to address the challenges we have. And some of the challenges are of course a very pressing one is food security. And in recent years that topic has really come up. It has become very important because it's a critical issue.
Droughts, we need drought monitoring, we see more and more extreme weather events. So these are challenges, these are, they have an effect on the society, on humankind. And
yeah, the question is what can we as a community that is addressing or dealing, working with local location information, what can we do to support or to help addressing these challenges? Yeah, interoperability is one aspect. So on the one side we have the human systems,
we have the natural systems, and then we have the physical infrastructure systems. And the question is how do we bring those together? And open spatial IT standards is one way and a critical requirement to bring all the data together and
to understand and manage the amount of data and that is produced or inherent in these systems. So when I talk about interoperability, you know, a lot of topics, workflows, data, products, and just visualize it a little bit. And I'm not going in detail and all that, what I will show you, it's just to give you an idea
about what we are talking. So before it's just, you know, one sensor, a browser, and a user using the data that came out of the, that comes out of the sensor. More sensors require additional devices or
an additional process, so it's the device registry. Then you add data services, you have an event feed, you need to check on ground truth. We do a lot of analytics, so, and there is data science, a very actual topic, again more analytics, ontologies.
So the system grows more complex automation tools, digitization, government governance, so it's growing bigger and bigger, and of course security as a topic, and all these balls you see, all these circles you see, it's, you know,
they require to communicate with each other, so it's all about interoperability. Software as a service application, edge services, machine learning, smart contracting, everything, and we need to handle that.
So, and how, how do we do that? And this is, well, how open standards come into play, and we at OTC, we're passionate to bring people together that talk about the challenges, that address the requirements from, from, from different communities, and
yeah, make location information available to everyone, and I think one aspect is, you know, we need to, to leave a better world for our kids and for future generations, and that's bringing together and connect communities, technologies, and decision-making.
It's very important to create a sustainable environment and sustainable future for all of us. And interoperability and the use of open standards is critical to use, share,
access, reuse information and data that come out of all, comes out of all the sensors. In OTC, and that's the bottom point, we have processes that are addressing, of course, standardization and innovation, and I will talk today,
you know, give you an insight into our programs, and I said the speakers after me, they will go into more detail with some more technical aspects of our programs. So these are the main programs in OTC. We have an innovation program, standards program, connected to the compliance program, and
communication outreach, or marketing and communication, as we call it now, and looking into detail, so the standards program, this is of course where the standards are developed, and
it's connected very closely to the compliance program, because if you have, the OTC standards can be implemented into software, and then you can test the software and say, okay, if you pass the test, I'm OTC compliant. So it's about product implementation. The OTC standards program has different kind of working groups. On the one side,
there are the domain working groups, and we are addressing, you know, a whole plethora of topics starting from agriculture, aviation, 3D, information management, citizen science, big data, earth observation exploitation platforms,
land administration, just, of course, spatial data on the web, marine SDIs, and all those domain working groups, they are, the mailing list that we have, they are open for non-members. So if you're interested to get an understanding of what we are discussing in these working groups, please let me know. I can help you to participate in these domain working groups.
So the standards working groups are for members only, and this is where the standards are developed. This is where the work on candidate standards takes place. Prior to the approval, they make revisions to existing standards. So this is,
we will see some of the discussions that are currently happening there in the presentation from Tom and Angelos. So in the last one and a half years, so we started, or maybe two years, we started to do a lot of the developments
on GitHub, and this makes it also more accessible for non-members. So we opened up our processes a little bit, and that is also due to the collaboration and cooperation with the OSGEO community. So remember
the standards program, this is where the standards are developed, implementations, the standards can be implemented into software, and this is, in very short, only one slide about the compliance program, and Dirk has a presentation tomorrow about TeamEngine, that is the software that is behind the compliance testing.
So, and if you have any questions, by the way, we are here a team, so please ask questions right now. We want to make it more interactive. Good. We covered, very short, and I could talk for hours about what we are doing in more detail, but in very short, that's a standards and compliance program.
Now we are looking at the innovation program. That's where prototype implementation takes place. It's the results of it, our engineering reports, the innovation program is addressing real-world scenarios, and the idea is to have an
agile development environment where we can rapidly develop, test, validate, and demonstrate the use of new standards in real-world use cases. So we have sponsors, they have a requirement on interoperability, remember the challenges ahead that are coming, and
so we as an organization and OGC, we are realigning the technology users and providers to work together identifying and addressing the requirements. So it's also a cost-sharing exercise, and Stefan
will, yeah, we'll talk about how they participate in the OGC innovation program. I have to change that. And it's a repeatable process, so we have run over a hundred initiatives in the innovation program. Who of you know Luis Bermúñez?
Yeah, he's our executive director for the standards program and the compliance program. So if you have questions about that ask Luis, or of course you can ask me and I connect you with Luis. Luis is based in the US, so, and I think he participated in the last,
usually participates in the North American Phosphor-G events. Good. Standards program with the compliance program, then the innovation program that feeds all the results back to the standards program. And then of course, it's all about market adoption.
We need to talk about what we are doing because that's also good for the community. If you do something, of course you want your results to be published to respectively the software, if you give a software developer that the software is used. So we have market and communication program. We are writing blogs,
press releases, and we promote what our members are doing and any gaps or enhancement that are identified, again go back to the innovation program and the innovation program then reports, so to say, back to the standards program. So this is a very, very brief
the interaction between the OTC programs. Good. I have a few more slides on what's new in 2019. So, so far so clear. If there are any questions, you know, we have time to discuss those and
yeah, as I said, I'd like to have more interaction with you. So what's new in 2019? We have, we had a very busy year. We have a new leadership in OTC. Nine standards have been approved, 30 engineering reports. That is the results that are the results of the innovation program activities.
We have discussion papers and white papers published, and we have new domain working groups and yeah, I want just to point out, we have Nadina Lamez, a former colleague. She came back, returned to OTC as our new CEO. Very glad to have her. She's based also in the DC area and Bart de Lattauer,
he is based outside of Antwerp in Belgium, and he's now our president. So we have also a leadership team that is partly in Europe, partly in North America and yeah, Mark Reichert is still with OTC. That's our previous, or my previous boss, still there.
Yeah. New domain working groups recently initiated, I mentioned Earth Observation Exploitation Platform domain working group. This is, it's a lot about the EO community in the industry in Europe,
but also, of course, connecting with other regions of the world. We have a statistical domain working group. We call them DWICs and artificial intelligence and geoinformatics. It's pretty new, so I think we just published the
the charter. Then blockchain and distributed ledger technologies and portrayal. Here you get an idea what topics we were addressing in the innovation program. So it's from smart cities, we do a reference in architecture pilots in North America, marine SDI concept development studies, maritime limits and boundaries pilot.
We work together with IHO, the International Hydrographic Organization, indoor mapping and navigation pilot, routing, testbed 15 is ongoing, and we plan some sprints on the OTC API
activities. And if you want to learn more, there's again is a link where you can read about these initiatives. Open API, open API, open API. You will hear about that later. One more slide. So we, the whole initiative started from a joint working group between OTC and
W3C. It's the spatial data on the web working group. And the focus of the open API next-generation standards is to focus on easing developer effort in today's app environment and getting content to the web.
So and for and expanding the reuse. So I was, we were asked questions like, oh what happens to the OTC web services standards? They are still there because they are broadly and globally implemented. We will continue to support them, but not on the level as we're doing, as we're doing it now. And
we see a lot of members engaging in this topic. The developer community is included and then there are some ideas between OSGO and OTC how to go ahead on the topic. And
one thing, just remember OTC API as a catalog and so that is something to keep in mind for later. You might wonder what is she talking about? But you will see. So if you want to get engaged or learn more or see how the OTC works,
we have so-called technical committee meetings. This is when the members come together, work in the working groups and yeah, it's also about networking. And here you have the the list of upcoming events. We are in Canada in September in Toulouse and in Banff in Canada in September, in Toulouse in France in December,
then Hong Kong in March, June, Montreal and then September, Munich. That's just the week before the Oktoberfest. So if you wanted to go to the Oktoberfest, make sure you be there a week earlier to go to come to the OTC meeting.
And how can you stay tuned? We have a blog, we have blogs on our on our website and the last blocks are really, they look into the, you know, they describe the process behind open API. You can read about past OTC member meetings and there's a lot of information there.
So one of my usual last slide, I would say stay curious and participate. Really avoid reinventing the wheel. If you have something just, you know, and then it's about interoperability, have a look at OTC, what we are doing or work through the Foscas community to get in touch with us,
then interoperability and open standards help to sustain investments and you know, I would say this conference is really a success because we have so many people from, we have over thousand people from yeah, all around the globe, so
key to success is contribution cooperation on an international level. Good. Thank you. Are there any questions?
Okay, so I'm moderating my own session. Latina, now we have now, you know, as I mentioned we have two more presentations here that relate to the OTC programs and already I want to, Stefan, maybe you can come already on stage because Stefan Meisel from EOX, he will talk about
EOX's experience in the OTC innovation program. So yeah, the schedule is, we have five minutes to change, but if you have any questions,
yes,
so if I understood correctly, the question is how do you get certified? Yeah, okay. So we have a, we have a process we have on our website. There is the OTC compliance test.
This test is run by the team engine and if you have a software that is implementing OTC standards, you can do this test. There's no cost
if you want to test things out and if you pass the test, you know, there are certain certain questions or certain technical aspects the software need to fulfill. If you pass them a hundred percent, you get a result and say, okay, you are fully compliant and
then if you want to have the logo, the logo I showed on one of the slides, that comes with the cost. But to understand if your software is OTC compliant or not, you don't have to pay anything and the process is a matter of
24 hours, 48 hours, it's really a fast process and the result you give, you get back is also showing where if you fail in the one or other aspect, it gives you also back where you fail so you can work on that. Maybe to add, to add one aspect,
there is a really, if you go to the OTC page, there's a really long list of software that's implementing stuff and there is two different types of, so you can say I'm implementing it, you can just register you for free. This doesn't cost anything. Only when you need the certified, when you want to have this certified label, that's when the fee comes into play.
But there is a, like, I don't know, maybe, I don't know the percentage, but it's a really long list of implementing software already as well there. Yeah.
That's a good question. I don't know the budget. I can tell you how we are financed. So we have over 500 member, 530 member organizations. They are paying a membership fee. So, just to give you an idea, a university in Europe pays 500 US dollar per year.
Government agency, 4,800 US dollars. Small company, 2,400 US dollars. But then we have technical members, they pay 12,000 US dollars. And we have principal members, they pay 55,000 US, 60,000 US dollars. And strategic members, they have a strategic interest, they pay
more. So this is how the money comes in. On the membership side, and the other revenue is the innovation program I mentioned. So, if a sponsor has interest, for example, take thing of the routing pilot,
they say, well, we are interested in doing that, and here is amount X. You know, do something with it. We, as OTC staff, we are looking for more sponsors to bring more money together. And this money then goes to the members that are working in this pilot.
So in testbed, I don't, I think the last OTC testbeds, these are really the major testbeds. They have always been between 1.8 and 3 million US dollars. And the money goes to the participants, which are members. But, for example, if you,
we have an open call usually for the testbeds, and if there are topics that are of interest for you, you can apply, even if you're not a member. And if the sponsor said, wow, this offered solution looks really interesting, I would like to work together with them.
Then, you have to become an OTC member. But this is really, you know, if you're a small company, given the amount. This is how the budget works. Maybe worth mentioning for the testbeds as well, you said it's 1.8 to 3 million. And this is typically then doubled because it's a cost-sharing model.
So you typically, a typical share would be that 50% of your cost is covered from the sponsors, but you are also contributing 50% of the cost when participating. In-kind contribution or whatever. Good. Thanks.