And welcome everyone and thank you for joining today. My name is Hamemed and I work with a product management group in Geographics and today I will take you through what's new in GIS Geographics for the 2024.2 version. We've packed a lot into this release and there are over 100 new features and improvements across Geographics to make your day-to-day work easier and faster. I won't go through every single one, but here's what I will cover today. Uh we will start with the major transition happening on the GIS side, moving away from RGIS engine runtime. Then we look at the upgrades to field planning, expanded integration with TGS, brand new connection to MJ logs, some major updates to query builder, and finally improvements to the geology and geoysics tools. We'll begin though with the most important and impactful change in the 2024.2 version. I'm referring of course to the deprecation of RGis engine runtime. Uh you've probably heard by now, Ezri is phasing out the RGIs engine runtime. This has a serious impact on geographics and how we deal with some of our GIS workflows. We made use of this technology for a long time for some critical functionality that a lot of users relied on. The good news is that even though the runtime is going away, we've transitioned to newer technology from EZRI. So we can keep providing the tools that you need. We've approached this in two ways. First, we've rewritten workflows to not require EZRI or any other third party for that matter. uh but where we couldn't avoid a third party dependency uh like connecting to mapping services for example RGS enterprise RGS online WMS WMTS for those kind of workflows we've switched to EZR's newer RGIs maps SDK second for workflows can that can now only be accessed inside RGis Pro we've built a new addin for RGis Pro which lets you transfer data between your geographics and pro projects the basic idea idea is to let geographics users easily access the advanced GIS capability that RGis Pro provides with a simple uncomplicated way to move layers back and forth. So, what does this mean for you? Um, most importantly, and I want to stress this again, all GIS workflows that were available in earlier geographics versions are still available in 2024.2. We spent a lot of time making sure of that. You're not losing any functionality. But on top of that, deployment is much simpler now. You don't need any extra installs, downloads, you know, no extra license configuration, anything like that. Everything is packaged within Geographics and it is ready to use right off the bat. You also get seamless integration with RGis Pro with a new added enabling that birectional transfer. And finally, any existing layers that EZRI has deprecated or no longer allows access to outside Pro are easily converted. your maps and projects upgrade with minimal disruption. All right, that's the background. Now, let's switch over and walk you through how all of this looks inside Geographics. Okay, so within geographics, uh we have rewritten a lot of the workflows that depend on Argis engine. As I me mentioned during my slides, um one of those workflows was geo referencing. Again, it's still available pretty much the same way that as it was before, only this time it's not dependent on the engine. we kind of have our own code uh written for it. You can still georreerence your images. Um, one of the other workflows that we used the uh RGis engine for was the ability to uh select wells within a polygon. So when with a polygon selected or multiple polygons selected, I can rightclick and say uh select wells that fall inside a polygon. Again, that still works. We have made it a little better. is a little faster uh and actually honors your uh selections a little better. Now, as you can see, only the two selected polygons have their wells selected. The ones that fell outside the polygons do not have those wells selected. We've also rewritten all of our field planning workflows like from the ground up again using code native to geographics. We're not dependent on any third party for that either. I will not go through that just now. I'll cover that during the section on field planner in a lot more detail. Um, so all of the workflows that we had which required our GIS engine like I said we've replaced either by writing our own functions for it or using Ezre's maps SDK. And one example of us using Ezre's maps SDK is when we connect to our mapping services. So I can still go to the import menu here and connect to an RGS feature server, a map server, WMS layer connect. Uh we've also added a WMTS connection now so you can connect to web map tile services uh RTS online portals uh and these work with Ezre's maps SDK which like I said are packaged within geographics so you don't need a separate install for it provide a URL here uh let's give it a layer name we'll fetch the layers choose the layers we want to display hit finish and that should then go to that server fetch the layer and display that on our map so this is now coming from that WM uh WMTS server Now one key difference in the way we're doing this now is that when we get data for this layer uh because we're not creating a static LR layer in the background anymore which is how we used to do it when we were implementing these connections via the Arc engine setup because we're not doing a static lyr layer anymore. This is just brought in uh live from the server. So as things will change uh as the server updates as these maps are updated uh your uh your maps will simply need to refresh the layer and you'll see the changes um in that map in geographics right away as well. So this is sort of a live connection. Now it does need a refresh or open the map reload the map for you or reload the layer at least. Uh but this will update as that data updates for you um on your servers. So that's kind of how we've done the the maps SDK part of things, rewriting part of things. Again, you'll really feel no uh no hindrance, no change changes here. Uh the only thing that's going to be different again is the deployment mechanism because you don't need to go in and uh configure anything separately. All right, the second part of our approach is to write a plug-in for RGis Pro. I've got a project for RGis Pro open here. Um, and I've got, you know, a couple of layers in there. Like I have some leases here. I've got, you know, those colored in colored color coded here. And then I've got, um, you know, open leases and some of the other leases here. And then I've got, uh, on top of that another layer overlaid green leases which are going to expire soon. So I've got two layers, leases here, uh, within this on top of a land grid and a and a topographic base map. Now to access our plugin, here's a new Geographics menu. that is going to be in your Arc Pro uh ribbon. And then in here, you can read and write to geographics. You can do a couple other things that I'm going to talk about in a second. But first, let's say you you're in geographics and you've got got a couple layers here. For example, I'm just going to hide this topographic map for now. Let's say you've got your wellspots layer and let's say you've got some contours that you want to take over into RGS Pro because you want to consume them in some workflows over there. transferring it does not require now taking a shape file moving it uh you know importing it into Arc Pro or anything like that. All you got to do is from your Argis uh Project in the geographics ribbon click on read from geographics that's going to go in bring up your active project all the layers in your active project including all your AOIS and then you can go through and you can choose the layers that you want to bring in. So, I wanted to bring in my contours for my uh Red River. There it is. And I wanted to bring in my wild spots. Hit load. And that will go through process those layers and put them in your ArcGIS project as they are in your geographics project. We've worked hard to make sure that we can make them as similar, as close as possible to each other in terms of symbology and their appearance. So along with the data that's coming in, you're also getting that appearance coming in pretty much the same way as it was in your geographics project. So there's my contours right there and I've got my wellspots coming in over here as well. And if I were to show you the expansion of these layers, so all the entities in that wellspots layer are available as features, right? Right. So, I've got my straight hole wells. I've got my deviated paths in the straight hole wells. You know, this is all all the different symbols for all the different entities I have. Um, I had some thematic mapping applied which I hadn't turned on in Geo Atlas. Uh, but all of that information does come through. So if you've got any or you know any of those renderers turned on theatic or bubble maps or proportional it will also come through as is and you can toggle them on or off within this uh rgis environment to get that information over here as well. Same thing for your contours and your isob layers all of those entities like data points and uh boundary polygons contours all of them come over as well. So that's one way uh transfer getting stuff from Geographics into ArcGIS Pro. Let me check those off. Let's say what about information that's in here and you want to send over into Geographics. Let's see these two lease layers for example. Select the ones that you want to move over to Geographics. Here's my right to geographics button. I'm going to click on that. Now that's going to prepare those layers. So, it takes those layers, does the format conversions that we need to be able to display these layers into geographics, and then it will let me add those layers into my geographics project. It will ask me a couple questions like what do I want to call the layers when they get in there? Do I want to override, you know, layers if they're already present in my geographics project? Which AOI do I want to keep them in? Also, these layers could be bigger than your projects. What happens then? Do you want to still add those layers that fall outside your project extense? Do you want to ignore them or do you want to crop your layers so that you know your project is not blown out of the current extents and it just kind of maintains its current extent? So all of those questions when you answer them here, it's going to go finish this and that is going to transfer that data over to my geographics project. So, I can go in here, go to my layer, select, and you should see your leases and your expiring leases coming in here. Let's turn that on. And that should rerender so that you have your expiring leases in here, which are those green polygons. Again, we're trying to make sure that we copy as much of the symbology and the colors and the format as possible. It's not always going to be exact because there are just some differences in the two applications, but we do try to get it to look as close as possible to each of them. Now, the key difference here between connecting through maps SDK to get that topographic image or connecting to a server, RQS online, RS map server, which was those live kind of connections where the layer is on your map, but if it updates, it changes in here if you refresh it. Um if you bring it through the plug-in though that's a static transfer right so things coming in will not automatically update uh we convert that layer into uh a format that we can use and that's what we are using to display here so if something changes on your pro project that is not going to be reflected here until you push that layer over to your project and vice versa um if you've you know moved a layer from geographics over to RJS Pro like our contours for example and changes, you reg grid or anything like that in geographics, that is not going to be reflected in Arc Pro until you push that over uh to to the Arc Pro project again. And that's how simple it is. Just a quick primer of what we're doing with our with our RGIs Pro plugin. Uh we've also added a couple of extra features. I mean, we do uh we cannot access Lyrx files or LYR files outside uh geographics anymore. So you can import them into into Arc Pro and export them through the plug-in or use the add files to geographics button to just kind of go through and add those Lyrx files in, you know, read them and process them within R Pro but end up with a layer in geographics without really having that extra step. And also we uh done a batch converter here. This is that utility that will let you go through will parse all your AOIS, spot any layers that are no longer supported or have been deprecated by EZRI in 24.2. to convert them into a format that geographics can understand. And this could be you know existing WMS layers for example or any any layer based on the LYR format. We'll convert those uh we'll also update your maps and everything like that. We also create backups of those layers so that in case you need to fall back on them at any point you are able to and your projects should be ready and good to go without requiring individual layers to be converted manually. So that's our um RGis Pro connector and um you know our transition away from RGis runtime. Um uh I know this was a brief overview. If you've got more questions, I'm sure you do. Please don't feel free to reach out and um I'd be happy to help you understand a bit more of uh what we've been up to. Let's move on though. And next up, let's talk about the changes to field planning. In 2024.1, back in November, we introduced our new multilateral planning capability that let you plan any multilateral configuration, stack laterals, planer, fishbones, unilaterals, or really whatever you needed directly on the map. In 2024.2, we've enhanced that capability significantly. You can now create lease tracks right from the map, flag surface and subsurface hazards, automatically enforce setback rules, even detect well collisions as you plan your laterals. We've also made it much faster to lay down well pads, define slots, automatically generate generate laterals with the spacing, direction, and length you need. So all of those kind of everyday useful features that help you plan your wells more rapidly, more quickly, and everything you design, wells, pads, surveys, they can be saved directly into Wellbase and then hand it off seamlessly to Gverse Planner when you're ready to build your actual drillable surveys. Let's switch uh back over to Geo Atlas. And let's say I want to digitize some laterals right here in this area. To do that, I'll go to my field planner, select the plan I want to modify, go into my create mode, and then digitize a heel and a toe to get my lateral going. I can also assign a surface location here. So, let's say I want the surface location to be right here. And that is basically my lateral. Now, if I want to be super precise and want to say I want it running exactly north south, I can specify an azimuth and a length, uh, I'm going to go 1600 m and meters because this is a meters project. If your project is in feet, this is these units are going to be in feet. But I can set an exact azimouth and a length. When I click okay, that gives me a lateral that is exactly going north south for 1,600 m. Now I can also set other information like a well name. I'm just going to call it plant one. Give it a name. That's my well ID. That's going to be a name. I can give it, you know, I can be very precise about the surface location. Give it a data elevation as well. I'm just going to ignore that. Um, so I've got my lateral planned 1.1 setting here. Now I can also give it a target layer. I'm going to go for the Bakan map layer. This is the TVDSS structure map that I need to target it on. Um, if you wanted to go 50 m above or below um, you know, 100 ft above or below your target layer, you can set that here. You can also give it a kickoff point uh, for that particular lateral. And then I have basically my uh my lateral ready to go. Now if I wanted to create copies of this um I can digitize this uh you know right next to another parallel lateral right next to it. But what we've also done this this release we've added this ability to add parallel laterals. So I can give it a spacing. Let's say I want these to be 300 m apart. I want two laterals on the left and two laterals on the right. That is going to give me when I click okay five laterals for that planned one configurations. Five wells in that particular configuration all originating from the same surface location but and all targeting my my bacon uh but planned uh but five different laterals planned really really quickly. And once I have them I can actually grab this configuration and copy paste that all over my map to get that rapid field planning uh field planning done. We can also do pads. So if you don't want surface locations, you want to digitize pads, you can do that on the graph as well. Point to where you want that pad. Give it a name. Going to use a dummy elevation here. Let's go 400 by 200 for the pad dimensions. Click okay. That's going to create that pad for you as well. Now again, these pads are not required, but if you do want to put them, you can. And then once you have the pad, you can also copy that around and move that around on your map. Let's say you want that pad over here. Uh on here you can also just copy the pad. Let's say you don't want the entire configuration, you just want that one pad. Because what we can do with the pad is that you can rightclick and say auto plan. That lets me define multiple slots. Let's say I want three slots each in in two rows. And I can give it a step out going to go 150. I want to know go north south. Let's say 1,200 m in this case for spacing 500 m. It's going to plan those laterals out of the pad for me under these three slots of the lateral. It's going to plan those for me. I could do the same thing for the second row. Uh, or I could just have this one row setting it up like that. Click. Okay. That's going to create that pad for me. I can also rotate this around. So, if I wanted at an angle or maybe flip it uh the other direction, I am able to just take that entire pad and move it like that as well. Uh, full undo redo support. So, you can always get back to where you were. And you don't you're not limited just, you know, straight laterals going right like that. You can also digitize as many points while you're digitizing a lateral. So, let's say I want to digitize one going right through here. Kind of curving a little bit. There's one. I can put another one here. Let's just add a few more curves to it. Double click there. And I'm going to put one right over here as well. Going to give this another surface location. All three from pretty much the same surface location here. Let's set some well properties here cuz we're going to save this well later into the database. And I also want to set my target surface as the bacon. So all of these are targeting the bacon well as well. That's how quickly you can digitize laterals and pads and all of that stuff uh on your map. Really, really quickly. Specialized tools to do that. I know a lot of people in the past have been using annotation lines and whatnot to be able to get to this point, but these are actual entities. well entities uh that you can use. These are shape files. So even if you want to take them somewhere else, some other software you can you can use the connector to move them into Pro and all of that stuff that comes with it being part of an actual layer. Um but you typically wouldn't be working in a void like this, just a blank, you know, sheet of paper and going in adding valves as you go. You obviously have other factors to consider. perhaps primary among them making sure that you are staying within the area that you want to stay in. So like a lease, right? Um and the new field planner lets you lets you do that interactively. So any geographics layer that you have in my case I've selected this land grid layer and I'm just going to select some sections here. Let's say my lease is this these 10 sections. Um I can rightclick add it to a lease. Select the lease I want to add them to. Click okay. And that's going to create that lease for me. So all of those 10 polygons have been added to this lease. Now they are added as individual polygons. Maybe you don't really want all of that. So I'm going to select them and merge them into a single polygon. And then I'm going to select all of their edges and add a setback. Let's say I want this to be at least 15 50 m from the edges. And I can clearly see the north end my wells are kind of leaving my lease. And I I don't need that. I need to clip it which we will get to in a second because there are there's other factors that you want to consider as well. U there's you know the surface elevation. I've got um this is my surface elevation. I want to make sure that my pads and my surface locations are in are not in areas that are too steep for me to put those in. Um I've got to make sure that I'm staying away again for my surface locations. My pads are away far enough away from rivers and streams and other you know roads and other culture data that I have available. there's other wells in the area. I want to make sure that my and and the wells are basically subsurface hazards. Not only do my surface surface locations need to be far enough away from these wells, but my well bors should also stay far away from these wells. So, all of this information needs to be considered uh when you're planning your well. Uh and we do that through our hazard layers. So, I'm going to go and create hazards for each one of those items that we were talking about. Starting with our DEM layer. So, you can bring in your DEM layers as is mapaps now. And once you select that isome map, you can specify a slope. This is a flat area. I'm just going to go three for demo purposes. I can click okay. And that's going to go through and it's going to highlight all of the areas that have a slope more than the value that I specified. These red boxes are indicating that these are too steep from according to my specifications. My pads and surface location seems to be far enough away from each of this. So that's not really affecting me. But if I had a pad or a surface location in these surface locations, I would know right away that this is, you know, I need to move that. I need to do something about it. Uh what about your uh uh rivers and roads and all of those surface features that you want to stay away from? Again, let's go back to that same layer. I'm going to update that. Uh now, I'm going to add that culture layer, right, which has all the roads and everything that I need. All of these entities are listed here. Let's say I want to stay 30 m uh away from my class 4 highways and I want to stay sorry I'm just going to duplicate that layer here because I also have my shoreline here. Let's say you want to stay 50 m uh away from that. All right. So that's uh basically we'll go in and generate those hazards. I've got wells in the area. Those remember were subsurface hazards. I'm going to choose a second layer called vertical wells here and I'm going to go through for my straight hole well entity. Again I can be specifying entities from this drop down here. Make sure you set it as a subsurface hazard. And let's say you want to be 250 m away from any wells that are in that area. Click okay. It's going to go through. It's going to create three different kinds of hazards. My slope hazards being these uh steep areas. My surface hazards being these areas around my shoreline. My roads. Again, my surface location seem to be okay. They're far enough away from everything. So, I don't really need to worry about it. But some of wells my wells are crossing over this subsurface hazard that I've identified. So how do we uh how do we address this problem? Well, back in our planner, go back to our field plan. We have the clipping ability which lets you select a lease layer, lets you select one or more hazard layer and then all of the well configurations that you want to check it against. I click okay. it goes through and then it'll clip anything that is um you know outside the definition of what you just defined. So these wells, let me clean this up just a little bit so we can kind of see this better. I'm going to rid bit of this and this. So you can see my wells were getting too close to this vertical well here. The subsurface has they've been clipped. My wells were leaving my lease area. They've been clipped uh to be inside the lease. So that's how easily and quickly you can go through and figure out, you know, if the wells that you're planning are following the rules that you have in mind for those wells. Um, and the sub surface hazard thing is great, but it is working off of things from a map, right? It it's not really zaware. By Z, I mean depth aware. So it doesn't know exactly where it is. It just kind of says, okay, this is a subsurface hazard. anything that gets close to it, wherever that depth may be, I'm going to clip it. But what you're really looking for if you got other welds in the area like I do. So, I'm just going to turn on my wild spots layer. And all of these pink wells are targeting the balcon. And right away, I can see this is not going to work. I've got too many collisions here. So, I'm just going to get rid of these to keep our results simple. So, deleted those two paths here. But these valves, they look okay. But, I don't know about this. This is getting a little too close. We can find out if that is colliding or not. We want to find out if that is too close or not. Um, and to do that, I'll go into my collision detection, which lets me select a well-based layer. So, I'm going to select my wild spots layer here. And you can select multiple. You don't have to be one single layer. Also, other field planning layers including the field planning layer itself. So, if you want to compare these two configurations or the laterals inside the configuration got too close, right? Specify a buffer distance. Again, let's go 250 m. Select the the wells that you want to run the collision detection for. Click okay. And it says, "Okay, I found two collisions, right? Uh, and it will give you the log for where the collisions are." So, it's it's kind of colliding with itself. No real well here that it's colliding with. Uh, and that's that's the one right here. Let me kind of just quickly modify this so I can actually show you the collision. So, if this val were to get too close, uh, like here, uh, we're going to also move this one so that this is far enough away so that we don't get the this collision highlighted. And I'm going to run my collision detection again. Let's say again for 250 m for both the wells. Uh, same layers. We'll comput it. Now, it detected four, right? It does give you a log file. It's telling you that plant 2, plant 2.1 is 244 meters from this particular well. And then getting closer again. And there's that red highlight showing that this well is getting too close to that one well that we already have. Again, we just kind of move this uh move this well out far enough away and then we should not get that same collision for the those wells coming in. See, no collisions detected. So that's how you can make everything you make your plans aware of all of the different things that are going on to get your plan locked down pretty quickly, pretty rapidly. And once you have it, you can either generate geoprog reports, you can generate drilling reports that will take all of this information of the surface location and the XYZ points from the target surface and the digitized points to give you the information that you need. You can also save these wells directly into Wellbase. And when you save them into well-base, it'll go through. It'll take these eight wells that we've planned, give it the IDs that we specify here, and save them as wells in your database. There's my wells. If I go back to my quick filter and because I'm just going to filter on the ID, it should give me the eight wells that we just created right there. Also going to calculate their proposed surveys really quickly. Uh, and that really means these wells are ready for me to use anywhere I want to use them in geographics. And as an example, if I take them into go plus is that same area in G+. I'm going to create add these wells that we just created. Sorry, I just do need to refresh this interpretation once so I can see the wells that I just created. And I'm just going to go here. We're going to go manage well list. Add wells. Let's sort by well ID. There's the wells that we just created. I'm going to select them. Click okay. Um add them into the well group to start showing up over here. here. They also start showing up in my 3D view. And you can see they're kind of following that botan surface really perfectly as we as we planned them. Um, and you know, they're here ready for me to use however I want to use them. Now, these were just kind of sticks digitized on the map. So they're not, you know, particularly detailed surveys. But once if you do want to make sure that you are, you know, these are in fact drillable wells, uh, and you're ready to get to that point where you want to do detailed individual surveys. You just open them, open the well in Gver Planner. That's our single well planning tool for for single wells where you can go in and actually uh digitize a survey as you need it to be. I'm just going to add one of these wells. Let's go 2.3 here. That's going to load that well as the default plan. You can see this is this one well right over here. Looks like a pretty good survey. You can actually go in and move this around as well. Uh and it'll look at the parameters that you set down here to make sure that this is a drillable. Well, if I if I do something too crazy, it kind of highlights everything in red. And once I have that done, I'm just going to do some things that are a little crazy so you can actually see the effect of it. That's it. Um, I'm going to put in that target surface here as well really quickly just to give you an idea of what's going on. So, there's that target surface that we're following and I've got my well kind of going dipping below it and then coming back up here. It's all green. It's all good. Uh, and if I go to well-base, back to well-base for well number 2.3. Now, the deviation survey is a lot more detailed because the planner has gone in and made that survey for me. It's not just those four or five points that I digitized. It's a much more detailed plan. Uh, and if I were to refresh my wells again here in Geo Plus because that survey has been updated in well-based because uh, everything is now kind of saved as part of the well, I can actually see what I did. And I did a pretty funky looking thing here for that one well. But that's how you'll go in and then you can uh, plan those individual wells per um, uh, you know, to make sure that you're getting the deviation service that you need. So that's a quick look at field planner and uh what we've all the new changes that we have done with it. Uh it's a pretty exciting new tool. Again, I don't didn't have the time to get into too much detail uh for it because we've got a lot of other things to cover. Got questions, feedback, you know, things you'd like to see it do even better, please let us know. Get in touch with us. let us know and we'd be very very happy to uh to get take that feedback in and make this tool even better than what it is right now. Next, let's talk about some data management. And first up is an update on our growing partnership with TGS. We first introduced a connection to TGS well data in 2024.1. It allowed you to bring TGS well headers, deviation surveys, raster logs, and digital logs straight into your geographics project. without needing separate workflows or manual imports. In 2024.2, we've expanded that capability even further. You can now bring in information tops, production data, completions, perforations, and DST data, all streamed directly from TGS servers straight into your Geographics projects. And to make things even easier, we've added automation tools to manage your TGS imports. You can now schedule recurring downloads automatically checking for new wells every week, every month, or even every day if you want. You can choose exactly what data you want to bring in and when you want to bring it in. Uh we've also introduced recency filters so you can download only wells that were added or updated in the last 30, 60, or 90 days depending on whatever fits your needs. In addition to these enhancements uh to our TGS connection, we are also actively working with other data providers to find ways to get data into geographics more easily. Um 20 24.2 introduces our partnership with MJ logs who are a big provider of log data, especially raster logs here in North America. If you subscribe to get rest data from MJ logs, you can now access those logs directly on the Geo Plus map. The whole thing is very interactive. You select a group of wells on the map and we'll search the ML logs database for you. You'll see what raster logs are available and then you can download them straight into your project depth registered ready to go. We have plans to extend this connection even further and integrate it into more geographics modules. Uh and all of this lines up with our focus on trying to make it as easy as possible for you to bring your data into geographics no matter where you're getting it from. All right. Now, we're going to move on to an area that hasn't gotten a lot of love for a while, and that's query builder. Uh 2024.2 adds a lot of flexibility in how you can design your query. So, we've added some functionality that lets you make queries that you couldn't make before or weren't easy to make before. Let me show you what I mean. First of all, you are now able to add as many criteria rows as you need. You're not stuck with a fixed five rows that we've had in the past. If your query needs 10 conditions, 20 conditions, even more, no problem. Just keeping adding rows as you need. Secondly, you can now define and rows, not just or rows. So, in the past, we've had those fixed five rows. All of them have been ores. Now, not only can you add as many rows as you need, you can add and rows. Like in this example that I have here on the screen, I'm finding wells that have picss both for the RDRV and the BKKN formations. In the past, to do something like this, you had to build two separate filters and then you'd combine them using a set operation. Not only is that a lot of extra steps, but the biggest downside of doing it like that, it is that it gives you a static filter. If your database changes, you add more vals, you take wells out, all of the component filters of that set operation have to be updated separately, and then you have to rerun or recreate your set operation to get your results. All of this is a lot of manual work. But with this small but powerful change, you can now build dynamic filters that automatically stay up to date as your database evolves, just like any other well-based filter. Additionally, we've added the ability to use the or operator within the same row. Instead of combining all the columns with ands, uh you now have the option to mix in an or. This also radically simplifies certain kinds of queries. For example, here I'm looking at wells that have production data either in valase or in zone manager. I don't need to build complicated set operations. I don't need to build separate queries. Just a quick easy setup right inside query builder. And lastly, you now have the a new option to return only distinct well IDs. So instead of getting a big list with multiple records for each well, you can get a nice clean list of just the wells that match your query. It makes it a lot easier to export or copy the results straight into other workflows without having to clean anything up. Um that's just the start. We've had even more enhancements not just in Query Built, but across all the data management apps. There's a ton of other stuff that I just don't have the time to go over today. Uh just a few highlights. You can now import well lists from text files into Wellbase. You can interpolate tops directly from MySim again in Wellbase. Uh when you're importing data into zone manager, you can now apply a well filter so you're not updating wells you don't want to update. We've got new time stamps for interval data for lock curve data. So any changes that you make, you will know when that was updated last time. And there's a lot of UI improvements to make things feel snappier, more intuitive, and just to get more information from what you're looking at uh on the interface. On the geoysics side, big news, our on the-fly attribute and inversion tool that we introduced again in 24.1 with its multi-panel viewer, that's now also available in the 3D view. You can apply on the attributes. You can apply inversions right there in the 3D view. You can adjust your parameters. You can tweak your inversion inversion filters and immediately see the impact in 3D without waiting on volume generation. And to help with the QC, you can now overlay logs in the multiv- view. So again, we introduced the multiv- view last release in 24.1. You can add your horizon data, you can add your fall data, you can add wells, but you weren't able to display log curves on top of those wells. And that is one of one one key QC tool that you need especially when you're doing inversion to understand what your wells how your wells and your seismic relates. So now you can overlay logs in your multiv- view. You can put it down as lines filled panels or full templates from J speics right on top of your inversion or your seismic or your attributes. Again, everything being computed on the fly and it just makes it a lot easier to compare your log curves with real-time data and fine-tune your model. On the geology front, uh, specifically in in Geo Plus, we focused a lot on the performance. That's pretty much what we worked on for this release in 24.2. We wanted to make it snappier, faster, easier to load interpretations, load well data, load layers, um, turning the model on or off that much faster. Uh, even rendering your cross-sections. So when you have a big cross-section with a heavy UD on it, we've tried to make that process a lot faster and just the general overall 3D view, map view, cross-section, just make it more responsive and also better integration, faster integration with other modules like wellbase and zone manager. So reading data and writing data to the rest of geographics should be a little bit faster. And one last highlight, Petraysics. You can now rename curves on import, resample curve sets, update headers, export wells in a single file, and more. Uh we've also added new options for posting core data and customizing your templates. So that's a quick look at what's new in 24.2. We've got over 100 new features in total, but these are the ones that I think you'll use right away. If you want a deeper dive, we're happy to set up follow-up sessions for specific workflows. Thanks for being here. Thanks for listening. Uh, and I hope you give 20 24.2 a try soon. Um, and I'm sure you'll find something that is useful specifically for you in there. As always, if you've got feedback, questions, do let us know. And with that, it's goodbye for me. Thank you.