TXPROS FIXMAP. Technical Description

Transcription

1 TXPROS FIXMAP Technical Description This technical and system overview provides detailed information for the Fixmap application. This application provides the means to maintain the base GIS data for the TxPROS system.

2 Copyright Notice This document (written or otherwise displayed on electronic media or other medium) contains confidential and proprietary information of ProMiles Software Development Corporation, its affiliates, and the Texas Department of Transportation. It has been furnished only for informational purposes, and no license or permission is hereby granted to use such information in any manner. In no event may this information be reproduced, distributed and/or publicly displayed in any form or by any means without prior expressed written permission of TxDOT. Texas Department of Transportation. All rights reserved. WHAT S NEW? i

3 Table of Contents CHAPTER 1 INSTALLATION AND LAUNCH... 1 PURPOSE 1 TECHNICAL ENVIRONMENT SPECIFICATION 1 Configuration Settings... 2 Database Server Requirements... 2 Application Server Requirements... 2 Workstation/Client Requirements... 2 Licensing Requirements... 3 INSTALLING FIXMAP 3 LAUNCHING FIXMAP 3 CHAPTER 2 MANIFEST... 4 FILES 4 DATABASE CONNECTIONS 4 OTHER ITEMS 4 CHAPTER 3 SYSTEM DIAGRAMS... 5 HIGH-LEVEL OVERVIEW 5 System and Network Overview... 5 Steps described in the TxPROS Fixmap Network Environment Overview:... 5 Application Overview... 6 Steps described in the TxPROS Fixmap Overview:... 6 COMPONENTS 7 DATA MODEL 7 DATA DESIGN 12 FIXMAP UPDATE FILE UPLOAD PROGRAM 13 BUILDING BLOCK FILES 14 CHAPTER 4 BUSINESS RULES CHAPTER 5 TROUBLESHOOTING TIPS CONTACT LIST 16 TROUBLESHOOTING 17 Installation Issues Problem: Program does not run Problem: Unable to connect to the GIS database CHAPTER 6 DEVELOPMENT ENVIRONMENT DEVELOPMENT ENVIRONMENT SPECIFICATION 18 GLOSSARY UPDATE HISTORY INDEX SIGNATURE PAGE ii

4 Table of Tables Table 1: Technical Environment Specification... 1 Table 2: Database Servers Specification... 1 Table 3: Database Server Requirements... 2 Table 4: Workstation/Client Requirements... 2 Table 5: Fixmap Files... 4 Table 6: File Layout for Fixmap Block Files... 8 Table 7: File Layout for Fixmap LCF.bin File... 8 Table 8: File Layout for Fixmap Counties.bin File... 9 Table 9: County Record Layout for Fixmap Counties.bin File... 9 Table 10: Polygon Record Layout for Fixmap Counties.bin File Table 11: Record Layout for Fixmap Update Files Table 12: Albers Equal Area Projection Parameters Table 13: Minimum/Maximum X/Y Values for Texas Table 14: Development Environment Specification iii

5 Table of Figures Figure 1: TxPros Fixmap Network Environment... 5 Figure 2: Fixmap Overview... 6 iv

6 CHAPTER 1 INSTALLATION AND LAUNCH PURPOSE This document provides technical details for the Fixmap application and its data files. This will cover installing and launching the application, provide an overview of the process for loading updates from the Fixmap application into the GIS database, and creating new data files for further revisions. File layouts for the data files used by the application are provided. Fixmap is a desktop application that allows users to edit the TxPROS base GIS data. TECHNICAL ENVIRONMENT SPECIFICATION TABLE 1: TECHNICAL ENVIRONMENT SPECIFICATION Elements Details Work Station Platform Server Platform Application Type Protocol Network Environment: IP Address or Server MS Windows XP R2 or later N/A Windows 32 bit executable Oracle TCP/IP, ASCII files Database Servers: TABLE 2: DATABASE SERVERS SPECIFICATION Server Name IP Address TXPROS DB See the TxPROS System Architecture Technical Description document for additional network environment information. Hardware Requirements 2GB ram, 10GB available hard drive space, 1.5 GHZ processor 1 core, VGA 1

