---
title: "System Admin Manual"
canonical: "https://servicedesk.maxgeo.com/space/DataShed4/1270349898/System%20Admin%20Manual"
format: markdown
---
> Macro (toc)
**Topics Covered in this module:**
- **Configuration settings**
- **Administration Tools**
**Expected outcomes:**
- **Ability to connect to relevant databases**
- **Customise configuration settings for database.**
- **Utilise Administration tools to management database.**
System Administration Form
The System Administrator is the only person who has access to the System Administration functions in DataShed.
## Database/Configuration
**Database**
This contains the actual raw data tables (tblDHColl, tblDHSurv, etc.), DataShed system tables and any site- specific extensions (reports, forms and queries) generated by the System Administrator. Any Access, SQL Server, or Oracle Database can be the back-end database. The database would ideally be situated on a network server so that multiple users and applications may share it.
The location and type of the SQL database is shown in the details at the top of the Database/Configuration tab.
**Configuration**
The tables from the SQL database that DataShed is required to access must first be configured and registered using the Configuration Manager.
Set the defaults for the following DataShed functions on this tab.
**Normalisation Edit Mode**: Set to Read Only or Edit for the assay normalisation process.
**Report error**: Opens a form to view the details of the last error message reported by DataShed and email to Maxwell Geo- Services if necessary.
**ODBC Startup: **Allows the Administrator to select if the user is prompted to select the ODBC connection when DataShed is opened.
**Screens**: Controls whether data sheets and report previews are displayed as maximised or at normal size.
**DataSet Label**: Allows the label ‘DataSet’ on DataShed’s forms to be replaced with an alias such as ‘Project’. Not recommended.
**Uni Query ODBC Timeout**: Timeout process for building RDMBS. The recommended default value is 3600 seconds.
**Import Directory**: The directory where the Import File browser will start in.
**Data Source Column Name**: The column name for the data source to be populated. The column name must be consistent throughout the entire database.
**Default Buffer Setting**: The System Administrator can set the import buffer for non-assay files to either Remove Successful Records if they have been successfully loaded into the selected table, or to Leave All Records and thus leave all the records in the buffer regardless of if they were successful or not.
**Default Decimal**: This will set the number of decimal places to view the data. This will not alter any database settings.
**Export Directory**: The directory where the Export File browser will start in.
**Monitoring Software**: External software can be used to monitor DataShed usage and licenses.
**Repair System Objects on Startup**: Will refresh the System Objects if one or more objects are absent from the System Objects the next time DataShed is opened. Click the **Repair Now **button to repair the System Objects immediately.
**Suppress Extensions Warning**: When this is selected, the Refresh Extensions message that appears on starting DataShed will not be shown.
## User Libraries
Library Tables are used, as a validation tool to ensure that the correct data is entered into the database. Individual library tables may exist in the SQL database. They must first be configured and registered in the Configuration Manager, as a User Library, to be visible in DataShed.
To edit a library table, highlight the table and click on the **Edit **button.
## Local Grids
The local grids tab shows a list of grids that do not have a datum selected in the
**Spatial Reference >Coord System**
Local grids can be added to the database via this form
**Stored Procedure Options**
The check boxes displayed in the Stored Procedure Options allow the System Administrator to control whether the DataShed process or the store Procedure is used for DeSurvey, Grid transformations and Intercept Calculations.
*Advantages of Stored Procedures*: Processing speed is greatly improved
*Disadvantages of Stored Procedure*: DataShed filtering and DataSet selections cannot be utilised.
## Batch Delete
The batch Delete functionality allows lab result files to be deleted from the database from all the relevant tables:
- tblAssay
- tbAssayFlat
- tblSYSAssBatch
- tblSYSBatchDetails
- tblSYSAssIncomingData
**NOTE:**
**Only One lab file can be deleted at a time**
# DATASHED TOOLS – SYSTEM OBJECTS
**Topics Covered in this module:**
- **Using the Drill Form**
- **Utilising the Check Intervals functionality**
- **Setup and use of Intercept Calculator**
- **Setup and use of Desurvey module**
- **Configuration and use of Strip Log**
**Expected outcomes:**
- **Customise the Drill Form**
- **Utilise the functionality of the Intercepts Calculator and Desurvey module**
- **Customise DataShed so that it is optimized for companies requirements**
- **Ability to produce graphical logs for drill holes.**
Functionality a User has the ability to use.
Functionality and tasks accessible to a Super User.
Functionality and tasks restricted to the System Administrator
The System Objects are tools in the DataShed application. The can be utilised by System Administrators and User Plus security levels.
# System Objects
###
## Drillhole Form
The Drillhole Form is a preconfigured form that comes with DataShed and enables the user to view all the data associated with the Hole Id
The Basic, Coordinates and Other tab are part of the basic Drilling Form. The associated downhole records for each drillhole are shown in the subforms, which are configured by the system administrator in Config Manager and MS Access.
## Check Intervals
The Check Intervals form is a preconfigured form that comes as part of the System Objects. It is used to validate downhole tables and checks for overlapping intervals, missing intervals, duplicate intervals and intervals past the maximum collar depth.
1. Choose the table and the fields to validate.
2. Select the errors you wish to check for and click the Check button to validate the data. DataShed shows the number of records being processed and the amount of errors found.
Once the process is complete, view the errors and sort out if necessary.
The View Errors button allows the intervals that have a validation issues to be viewed and exported but not edited. It is possible to view the errors either as a summary or a Data Sheet view
Both the Summary and the Data Records views of the errors can be exported to an Excel spreadsheet for further validation.
**NOTE:**
**Use the Group By function to sort the data records into the error types.**
## Intercept Calculator
The Intercept Calculator allows the user to specify a set of parameters within which significant assay intervals within the specified parameters are calculated.
To create a new intercept calculator package, click
To modify an existing intercept calculator package, click
### Data Source
The source for the data to calculate the significant intercepts is defined in the DataSource form.
**Sample ****T****able**: This is the table which contains both the interval and assay information. Typically the view DHAssay which is a view joining the flat assay table (tblAssayFlat) with the downhole sample table (tblDHSample) is used.
**Depth From**: The drop down list is contains all the columns in the sample table selected and will be the top of the grade interval.
**Depth ****T****o**: The drop down list is contains all the columns in the sample table selected and will be the bottom of the grade interval.
**Filter Superseded Samples**: This allows the users to only use samples that are not superseded and thus avoid intervals which overlap. The definition of the superseded field is defined in the configuration form.
**Use SG ****W****eighting**: This allows the user to add the SG of intersection to the calculation. The SG value must be in the Sample table.
**Element Field**: This is the primary element for the intersection to be calculated. This field is compulsory. The values selected on the parameter are based on the element selected in this field.
**Co Elements: **The Co elements grade will be calculated over the intersection defined for the primary element selected. Up to 3 elements may be selected as co elements. Optional fields may be used as co elements.
## Parameters
**Minimum Cutoff Grade: **The grade value used as the minimum cutoff is the lowest grade that will be used in the intercept calculation. In the instances where there is 2 significant intervals separated by an area of waste, which when the intercept is calculated the total intersections grade value will be less than the cutoff grade, this intersection will still be reported.
**Maximum Cutoff Grade**: This is the highest value to be used in the intercept calculation. Any value that is higher than the maximum cutoff grade will be treated as this grade i.e. an interval that is 120 ppm will be treated as 100ppm.
**Null / Negative Values**: Set the way in which these are to be treated in the intercept calculation. .
**Minimum interval**: This is the narrowest width of a significant intersection taking into account the maximum waste width.
**Maximum ****W****aste: **This is the greatest allowable interval that has grade lower than the minimum cutoff grade.
**Reported units**: The units in which all the parameters are defined. All elements used in the calculation must be reported in the same unit.
**Decimals in Grade**: Defines the number of decimal places to be used in the final grade calculation.
**Decimals in ****W****idth**: Defines the number of decimal places to be used in the final intersection interval.
### Configuration
**Superseded Field: **Select the field in the sample table used to flag samples that are superseded samples.
**Field Type: **Select the option that defines the superceded field in the database
- Numeric: numeric field
- Text: any text field or varchar and nvarchar in SQL
- True/False: 0 is used as false
**Value if True**: the flag used to identify superseded samples.
**SG Field: **The field which stores the numeric SG value to be used in the intercept calculation. This field must be contained in the sample table.
By selecting the above options, filter by Package or Filter by User, when the intercepts table is opened then on the results for the selected package and the current User will be displayed.
### Intercept Calculator Results
The time taken to run the Intercept Calculator is dependent on the number of intervals to process as well as the number of elements selected.
Once the process is finished the results can be viewed in the DH Intercepts table
### Intercept Calculator Trouble Shooting.
**Validation Issues**
The Intercept Calculator will run if there are overlapping intervals in the sample table. However the hole with overlapping intervals will not have any intercepts calculated.
## DeSurveying Module
The Desurveying Module allows the users to generate real x y z points relative using the survey table data. These 3D coordinates are able to be generated for any downhole table.
### Desurvey Module Configuration
To configure a desurveying package:
1. Select a ** **desurveying package.
2. Enter a description of the package.
3. Select a method to determine the desurveying.
4. Select the **Use Negative Dip Values **if the dips in the database are negative for down dips and positive for holes that go up.
5. Once the method has been select click **Next **to progress to the next form.
### Compulsory Tables Setup
For the desurveying package to calculate, the collar and survey tables must be defined.
The fields in yellow are fields from which data is obtained to desurvey the hole. Fields in white are the fields that will be populated by the Desurvey Module.
**Note:**
**All coordinate fields should be in the same grid**
### Optional Tables Setup
Any other downhole table which contains a depthfrom and a depthto field can be configured to contain
desurveyed coordinates.
Once the table has been configured, the **Save **button must be clicked
To add a new table, click the **New **button.
Depth priority, there are 3 options which can be used to determine the desurveyed coordinates, use depth to, use depth from or calculate midpoint.
**NOTE:**
**The X Y and TVD fields must be added to the appropriate table prior to the desurveying package being configured.**
When the configuration is complete select **Finish**.
Press **Go **to run the Desurvey Package and populate the selected fields.
### Editing a Desurvey Package
A configured desurvey package can be edited at any stage to add more optional tables. Select the desurvey package from the Desurvey Module form and edit the required fields. Click **Finish **to run the package.
To delete a desurvey package, click the **Delete **button on the Desurvey Module form.
# STRIP LOG
The Strip Log module provides an interface to create graphical logs.
For the Strip Log installation and SQL Database requirements refer to the DataShed installation Guide.
## Pattern Manager
To utilise images in the strip log, codes must be first assigned an image in the library table. The Pattern Manager is a tool to assist this process.
1. Open Pattern Manager and select the library table.
2. From the dropdown boxes select the pattern, colour and image fields
3. Browse to assign the image by double clicking in the field to update. This opens the Image editor shown below. Right click on blank image data box and select load.
Browse to the image required and click open. Click Autosize to ensure that the image details are displayed in Striplog.
To add a pattern, double click in the pattern box to be edited to open the Pattern Editor
1. Create a new pattern or use one of the existing ones. Then click OK.
2. To add a colour click on the relevant colour cell and choose the colour to use.
**Save Changes **before exiting.
**NOTE:**
**Only bitmap files can be loaded using the Pattern Manager.**
## Strip Log Designer
**New Strip Log**
Open Strip Log and select Strip Log Designer
Assign the strip log a name by typing in the **Properties > Name.**
Add a column by right clicking in the column of the form or use the **Add Column **button on the tool bar.
Select the table containing the column that you wish to view and maximise it so that the fields are visible. Select the column and drag it onto the StripLog Column
The table setting box will be shown and map the fields shown if needed.
**Column Header**: the name which will be displayed at the top of the column on the strip log.
**Draw Type**: Choose from the dropdown list.
**Font**: Choose from options available using browse button.
**Source table**: Details of base table and information needed to construct the Strip Log.
**Library Lookup**: library table linked to the column being configured.
**Code Column**: the column in the library table that is referenced by the downhole table
**Lookup Column**: Column to be used in the strip log. Can be different to the Code Column
**Show Text**: Is the text to be shown in the Strip Log?
**Text Horizontal Alignment**: Choose from options in dropdown list.
**Text Vertical Alignment**: Choose from options in dropdown list.
If Line Chart or Bar Chart is selected as the Draw Type Bar/Line properties can be set.
**Auto Scale**: if set to False the Scale maximum and Scale Minimum should be set.
Views can be configured for the Strip Log. Shown below are the settings for tblvwDHAssay using Au_ppm as a line graph.
Click Save to preserve the design of the Strip Log.
## Strip Log Viewer.
To Open the Strip Log click on **System Objects> Strip Log**
Select the Strip Log configuration to use.
Select the DataSet and Hole Id. The strip log will open
**Note:**
**Only the DataSets selected in DataSet Manager will be available in the dropdown list.**
To change hole, select a new hole id and Strip Log will refresh.
Use the **Print Preview **option to view the Strip Log prior to printing.
# CONFIGURATION MANAGER
**Topics Covered in this module:**
- **Introduction to Configuration Manager**
- **Using Registration Manager**
- **Creating and managing Modules and Users**
- **Creating and managing DataSets and Projects**
- **Configuring additional tools, Spatial Search and Index Manager**
**Expected outcomes:**
- **Have the ability to add objects so that they are accessible in DataShed**
- **Understand how Users can be restricted both in the functionality of DataShed and the data that they have access to**
- **Customise DataShed so that it is optimized for companies requirements**
Database Configuration Setup Steps
The Configuration Manger allows the System Administrator to customise how objects in the SQL database are viewed through DataShed
## Registration Manager
The Registration Manager is used to configure the Tables, Extensions, Files, Projects and DataSets that are to be used and viewed through DataShed. Once created, these objects are available to be registered and then assigned Modules, Data Groups, User Groups and Users.
The Registration Manager can be accessed via the following menu selection: **View****Registration Manager**, or by pressing **Ctrl-R**.
Tables, extensions and files that have not yet been registered can be edited or deleted from the Registration Manager. The SQL database objects or files will not be affected by any changes or deletions in the Registration Manager of Tables, Extensions or Files. **The deletion of Projects and DataSets will affect the data in the DataShed database.**
### Adding a Table
1. Click on the Table button in the Registration Manager and the Available and Assigned tables will be displayed.
2. Click on the **Add **button and the Add Table screen is displayed. This screen allows information to be entered about the table.
3. Enter the Table Name. The Display Name is automatically populated, although the display name can be changed if required. The Display Name must be a unique name. An error message will alert you if the Table Name has already been used.
4. Tick the Shown in Tree box to make the table visible in DataShed.
5. Select the Object Class from the following options:
- **Assay**: Used for normalised assay tables and only one configuration entry with the Assay Object Class should be entered for each normalised assay table.
- **Collar**: Only one collar Object required and this will be populated automatically if there is a table called tblDHCollar
- **DownHole**: Object Class for all downhole data i.e. downhole survey data, drill hole geology, samples
- **Point**: For all point sample data, such as surface geochemistry
- **User Library: **All library tables.
1. Select the table or view name from the drop down list provided. Once the table has been selected, the table fields appear in the Order By: box.
2. **Order By **is only applicable for Access databases. Any SQL table or view will utilise the SQL indexing
3. Tick the **Selected Items Only **box to view only the selected fields. This is useful if there are numerous fields in the table or view.
4. Enter a form name for the Table or view to be seen in the DataShed Drilling Form. The form name is only used for DOWNHOLE object classes and relates to previously configured forms in the SQL database
5. Press **OK **to close the form once the table details have been entered. The Table will be visible on the left hand side of the screen.
6. Select the Table or Tables to be registered and click the **Register **button and the table name will move to the right of the screen.
7. To unregister a Table, highlight the table and click the **Unregister **button. The Table will now be visible on the left of the screen. Tables cannot be unregistered unless all associations with the table have been removed. If this is not the case, an error message will appear.
### Edit and Copy a Table Configuration
1. Select an unregistered table and clicking on the **Edit **button will display the Edit Table screen. This screen allows configured tables to be edited or copied. If the table is registered and attached to a module when the table is elected to be unregistered a prompt will be shown asking whether the table should be unattached so that the table configuration can be edited.
2. Make the changes to the table configuration as required then click **Save**.
3. The Table Name cannot be edited.
4. The Copy button shows the Add Table screen with everything but the Table and Display names detailed thus allowing a new table name to be entered.
5. Having the table selected and right clicking the mouse can also access the copy function.
### Load and Register Extensions
To Load Extensions from an Access database into the Config Manager click on the Load button on the Extension Form
Browser window will be displayed. Browse to the Access database containing the extensions to be loaded and click **Open**
1. The Load Extensions screen displays a List View on the left that is populated with all Queries, Reports and Forms in the database. Multiple extensions can be selected by holding down the Shift key. Click **Add **to move the extensions from the left side of the form to the right.
2. Extensions from multiple databases loaded by selecting a different database when repeating the load process.
1. Once extensions have been loaded, they must be registered before they can be assigned to Modules.
2. The view on the left shows the Extensions that are available to be registered to DataShed.
3. To register an Extension, highlight the extension and click the **Add **button. The Extension will be visible on the right when it is registered.
4. To register multiple Extensions highlight all the Extensions to register and click **Add All**.
5. To unregister an Extension, highlight the Extension and click **Remove**
6. Extensions cannot be unregistered unless all associations with the extension have been removed. If associations still exist an error message will appear.
**NOTE:**
**The naming convention for viewing extensions through DataShed applies therefore only extension prefixed with ext will be able to be loaded into the Config Manager and Extensions without the suffix Sub will be visible in DataShed.**
### Extension Trouble Shooting
The extensions names and paths are stored in the back end database in the table tblExtensions. Check that the path for the extension is the explicit path i.e. \\SnapServer\Shared rather than the drive letter i.e. Geology (G:). Ensure that an extension is unattached from a module and the registration is deleted prior to deleting the extension Access database.
### Registering Projects and DataSets
Clicking on the **Project **button in the Registration Manager will display the Projects registered to DataShed. All the DataSets that belong to a Project will be displayed in the list view. Projects are identified with a yellow icon and DataSets with a blue icon.
**Adding Projects and DataSets**
Click on **Add **to display the Add Project/DataSet screen.
1. Select either Project or DataSet from the dropdown Type list
Enter the Code and Name for the Project or DataSet. Tick the **Is Current **box if the SampleIDs in the DataSet are to be available for assay merging.
3. Close the form and save the data by clicking on the **OK **button.
**NOTES:**
- **All Project and DataSet names must be unique, and DataSets may not have names the same as any Projects. Project names must be unique from Module, User and User Group names.**
- **The Project or DataSet will be located in the List View below the Parent node. If a Project or DataSet is incorrectly located in the Project tree, select it and drag and drop it in the appropriate location.**
- **Use the Select Current Projects to set multiple DataSets to “Is Current”.**
## Modules
A Module groups a selection of associated Tables and Extensions.
### Creating and Customising Modules
1. To add a new user module right click in the User Module panel or Select **File > New > User Module**.
2. Enter a unique name for the Module. For example, you might use Collar Survey for all collar and survey tables, Environmental for all tables related to rehabilitation, Geology for all lithology, minerals and veining tables or Surface
3. A Tables and Extension folder is visible in the right panel for the new Module.
4. Highlight and right mouse click on the Table or Extension option to enable the edit function.
1. Highlight and add the Tables or Extensions that are to be associated with the Module.
2. A Table can only belong to one Module. An error message will alert you to the fact that the table is already assigned to another Module. To assign the same Table to different Modules the Table must first be registered in the Table Registration Manager with unique display names.
Order the tables within a module use the Up and Down buttons.
To enable ‘User Plus’ users to have edit rights any of these tables, tick the check boxes to the left of those tables. The **Edit All **and **Edit None **buttons will respectively tick all or none of the check boxes in the list.
Only the tables available to be added to module are visible on the left hand side. Once a table is attached to a
module it is removed from the available table list.
**NOTE:**
**The User Module name must be unique and not the same as a registered table name or description.**
## Users
A User can have associations to User Groups, Data Groups, Files, User Modules and Projects. To view all Users in the Config Manager click on User in the toolbar. A User’s name must be exactly the same as the user’s computer log on name, and is case sensitive.
### Creating User Profile
A User is created by clicking on **File > New > User **from the main Config Manager screen, or by right clicking in the left User panel.
The DataShed properties for each User can be configured by highlighting the Users name and right clicking, Properties
**DataSet Manager Expanded**: If this setting is set to True all DataSets will be displayed in DataShed under their relevant Project. If this is set to False, only the Projects will be displayed.
**QAQCR**: This should be set to false. This is a setting for future development.
**Security Level**: Each User is assigned a security level based on the functionality that they will have access to in DataShed. In summary:
- User: Has the ability to view and export data
- User Plus: Can view, export and import data
- Sys Admin: Has access to the full functionality of DataShed.
The internal SQL database security overrides the DataShed Security Levels.
**Suppress Extension Warning**: On opening DataShed the message box to update the extensions will be suppressed.
By default the right hand panel shows the options available for each user. Edit each option by right clicking and add each associated object to the User. Users can be assigned to as many User Groups as required.
### Assigning Projects
Every project that has been set up in the Registration Manager is visible in the right hand panel. Right click on the projects and tick the appropriate boxes to assign write privileges to the Projects and DataSets for each user.
The **Select All **and **Select None **buttons select or de-select every project below the currently highlighted project. For example if the Mines Project is selected and Select All or Select None, every project below will be automatically selected or unselected. Other projects outside of that sub-tree will not be affected.
The **Assign **Function allows the project selection for the selected user to be able to be applied to other users.
**NOTE:**
**Copying a User Profile and renaming it to a new User is a quick and efficient way of configuring Users with the same requirements.**
## Index Manager
The Index Manager allows the creation of indexes on views to improve performance of views in DataShed.
### Configuration of an Index
To open the Index Manager go to the View Menu and select Index Manager from the Menu.
1. Select **New **from the Index.
2. Select the view to Index from the drop down list
1. Select the index fields by checking the box to the left of the field name.
2. The order in which the fields are indexed can be changed by highlighting the field and using the up and down sequence arrows
3. Once the configuration is correct, click the **Save **button and the view name will be visible in the left box.
**NOTE:**
**Indexes must be applied to views that are required to be editable in DataShed. The minimum amount of**
**Indexes should be applied to the views/tables to allow for optimum performance.**
## Spatial Search
### Configuring Tables and Views for Spatial Search
To open the Spatial Search go to **View > Spatial Search**.
Click the **Add **button to enter the table or views parameters.
1. Select the source table, view or query.
2. Select the field that contains the DataSet. In most instances this will be the DataSet field
3. Select the field name of the object that will be the basis for any filtering. In tables containing drill hole information, this will Hole Id. In surface sample data it will be sample id.
4. Choose the coordinate data source. It can be any coordinate system including local coordinate systems.
5. Select the colours for selected and unselected points. The default colours are black for unselected points and red for selected points.
6. Once all the details are completed, click **OK **and the initial spatial search form will reopen, showing all the tables, views and extensions that have been configured.
1. To EDIT a configuration, select the table or view to edit and click on the **Edit **button and make the required changes.
2. To DELETE an entry, click on the **Delete **button and the configuration for the selected table will be removed.
### Configuring MapInfo or Arc Files for Spatial Search
In the **Spatial Search **Window, select the **Shape Files **button
1. Click **Add **to open the shape file configuration form.
2. Enter a name for the shape file.
3. Select appropriate Project and DataSet.
4. Enter the projection of the file. This will not restrict what drill holes you can open with the shape file.
5. Browse to the location of the file and select the file.
6. If the shape is to be hidden at startup, tick the hidden shape box. The shape file can be viewed but it will have to be started explicitly in DataShed.
## Configuring Coordinate Systems
**Topics Covered in this module:**
- **Adding data to spatial reference system in DataShed Config Manager**
- **Creating Grid transformations for Drill holes and Surface samples**
- **Transforming drillhole and surface coordinates.**
- **Using Keyboard transformation function**
**Expected outcomes:**
- Ability to add new National and Local coordinate systems into the database
- Create and use a variety of grid transformations.
DataShed has the functionality to manage and store all grid transformations for spatial data. The transformation process will occur on data, which has, the appropriate grid selected and only on the DataSets selected and the data, which is currently filtered.
It is important that you have correctly selected the data you want to transform. View the data once you have selected it either in Query Mode and/or Filter, and make a note of the number of records before you transform co-ordinates.
**Note**
**Converting between GDA94 (MGA94) and AGD84 (AMG84) High Accuracy method**
- NTv2 Grid Interpolation:
- Absolute accuracy +/-0.1m
**Medium Accuracy Method: DataShed**
- 7 parameter transformation calculation using National Grid generated 7 parameters.
- Absolute accuracy +/- 1m
**If < 1 meter accuracy is required for transforming coordinates between AGD84 or AGD66 and GDA94, it is recommended that DataShed Grid transformation are not appropriate.**
*Reference:*
*Geocentric Datum of Australia Technical Manual v2.4*
## Configuring Grids
### National Grids
#### A National Grid is a grid which references a Datum , an Ellipsiod and a Projection. This information is stored in the database
**Adding a New National Grid.**
Entering a new national Grid, the following information must be obtained:
- Ellipsoid code, Semi Major Axis and Inverse Flattening.
- Datum, dxWGS84, dyWGS84, dzWGS84
UTM Projection, projection type, Central meridian, False Easting, False Northing, Scale factor The Spatial Reference configuration settings are accessed through the Config Manager.
To open the Spatial Reference data in Config manager go to **View****Spatial Reference**. Spatial Reference allows the creation of Ellipsoids Datums, Projections and Coordinate System Codes.
### Adding an Ellipsoid
This screen allows the creation of Ellipsoid Codes.
To create a new Ellipsoid, click the **Add **button. Enter the unique Ellipsoid Code, Description, Semi Major Axis,
InverseFlattening, Source Ref, Added By and Notes. If possible it is important to record the Source reference for the data.
To edit an existing Ellipsoid select an Ellipsoid Code from the List View on the left. Edit the values necessary and click **Save**
To delete an Ellipsoid select an Ellipsoid Code from the List View on the left and click **Delete**.
### Adding a Datum
This screen allows the creation of Datum Codes.
**NOTE:**
**The seven point transformation is automatically used by the DataShed transformation function if the rotxWGS84, rotyWGS84, rotzWGS84, scale correction fields are populated as shown below. If this information is not available then the transformation will revert to a three point transformation.**
To create a new Datum, click on the Add button. Enter the unique Datum Code, Description, Ellipsoid Code, dxWGS84, dyWGS84, dzWGS84, rotxWGS84, rotyWGS84, rotzWGS84, Scale Correction, Source Ref, Added By and Notes.
To edit an existing Datum select a Datum Code from the List View on the left. Edit the required values and click
**Save**.
To delete a Datum select a Datum Code from the List View on the left and click on **Delete**.
**NOTE:**
**All datum codes rotations must be set to 0 if they are unknown.**
### Adding a Projection
This screen allows Projection Codes to be created, edited and deleted. .
To create a new Projection, click on the **Add **button. Enter the unique Projection Code, Description, Projection Type Code, Central Meridian, Original Latitude, First Standard, Second Standard, False Easting, False Northing, Scale Factor, Azimuth Angle, Source Ref, Added By and Notes.
### Adding National Grid Coordinate Systems
This screen allows the creation of Coordinate System Codes.
To create a new Coordinate System Code click on the Add button. Enter the unique System Code, Description, Projection Code, Datum Code, Source Ref, Added By and Notes.