Speaker 1: Touch on survey control like our friends Compass did in the last presentation. We have a preferred method. With our mobile mapper, we really like the checkerboard like this and we like to point it towards the road to where the tip of it is perpendicular to the road. It's not catastrophic if control is done in other ways, but we have tested it many ways and in Tremble as well and we see the value in setting it up a particular way. Speaking of Tremble, some of these screenshots you're seeing in here are based on their experiences and opinion as well, so I've mixed that in as well. Some other methods, just as we think about aerial acquisition on control, I always leave this slide in here. Table method often applies, so that's kind of what I'm showing you here, but focus on mobile mapper. If we feel we're having good solution, we'll stretch our control out 1,500 feet at times, but commonplace is we like to do a control point every 500 foot, sometimes 1,000. It just depends on the circumstances of the project, but we're certainly always getting at least a check shot. That's what you're seeing here, those validation points every 500 foot. It often makes sense to do what we call zipper method if it's a narrow enough corridor to where you don't have to set control on both sides, one across from the other. You can kind of zipper your control down the road like that, because as we all know, a couple of things with control. Number one, it can be time consuming to some degree. What I mean to say is, obviously, we're trying to minimize the amount of time we have to put the boots on the ground. For me, a big part of it is also safety. If I know I can spread my control out more because the terrain and the project allows that, I'm going to do all I can to keep my surveyors off the side of a road as much as possible. Again, just another example of a control layout. This one would be for large area mapping, but kind of table method. Previous presenter I saw had some great photo ID examples, and we are a fan of that, both with aerial drone, but also mobile mapping. We try to use existing markings and other existing features when it makes sense on a project to minimize, again, the amount of effort on the roadside. TBC has some wonderful tools. I'm going to show you some examples. Wonderful control capabilities. I'm a huge fan of the ability to, because we also have other software vendors with our other tools that don't quite have the flexibility that TBC does as far as being able to look at your control point in three dimensions and overlay the imagery from the Ladybug, so a lot of great functionality. From TBC tying down our data sets. We like the previous presenter are big on validation. So this is just an example of steps that are built into our software that we use for our data extraction that is giving us a few things. We can validate conventional ground truthing shots. GCP type, you know, survey shots against the point cloud, like you're seeing here. We can also do it against the ultimate DTM, which to me is very important because sometimes I fear that people validate their point cloud and they check that, but they don't validate their DTM at the end. And their DTM was not derived properly with enough proper breakouts. So that's one of the things that we try to do. We try to find enough proper break lines. And that's really, you know, you need to be checking that. And when you find, and that's what the NSSDA check spreadsheet and processes is all about. And so when you find bust in your DTM that don't meet your accuracy standards, it's not necessarily that your point cloud is bad, it's that your extraction folks did not derive enough break lines or enough detail to pass the, to pass that.