7 Chapter 1 Installation and Launch CONFIGURATION SETTINGS N/A DATABASE SERVER REQUIREMENTS TABLE 3: DATABASE SERVER REQUIREMENTS Requirement How Is This Requirement Met? Platform Domain Operating System Database Version Server Installation RAM Hard drive space Processors Oracle N/A Windows Server 2008 R2 10g See the TxPROS System Architecture Technical Description document 16 GB 1 TB 2.5 GHZ, 8 core or more APPLICATION SERVER REQUIREMENTS N/A WORKSTATION/CLIENT REQUIREMENTS TABLE 4: WORKSTATION/CLIENT REQUIREMENTS Workstation Client System Description Operating System RAM Hard drive space Oracle client Processor Video card MS Windows XP or higher 2GB or more 10GB or more See TxPROS Software Current Release Notes document for current version 1.5 GHZ, 1 core VGA 2

8 Chapter 1 Installation and Launch LICENSING REQUIREMENTS N/A INSTALLING FIXMAP 1. Install the current Oracle client. (See TxPROS Software Current Release Notes document for current version). These files can be found at ftp:// Run Fixmap install program See the Fixmap User Guide for details. (See TxPROS Software Current Release Notes document for current version). LAUNCHING FIXMAP 1. Double click on Fixmap icon See the Fixmap User Guide for details. 3

9 CHAPTER 2 MANIFEST FILES All files listed below are in the root Fixmap folder as it is installed. Any files found in sub folders will have the relative path to the files from this base folder. TABLE 5: FIXMAP FILES Files Description Fixmap.exe Allroad\Block x.bin OnSysOnly\Block x.bin Rhinobin\Block x.bin Counties.bin Interop.PROJ4VBLib.dll LCF.bin NewRoads.txt RoadbedName.txt TxDot_Districts.dbf TxDot_Districts.shp Fixmap.config Fixmap application All roads block files (324 files) On system block files (322 files) Rhino block files (320 files) File containing outlines of counties Program component used to project points Road segment lookup file File containing road segment numbers for new roads File with roadbed changes Shape file with TxDOT district boundaries Shape file with TxDOT district boundaries XML configuration file for Fixmap DATABASE CONNECTIONS The Fixmap application maintains a connection to the GIS Database in the TxPROS Database Server. This connection is configured within the program. OTHER ITEMS N/A 4

10 CHAPTER 3 SYSTEM DIAGRAMS HIGH LEVEL OVERVIEW SYSTEM AND NETWORK OVERVIEW FIGURE 1: TXPROS FIXMAP NETWORK ENVIRONMENT STEPS DESCRIBED IN THE TXPROS FIXMAP NETWORK ENVIRONMENT OVERVIEW: 1. Using the GIS database server, the install build programs create a new version of the Fixmap application. 2. Map coordinators download the new version and install on their computer. 3. Map coordinators add and correct GIS attributes using the Fixmap application. 4. The Fixmap application creates Fixmap files with these changes. 5. Map coordinators the Fixmap files to ProMiles. 6. ProMiles GIS specialists load the Fixmap files into the database and add geometry changes which are also loaded into the GIS database. 5

11 Chapter 3 System Diagrams APPLICATION OVERVIEW FIGURE 2: FIXMAP OVERVIEW STEPS DESCRIBED IN THE TXPROS FIXMAP OVERVIEW: 1. Using the GIS database server, new block and look files are created and the install build programs create a new version of the Fixmap application. 2. The Fixmap application accesses block files and lookup files to provide maps to the users. 3. The Fixmap application creates Fixmap files with these changes. 4. Map coordinators the Fixmap files to ProMiles. 5. ProMiles GIS specialists load the Fixmap files into the database and add geometry changes which are also loaded into the GIS database. 6

12 Chapter 3 System Diagrams COMPONENTS The following are the components: Fixmap program o Block files o Rhino block files o Fixmap update files Fixmap update file upload program Database Block file build program DATA MODEL The Fixmap program uses the GIS database to store the GIS data. A data model of this database can be found in the Database Design Document Entities and Attributes. In addition to the GIS database, the Fixmap program uses the following files: Block Files Road number lookup file New roads file Counties file TxDOT district file Fixmap update file Block files are used to store the GIS data used displayed by the Fixmap program. There are three sets of block files: On system only All roads Rhino The block files are separated for performance reasons. Most Fixmap work is performed looking at only TxDOT maintained roads. This data is stored in the On system only block files. When a user wishes to look at all roads, the system loads the All roads block files. The all roads block files include TxDOT maintained roads and are approximately 6 times larger than the On system only block files. The block files are stored in binary files in the following format: Block X.bin where the X represents the 4 or 5 digit block. 7

