b'Data trends Amore sophisticated version would offer variable search radius and weightings to fill more of the bottom right hand hole in the initial stages\x08 The process would also be better managed with two tools\x08 One tool to create the series of point sets assigned with nearest real values, and another to import the grids and to fill gaps in the point sets\x08The procedure is as follows:1\x08Add a new script in ArcMap toolbox that points to this script\x08 Create 5 parameters with relevant data types (Figure 4)\x08a\x08Layerto choose the point shapefile/feature that will be regularisedb\x08Workspaceto choose the folder/directory all files will be written toc\x08Point separationthe largest starting that will begin the processd\x08Iterationshow many times the separation size will be halvede\x08Fractionthe grid cell size is calculated as fraction of current point separationFigure 3.Grey scale image of grids in Figure 3 displaying grid artefacts. Topusing original location data.2\x08Add a point shape file to ArcMap so it Bottomusing regularised location data. is now a layer3\x08Run the script\x08800 m grid\x08 This, in turn, generated a 400m grid to feed the next iteration\x08Five iterations finished with a set of points 200 m apart (Figure1 bottom)\x08 The null points were removed outside this process and a grid at 50 m cell size produced (Figure2bottom)\x08 Artefacts have been visibly subdued with both the high frequency and linear features greatly reduced (Figure3bottom)\x08 The result still warrants comparison with other smoothing techniques, but linear features that could be mistaken for structures have been successfully removed\x08Of course, this process demonstrates that a cycle of nice solutions can hide problems, and I do not pretend that the method is a substitute for removing or correcting conflicts in data\x08 It is worth remembering that smoother, less fractious grids may not be a good basis for a drilling programme\x08 If you intend to use the data for that purpose then have a think about possible data conflicts before you start\x08The code was written with ArcGIS high level functions so that you can copy and run or read as pseudo code\x08 Function names either sound like their output or can be looked up online (Appendix1)\x08Figure 4.Screenshot of ArcGIS toolbox parameters used to run the code.35 PREVIEW APRIL 2021'