We hope you enjoyed the webinar, “Extending the OSDU Data Platform with the Geospatial Consumption Zone (GCZ).”
You may watch the recording here: https://mediaspace.esri.com/media/t/1_9o5jrptp
In this webinar we discussed the OSDU Data Platform and how geospatial can be managed and streamed to dynamic web services via the Geospatial Consumption Zone (GCZ) industry project. In addition, we shared a brief history of OSDU and how it has evolved and described the GCZ, its purpose, architecture, and value. Lastly we shared insights from user stories centered around enterprise geospatial data management driving the GCZ development effort.
For further information or questions, please contact the following Esri staff:
• Brian Boulmay: bboulmay@esri.com
• David Jacob: djacob@esri.com
Please view the webinar deck below.
Select Questions and Answers from the webinar:
Q: Will the GCZ work with local project coordinates?
- A: Within the OSDU framework they have their own coordinate handling service. Everything thr GCZ does uses that service. So however, your data is handled, it will be handled in the same way regardless of it’s for a different OSDU process or for the GCZ process. For step one of the GCZ we are focused on that kind of global normalized view which also means global normalized projection, but the tool has been designed to where you can also run a local coordinate spatial layer as well. So, yes, you would be able to choose a local project CRS to produce some spatial layers that may serve a specific project choice. That would be a decision you make when you setup the transformer.
Q: Will this project manage other geospatial data for our users?
- A: OSDU is designed to handle subsurface data and as time goes on, they will pick up other datatypes. But most of these datatypes tend to be quite complex, kind of structured data. It’s really not designed to handle geospatial data. So the consumption zone architecture by default is a read-only architecture out of OSDU. So, the consumption zone is more about getting spatial data out of OSDU not putting spatial data into OSDU.
Q: Does this change anything about how ArcGIS enterprise is deployed?
- A: Absolutely not, all those other data types we talked about and all the other different formats you already must manage that will stay the same. What it will change is potentially a lot of ETL or processing that you do today to get wells or seismic out of your Master System and into your geo-spatial stack. In theory, you won’t have to do that anymore because that data will just be there as part of OSDU. You’ll just take those service endpoints and you’ll register them with your portal and now that data is just there to participate in your portal straight off of OSDU. Could you take that data and still put it into your enterprise? You could but then you’re right back to making copies and managing separate services. So the pattern we believe we’re going to see is that people will have their ARCGIS enterprise still up and running serving out all those other data types that support the upstream business and your OSDU will provide the geo-spatial consumption zone for those data types that are specific inside of the OSDU framework. We see these two things working in parallel, and they don’t even have to be in the same place.
Q: Any plans for incorporating Azure Cloud?
- A: There’s four cloud provides that are involved with OSDU: Microsoft Azure, AWS, IBM, and Google. IBM and Google were the first two to pickup support for the GCZ., right away around M13, M14. AWS is picking it up, I believe it was M16 and Microsoft has told us it’ll be M17, potentially M18. So the difference there is each choice and what pace they pickup the different modules of OSDU. It has been out there and publicly available since M13. We have customers that are running in Azure that have downloaded it and started using it without waiting for the cloud provider to do their part. So, it just depends on how your OSDU is involved. It will run in Azure now. If you’re managing your OSDU environment in Azure you can go to the OSDU website, you can pull down what you need to install and configure this and you can start running today. If you’re waiting for a Microsoft Managed OSDU then you should get that either in M17 or M18. Microsoft hasn’t nailed down the exact one. So, yes, we will be on the Azure cloud.
Thank you for your time and attention. Be on the lookout for additional petroleum webinars.
Warm Regards,
The Petroleum Team