13 Chapter 3 System Diagrams The block numbering is described on page 13. The block files are binary files with the following general format: TABLE 6: FILE LAYOUT FOR FIXMAP BLOCK FILES Bytes Description byte segment count for block 5 N 1 Data for road segment 1 N N 2 Data for road segment 2 N n N n Data for road segment n The data for the road segments are saved in a variable length binary format based on field type using the.net binary reader. The list of the fields can be found in the ByteArrayToBlock and BlockToByteArray functions in the Fixmap program. The Rhino block files contain TxDOT certified roadbed data as made available to the TxPROS project. This data is created during the migration process and provides reference information for modifying the TxPROS GIS data. The road number lookup file (LCF.bin) is a binary file that identifies the latitude and longitude of the center point for each road segments based on their Fixmap segment ID. This lat/lon allows Fixmap users to quickly go to a road segment by its ID. The following table describes the LCF.bin file: TABLE 7: FILE LAYOUT FOR FIXMAP LCF.BIN FILE Bytes Description 1 4 X value for road segment 1 N * N *8 X value for road segment 2 N N + 3 X value for high road segment N + 4 N +7 Y value for road segment 1 M m + 3 Y value for high road segment 8

14 Chapter 3 System Diagrams The x and y values are calculated as described on page 12 and are the x and y values for the first point in each road segment. The New Roads file (NewRoads.txt) is a text file that has the TxPROS road segment IDs for each new road segment in the latest migration. This file is used to identify road segments that need to be reviewed during a migration. The road segment numbers are listed one to a line. The county file (counties.bin) is a binary file that Fixmap uses to draw county lines on the map. The following table describes the counties.bin file: TABLE 8: FILE LAYOUT FOR FIXMAP COUNTIES.BIN FILE Bytes Description 1 4 Record count 5 N 1 County record 1 M P County record n The following table describes the layout of the county records in the counties.bin file: TABLE 9: COUNTY RECORD LAYOUT FOR FIXMAP COUNTIES.BIN FILE Bytes Description 1 4 Length of county name N County name 4 Padding 4 Number of polygons for county 4 Padding N 1 Polygon 1 record N n Polygon n record 9

15 Chapter 3 System Diagrams The following table describes the layout of the polygon records in the counties.bin file: TABLE 10: POLYGON RECORD LAYOUT FOR FIXMAP COUNTIES.BIN FILE Bytes Description 8 Padding 4 Point count 4 X value for point 1 4 X value for point n 10 Padding 4 Y value for point 1 4 Y value for point n The TxDOT district files (TxDot_Districts.shp, TxDot_Districts.dbf) are standard shape files with outlines of the districts. These files were provided by TxDOT. 10

16 Chapter 3 System Diagrams Fixmap update files (RoadbedUpdate.txt) are text files created by the Fixmap program that have updated roadbed data. These are text files that use the tab character as a delimiter. The following table describes the layout of the Fixmap update files: TABLE 11: RECORD LAYOUT FOR FIXMAP UPDATE FILES Field Description 1 TxPROS road segment ID 2 Action: Literal On system flag FRTGRD Loop ClearAllSecond AddSecond ClearSecond Roadbed name Description Sets or clears the on system flag Sets the frontage road type Sets the loop direction Clears all additional roadbed names Adds additional roadbed name Clears an additional roadbed name Sets primary roadbed name 3 Attribute: Roadbed name, roadbed type, frontage road type, loop direction, Onsystem Flag 11

17 Chapter 3 System Diagrams DATA DESIGN The Fixmap program is designed to allow map coordinators and other users to quickly add and correct GIS data in the TxPROS GIS database. In order to efficiently perform these actions, fast map redraws is essential. Fixmap uses three techniques to facilitate this fast redraw capability: 1. All points are projected onto the Cartesian plane and are recorded and drawn using projected x and y values instead of the latitude and longitude. 2. The GIS data is divided into geographic blocks. Each block is stored in a separate file and loaded on demand. 3. The GIS data is separated into 2 layers: On system only, and all roads. Each layer is stored in separate blocks. The TxPROS system uses the Albers Equal Area projection method with the following parameters: TABLE 12: ALBERS EQUAL AREA PROJECTION PARAMETERS Parameter Value Longitude Origin 96 Latitude Origin 23 Standard Parallel Standard Parallel Spheroid GRS80/WGS84 12

