scrollbar |
---|
----
Section | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
Expand | ||||||||||||||||||||||||||
Click to view Table of contents for this step | Click to view Table of contents for this step | toc
|
...
Step 5.1 Check table structure of all worksheets in Data spreadsheet handed over
Go to #Step Step 5.2. Grids_loc
The starting condition of this step is a populated DataTemplate, which contains all relevant information for the model.
When running the NGMS_Locations_Generator locations-generator macro, it will pick up this spreadsheet, conduct a variety of checks and sorts all locations in the appropriate order. For this purpose, the Generator uses hard-coded references to named worksheets and specific columns within a worksheet. To prevent failure in this processing, the following checks the need to be conducted on the table structure of the populated DataTemplate.
The comparison is done against the Empty_DataTemplate spreadsheet.
- worksheet GWabs_org
- ensure that no more than 4 runs are listed (column A-D), as the IdMapping can currently handle 4 runs only
Note: If more than 4 runs are to be processed, use a second spreadsheet and fill column A-D with the line numbers of the wells in those runs. Please ensure that both spreadsheets contain the same locations. - ensure that LicenceNo starts in column F (i.e. C6)
- ensure that no more than 4 runs are listed (column A-D), as the IdMapping can currently handle 4 runs only
- worksheet SWlat_org
- See above: ensure that no more than 4 runs are listed (column A-D), as the IdMapping can currently handle 4 runs only
Note: If more than 4 runs are to be processed, use a second spreadsheet and fill column A-D with the line numbers of the wells in those runs. Please ensure that both spreadsheets contain the same locations. - ensure that ConsentNo/LicenceNo starts in column I (i.e. C9).
- See above: ensure that no more than 4 runs are listed (column A-D), as the IdMapping can currently handle 4 runs only
- worksheet Branches_org
- check if reachNr is in column C (C3); chainage is in column D (C4), OSRef is in column J (C10)
- if not, copy the worksheet from the Empty_DataTemplate and populate again
or - add column D and column J from the Empty_DataTemplate.xls
- worksheet GWabs_IDmap_hist; GWabs_IDmap_nat; GWabs_IDmap_recact; GWabs_IDmap_fullic
- if not available, copy all 4 from Empty_DataTemplate
- worksheet SWlat_IDmap_hist; SWlat_IDmap_nat; SWlat_IDmap_recact; SWlat_IDmap_fullic
- if not available, copy all 4 from Empty_DataTemplate
The DataTemplate contains one macro, called 'CheckData' which checks if the essential data is in place. While the details will be addressed in the various steps below, most errors are caused if abovementioned steps are not properly conducted or if the OSreference column is empty. An OSreference column with empty or 'na' is not acceptable as this column is the key for creating a unique locationId
...
Step 5.2 Create and populate worksheets for Grids: Grids_loc and Grids_locSets
Go to #Step 5.3. GW management units
The worksheets Grids_loc and Grids_locSets are manually prepared. They specify the grid geometry and associated location sets as used in the data processing.
...
Info | ||
---|---|---|
| ||
Please pay attention to the calculation mode specified in Excel. This mode should be set to Automatic. If this is not set to automatic it could result in a wrong interpretation of abstraction for child wells. |
The comparison is done against the Empty_DataTemplate spreadsheet.
- worksheet Model_info
- ensure that the geological layers record are filled, as the generator checks this list to assign the observation boreholes to model layers
- calculate the simulation length in days by subtracting end-date - start-date (B65-B64) and setting the cell format to general. this simulation length needs to be used in the runMF-spreadsheet to specify the export length
- worksheet GWabs_org
- ensure that no more than 4 runs are listed (column A-D), as the IdMapping can currently handle 4 runs only
Note: If more than 4 runs are to be processed, use a second spreadsheet and fill column A-D with the line numbers of the wells in those runs. Please ensure that both spreadsheets contain the same locations. - ensure that LicenceNo starts in column F (i.e. C6)
- ensure that no more than 4 runs are listed (column A-D), as the IdMapping can currently handle 4 runs only
- worksheet SWlat_org
- See above: ensure that no more than 4 runs are listed (column A-D), as the IdMapping can currently handle 4 runs only
Note: If more than 4 runs are to be processed, use a second spreadsheet and fill column A-D with the line numbers of the wells in those runs. Please ensure that both spreadsheets contain the same locations. - ensure that ConsentNo/LicenceNo starts in column I (i.e. C9).
- See above: ensure that no more than 4 runs are listed (column A-D), as the IdMapping can currently handle 4 runs only
- worksheet Branches_org
- check if reachNr is in column C (C3); chainage is in column D (C4), OSRef is in column J (C10)
- if not, copy the worksheet from the Empty_DataTemplate and populate again
or - add column D and column J from the Empty_DataTemplate.xls
- worksheet GWabs_IDmap_hist; GWabs_IDmap_nat; GWabs_IDmap_recact; GWabs_IDmap_fullic
- if not available, copy all 4 from Empty_DataTemplate
- worksheet SWlat_IDmap_hist; SWlat_IDmap_nat; SWlat_IDmap_recact; SWlat_IDmap_fullic
- if not available, copy all 4 from Empty_DataTemplate
The DataTemplate contains one macro, called 'CheckData' which checks if the essential data is in place. While the details will be addressed in the various steps below, most errors are caused if abovementioned steps are not properly conducted or if the OSreference column is empty. An OSreference column with empty or 'na' is not acceptable as this column is the key for creating a unique locationId
Anchor | ||||
---|---|---|---|---|
|
Step 5.2 Create and populate worksheets for Grids: Grids_loc and Grids_locSets
Go to #Step 5.43. GW abstractionsmanagement units
The worksheets GWunitsGrids_loc and GWunitsGrids_locSets are manually prepared. They specify the predefined GWMUs (groundwater management units) grid geometry and associated location sets as used in the data processing.
Anchor | ||||
---|---|---|---|---|
|
Step 5.
...
3 Create and
...
populate worksheet for
...
GW management units: GWunits_loc and GWunits_locSets
Go to #Step 5.54. Observation boreholesGW abstractions
The worksheets GWunits_loc and GWunits_locSets are manually prepared. They specify the predefined GWMUs (groundwater management units) and associated location sets as used in the data processing.
Anchor | ||||
---|---|---|---|---|
|
Step 5.4 Populate and verify worksheet for groundwater abstractions: GWabs_org
Go to #Step 5.5. Observation boreholes
The worksheet GWabs_org holds location information on the groundwater abstractions as worksheet GWabs_org holds location information on the groundwater abstractions as defined in the model runs (WEL file). The worksheet GWabs_org is populated by the data provider. The information is used to generate the Locations.xml holding the XY-position of the abstraction as well as the tooltip shown on the Explorer.map. Multi-layer abstractions or multi-licence abstractions will be sorted by the macro and assigned a 'parent' location shown on the Explorer-map. Various grouping methods will be applied to assign the abstractions to different location sets. The macro will use this worksheet in combation combination with the GWabs_IDmap-worksheets to define the IdMapping between the location defined in the spreadsheet and the time series as held in the WEL file.
...
- Remove the example rows (if any) such that the row 40 is the first one containing the actual data
- Populate column I (OSreference) based on NGR (Easting, Northing) of borehole (column K and L).
- Check that column A,B,C,D are populated in correspondence to the provided runs (ModuleDataSets)
- Check that the number of locations/licences as listed in the spreadsheet corresponds (at least) to the number of wells in each WEL-file
- Define concatenate functions for cell B16, B17, B18, B19, B21, B22. The actual contents depends on data availability.
- Verify that the column(s) as used for the concatenate functions are properly populated with appropriate information (i.e. preferably no empty cells, 'unknowns, 'na' etc.). If necessary apply an 'IF-construction on the concatenate function. This verification is especially critical for columns being used in location names.
Info Expand Expand recommended concatenations with max. 4 WEL files Expand recommended concatenations with max. 4 WEL files cell
item
used in
recommended content
recommended concatenate function
B16
LocationName
Explorer (map and filter)
licence code, purpose code (if any), site name, layer
=IF(O40<>"";F40&""&G40&" - "&S40&" (L"&O40&")";F40&""&G40&" - "&S40)
B17
ShortName
Graph legends
if possible shorter version of above
B18
LocationDescription
Description in Explorer-tooltip
location type, GW-unit, Formation
=T40 & " in modelled at ("&M40&", "&N40&") [R"&p40&", C"&q40&"] in GW-unit " & W40 & " ("&X40&") from " & Y40 &" formation."
B19
Tooltip on map
free text Explorer-tooltip
licence holder, licence details, NGR, model coordinates (XYZ and RC)
=IF(U40="";"";"Licence holder: " &U40 & " (" &F40 & " - "&G40&") \n ")& "Easting: "located at NGR ("&K40&", Northing: " &L40& ""&M40& ", Model-Y), Row: "&N40&""&P40&", Column: "&Q40&", Layer: "&O40&" " \
B21
Caption
Shortcuts in GraphDisplay
see shortname or variations
see shortname or variations
B22
Shortcut
Shortcuts in GraphDisplay
see shortname or variations
see shortname or variations
...
- Remove the example rows (if any) such that the row 36 is the first one containing the actual data
- Populate column D (OSreference) based on XY-coordinate of the associated grid cell (column H and I).
- Define concatenate functions for cell B14, B15, B16, B17, B19, B20. The actual contents depends on data availability.
- Verify that the column(s) as used for the concatenate functions are properly populated with appropriate information (i.e. preferably no empty cells, 'unknowns, 'na' etc.). If necessary apply an 'IF-construction on the concatenate function. This verification is especially critical for columns being used in location names.
- Verify that observation locations do not refer to layer numbers which are not supported by the model. Data mapping is done on a model layer basis. Hence, an observation in layer 0 will not receive information if the model contains layer 1-3.
Info Expand Expand recommended concatenations Expand recommended concatenations cell
item
used in
recommended content
recommended concatenate function
B14
LocationName
Explorer (map and filter)
site name & site code (optional layer)
=N36&" - "&C36
B15
ShortName
Graph legends
if possible shorter version of above
B16
LocationDescription
Description in Explorer-tooltip
location type, GW-unit, Formation
=O36 & " in GW-unit modelled at ("& P36 H36&" (, "&Q36I36&") [R"&K36&", C"&L36&") in GW-unit " & P36 & " ("&Q36&") from " & R36 &" formation."
B17
Tooltip on map
free text Explorer-tooltip
borehole details (if any), NGR, model coordinates (XYZ and RC)
="Top of boreholeBH top: "&U36&" mAOD, Base of boreholebase: "&V36&" mAOD\n Easting: , located at NGR ("&F36&", Northing: "&G36&" "&H36& ", Model-Y: "&I36&" ), Row: "&K36&", Column: "&L36&", Layer: "&J36&" " \
B19
Caption
Shortcuts in GraphDisplay
see shortname or variations
see shortname or variations
B20
Shortcut
Shortcuts in GraphDisplay
see shortname or variations
see shortname or variations
...
- Remove the example rows (if any) such that the row 35 is the first one containing the actual data
- Populate column B (OSreference) based on XY-coordinate of the associated grid cell(column F and G).
- Define concatenate functions for cell B12, B13, B14, B15, B17, B18. The actual contents depends on data availability.
- Verify that the column(s) as used for the location name are properly populated with appropriate information (i.e. preferably no 'unknowns, 'na' etc.)
- Verify that observations do not refer to layer numbers which are not supported by the model. Data mapping is done on a model layer basis. Hence, gaugeboards in layer 0 do not receive information if the model contains layer 1-3).
Info Expand Expand recommended concatenations Expand recommended concatenations cell
item
used in
recommended content
recommended concatenate function
B12
LocationName
Explorer (map and filter)
site name & site code
=L35&" - "&A35
B13
ShortName
Graph legends
if possible shorter version of above
B14
LocationDescription
Description in Explorer-tooltip
site description, river (if necessary)
=M35 & " " & N35
B15
Tooltip on map
free text Explorer-tooltip
NGR, model coordinates (XYZ and RC)
="Easting: "&D35&", Northing: " &E35& " Model-X: "&F35& ", Model-Y: "&G35&" "\Row: "&I35&", Column: "&J35&", Layer: "&H35&" \"
B17
Caption
Shortcuts in GraphDisplay
see shortname or variations
see shortname or variations
B18
Shortcut
Shortcuts in GraphDisplay
see shortname or variations
see shortname or variations
...
- Remove the example rows (if any) such that the row 37 is the first one containing the actual data
- Populate column L (OSreference) based on the NGR-coordinate of the discharge or abstraction point (column N and O).
- Define concatenate functions for cell B14, B15, B16, B17, B19, B20. The actual contents depends on data availability.
- Verify that the column(s) as used for the concatenate functions are properly populated with appropriate information (i.e. preferably no empty cells, 'unknowns, 'na' etc.). If necessary apply an 'IF-construction on the concatenate function. This verification is especially critical for columns being used in location names.
...
Step 5.8 Populate and verify worksheet for river branches: Branches_org
Go to #Step 5.9. IdMaps for GW abstraction
The worksheet Branches_org holds location information on the branches shown as an accretion profile, including the sequence of stream cells within a branch. The worksheet Branches_org is populated by the data provider. The information is used to generate the Branches.xml as well as the Locations.xml. Branches should be defined from source to outlet, to ensure that the accretion profile builds up from left to right.
Notes on the use of columns:
- The Stream/rivername is normally used as unique identifier. Please do not use a slash (/) in the name.
- A new branch is identified by a changing name.
Please conduct the following verification and preparation steps:
- Remove the example rows (if any) such that the row 12 is the first one containing the actual data
- Ensure that you use the correct table format: column C should say reachNr and column J should be OSreference
- Populate column J (OSreference) based on the XY-coordinate of the associated streamcell (column H and I).
- Check that the number of features is limited to keep a clear display
- Ensure that each branch is sorted from source (chainage = 0 m) to outlet (chainage= ???? m). Chainage should be in meters
...
Info Expand Expand recommended concatenations Expand recommended concatenations cell
item
used in
recommended content
recommended concatenate function
B14
LocationName
Explorer (map and filter)
consentNo, purpose code, sitename
=IF(I37="";X37;IF(J37<>"";I37&"_"&J37&" - "&X37;I37 &" - "&X37))
B15
ShortName
Graph legends
if possible shorter version of above
=IF(I37="";X37;IF(J37<>"";I37&"_"&J37;I37))
B16
LocationDescription
Description in Explorer-tooltip
site description, purpose, remark if any
=Y37&" for "&AA37 &" purposes. "&AE37
B17
Tooltip on map
free text Explorer-tooltip
licence holder (if any), NGR, model coordinates (XYZ and RC)
="Licenceholder: " &Z37&"\n Easting: "&N37&", Northing: " &M37& " Model-X: "&P37& ", Model-Y: "&Q37&" \Row: "&S37&", Column: "&T37&", Layer: "&R37&" \"
B19
Caption
Shortcuts in GraphDisplay
see shortname or variations
see shortname or variations
B20
Shortcut
Shortcuts in GraphDisplay
see shortname or variations
see shortname or variations
Anchor | ||||
---|---|---|---|---|
|
Step 5.8 Populate and verify worksheet for river branches: Branches_org
Go to #Step 5.9. IdMaps for GW abstraction
The worksheet Branches_org holds location information on the branches shown as an accretion profile, including the sequence of stream cells within a branch. The worksheet Branches_org is populated by the data provider. The information is used to generate the Branches.xml as well as the Locations.xml. Branches should be defined from source to outlet, to ensure that the accretion profile builds up from left to right.
Notes on the use of columns:
- The Stream/rivername is normally used as unique identifier. Please do not use a slash in the name.
- A new branch is identified by a changing name.
Please conduct the following verification and preparation steps:
- Remove the example rows (if any) such that the row 12 is the first one containing the actual data
- Ensure that you use the correct table format: column C should say reachNr and column J should be OSreference
- Populate column J (OSreference) based on the XY-coordinate of the associated streamcell (column H and I).
- Check that the number of features is limited to keep a clear display
- Ensure that each branch is sorted from source (chainage = 0 m) to outlet (chainage= ???? m). Chainage should be in meters
Anchor | ||||
---|---|---|---|---|
|
Step 5.9 Populate and verify worksheets with IdMap data for GW abstractions: GWabs_IDMap (4 worksheets)
Go to #Step 5.10. IdMaps for SW laterals
If step 5.1 is done correctly, 4 worksheets have been added: GWabs_IDmap_hist; GWabs_IDmap_nat; GWabs_IDmap_recact; GWabs_IDmap_fullic
The worksheets need to be populated with results from step 4.
- Go to the XML-files as generated in step 4.8
- For each scenario-type conduct the following steps:
- copy the individual locations (id, x,y,z) as listed in XXX_GW_abstractions_Locations.xml
- paste into column H,I,J,K (starting at row 3)
- copy the parent locations (id, x,y,z) as listed in XXX_GW_abstractions_Locations_MultiLayer.xml
- paste into column B,C,D,E (starting at row 3)
If you do have an XML-editor which can only copy-paste the table with XML-structure, it might be wise to create a macro in your text editor which converts the table into a comma seperated table which can be loaded into Excel.
Anchor | ||||
---|---|---|---|---|
|
Step 5.10 Populate and verify worksheets for SW laterals: SWlat_IDMap (4 worksheets)
Go to #Step Step 5.10. IdMaps for SW laterals11. Generate Location XML-files
If step 5.1 is done correctly, 4 worksheets have been added: GWabsSWlat_IDmap_hist; GWabs_IDmap_nat; GWabs_IDmap_recact; GWabs_IDmap_fullic
The worksheets need to be populated with results from step 4.
- Go to the XML-files as generated in step 4.8
- For each scenario-type conduct the following steps:
- copy the individual locations (id, x,y,z) as listed in XXX_GW_abstractions_Locations.xml
- paste into column H,I,J,K (starting at row 3)
- copy the parent locations (id, x,y,z) as listed in XXX_GW_abstractions_Locations_MultiLayer.xml
- paste into column B,C,D,E (starting at row 3)
If you do have an XML-editor which can only copy-paste the table with XML-structure, it might be wise to create a macro in your text editor which converts the table into a comma seperated table which can be loaded into Excel.
...
SWlat_IDmap_nat; SWlat_IDmap_recact; SWlat_IDmap_fullic
The worksheets need to be populated with results from step 4.
- Go to the XML-files as generated in step 4.8
- For each scenario-type conduct the following steps:
- copy the individual locations (id, x,y,z) as listed in XXX_Stream_Cell_Locations.xml
- paste into column H,I,J,K (starting at row 3)
If you do have an XML-editor which can only copy-paste the table with XML-structure, it might be wise to create a macro in your text editor which converts the table into a comma seperated table which can be loaded into Excel.
TO DO Step Add 'new wells'
Anchor | ||||
---|---|---|---|---|
|
Step 5.11 Generate Location files
Go to #Step 5.12. Update Grids.xml file
If everything is ready, you can run the macros. Note that the macro version 5 assumes that you use FEWS-software build 20300 or higher.
- To run the macro, conduct the following steps:*
- Open the spreadsheet NGMS-locations_Generator_v5.00.xls.
- Activate the data-spreadsheet and run the macro 'SortLocationsAddParents' held in the NGMS_Locations_generator-spreadsheet.
- The macro asks what to items to process. Normally you would like to process all. Since file saving to DBF4 contains some layout issues, the macro can do this automatically. Note that it shows a message at the time of saving if the file already exists. Dependent on the model size it can take up to 2 hours (e.g. YNN).
- Check the results
- Are the newly generated worksheets properly filled ?
- Did the concatenate functions give proper results (especially for parents) ?
- Is the IDMapping OK ?
- If anything is incorrect:
- Fix the error in the _org worksheet
- Remove the associated worksheets generated by the macro.
- Save again under the same name (possibly with a version number)
- Run the macro 'SortLocationsAddParents' again and pick only the relevant location types.
- Check again.
If everything seems OK one can continue with the generation of the XML-files.
To generate the XML-files, conduct the following steps:
- Run macro 'create_XMLfiles'. (NB at the end of the Sort-macro, it also asks if this next step should be conducted autiomatically).
- The macro creates XML-files in the directory of the data-spreadsheet.
- The macro overwrites existing files
- You can skip location types to be generated (e.g. if you want to update a branches file), but be aware:
If you skip any of the location types listed, your Locations.xml file might not be complete.
- Check the contents of the files. It might be wise to validate with an XML-validation tool.
- Copy the files which are OK to your configuration:
- Any DBF-file to \Config\MapLayerfiles
- Locations.XML, LocationSets.xml, Branches.xml, Polygons.xml --> region-root\Config\RegionConfigFiles
- IdMap files --> \Config\IdMapfiles
- Leave the Grids.xml file to be updated in the next step
Anchor | ||||
---|---|---|---|---|
|
Step 5.12 Update Grids.XML file
The Grids.xml file needs to be update with some data from step 4.
The Grids-file, generated in the previous step is not complete yet. if properly setup in step 5.2 it contains all regular grid definitions as well as the irregular grid-definition (placeholder) for the StreamCells_sparse_grid, i.e. the vector of streamcells. To be valid, such irregular grid needs cell centre coordinates for each grid cell. These coordinates have been generated by the ModuleAdapter in step 4.8 as file XXX_StreamCell_Locations_Grid.xml.
To complete the Grids.xml file, conduct the following steps (assuming that all scenario-types share the same streamcells):
- Go to the XML-files as generated in step 4.8
- Copy the individual locations in XML-structure (cell centre) as listed in XXX_Stream_Cell_Locations_Grid.xml
- Paste into the associated irregular grids section of the Grids.xml file.
- Update the number of rows to 1
- Update the number of columns to the total number of streamcells
- Save the file and copy to \Config\RegionConfigFiles
...
Step 5.10 Populate and verify worksheets for SW laterals: SWlat_IDMap (4 worksheets)
Go to #Step 5.11. Generate Location XML-files
If step 5.1 is done correctly, 4 worksheets have been added: SWlat_IDmap_hist; SWlat_IDmap_nat; SWlat_IDmap_recact; SWlat_IDmap_fullic
The worksheets need to be populated with results from step 4.
- Go to the XML-files as generated in step 4.8
- For each scenario-type conduct the following steps:
- copy the individual locations (id, x,y,z) as listed in XXX_Stream_Cell_Locations.xml
- paste into column H,I,J,K (starting at row 3)
If you do have an XML-editor which can only copy-paste the table with XML-structure, it might be wise to create a macro in your text editor which converts the table into a comma seperated table which can be loaded into Excel.
TO DO Step Add 'new wells'
...
Step 5.11 Generate Location XML-files
Go to #Step 5.12. Update Grids.xml file
If everything is ready, you can run the macros.
- Create a backup-file with name XXX_LocationsProcessed_originals_versionnumber.xls.
- Open the spreadsheet NGMS-locations_Generator.xls.
- Activate the data-spreadsheet and run the macro 'SortLocationsAddParents' held in the NGMS_Locations_generator-spreadsheet.
- The macro asks what to items to process. Normally you would like to process all. Dependent on the model size it can take up to 2 hours (e.g. YNN).
- Check the results
- Are the newly generated worksheets properly filled ?
- Did the concatenate functions give proper results (especially for parents) ?
- Is the IDMapping OK ?
- If anything is incorrect:
- Fix the error in the _org worksheet
- Remove the associated worksheets generated by the macro.
- Save again under the same name (possibly with a version number)
- Run the macro 'SortLocationsAddParents' again and pick only the relevant location types.
- Check again.
If everything seems OK one can continue with the generation of the XML-files
- Create a backup with name XXX_LocationsResults_versionnumber.xls
- Run macro 'create_XMLfiles'.
- The macro creates XML-files in the directory of the data-spreadsheet.
- The macro overwrites existing files
- You can skip location types to be generated (e.g. if you want to update a branches file), but be aware:
If you skip any of the location types listed, your Locations.xml file might not be complete.
- Check the contents of the files. It might be wise to validate with an XML-validation tool.
- Copy the files which are OK to your configuration:
- Locations.XML, LocationSets.xml, Branches.xml, Polygons.xml --> region-root\Config\RegionConfigFiles
- IdMap files --> \Config\IdMapfiles
- Leave the Grids.xml file to be updated in the next step
...
Step 5.12 Update Grids.XML file
...