Plan View requirements for the tool to work

Plan View tool requirements basic explanation.

For the plan view to work, there are some requirements to show point data from within the tool.

Below is the standard query that is used to draw data from the database and display said data in the plan view tool.

“

SELECT  S.PROJECT ,

        S.SITE_ID ,

        S.END_DEPTH ,

        S.COORDSYS ,

        S.EASTING ,

        S.NORTHING ,

        S.HEIGHT

FROM    DBO.VW_SITE_WITH_BEST_SURVEY S

WHERE   S.PROJECT = '?Select a Project?'

        AND S.COORDSYS IS NOT NULL

ORDER BY S.PROJECT ,

        S.SITE_ID

“

From the query we can see that data is read from a view that is built into the standard model of the Geobank database.

Please see the design element below.

“

SELECT 

 S.PROJECT,

S.SITE_ID,

S.SITE_TYPE,

S.PARENT_SITE_ID,

S.START_DEPTH,

S.END_DEPTH,

S.ORIGINAL_END_DEPTH,

S.PRECOLLAR_DEPTH,

S.DATE_STARTED,

S.DATE_COMPLETED,

                S.COMPANY,

S.GEOLOGIST,

S.SITE_STATUS,

S.SITE_PURPOSE,

S.LEASE,

S.FARM,

S.SOFTSEDS,

S.WEATHDS,

S.HISTORIC_SITE_ID,

S.MAP_SHEET_100K,

S.MAP_SHEET_250K,

                S.COMMENTS,

S.SAMPLE_FROM,

S.SAMPLE_TO,

S.NUMBER_SAMPLES,

S.DATE_YEAR,

S.PLATEAU,

S.DRILL_SOURCE,

S.REOH,

S.GRID,

S.PIT,

R.COORDSYS,

R.EASTING,

                R.EQUIPMENT,

R.HEIGHT,

R.NORTHING,

R.RELIABILITY,

R.SURVEY_COMPANY,

R.SURVEY_METHOD,

R.SURVEY_TYPE,

R.DATE_SURVEYED,

R.CONVERT_LOG, R.BLOCK,

                R.ORIGINAL_HEIGHT, R.END_DEPTH AS END_DEPTH_2

FROM        

dbo.GB_SITE AS S LEFT OUTER JOIN

                 dbo.VW_RANKED_SURVEY AS R ON

S.SITE_ID = R.SITE_ID

AND

S.PROJECT = R.PROJECT

AND

R.SURVEY_RANK = 1

“

As we can see there are multiple layers of views and functions being referenced when loading the data for the plan view tool.

In the above query (view) we are simply selecting data from the GB_SITE table and a view.

What is important here is that the data selected is only for any coordinate data that is marked as rank 1. The rank 1 here is used to define the default coordinate system used.

As we can see there are multiple elements that finally build up the data required for the plan view to work. These elements are built into the standard model that Geobank uses and would normally not have to be added or configured.

We do however need to ensure that our survey data is logged into the GB_SITE table and into the
GB_SITE_SURVEY table.

GB_SITE table:

GB_SITE_SURVEY table:

It is possible to start using the plan view tool if all the tables, stored procedures and functions are in place. If the standard model for Geobank was used for the configuration of your database, you will already have everything that you need.

You only need to import your data into the GB_SITE and GB_SITE_SURVEY tables, once imported, the plan view should be able to read the data and display the point data.

It should be noted that the plan view tool requires certain columns to contain data to run, it will otherwise produce an error message.

These are PROJECT, SITE_ID, COORDSYS, NORHTING, EASTING, HEIGHT, INSTANCE, RANKING

If your database model is not in line with the standard model in these regards, we can push the database through a process to get all the backend configurations built in that is required.

This will have to be done by Micromine Geobank specialists.

Want to learn more?

Online Help Manuals - Click here for the latest version

Learning Management System - Click here to login or here to request access