--- title: "Grid Transformations v3.2.0.1" canonical: "https://servicedesk.maxgeo.com/space/DS/1712259155/Grid%20Transformations%20%20v3.2.0.1" format: markdown --- | | | | | | --- | --- | --- | --- | | Application: | DataShed | Build Number: | 3.2.0.1 | --- > Macro (iframe) ## Transcript ``` Welcome to this walkthrough of Grid Transformations in DataShed5. Focusing on the MDS5 system, most of the transformation changes have taken place 00:04 behind the scenes in the MDS backend and the DataShed5 Admin area rather than in the main DataShed5 00:14 interface itself. Let's start with what's changed in MDS5. In terms of the MDS5, the collar and site tables have changed significantly. 00:21 We no longer have the Orig, Nat and Local set of columns in the collar or the site tables. The LL coordinates have been retained such as Grid id, 00:33 lat Long and rl, but are now purely the result of transformations. The ll geometry columns have been removed and a new LLRL method column has been added. 00:46 Each module now has its own normalized table to contain measured and transformed coordinates such as tblDHcoordinates, tblFScoordinates, LScoordinates, and PTcoordinates. 00:56 In these normalized tables, data is divided into three confidence levels where Planned is the lowest level for coordinates sourced from maps, planned grids, et cetera. 01:09 Where Field Sited are for coordinates sourced from a handheld GPS or Compass or something like that, and Surveyed is the highest 01:20 confidence level for coordinates from a DGPS or THEODOLITE or actual survey methods. Each confidence level can contain coordinates in multiple 01:28 grid IDs or the same grid ID where they may have been remeasured. Each confidence level can contain original measured 01:38 coordinates and all configured transformation results. The priority column is calculated by a trigger the same as the one on the downhole survey table 01:46 and uses the priority values defined in the survey method library table. Every time new coordinates are added or edited, two things will happen. 01:56 The Latlong WGS 84 coordinates in the collar or sites tables are updated using the best available confidence level and priority combination 02:06 and are always updated as the available source coordinates change any other transformations configured by the system administrator in DataShed5 Admin are also 02:16 performed at the same time. Another addition are two standard views per module, the tblVWDHcoordinates and DHcoordinate transformations. 02:28 The coordinates view contains only one record per whole or per site. It has columns for preferred, planned, field sited and surveyed 02:42 and lat long coordinates where it uses the priority zero for each of those. And there is also the planned addition of geometry columns 02:51 to the view rather to replace the LL geometry columns, which will use projected grid coordinates. Then the other view VW Coordinate transformations will 02:59 contain multiple records per hole or site depending on whether you have defined multiple transformations. It contains all of the transformation results. 03:10 It uses the best priority for each, and there is also the planned addition of a geometry column using projected grid coordinates 03:20 to this view in DataShed5 Admin itself. On the database menu, you select the database that you want 03:28 to configure and then details which will bring you to this screen. And then the spatial reference tab. Coordinate systems and transformations should be configured 03:37 on this tab and you will see a dropdown menu with the two options for global coordinate systems. From the dropdown menu On this page, 03:47 select coordinate system and check if the systems you will be using both as input and transformation output are already listed or not. 03:55 Note that there is a new column in this table called Authority Code. In order to define any new coordinate system, you will need 04:05 to know its EPSG code. These codes can be looked up in most GIS software like QGIS in the project coordinate, reference system menu window, 04:12 or else from the EPSG website. An EPSG code implies a certain combination of projection, ellipsoid and datum, so these are no longer necessary 04:21 to be defined separately and those tabs have been removed from the spatial reference page. To edit an existing coordinate system, 04:33 click on the pencil icon in the action column next to the relevant code. To add a new coordinate system, 04:43 you click on the green button, add new coordinate system, and add as much information as possible. But at the very least, the required boxes denoted 04:52 by the red asterisks Coordinate System Code, Is Active and Authority Code. You have to be very specific with the spelling 05:01 of the EPSG code. It should always be EPSG colon and the number. No spaces are allowed, no other spelling is allowed. 05:09 It is always good practice to keep the wording of descriptions consistent. So when you're back in your list, these descriptions, 05:18 if you have multiple zones in a coordinate system, Try to copy the description and use it in your new coordinate system. 05:26 For local coordinate systems, they're also created on this tab, But The authority code must be set as local. When The grid has been configured, it's necessary 05:34 DataShed5 front end from a CSV file using the standard import layout called control points. So I'm going to add a new coordinate system. 05:56 We're going to call it KNO, the EPSG code will simply be local and that's the minimum that I need. 06:05 However, If the grid already exists, you will get an error message warning you that it already exists and there's a primary key violation. 06:13 So once the local grid has been set up, you can then go to DataShed and the import data. 06:30 You will select the standard import layout called Control Points. And the control points file needs to look exactly like this. 06:36 There will be a local grid id, it's X, Y, and Z coordinates the global grid ID and it's X, Y, and Z coordinates. 06:44 Loading the file, selecting the CSV file. As you can see, the information description over here describes exactly what the import layout is looking for 06:56 and what the file needs to look like. Check that your columns all match up and press the load button and then import data. 07:12 Once completed, you can go to view data database management and SRS Control Points to see your control points have been imported successfully 07:20 These transformation parameters are in three dimensions and will also affect the RL values After they have been set up, they're simply treated 08:15 as any other grid for transformations themselves. We go to the other tab on spatial reference and select transformation and any existing configured coordinate system 08:24 transformations should be displayed here. You can edit, delete, copy, or rerun a transformation on existing data. To add a new transformation, click on the green, 08:36 add new transformation button, select the from grid ID and the two grid ID values and set the transformation type 08:46 to coordinate reference system transformation and provide a data source. So for instance, we can do KNO to MGA 94 51 transformation coordinate reference system, 08:54 and you need to specify a data source, and Save. You'll get a green successful message and then you can go back to list. 09:06 And the new transformation we have just specified should now be listed. As you can see it is here. We now have a transformation set up for KNO 09:16 to MGA 94 51 grid in DataShed5. Now to import coordinates into one of the four coordinates tables, 09:25 you simply use the standard import tools for a CSV or an Excel file. Under import data transformations are performed as soon 09:33 as the data is imported. You go to DataShed Import Data, use import layout, any Excel spreadsheet, click on load file, 09:41 set the destination database table as DH coordinates, normalized, Select Your Excel file and select the worksheet that contains the coordinates 09:52 and then press load. Once you are faced with the import screen, you can then click on the append data button 10:14 and you will see the wheel spinning until the data has been imported and then you'll get a successful importing 10:24 data has been completed. Message. If you go back to view data drilling management and coordinates normalized, you will see 10:35 that the coordinates have been imported into the coordinates table, but also the transformations have been performed. So the imported coordinates for the KNO local grid 10:53 and the specified transformation. MGA 94 51 has also been performed at the same time. If You look at the collars table, you will see 11:05 that the lat long WGS 84 columns have been updated with the transformation results using the best available coordinates. If you need to run a new transformation on existing 11:18 coordinates data that you imported previously, you can do so in DataShed5 Admin on the transformation screen as well. 11:30 Go to the database details, spatial reference, select transformation, and locate the transformation that you want to run in the list. 11:39 You then click on the run transformation button, which looks like two circular arrows, so we can run the same KNO 11:49 to MGA 94 51 by clicking on this button run transformation. A message will appear, warning that the process could take a long time depending on the 11:55 number of records being processed, as the transformation will be run on all records using the source coordinate system in the down hole, linear, face, 12:06 and point modules of the database. To proceed, click on the transform button and the run transformation button will change 12:16 to arrows pointing left and right when the circular icon reappears the transformation has completed. And you will receive an email confirming this 12:24 and that's the DataShed5 and MDS Coordinate system. Thank you for watching this video. 12:34 ```