ADDENDUM TO APRIL 2003 MANUAL 1. INTRODUCTION 1 2. GIS PROGRAMS 1 3. IMPORTING AND EXPORTING GIS FILES 2 4. IMPORTING ESRI FILES 3

Transcription

1 DRAINS ADDENDUM TO APRIL 2003 MANUAL 29 May 2003 CONTENTS 1. INTRODUCTION 1 2. GIS PROGRAMS 1 3. IMPORTING AND EXPORTING GIS FILES 2 4. IMPORTING ESRI FILES 3 5. EXPORTING ESRI FILES 9 6. IMPORTING MAPINFO FILES EXPORTING MAPINFO FILES 18 1

2 1. INTRODUCTION An important additional capacity has been added to the DRAINS program since the April 2003 Manual was produced. This is the ability to transfer DRAINS model data and results to Geographic Information Systems (GISs). This optional feature complements the ability of DRAINS to import and export data to DXF and DWG files, and will be particularly useful to drainage asset managers and council engineers and consultants modelling complex, areawide drainage networks. It will assist in setting up DRAINS models by allowing users to import data on positions of components, attributes such as pipe lengths or pit surface levels, and backgrounds into a new DRAINS model. Once additional data has been added and the model has been fully developed, the data it contains can be exported in GIS formats. As well as the data describing the system, a number of results of runs can be included, so that a GIS file may contain flowrates and HGL levels for average recurrence intervals of 1, 2, 5, 10, 20, 50 and 100 years, plus probable maximum precipitation (PMP) storms. The mapping powers of GIS programs can then be used to present results using colourcoded symbols and lines. The GIS will also act as a means of querying the underlying database, so that flows or HGL levels at particular locations can be checked on-screen. DRAINS allows for the transfer of data in two common GIS formats, ESRI ArcView shapefiles and MapInfo MIF/MID files. Ultimately, drainage system managers can develop systems where revised DRAINS models can be created from information on previous DRAINS models in their GIS. As new developments and re-developments occur, it will be possible to include these. Results from various models can be retained in the GIS system. The combination of DRAINS with GIS allows managers to maintain and ongoing record of their drainage systems that included records of performance and flooding risk. This GIS transfer capability is available as an optional addition to DRAINS. Contact Bob Stack of Watercom Pty Ltd for price details on (02) or bobstack@watercom.com.au. The following sections outline the ways that transfers can be made. You can test these using the demonstration version of DRAINS available on 2. GIS PROGRAMS Geographic Information System (GIS) programs combine a mapping facility with a data base of information on the spatial position of components, such as drainage pits and pipes, and on their other attributes, such as pipe diameters. Objects are displayed in different ways, according to some of their attributes. Maps can be produced on paper or can be inspected electronically. The most common products used in Australia are ArcView (produced by ESRI ( and MapInfo (produced by MapInfo Corporation ( but 1

3 there are other products used such as Cadcorp SIS ( Autodesk Map ( and Intergraph ( There are also a number of companies that provide systems based on the main types of software. In addition to the existing 12D, Land Desktop and DXF transfers DRAINS now provides transfers in the form of ArcView shapefiles and Mapinfo MID/MIF files, which are the most commonly-used GIS formats. These can be imported and exported by nearly all GIS programs. For authorities managing drainage systems, the connection of DRAINS with their GIS systems allows the results of DRAINS analyses, such as flowrates and hydraulic grade line levels, to be included in the GIS. DRAINS results can then be mapped and displayed in many ways. The linkage also allows DRAINS models to be created from a GIS. GIS file structures can be complex. In Arcview, to fully specify an object such as a pipe, it is necessary to establish three files, with the suffixes: SHP, SHX and DBF. The transfer from DRAINS provides shapefiles for six objects - pits, sub-catchments, pipes, overflow routes, survey data on ground levels along pipe routes and positions of other services, so that it generates 18 files. If there is a background in the DRAINS file, this will generate a DXF file. In MapInfo, two file types, with suffixes MID and MIF, are required, so that 12 files are generated in a transfer from DRAINS. If there is a background in the DRAINS file, this will generate a DXF file. 3. IMPORTING AND EXPORTING GIS FILES DRAINS provides transfers of system data and results between GIS programs and DRAINS, reading from and creating ESRI (ArcView) shapefiles and Mapinfo MIF files. This facility is not standard in DRAINS, but is available at an additional cost. The transfers take place through options in the File menu. To import data you must set up GIS files in a required format (which is explained in the importing information for ESRI and MapInfo files, and which can be viewed in exported demonstration files). The files involved are shown below: It is not necessary to create all the GIS files listed above. The minimum requirement is the SHP, SHX and DBF or MID and MIF files for the nodes. The others are optional. 2

4 The exporting process is similar to the transfer from DRAINS to a spreadsheet program. It is possible to export into ESRI and MapInfo files both the data for various components and the results of analyses using storms of different magnitudes. 4. IMPORTING ESRI FILES This process enables you to import data into DRAINS from one to six sets of ESRI or ArcView files, plus an optional background from a DXF file. The procedure is pretty much the reverse of the exporting process for ESRI files. ArcView stores spatial information in a set of three ASCII files: a SHP is the main file defining a number of records for shapes (points, lines, polylines or polygons), defined by the coordinates of their vertices, a SHX file acting as an index to the records in the main file, a DBF file containing a DBASE table of attributes associated with each record. The records describe pits, pipes and other components of a drainage system. If you wish to model an existing drainage system in DRAINS, and ArcView records are already available, you need to edit these into the format required by DRAINS, which is the same as the format generated in the export process that creates ESRI files from DRAINS data. You can see this format by exporting a small system and examining the resulting DBASE tables in your GIS. For nodes, a table with the following 13 headers for columns or "fields' are required: Shape - the nature of the object (point), Name - any name up to 10 characters, DRAINSid - an internal number used by DRAINS to connect nodes and links you should leave this blank. If DRAINS has generated a number, you should not delete or change it. Type - type of node; "OnGrade", "Sag" or "Node", Family - the pit family, corresponding to a family in the pit data base in the DRAINS model to which the data is being transferred, or "N/A", Size - a pit size within the nominated pit family, or "N/A", Pondingvol - the volume of water that can pond over a sag pit (m 3 ), Ku - the pit pressure change coefficient (Use "N/A" for simple nodes), Surfaceel - the surface elevation at the node (m), Ponddepth - a Colebrook-White or Manning's roughness coefficient, Baseflow - any constant baseflow (m 3 /s) originating at the node, Blockfactr - a blocking factor to be applied at pits ("N/A" is used for nodes), Boltdnlid - Yes or No for a bolt down lid. For pipes, a table with the following 12 headers for columns or "fields' are required: Shape Name - the nature of the object (pline), - any name up to 10 characters, 3

5 DRAINSid - an internal number used by DRAINS to connect nodes and links - you should leave this blank. If DRAINS has generated a number, you should not delete or change it. Length - the pipe length (m), UpstreamIL - the invert level at the upstream end of the pipe (m), DownStrmIL - the downstream invert level (m), Slope(%) - the pipe slope (%), Type - the pipe type, which must correspond to a type in the pipe database of the DRAINS model to which the data is being transferred, NomDia - the nominal pipe diameter (mm) corresponding to diameters in the pipe type nominated, Roughness - a Colebrook-White or Manning's roughness coefficient, Status - "New" or "Existing", NumPipes - the number of parallel pipes, usually 1. For information on the other four components, refer to the exported ESRI file formats. If this is an initial transfer, it is unlikely that all the information required by DRAINS will be available in the GIS. In the files to be transferred, all the required information that is already in the GIS should be included. It is then a matter of judgment as to whether you add additional data in these files, or use dummy values and change them in DRAINS. To illustrate the process, consider the following example, named "Oldtown". The node "theme" is associated with the following table, which has been created by editing, which can take place in ArcView, Microsoft Access or Excel. 4

6 The corresponding pipes table is: 5

7 From the ArcView themes, a DXF file containing a background for the DRAINS model can be created. All layers in this will be included in the background. You will need to place all the files to be transferred into the same Windows folder. The transfer must include at least the nodes file. To make the transfer, you need to set up a DRAINS model with the ILSAX hydrological model and pit and pipe data bases that you require, and then use the File -> Import -> ESRI Shapefiles option, which will display the following message: 6

8 After "Yes" is entered, you must select one of the ESRI files to be transferred. The transfer will then take place, and the pits and pipes will come into view. As the window below shows, the data information is transferred over, and further data can be added to the property sheets. 7

9 With this setup it is possible to import a new or additional background. Using the File -> Import -> Import DXF background option brings up a dialog box from which a DXF file can be opened. When a file is selected, the following window appears: When a choice is made, the background is replaced. 8

10 5. EXPORTING ESRI FILES It is first necessary to establish a system that is capable of being run, such as the demo example shown below: Selecting the ESRI Shapefiles option from the File -> Export menu presents the following message: 9

11 If you continue, you will then need to nominate a filename for shapefiles in the following dialog box: You can see from the existing files in this example how six ESRI SHP files are established. Another 12 SHX and DBF files will also be produced. After a name is entered, the process is complete if there are no results. If results are available, the following dialog box appears: A suitable name should be added describing the results; here they are for a 2 year average recurrence interval storm. The limited size is due to restrictions on the size of column headings in the database files used in ArcView. After this is entered, the process is finished. If a background is present in the DRAINS model, this will be transferred with the ESRI files. The transferred files can now be viewed in ArcView and ArcMap: 10

12 11

13 A database table is associated with each theme, as shown below: Note that this includes results with the "2Yr" added to headings as a suffix. If another run is made and the process is repeated with one of the existing shapefiles nominated in the Save As dialog box, additional results will be appended, as shown below: If data from a GIS data base can be assembled into this same format, less the results, the File Import option ESRI Shapefiles can be used to import data into DRAINS. 12

14 6. IMPORTING MAPINFO FILES This process enables you to import data into DRAINS from one to six sets of MapInfo files, plus an optional background from a DXF file. The procedure is pretty much the reverse of the exporting process for MapInfo files. Mapinfo stores spatial information in a set of two ASCII files: a MIF (Mapinfo Interchange File) is the main file defining a format for data records associated with objects (points, lines or polygons) and the coordinates of the vertices of objects, a MID file containing a contents of a table of attributes associated with each object. The tablular data describes pits, pipes and other components of a drainage system. If you wish to model an existing drainage system in DRAINS, and MapInfo records are already available, you need to edit these into the format required by DRAINS, which is the same as that generated in the export process that creates MapInfo files from DRAINS data. You can see this format by exporting a small system and examining the resulting tables. For nodes, a table with the following 13 headers for columns or "fields' are required: Shape - the nature of the object (point), Name - any name up to 10 characters, DRAINSid - an internal number used by DRAINS to connect nodes and links - this must be kept blank, Type - type of node; "OnGrade", "Sag" or "Node", Family - the pit family, corresponding to a family in the pit data base in the DRAINS model to which the data is being transferred, or "N/A", Size - a pit size within the nominated pit family, or "N/A", Pondingvol - the volume of water that can pond over a sag pit (m 3 ), Ku - the pit pressure change coefficient (Use "N/A" for simple nodes), Surfaceel - the surface elevation at the node (m), Ponddepth - a Colebrook-White or Manning's roughness coefficient, Baseflow - any constant baseflow (m 3 /s) originating at the node, Blockfactr - a blocking factor to be applied at pits ("N/A" is used for nodes), Boltdnlid - Yes or No for a bolt down lid. For pipes, a table with the following 12 headers for columns or "fields' are required: Shape - the nature of the object (pline), Name - any name up to 10 characters, DRAINSid - an internal number used by DRAINS to connect nodes and links - you should leave this blank. If DRAINS has generated a number, you should not delete or change it. Length - the pipe length (m), UpstreamIL - the invert level at the upstream end of the pipe, DownStrmIL - the downstream invert level, Slope_pct - the pipe slope, Type - the pipe type, which must correspond to a type in the pipe database of the DRAINS model to which the data is being transferred, NomDia - the nominal pipe diameter (mm) corresponding to diameters in the pipe type 13

15 nominated, Roughness - a Colebrook-White or Manning's roughness coefficient, Status - "New" or "Existing", NumPipes - the number of parallel pipes, usually 1. Results of analyses are not required, and will be ignored if present. For information on the other four components, refer to the exported MapInfo file formats. If this is an initial transfer, it is unlikely that all the information required by DRAINS will be available in the GIS. In the files to be transferred, all the required information that is already in the GIS should be included. It is then a matter of judgment as to whether you add additional data in these files, or use dummy values, and change them within DRAINS later. To illustrate the process, consider the following example, named "Oldtown". The node information is associated with the table shown above, which can be set up in MapInfo or a text editor. The corresponding pipes table is similar. From the Mapinfo themes, a DXF file containing a background for the DRAINS model can be created. All layers in this will be included in the background. 14

16 You will need to place all the files to be transferred into the same Windows folder. The transfer must include at least the nodes file. To make the transfer, you need to set up a DRAINS model with the ILSAX hydrological model and pit and pipe data bases that you require, and then use the File -> Import -> Mapinfo MIF files option, which will display the following message: 15

17 After "Yes" is entered, you must select one of the MapInfo MIF files to be transferred. The transfer will then take place, and the pits and pipes will come into view. As the window below shows, the data information is transferred over, and further data can be added to the property sheets. 16

18 With this setup it is possible to import a new or additional background. Using the File -> Import -> Import DXF background option brings up a dialog box from which a DXF file can be opened. When a file is selected, the following window appears: When a choice is made, the background is replaced. 17

19 7. EXPORTING MAPINFO FILES It is first necessary to establish a system that is capable of being run, such as the demo example shown below: Selecting the MapInfo files option from the File -> Export menu presents the following message: 18

20 If you continue, you will then need to nominate a filename for MID/MIF files in the following dialog box: You can see from the existing files in this example how six MapInfo MIF files are created. Another six MID files are also created. If a background is present a DXF file will also be created. After a name is entered, the process is complete if there are no results. If results are available, the following dialog box appears: A suitable name should be added describing the results; here they are for a 2 year average recurrence interval storm. The limited size is due to restrictions on the size of column headings in the database files used in MapInfo. After this is entered, the process is finished. If a background is present in the DRAINS model, this will be transferred with the MapInfo files. The transferred files can now be viewed in MapInfo: 19

21 Note that this includes results with the "2Yr" added to headings as a suffix. If another run is made and the process is repeated with one of the existing shapefiles nominated in the Save As dialog box, additional results will be appended, as shown below: 20

22 If data from a GIS data base can be assembled into this same format, less the results, the File Import option ESRI Shapefiles can be used to import data into DRAINS. 21