18 Chapter 3 System Diagrams This projection method produces a pleasing map with very minor distortion for the State of Texas. This projection method also guarantees that distances in the projected plane vary by less than 1% with distances on the surface of the Earth. All points in the system are converted from lat/lon coordinates to x, y coordinates measured in meters. The x, y coordinate ranges for the State of Texas are as follows: TABLE 13: MINIMUM/MAXIMUM X/Y VALUES FOR TEXAS Parameter Value Min x 999,000 Max x 236,000 Min y 313,000 Max y 1,517,000 Using the x, y coordinates derived from the projection method, the GIS data is divided into square blocks 25 kilometers on a side. The block numbers are derived using the following formula: i = (x ) / j = (y ) / Block number = i + (j * 200) Each road segment is assigned to a block using this formula for the first point in the road segment. FIXMAP UPDATE FILE UPLOAD PROGRAM The Fixmap update file upload program is a Windows application that uploads the Fixmap update files into the database. This program can be copied onto and run on any computer with the correct Oracle client installed. 13

19 Chapter 3 System Diagrams BUILDING BLOCK FILES The Fixmap program will also build block files. To configure the Fixmap program to create block files, add the following section to the Fixmap.config file: <usersettings> <Fixmap.Properties.Settings> <setting name="buildblockfile" serializeas="string"> <value>true</value> </setting> </Fixmap.Properties.Settings> </usersettings> This instance of Fixmap must have the Oracle client installed and must have a fast connection to the database. Building block files currently takes about 2 hours. 14

20 CHAPTER 4 BUSINESS RULES This section describes the business rules related to using each screen and/or component in this application. N/A 15

21 CHAPTER 5 TROUBLESHOOTING TIPS CONTACT LIST The following table details specific contact information for application support, including support for additional required or optional applications. These are the individuals contacted when a TxDOT staff member has a technical issue with the application. Responsibility Contact Phone Cell Phone Project Manager Tim Pilcher tim@promiles.com Assistant Project Manager Mike Webb mike@promiles.com PSDC Network Support Eddie Moore ext 232 eddie@promiles.com Support Michelle Hudson ext 235 michelle@promiles.com Support Support Support Brian Murphy brianm@promiles.com Brian Fuller brian@promiles.com Tony Stroncheck tony@promiles.com

22 Chapter 5 Troubleshooting Tips TROUBLESHOOTING INSTALLATION ISSUES PROBLEM: PROGRAM DOES NOT RUN Cause: 1. Incorrect or corrupted installation Resolutions: 1. Reinstall program PROBLEM: UNABLE TO CONNECT TO THE GIS DATABASE Cause: 1. Oracle client incorrectly installed 2. No access to database 3. Database problems Resolutions: 1. Install or reinstall correct Oracle client 2. Insure access to database server using standard network connectivity tools 3. Insure GIS database operating correctly using standard database diagnostic tools 17

23 CHAPTER 6 DEVELOPMENT ENVIRONMENT DEVELOPMENT ENVIRONMENT SPECIFICATION TABLE 14: DEVELOPMENT ENVIRONMENT SPECIFICATION Elements Details Work Station Platform Server Platform Application Type Development Environment Database Environment Windows XP R2 or higher N/A Microsoft VB.NET application Microsoft Visual Studio 2010, WFC 3.5 Oracle 10g 18

24 GLOSSARY Terms Albers equal area projection On system road Rhino data WFC Definitions Conic projection that does a good job of projecting rectangular areas with minimal distortion between 2 standard parallels. Often used by the United State Geological Survey for projecting large states with similar latitude and longitude distances. Road segment representing part of the TxDOT maintained highway network or a section of road used in the routing of OS/OW loads in the normal course of business. TxDOT roadbed data provided to the project consisting of roadbed geometry, roadbed name and roadbed type. Windows Foundation Classes is a collection of.net classes that assists developers by providing them with many standard programming functions. WFC is part of the Microsoft s Visual Studio development environment. 19

25 UPDATE HISTORY The revision history shows the changes of this document as subsequent versions are released. Version Date Name Description /24/2011 Tim Pilcher, Michelle Hudson /13/2011 Tim Pilcher, Michelle Hudson /14/2011 Tim Pilcher, Michelle Hudson Created as part of Deliverable for MS12. Submitted with feedback from MCD as part of Deliverable for MS12. Submitted with feedback from MCD dated 7/27/11 and meetings at MCD 8/9/11 as part of Deliverable for MS12. 20

26 INDEX No index entries found. 21

27 TxPROS Fixmap Technical Description SIGNATURE PAGE Tim Pilcher, Project Manager Date Michelle Hudson, Document Manager Date TXDOT Reviewers/Approvers By signing below, you signify that you have reviewed this document and approve the project to move forward to the next phase. Lois Johnson, Technical Project Contract Admin. Date Ray Hutchinson, MCD Business Area Project Manager Date 22