 Okay, our next set of presentations are pretty exciting from the perspective of what you've heard this morning with some operator inputs and some of the panel discussion and also our keynote speech talking about the objectives and such. But now we're going to move into three presentations where this forum is actually bending metal and soldering wires and creating the code. So these are three specific examples where we're invoking the idea of creating capabilities in the OSDU forum. And so the first one is from the geospatial consumption zone and David Jacob, there you are. Welcome. Hello everybody. David Jacob, I'm the lead solution engineer with ESRI, mapping technology software. And we have a shout out to my mentor, Brian Bullme, who received recognition this morning. Thank you to the forum for that on his behalf. So we heard a lot of inspirational words this morning and just a preceding presentation by ThoughtWorks inspirational messages about how to organize and get work done. This is one example of what this forum has enabled technology to do and people to bring the technology together. So this is the geospatial consumption zone. So a lot of words there but I'll just get into it. So essentially the GCZ or Z, and there's even no standards there apparently. So its primary task is to enable the creation, management, and delivery of any data you have in OSDU in a geospatial way. So you have welds, you have seismic, you have weld boars, weld locations, surface, bottom, weld paths, all of that. You guys do great in modeling the reservoirs and the running simulations but there's a whole lot of other people in your companies who would like to see the fruits of your labor, bring that up to the surface, show them on maps and that's what we help enable. And so what this consumption zone does is to provide an open API so we have geospatial data layers as web services coming directly out of OSDU data platform. We expose those attributes that are in the data as much as possible in formats that are geospatially friendly. We allow geospatial search which includes just irregular polygon searches and things like that. We normalize the data because a lot of the data sets in OSDU it's in different schemas and such and to bring it into a sort of a normalized view is important for the mapping applications and importantly we also handle coordinate conversions. So you can work in local projects and show the data on a world map, et cetera. So fundamentally the consumption zone geo enables or provides map services out of the OSDU data platform. Architecturally speaking we have the geospatial consumption zone sitting on the top right under the consumption API's area alongside the other domain APIs and the generic API. So it's a layer on top of your core system. So what data have we and geospatially enabled to date? We have well tops and bottoms and pads and 2D surveys and also 3D surveys and 3D live traces. The list is long of the coverage but we are slowly bringing them online and some of those are dependent on whether that data set or type is available in OSDU then we bring geo enable that. We have also goals for future data coverage of other data elements, renewable energy items, open footprint, ecological, biodiversity items, et cetera. So those are things for the future. But if you work with map data, it's points, lines, polygons and a few other things so I think we've figured out the fundamental way of how to get data out of OSDU of those types and show it. So whatever other data sets that might come our way, we're positioned to deliver that. So I gave you the context of all of that, what we do and now this shows who has done it. I've only been in the project two months so I can't really take credit for any of this. You heard Brian Bullmay, he's a project coordinator from Esri but there's a whole lot of other operators and developers that are constantly contributing to this effort and I'd like to give a special shout out to our scrum master Joel Romero from Chevron who keeps us all to task and keeps that agile methodology at work in our teams from week to week. So I gave you the context of Geospatial Consumption Zone and just wanted to, before I talk about this project as an example of OSDU forum at work, right? So how did this project kind of come about? Well first of all I guess a subject matter kind of lends itself to it that everybody loves maps, right? You guys use maps to get here in some form or fashion. So that popularity of map visualization drove the engagement of folks from different industry groups and operators, vendors, etc., to come to the table. A lot of input from the requirements, use of stories perspective and that participation level was kept at a high level and so we've been able to work through the backlog and keep the focus. So as you might imagine our project team is geographically diverse as a lot of the other project teams are, split across companies, continents and time zones so it's been really helpful for the tools that OSDU forum provides to enable this work, right? So we have a big lab and Slack and the backlog tools we use, without them we would not be able to be productive and efficient in our work and of course again back to that scrum master that critical component of that individual that keeps the efforts going and keeping the lights on for the project. You know there are some areas for improvements or opportunities that we've kind of recognized and one is the nature of the world we work in where data is hard to come by in the space and so we've been set back about 50% of our time just looking for data of various types to then pull data into the example data sets that we need in order to code the geospatial side of the house. So that's an area that we want to keenly focus on is having a data ecosystem or an example data set that we can work toward. And then the other aspect is the environment itself, the cloud environment where we've had to work and we've been a little bit of a transient team going from one cloud environment to another so I think we're on our third development environment in just in a year so as you may know any cloud migrations of any type is challenging, right? And so that has set us back a few sprints, etc. So those are some of the challenges and opportunities that we have to even make further progress. So we have a blog out there on the consumption zone that was released at Mercury M15 and it's so it should be rolling out with all the cloud providers and then in this coming year for sure. Yeah, so here's our contact information as well. So with that, thank you.