Enhancing GDOT's computerized pavement condition evaluation system for pavement condition survey

GEORGIA DOT RESEARCH PROJECT 16-29 FINAL REPORT
ENHANCING GDOT'S COMPUTERIZED PAVEMENT CONDITION EVALUATION SYSTEM FOR PAVEMENT
CONDITION SURVEY
OFFICE OF RESEARCH 15 KENNDY DRIVE
FOREST PARK, GA 30297-2534

1.Report No.: FHWA-GA-17-1629

2. Government Accession 3. Recipient's Catalog No.: No.:

4. Title and Subtitle: Enhancing GDOT's Computerized Pavement Condition Evaluation System for Pavement Condition Survey
7. Author(s): Yichang (James) Tsai; Zhaohua Wang

5. Report Date: September 2017
6. Performing Organization Code: 8. Performing Organ. Report No.:
RP 16-29

9. Performing Organization Name and Address: Georgia Institute of Technology 790 Atlantic Drive Atlanta, GA 30332-0355

10. Work Unit No.:
11. Contract or Grant No.: PI# 0012795

12. Sponsoring Agency Name and Address: Georgia Department of Transportation Office of Research 15 Kennedy Drive Forest Park, GA 30297-2534

13. Type of Report and Period Covered: Final; September 19, 2016 December 19, 2017
14. Sponsoring Agency Code:

15. Supplementary Notes: Prepared in cooperation with the U.S. Department of Transportation, Federal Highway Administration.
16. Abstract: The Computerized Pavement Condition Evaluation System (COPACES) is a software tool that has been used by the Georgia Department of Transportation (GDOT) for its statewide pavement condition survey since the late 1990s. The previous version was released in 2008, which ran on Windows XP laptops. To improve the productivity, this project developed a new version of COPACES (named COPACES for Tablet) that runs on tablet computers with Windows 8.1 or Windows 10 and fully utilizes the convenience of finger-touch-based operations. Because a tablet computer is not available for everyone at the current stage, the previous version of COPACES (named COPACES for Laptop) was upgraded to be compatible with the newer operating systems, i.e., Windows 7, 8.1, and 10. Two other programs, COPADQA and Upload, which are used for data quality checking and data uploading, were also upgraded to be compatible with the newer operating systems. To further improve the quality of field-collected data, several historical-data-based quality checking criteria were developed based on discussions with GDOT's pavement maintenance engineers and have been implemented in both COPACES for Tablet and COPACES for Laptop. The developed programs have been successfully implemented in GDOT to collect the COPACES data for the fiscal year 2017. Future development and further implementation considerations are discussed and recommended.

17. Key Words: COPACES; Tablet Computer; Pavement Condition Data

18. Distribution Statement: No Restriction

19. Security Classification (of this report): 20. Security classification (of 21. Number 22. Price:

Unclassified

this page): Unclassified

of Pages: 132

GDOT Research Project No. 16-29 Final Report
ENHANCING GDOT'S COMPUTERIZED PAVEMENT CONDITION EVALUATION SYSTEM FOR PAVEMENT CONDITION SURVEY
By Yichang (James) Tsai, Ph.D., P.E.
Zhaohua Wang, Ph.D., P.E.
Georgia Institute of Technology
Contract with Georgia Department of Transportation
In cooperation with
U.S. Department of Transportation Federal Highway Administration
December 2017
The contents of this report reflect the views of the author(s) who is (are) responsible for the facts and the accuracy of the data presented herein. The contents do not necessarily reflect the official views or policies of the Georgia Department of Transportation or of the Federal Highway Administration. This report does not constitute a standard, specification, or regulation.

TABLE OF CONTENTS

LIST OF TABLES

vi

LIST OF FIGURES

viii

ACRONYMS AND ABBREVIATIONS

xii

EXECUTIVE SUMMARY

xiv

ACKNOWLEDGEMENTS

xvi

Chapter 1 INTRODUCTION

1

1. Research Background and Research Need .......................................................................... 1

2. Research Objectives............................................................................................................. 3

3. Report Organization............................................................................................................. 6

References................................................................................................................................... 7

Chapter 2 COPACES FOR LAPTOP

9

1. System Architecture............................................................................................................. 9

2. Update of Route and RC Lookup Tables ........................................................................... 11

3. Operation Flow .................................................................................................................. 20

3.1 COPACES User Profile.................................................................................. 21

3.2 Project Information......................................................................................... 22

3.3 Pavement Condition Survey on Segments...................................................... 24

3.4 Error Checking ............................................................................................... 25

ii

3.5 Submission of Completed COPACES Database File..................................... 27

4. Automatic Software Update............................................................................................... 28

Chapter 3 COPACES FOR TABLET

33

1. System Design ................................................................................................................... 33

1.1 Main Functions ............................................................................................... 34

1.2 Internal Data Storage ...................................................................................... 34

2. Operations of COPACES for Tablet.................................................................................. 36

2.1 COPACES User Profile.................................................................................. 36

2.2 Functions on Main Page ................................................................................. 37

2.3 Creating New Project...................................................................................... 38

2.4 Creating New Segments ................................................................................. 41

2.5 Loading Data from Previous Year.................................................................. 45

2.6 Open Existing Project ..................................................................................... 46

2.7 Export Data..................................................................................................... 48

3. Converting Survey Data to Access Database..................................................................... 50

4. Enhanced Field Data Quality Checking............................................................................. 53

4.1 Quality Checking Criteria............................................................................... 54

4.2 Operations on Enhanced Data Quality Checking ........................................... 55

5. Automatic Software Update............................................................................................... 58

Chapter 4 CONCLUSIONS AND RECOMMENDATIONS

59

iii

Appendix I: List of state routes

1

Appendix II: User's Guide for Installing COPACES for tablet on Windows 8.1

41

Appendix II: User's Guide for Installing COPACES for tablet on Windows 10

45

iv

v

LIST OF TABLES
TABLE 2.1: List of Split Routes ...................................................................................... 12 TABLE 2.2: List of Routes in GAMS Only ..................................................................... 16 TABLE 2.3: List of Routes in GAMS Only ..................................................................... 17 TABLE 2.4: Data Dictionary of RC Lookup Table.......................................................... 18 TABLE 4.1: Summary of FY 2017 COPACES Data ....................................................... 60
vi

vii

LIST OF FIGURES
FIGURE 1.1: Major Programs for Pavement Management................................................ 2 FIGURE 2.1: System Architecture of Four Programs ...................................................... 10 FIGURE 2.2: State Route Cross Several Counties ........................................................... 12 FIGURE 2.3: Operation Flow of Using COPACES for Laptop ....................................... 21 FIGURE 2.4: COPACES User Profile.............................................................................. 22 FIGURE 2.5: Project Information..................................................................................... 23 FIGURE 2.6: Pavement Condition Survey on Segment ................................................... 24 FIGURE 2.7: Error Checking ........................................................................................... 26 FIGURE 2.8: Data Transfer Function............................................................................... 27 FIGURE 2.9: Confirmation on Data Completeness and Error Checking......................... 28 FIGURE 2.10: Previous Software Delivery Process ........................................................ 29 FIGURE 2.11: Software Delivery Process with Automatic Update................................. 31 FIGURE 3.1: Program Operation Diagram ...................................................................... 35 FIGURE 3.2: Internal Database File................................................................................. 36 FIGURE 3.3: COPACES User Profile.............................................................................. 37 FIGURE 3.4: Layout of Functions on Main Page ............................................................ 37
viii

FIGURE 3.5: Creating New Project Page......................................................................... 38 FIGURE 3.6: Project Location Information ..................................................................... 39 FIGURE 3.7: Road Information ....................................................................................... 40 FIGURE 3.8: Segment Survey Page................................................................................. 41 FIGURE 3.9: Segment Location Information................................................................... 42 FIGURE 3.10: Distress Survey Example for Load Cracking ........................................... 43 FIGURE 3.11: Distress Survey Example for Rutting....................................................... 44 FIGURE 3.12: Segment Navigation Bar .......................................................................... 45 FIGURE 3.13: Load Data Page ........................................................................................ 46 FIGURE 3.14: Open Existing Project Page ...................................................................... 47 FIGURE 3.15: List of Searched Projects .......................................................................... 48 FIGURE 3.16: Export Data Page...................................................................................... 49 FIGURE 3.17: Export Data List View.............................................................................. 50 FIGURE 3.18: Export Result Example............................................................................. 50 FIGURE 3.19: Menu Item for Importing Data from COPACES for Tablet .................... 51 FIGURE 3.20: Data Import Form ..................................................................................... 52 FIGURE 3.21: Selecting Source Data Folder ................................................................... 53
ix

FIGURE 3.22: Collected Data Fails at Quality Checking in COPACES for Tablet ........ 56 FIGURE 3.23: Quality Checking Function in COPACES for Laptop ............................. 57 FIGURE 3.24: Table of All Questionable Surveys .......................................................... 57 FIGURE 4.1: COPACES Training in Macon ................................................................... 61
x

xi

ACRONYMS AND ABBREVIATIONS

AADT COPACES CSV FY GAMS GDOT MR&R OIT OM OTD PACES RC

Annual average daily traffic Computerized Pavement Condition Evaluation System Comma-separated values Fiscal year Georgia Asset Management System Georgia Department of Transportation Maintenance, rehabilitation, and reconstruction Office of Information Technology Office of Maintenance Office of Transportation Data Pavement Condition Evaluation System Road characteristics

xii

xiii

EXECUTIVE SUMMARY
The Computerized Pavement Condition Evaluation System (COPACES) has been an indispensable tool for the Georgia Department of Transportation (GDOT) to annually collect pavement condition distress data. The COPACES data is used by GDOT to make informed decisions on statewide pavement maintenance, rehabilitation, and reconstruction (MR&R).
To improve the productivity of field data collection, this project developed a new program, COPACES for Tablet, that runs on tablet computers with Windows 8.1 or Windows 10 and fully utilizes their convenience of fingertouch-based operations. Also, the previous version of COPACES that was released in 2008 and ran on Windows XP was upgraded to be compatible with the newer operating systems, i.e., Windows 7, 8.1, and 10. Though it is out of the scope of this project, two other programs, COPADQA and Upload, were also upgraded to be compatible with the newer operating systems because GDOT needs them to check the district-level COPACES data quality and integrate it with the central COPACES database.
To be consistent with GDOT's GAMS (Georgia Asset Management System), the state route lookup table in COPACES has been comprehensively cleaned up and updated. Also, the road characteristics (RC) data in COPACES was updated using the most up-todate RC data provided by the Office of Information Technology.
To improve the efficiency of software installation and update, an approach to automatically updating programs, including COPACES for Tablet, COPACES for Laptop, COPADQA, and Upload, has been applied. The software setup packages are stored in
xiv

GDOT's web repository. Whenever an update is available, the software on a user's computer can be automatically updated. Data quality is of the most importance in a data-driven pavement management system. Thus, data quality checking has been rigorously implemented in the previous version of COPACES. However, the historical data was not utilized for that purpose. In this project, several historical-data-based quality checking criteria were developed based on the discussions with GDOT's pavement maintenance engineers. These criteria were implemented in both COPACES for Tablet and COPACES for Laptop to enhance the field-collected data quality. Thus, the accuracy of the decision-making on pavement MR&R could also be improved. The developed programs have been successfully implemented in GDOT to collect the COPACES data for the fiscal year 2017. GDOT has used the data to select statewide pavement maintenance projects and allocate funding. Finally, future development and further implementation considerations are discussed and recommended.
xv

ACKNOWLEDGEMENTS
The work described in this final report was supported by the Georgia Department of Transportation (GDOT) research project 16-29. We would like to thank Ms. Ernay Robinson, Mr. Larry Barnes, Mr. David Sparks, Mr. Sam Wheeler, and Mr. Michael Keene from the Office of Maintenance; Mr. Teague Buchanan, Mr. Donald Jordan, and Mr. Keith Dickie from the Office of Information Technology; and Mr. David Jared and Mr. Binh Bui from the Office of Research for their strong support and heavy involvement. We would like to thank members of the research team at the Georgia Institute of Technology for their diligent work.
xvi

xvii

CHAPTER 1 INTRODUCTION
1. Research Background and Research Need
The Computerized Pavement Condition Evaluation System (COPACES) and other relative software tools have been used by the Georgia Department of Transportation (GDOT) to conduct pavement condition survey, and manage and maintain its statewide asphalt pavements since the late 1990s (RP 05-19: Tsai, et al. 2009; Tsai & Lai, 2001; Tsai & Lai, 2002; Tsai, et al. 2008). It consists of three major components, including data acquisition, data management, and decision support. FIGURE 1.1 shows the programs to implement these three components.
As shown in FIGURE 1.1, COPACES is a laptop-based computer program used by the Office of Maintenance (OM) in GDOT to conduct the statewide asphalt pavement condition survey in accordance with GDOT's Pavement Condition Evaluation System (PACES) manual (GDOT, 2007), which is the impetus for the following data management and decision support.
The previous version of COPACES (released in 2008) ran on a laptop with Windows XP. To improve the productivity, OM has adopted tablet computers to gradually replace laptops. More importantly, the previous version of COPACES was developed using Microsoft Visual Basic 6.0, which has become obsolete and abandoned by Microsoft. The supported operating system, Windows XP, was also obsolete. As a result, the previous version of COPACES has some compatibility issues with the newer Windows operating systems, e.g., Windows 7, Windows 8.1, and Windows 10. Thus, there was a
1

need to upgrade the previous COPACES by re-writing it with the most up-to-date programming language. Through the discussion with GDOT, Microsoft C# was adopted to develop the new version of COPACES. In addition, to fully utilize the convenience of tablet computers, e.g. Microsoft Surface, a new version of COPACES needed to be developed by using touch-based input instead of mouse and keyboard.
FIGURE 1.1: Major Programs for Pavement Management Data quality is of the most concern in COPACES because it supports data-driven pavement maintenance decision-making (Tsai, et al. 2008). A systematic procedure for
2

checking COPACES data quality has been identified by GDOT pavement maintenance engineers to improve the quality of COAPCES data. Thus, there is a need to further enhance the data quality checking capability for field data collection using COPACES.
2. Research Objectives
The objective of this proposed project is to enhance GDOT's COPACES 1) to take full advantage of tablet computers for more productive data input and 2) to implement more rigorous in-field data quality checking.
The following are the originally proposed tasks:
1) Enhance COPACES by developing a tablet-based application; 2) Develop training materials and conducting training; 3) Enhance the field data quality checking for COPACES; 4) Summarize research findings and developing a final report.
Because OM started collecting COPACES data for the fiscal year (FY) 2017, the Georgia Tech research team closely worked with the OM Liaison Engineers (who oversee the statewide pavement condition survey and provide technical assistance to district and area engineers) and other district engineers to facilitate the data collection using the new version of COPACES. For this purpose, the following new tasks were added, though they are out of the scope of the original task orders:
1) A tablet-based application using finger-touch as the main input method is called a Windows Store App on Windows 8.1 or Windows 10. It is designed as a mobile application that directly communicates with online services. For safety concerns,
3

the Windows Store App has limited capability to access local files stored on hard drives. It cannot directly generate Microsoft Access database files as the previous version of COPACES could do. As shown in FIGURE 1.1, the output from COPACES will be used by COPADQA for district-level quality checking. Thus, a mechanism is needed to convert the output from the tablet-based COPACES to Microsoft Access database files. In addition, when OM started FY 2017 data collection, not everyone had a tablet computer running on Windows 8.1 or Windows 10. Instead, most of them were still using laptop computers running on Windows 7. Thus, they must use laptop-based COPACES. As mentioned above, the previous version of COPACES has some compatibility issues with Windows 7. It must be rewritten using the new programming language, Microsoft C#. Thus, two versions of COPACES (COPACES for Tablet and COPACES for Laptop) were developed in this project. COPACES for Tablet focuses on field data collection if a tablet computer is available. In the new version of COPACES for Laptop, some new functions were added to convert the output from COPACES for Tablet to Microsoft Access database files. 2) As shown in FIGURE 1.1, after COPACES data is collected, two other programs, COPADQA (COPACES Data Quality Assurance Program) and Upload, are needed before the data can be transferred and integrated into the central database to support the statewide project selection and funding allocation. COPADQA is responsible for performing district-level quality checking of the COPACES data collected by area offices in each working district. It will also combine all the data collected in each working district for uploading to the central database. The
4

Upload program is for uploading the collected COPACES data into the central database. Since the previous versions (released in 2008) of these two programs were also developed using Microsoft Visual Basic 6.0, they needed to be rewritten using the most up-to-date programming language, Microsoft C#. To facilitate OM's ability to complete the FY 2017 COPACES data collection, the Georgia Tech research team performed the system upgrade for COPADQA and Upload, even though doing so was not in the original task orders. 3) A COPACES survey is conducted on projects that are defined by RCLINK, along with starting and ending milepoints. During the project development, the Office of Information Technology (OIT) requested the routes in COPACES comply with the ones defined in GDOT's GAMS (Georgia Asset Management System); thus, the COPACES data can be conveniently migrated to the GAMS database. The Georgia Tech research team closely worked with OIT to acquire the most up-todate projects from GAMS and converted them to the new version of COPACES, COPADQA and Upload. 4) In COPACES, a user needs to input road characteristics (RC) data for each project, such as AADT, truck percent, etc. However, most of the RC data is difficult to extract in field. To solve this issue, a lookup table that contains the RC data for each predefined route is embedded in the COPACES program. . The RC data is currently collected and maintained by the Office of Transportation Data (OTD) in GDOT. In this project, the Georgia Tech research team acquired the most up-todate RC data from OIT and converted it to a COPACES lookup table.
5

5) When OM started to use the new version of COPACES (both laptop and tablet versions) to conduct FY 2017 data collection, it was found that the previous software distribution process in GDOT was inefficient when problems were encountered. In the previous software distribution process, when a user in an area office encountered a problem, he reported it to the district engineer. Then, the district engineer reported it to a Liaison Engineer, and then to the Georgia Tech research team. After the problem was solved, a new setup package would be developed and submitted to OM. OM would send the software to OIT and then to each working district. The IT personnel in each working district would perform the software update for each user in area offices. This process was very timeconsuming. More importantly, some users might forget to update the software, which caused the problem of some of the versions of same software not being consistent among different users. To solve this issue and make it more efficient for OM to conduct the FY 2017 data collection, a new software distribution and update mechanism were developed in which software setup packages are centrally stored on OIT's server. When any update is available, the software on a user's computer will be automatically updated.
3. Report Organization
This report is organized into four chapters. Chapter 1 introduces the project background, need, objective, and tasks. Chapter 2 introduces the COPACES for Laptop program. Chapter 3 presents the COPACES for Tablet program. Chapter 4 summarizes the project
6

implementation and offers recommendations for future development and further implementation.
References
GDOT. "Pavement Condition Evaluation System." Georgia Department of Transportation, 2007.
Tsai, Y. and J. S Lai. "Utilization of Information Technology to Enhance Asphalt Pavement Condition Evaluation Program." The International Journal of Pavement Engineering, Vol. 2(1), pp.17-32, 2001.
Tsai, Y. and J. S. Lai. "A Framework and Strategy for Implementing An IT-based Pavement Management System." Transportation Research Record: Journal of Transportation Research Board, No. 1816, TRB, National Research Council, Washington, D.C., 2002, pp. 56-64, 2002.
Tsai, Y., Wang, Z., and Purcell, R. "Improving GDOT's Highway Pavement Preservation", Final Report, Georgia Department of Transportation, 2009.
Tsai, Y., Wu, Y., and Pitts, E. "Improving GDOT's Annual Preventive Maintenance Using a Collaborative Decision Support System." 7th International Conference on Managing Pavement Assets, 2008
7

8

CHAPTER 2 COPACES FOR LAPTOP
This chapter presents the development of COPACES for Laptop. The major functions of this program are the same as the previous version of COPACES that was released in 2008. However, the entire program was rewritten using the new programming language, Microsoft C#. Some new functions were added to convert the output from COPACES for Tablet to Microsoft Access database files that can be used by COPADQA. The development of COPACES for Tablet will be presented in Chapter 3. In addition, the embedded lookup tables for all state routes were updated to comply with GDOT's GAMS. RC data was also updated using the most up-to-date data provided by OIT.
1. System Architecture
In this project, four programs were developed: COPACES for Laptop, COPACES for Tablet, COPADQA, and Upload. To reduce the resource use for system development, this project did not change the entire system architecture, as shown in FIGURE 1.1. Instead, only the previous COPACES program was replaced by COPACES for Laptop and COPACES for Tablet to make it convenient for both Windows 7 users using laptops and Windows 8.1/Windows 10 users using tablet computers. COPADQA and Upload have the same functions as the previous versions that were released in 2008, but they were rewritten using C# to be compatible with Windows 7 or newer Windows operating systems. FIGURE 2.1 shows the relationship and information flow of these four programs.
9

As shown in FIGURE 2.1, Windows 7 users who use laptops can only use COPACES for Laptop to collect data in the field. For Windows 8.1/10 users who use tablet computers, both COPACES for Laptop and COPACES for Tablet are needed. In the field, COPACES for Tablet is used for data collection. After that, the output from COPACES for Tablet will be converted to Microsoft Access database files using functions in COPACES for Laptop. The Access database files created by COPACES for Laptop will be fed into COPADQA for district-level quality checking and combining. Finally, the output from COPADQA will be uploaded to the central COPACES database using the Upload program.
Windows 7 Users using Laptops
Windows 8.1/10 Users using Tablet Computers
FIGURE 2.1: System Architecture of Four Programs The following sections in this chapter introduce the new state route lookup table, the major functions, and operation flow of COPACES for Laptop.
10

2. Update of Route and RC Lookup Tables
During the project development, OIT in GDOT requested that the state routes in COPACES should be consistent with the ones defined in GDOT's GAMS; thus, COPACES data can be conveniently migrated to GAMS. After several meetings with OIT, the Georgia Tech research team acquired the list of all the state routes defined by RCLINK and milepoints.
The lookup table of all the state routes is important to make sure the spatial definition of each COPACES project is consistent over time. In the central COPACES database, there exists data back to FY 1986. Thus, after discussion with OM engineers, it was decided to create a list of state routes that contains both the original routes and the updated routes from GAMS (the complete list of state routes can be found in Appendix I). For this purpose, a careful comparison between the existing and new state routes was performed. The following differences were identified:
1) In the existing list of state routes, each route is identified by a single RCLINK, along with starting and ending milepoints. When a route goes out of a county and back to the same county, the route is not split even if some portion of the route has different RCLINK data. In contrast, a route will be split into two or more routes if it goes out of and back to the same county in GAMS. As illustrated in FIGURE 2.2, a route in County 1 goes to County 2, as indicated in red, then back to County 1. Because RCLINK changes when the county changes, the red portion of this route has a different RCLINK. However, in the existing COPACES state route lookup table, this route is defined as the RCLINK in County 1 along with
11

MP-1 and MP-4 as the starting and ending milepoint, respectively. The rater will add the red portion of this route to the same project with different RCLINK data, along with MP-2 and MP-3. In GAMS, this route is split into two routes, as shown in FIGURE 2.2. If a route goes out of and back to the same county several times, it will be split into more than two pieces. TABLE 2.1 lists all routes that are split in GAMS.

MP-4

County 1

MP-2

MP-3 County 2

MP-1

Existing COPACES Starting: MP-1 Ending: MP-4
GAMS Route 1 Starting: MP-1 Ending: MP-2 Route 2 Starting: MP-3 Starting: MP-4

FIGURE 2.2: State Route Cross Several Counties

TABLE 2.1: List of Split Routes

CountyNo 047 243 259 295
123 213

RouteNo 0001 0001 0001 0001
0002 0002

RouteSuffix 00 00 00 00
00 00

Existing COPACES

MilepostFrom MilepostTo

0

9.99

0

22.85

0

23.15

0

31.03

0

26.24

0

32.73

GAMS LRS

MilepostFrom MilepostTo

0

1.36

8.23

9.65

0

22.72

23.22

23.34

0

0.54

0.62

23.12

20.46

27.33

0

19.1

28.75

30.64

0.89

26.25

0.57

0.75

32.63

32.73

32.08

32.48

12

CountyNo 249 121 121 119 147 145 001 161 107 167 037 061 037 243 089 175 309 019 173 121

RouteNo 0003 0006 0014 0017 0017 0018 0019 0019 0026 0026 0037 0037 0041 0041 0042 0046 0046 0064 0064 0070

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Existing COPACES MilepostFrom MilepostTo

0

16.12

0

12.05

0

25.08

0

16.33

0

13.59

0

12.84

0

3.04

0

18.5

0

35.3

0

6.52

0

25.85

0

14.59

0

5.71

0

22.55

0

13.87

0

16.32

0

5.81

0

13.38

0

15.08

0

28.83

GAMS LRS

MilepostFrom MilepostTo

0

31.88

0.47

15.7

0

0.47

11.83

12.06

0

11.51

16.64

25.09

0

16.26

0

4.35

7.47

16.29

10.5

13.61

0

6.17

0

0.41

0.41

12.69

0

0.3

2.04

3.05

2.74

18.36

0

1.73

0

0.44

1.78

35.38

0

4.67

5.11

6.45

0

0.38

0.68

25.75

14.25

14.55

0

13.87

0

5.15

5.69

5.81

0.67

22.38

0

0.55

0

3.08

9.12

13.92

0

15.4

16

16.35

0

0.6

0.95

5.76

9.23

13.34

0

3.1

0

6.13

10.24

15

0

16.97

13

CountyNo 189 301 023 091 067
121 223 079 225 045 143 063 151 121 121 151 083
295

RouteNo 0080 0080 0087 0087 0092
0092 0092 0096 0096 0113 0113 0138 0138 0141 0154 0155 0157
0157

RouteSuffix 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
00

Existing COPACES MilepostFrom MilepostTo

0

1.76

0

25.06

0

15.01

0

29.13

0

29.99

0

74.69

0

18.56

0

3.92

0

14.98

0

17.37

0

5.39

0

12.56

0

10.79

0

21.04

0

33.68

0

23.85

0

20.04

0

33.35

GAMS LRS

MilepostFrom MilepostTo

22.63

33.47

0

0.87

0.92

1.69

24.13

24.87

0

23.27

1.76

15.15

0

0.87

0

27.31

28.18

29.07

28.56

29.63

6.57

14.01

0

2.12

69.88

74.87

0

14.2

13.89

18.35

0

11.77

3.45

4.19

0

2.75

1.44

15.07

0

0.7

0

13.44

17.07

17.25

3.81

5.37

0

3.63

0

10.56

11.78

12.66

0

1.19

1.98

10.75

0

2.32

15.61

21

17.13

36.28

0

9.9

0

19.16

21.01

23.83

20.27

20.34

16.36

20.05

0

1.52

31.47

33.28

12.62

27.5

31.19

31.4

14

CountyNo 091 107 167 299 083 295 199 159
217
197 263 137 311 061 243 107 197 063 121

RouteNo 0165 0171 0171 0177 0189 0189 0190 0212
0212
0240 0240 0255 0255 0266 0266 0297 0355 0403 0403

RouteSuffix 00 00 00 00 00 00 00 00
00
00 00 00 00 00 00 00 00 00 00

Existing COPACES MilepostFrom MilepostTo

0

29.48

0

10.4

0

13.4

0

18.64

0

15.15

0

13.34

0

7.95

0

22.97

0

16.71

0

18.44

0

3.12

0

14.16

0

15.68

0

7.02

0

11.27

0

14.66

0

17.7

0

1.36

0

31.27

GAMS LRS

MilepostFrom MilepostTo

0

11.1

0

26.71

27.99

29.42

9.65

10.43

0

9.53

0

0.12

0.9

13.33

0

4.27

6.88

18.57

0

2.22

2.75

15.03

0

0.52

12.81

13.43

0

3.66

7.78

8

1.71

22.93

0

0.5

0.7

1.15

15.46

15.66

16.11

16.67

0

14.96

0.64

18.54

0

0.17

0

2.55

2.73

3.2

10.17

14.12

0

4.48

9.98

15.68

0

5.54

0

6.62

6.92

7.58

0

0.3

0.97

11.63

0

0.76

6.43

14.69

2.17

17.67

0

1.37

0

1.36

1.79

2.03

0

13.39

15

CountyNo 121
177 273

RouteNo 0407
0520 0520

RouteSuffix 00
00 00

Existing COPACES MilepostFrom MilepostTo

0

62.66

0

7.35

0

23.83

GAMS LRS

MilepostFrom MilepostTo

14.75

15.17

15.41

31.16

60.62

62.66

53.03

54.69

0

13.22

20.82

26.71

1.38

6.7

0

0.61

0

22.43

23.04

23.81

2) After careful comparison, it was found that 19 routes from GAMS don't exist in the existing COPACES lookup table. In the meantime, 39 routes in the existing COPACES lookup table were not found in GAMS. To maintain the data consistency, all these routes are now added to COPACES for Laptop as well as the other three programs that will be presented in the following chapters. These two categories of routes are listed in TABLE 2.2 and TABLE 2.3, respectively. TABLE 2.2: List of Routes in GAMS Only

COUNTY 015 015 015 077 097 097 141 143 151 151 151 173 185 199

RouteNo 0003 0113 1000 0016 0008 0154 0016 0100 0920 0920 0921 0038 0007 0100

RouteSuffix CO CO 00 NO CO 00 WE SP CO WE CO WE SB SO

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 4.77 0.35 3.3 0.63 0.39 5.64 0.05 0.9 0.2 0.27 0.05 1.29 0.45 0.12

16

275

0035

CO

279

0015

EA

279

0029

EA

279

0030

WE

305

0038

WE

0

1.15

0

0.72

0

0.72

0

1.31

0

2.08

TABLE 2.3: List of Routes in GAMS Only

CountyNo 019 019 027 067 067 067 077 113 121 131 131 137 141 151 153 157 163 167 173 175 179 185 185 185 187 187 187 187 187 211 217 225 225

RouteNo 0076 0158 0033 0005 0120 0176 0016 0138 0014 0038 0262 0365 0016 0020 0329 0052 0004 0086 0037 0029 0119 0007 0031 0094 0009 0009 0052 0052 0060 0186 0036 0011 0127

RouteSuffix CO 00 00 SO LO 00 SO 00 SP SP 00 00 SO DU 00 00 BN 00 CO WE SO SO SO WE BU SO BU SO SB 00 SO 00 00 17

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1.73 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 0.11 5.43 3.06 0.81 8.61
14.95 0.63 1.13 2.42 0.85 7.53
17.91 0.09 0.05 0.99 4.63 0.1 1.67 0.04 0.11 2.93 0.45 0.48 0.73 1.21 0.06 1.21 0.06 0.06 0.65 0.39 0.1 0.52

CountyNo 235 245 269 273 275 301 319

RouteNo 0011 0056 0090 0041 0035 0223 0018

RouteSuffix EA SP CO 00 BU 00 SP

MilepostFrom 0 0 0 0 0 0 0

MilepostTo 0.28 6.58 0.07 2.4 5.51 0.7 0.65

Other than the state route data, the lookup table for RC data was also updated because the traffic data, i.e., AADT and truck percent, was outdated in the existing COPACES program. Working with OIT in GDOT, the Georgia Tech research team acquired all the up-to-date RC data, which was converted to the lookup table in COPACES. TABLE 2.4 lists the definition of each field in the RC lookup table in COPACES.

TABLE 2.4: Data Dictionary of RC Lookup Table

Column Name ID
District
RouteType
RouteNo RouteSuffix

Description

An automatic number starting from 1

A one-digit number indicating GDOT's construction district where the inventory

data is located.

1

1st District

2

2nd District

3

3rd District

4

4th District

5

5th District

6

6th District

7

7th District

It is a one-digit number. The following is the definition of each code.

Route Type

CODE

State Route

1

County Road

2

City Street

3

Ramp

6

Private Road

7

Public Road Non Accepted Road

8

Collector-Distributor

9

Four-digit number for each road. Example: SR 3 is 0003; CR 361 is 0361.

A two-digit number.

For State Route or County Road

00

(Numeric Zero Zero) None of the following

NO

NOrth

SO

SOuth

18

Column Name
RouteSequence Shoulder1 Surface1 Shoulder2 Shoulder3 Surface2 Shoulder4
SurfaceType1
SurfaceType2

Description

EA

EAst

WE

WEst

AL

ALternate

BY

BYpass

BU

BUsiness

SP

SPur

CO

COnnector

LO

LOop

TO

TOll

EA

EAst Spur

DU

DUal Mileage*

AD

Alternate Dual*

BD

BUsiness Dual*

BC

Bypass Connector*

CD

Connector Dual*

SD

Spur Dual*

BN

Business North

Not used; blank

For divided highway, it is the left shoulder width in feet in the direction of

inventory

For undivided highway, it is the left shoulder width in feet on the opposite

direction of inventory

For divided highway, it is the total width of travel lanes in feet in the direction of

inventory

For undivided highway, it is the total width of travel lanes in both directions of

inventory

For divided highway, it is the right shoulder width in feet in the direction of

inventory

For undivided highway, it is the right shoulder width in feet in the direction of

inventory

Only used for divided highway. It is the left shoulder width in feet on the opposite

direction of inventory

Only used for divided highway. It is the total width of travel lanes in feet on the

opposite direction of inventory

Only used for divided highway. It is the right shoulder width in feet on the

opposite direction of inventory

For divided highway, it is the surface type in the direction of inventory.

For undivided highway, it is the surface type in the both directions of inventory.

It is a single character defined as follows:

A

Unpaved Primitive Road

B

Unpaved unimproved road

C

Unpaved Graded and drained road

D

Unpaved Soil - surfaced road

E

Unpaved Gravel and Stone

F

Paved Bituminous surfaced treated

G

Paved Mixed bituminous pavement

I

Paved High Flexible

J

Paved High rigid

K

Paved Brick

L

Paved Block

N

Not Divided

Only used for divided highway, it is the surface type on the opposite direction of

inventory.

19

Column Name
AADT STAA
Truck CountyNo MilepostFrom MilepostTo
TL_R TL_L Field23 Field24 Field25 Field26 Field27

Description

It is a single character defined as follows:

A

Unpaved Primitive Road

B

Unpaved unimproved road

C

Unpaved Graded and drained road

D

Unpaved Soil - surfaced road

E

Unpaved Gravel and Stone

F

Paved Bituminous surfaced treated

G

Paved Mixed bituminous pavement

I

Paved High Flexible

J

Paved High rigid

K

Paved Brick

L

Paved Block

N

Not Divided

The current Average Annual Daily Traffic (AADT) for the route segment.

One character for designated truck route. The definitions are as follows:

A- Designated Access Routes for oversize trucks allowing single and twin

trailers.

B- Designated Access Routes for oversize trucks allowing single trailers

only.

C-

Designated Access Routes for oversize trucks routes allowing twin

trailers only.

D- All Interstate Routes.

E-

Designated Local truck route.

T-

Federally Designated National Network Truck Routes other than

Interstate

Calculated percentage of truck volume on the highway system

County FIPS Code (three digits)

The starting milepoint of inventory road segment

The ending milepoint of inventory road segment

Number of Lanes in the direction of Inventory

Number of Lanes on the opposite direction of inventory

Reserved; blank

Reserved; blank

Reserved; blank

Reserved; blank

Reserved; blank

3. Operation Flow
In this subsection, the system's operational flow and some major functions are presented. FIGURE 2.3 lists the major steps for operating COPACES for Laptop for Windows 7 users. The introduction of the data conversion from COPACES for Tablet will be presented in the next chapter.
20

Step 1: Fill out COPACES user profile
Step 2: Create a new project or open an existing project
Step 3: Conduct segment survey
Step 4: Conduct error checking
Step 5: Export COPACES data
FIGURE 2.3: Operation Flow of Using COPACES for Laptop 3.1 COPACES User Profile The COPACES User Profile form will pop up when COPACES for Laptop launches as shown in FIGURE 2.4. The Fiscal Year box is automatically filled based on the current date. Other boxes, Rater, District, and Office, need to be filled. After that, a Microsoft Access database file will be automatically generated. The naming convention of this database file is "FY{current fiscal year}_D{district number}_{office number}_{rater}.accdb." The texts in the curly parentheses need to be replaced with the actual content. For example, when user JS in District 1, Area Office 1 fills the form, a database file named FY2018_D1_A1_JS.accdb will be generated and stored in the folder of COPACES\Data\FY2018 in the "My Documents" folder. For a user, the user profile needs to be filled once in each fiscal year. The program will memorize the last input. After the user profile information is filled, the user clicks OK to proceed.
21

FIGURE 2.4: COPACES User Profile
3.2 Project Information
COPACES data is organized by projects. As defined in GDOT's PACES manual, "a project is a length of a roadway with a common pavement section, similar structural conditions, and logical beginning and ending points." When a rater starts a pavement condition survey, the information of the project needs to be filled.
As shown in FIGURE 2.5, two categories of project-related information need to be input: location information and RC data. For a project location, all RCLINK-related information, e.g., route type, route number, route suffix, and county name, along with the starting and ending milepoints (it is shown as "Milepost" on the Project Information form), is included. As shown in FIGURE 2.2, if a project goes out of the county, the additional county name and milepoints need to be input. In COPACES for Laptop, a project can cover up to three counties.
22

FIGURE 2.5: Project Information RC data can be automatically extracted from the lookup table based on the input project location information by clicking RC Info. However, if some items are missed, they need to be manually input. After project information is filled, Save is clicked, and then Segment Info is clicked to start the pavement condition survey on segments.
23

3.3 Pavement Condition Survey on Segments For rating purposes, a project is divided into several segments, each of which is about one-mile long except the beginning and ending ones. FIGURE 2.6 shows the survey form for the first segment of the project defined in FIGURE 2.5.
FIGURE 2.6: Pavement Condition Survey on Segment Based on GDOT's PACES manual, cracking distress (load, block/transverse, and reflection cracking) is only rated on a 100-foot sample location, which should represent the majority of the cracking distresses found in the rating segment. As suggested by the PACES manual, the 100-foot section is selected by a rater and can be located anywhere within the rating segment. Normally, a rater should drive slowly, make two or three stops within the first half of the rating segment, and look at the pavement from the car to
24

determine the type of cracking distress and the level of severity that are present. The 100-foot sample section can then be selected after the rater knows the overall pavement condition. In the Sample Location box, a number between 0 and 9 can be input. For example, 6 means the 100-foot sample location is selected between 0.6 ~ 0.7 miles of this segment. Based on the definitions in the PACES manual, ten types of distresses need to be input. However, if a type of distress doesn't exist, it should be left blank. The program will perform real-time error checking when distress data is entered. For example, each % box needs a number between 0 ~ 100. If the input is out of the range, an error message will pop up. The real-time error checking significantly improves the data quality. After the current segment survey is entered, Save is clicked and then Add to conduct the survey on the next segment. 3.4 Error Checking When a rater completes the entire pavement condition survey and is ready to submit the data to a district engineer for district-level data quality checking using COPADQA, a comprehensive error check should be performed. Unlike the real-time error check introduced in Section 3.3, these error checking functions mainly focus on checking data completeness and data consistency. FIGURE 2.7 shows functions for error checking:
25

FIGURE 2.7: Error Checking
1) List Non-Current FY Projects
This function checks if the current database file contains any projects that are not in the current fiscal year. This could happen if a rater starts a pavement condition survey using the data in the previous fiscal year. If the trip date is not updated by clicking Now in FIGURE 2.5, the corresponding project would have an old date. If any error is found using this function, it should be corrected before submission.
2) List Projects with No Segment This function checks if there is any normal project in the current database without a segment in it. The status of a project could be "Normal" or "Under Construction," which can be set using the Status box as shown in FIGURE 2.5. For a normal project, there should be at least one segment in it. Otherwise, it should be discarded or be added with a segment survey.
3) List UC Projects with Segments This function checks if an under-construction project has any segments in it or not. In GDOT, no pavement survey will be done on an under-construction project.
4) List Duplicated TripDate and RouteNo
26

In the database file, the trip date and route number of a project are used as a combined primary key to identify a unique project. If there are two or more projects that have the same trip date and route number, the uniqueness criteria will be violated. When all errors, if any, are corrected, the database file is ready to be submitted to a district engineer. During the project development, it was found some raters forgot to conduct the above error check, which caused running COPADQA for district-level data quality checking and combining to fail. The database file had to be returned to the rater for correction. 3.5 Submission of Completed COPACES Database File As a final step, a rater will submit the completed COPACES database file to the district engineer for district-level quality checking and combining with other raters' data files. The function can be accessed from the Database menu as shown in FIGURE 2.8.
FIGURE 2.8: Data Transfer Function
27

After the Transfer COPACES File menu item is clicked, a message box will pop up to ask if the survey is completed and error checking is done. If the survey is incomplete or error checking is not conducted, the database file should not be submitted.
FIGURE 2.9: Confirmation on Data Completeness and Error Checking If Yes is confirmed in the above message box, the database file can be saved on a userdesignated drive and folder, which is ready to be submitted to the district engineer.
4. Automatic Software Update
Software delivery is an important process to make sure each user has the most up-to-date version. The Georgia Tech research team started this project shortly before OM started its FY 2017 COPACES data collection. Thus, the first version of COPACES for Laptop was quickly completed for raters to collect data, which caused inevitable program bugs. In addition, the change of state route and RC lookup tables also interrupted the use of the first version of COPACES for Laptop. Each time the program needed to be modified, the software delivery process had to be evaluated to ensure each user had the most up-to-date version. FIGURE 2.10 shows the original software delivery and feedback process. After a new version of the software was ready, it would be submitted to OM. Then, it would be
28

passed to OIT. The designated IT personnel in OIT would disseminate the software to each working district. Finally, the raters in area offices needed to drive to the district office to have the software installed on their computers. This process was timeconsuming, taking approximately two weeks. The feedback process was much faster. When an issue was identified, a rater normally reported it to the district engineer. Then, the Liaison Engineers in OM contacted the Georgia Tech research team. At the early stages of the software implementation, this process had to be often used. Due to the slow software delivery process, the data collection process was severely slowed down. More importantly, because a rater needed to go to the district office to install the software, some raters may have forgotten to update the software for various reasons. The inconsistency of software versions among raters eventually degraded the quality of the collected data.
Georgia Tech

GDOT OM

GDOT OIT

GDOT District IT Support
GDOT Area Office Raters

GDOT District Engineer

FIGURE 2.10: Previous Software Delivery Process
29

To solve the above issue, the Georgia Tech research team closely worked with OIT and devised a solution using automatic update functions. First, the setup package of COPACES for Laptop was developed using Microsoft ClickOnce; this Microsoft technology enables a user to install and run a Windows-based smart client application by downloading it from a web repository. Second, OIT helped to generate a web repository, http://software.dot.ga.gov/COPACESLaptop/, to store the ClickOnce setup files. During the first installation, the light-weight "setup.exe" file was sent to district offices for installation. During the installation, the major program was downloaded from the web repository, which makes the size of the setup.exe file very small (only 575KB). In future software updates, there is no need to disseminate the setup file to district offices. After GDOT OIT receives a software update, a designated IT person will replace the files in the web repository using the new update. In the meantime, when a rater launches COPACES for Laptop and the computer has access to the internet, the program will automatically detect software updates and prompt the engineer to complete the software update process. The above process is illustrated in FIGURE 2.11. In comparison with the process in FIGURE 2.10, the four-step software delivery process was reduced to essentially one step because the raters don't need to ask for software updates because of the automatic update functions (indicated by the dotted arrow in FIGURE 2.11.
30

Georgia Tech New Version is Ready

GDOT OM

GDOT OIT
Automatic Update
GDOT Area Office Raters

GDOT District Engineer

FIGURE 2.11: Software Delivery Process with Automatic Update

31

32

CHAPTER 3 COPACES FOR TABLET
Since the last release of COPACES in 2008, more easy-to-carry tablet computers have become available. Compared to the use of a tablet computer, it is inconvenient to use a laptop for collecting pavement condition data in the field. To improve the productivity of a field pavement condition survey, the engineers in OM have gradually adopted tablet computers. However, even though the original laptop-based COPACES program can run on a tablet computer if the operating system is compatible, the user experience has been poor because of the use of a keyboard and a touchpad on a smaller screen (the size of a tablet computer screen is normally less than 12 inches). A user may operate a laptopbased COPACES program using finger touch, but it is difficult because the controls and buttons are designed for mouse and keyboard. Thus, to fully utilize the convenience and productivity of a tablet computer, there is a need to develop a new COPACES program that can be operated using finger touch. The current Windows operating system (Windows 8.1 or Windows 10) provides two modes: the desktop mode and tablet mode. Under the desktop mode, only the classic programs (like COPACES for Laptop) can run; the program running the tablet mode uses different resources of the operating systems, but it provides full capability of finger-touch operations. Based on discussions with the engineers in OM, the new COPACES program (named COPACES for Tablet) is designed to run in the tablet mode; an end user can operate it using finger touch.
1. System Design
This section introduces the system design of COPACES for Tablet.
33

1.1 Main Functions
COPACES for Tablet includes four main functions: 1) Creating New Project: In creating a new project page, a user can create a new project and corresponding new segments in the corresponding district and area offices. 2) Modifying Existing Project: A user can review and modify any existing project. A user may also change a project's key information, such as "route number," but it will lead to creating a new project, which is not recommended. 3) Loading Data from Previous Year: A user can import the data from previous fiscal years as templates. These imported data are originally marked as "TODO" items until they are edited and saved. In FY 2017, due to the changes in the state route lookup table (see Chapter 2), no previous data should be used as templates. Thus, each project will be surveyed from scratch. 4) Export Data: Under the tablet mode, the survey data cannot be exported and saved as a Microsoft Access database file. As a remedy, COPACES for Tablet exports survey data in csv format. However, as mentioned in Chapter 2, a user needs to use COPACES for Laptop to convert it into an Access database file that can be submitted to a district engineer.
FIGURE 3.1 shows the program operation diagram. 1.2 Internal Data Storage
COPACES for Tablet is a Windows Store application, built on the Windows 8.1 Development Toolkit (it can also run in Windows 10). It uses an SQLite database as an
34

internal data storage format, stores data in local user app packages folder (FIGURE 3.2) named "copaces." A user may open this database file using other software to check the data directly (e.g. DB Browser). The file path is also shown on the start page of the program.
FIGURE 3.1: Program Operation Diagram By default, this database contains 10 data tables inherited from the original COPACES software that was released in 2008. These 10 data tables are "tblCounty," "tblRoute," "tblpaces," "tblRouteSuffix," "tblRouteType," "tblRCLink," "tblPrjLocat," "tblPrjSurvey," "tbSegInfo," and "tblSegSurvey."
35

FIGURE 3.2: Internal Database File
2. Operations of COPACES for Tablet
This section presents all the major functions provided by COPACES for Tablet. 2.1 COPACES User Profile Like COPACES for Laptop, a user profile is needed for COPACES for Tablet, which is found on the first page when the program is launched (see FIGURE 3.3). While the fiscal year number is automatically filled, users need to type in their name and select their current district and office. No user name or password is required. At the bottom, two file paths are shown. The one in the larger font indicates the output file's location with a file name sample when it is exported. By default, this is in the "Downloads" folder. The other path is the location of the internal database file on a local tablet computer. The file is named "copaces.db." A user can read it using third-party software, such as "DB Browser," to check the data directly. Clicking OK will navigate to the main page.
36

FIGURE 3.3: COPACES User Profile 2.2 Functions on Main Page From the main page, a user can start any of the four main functions of the program by tapping on the item using finger touch, as shown in FIGURE 3.4.
FIGURE 3.4: Layout of Functions on Main Page
37

2.3 Creating New Project By clicking Create Project on the main page, a user is led to a new page, as shown in FIGURE 3.5. On this page, a user can create a new project with a unique date and time. This page is divided into two parts: "Project Location" and "Road Information." A user should fill in all necessary fields in the project location part before editing road information.
FIGURE 3.5: Creating New Project Page FIGURE 3.6 shows all the items for the project information. Once a new project page is opened, several fields will be automatically filled. Date is always the current date . If one wants to update it, NOW should be clicked on, and an updated date and time will be filled. Rater, office and district are filled with the information the user has provided on the start page, which is not editable. The Change Rater button is only used when a user opens an existing project and the rater is not the user.
38

FIGURE 3.6: Project Location Information
There is a list of selectable route numbers based on the user's district. After choosing a route number, the route suffix will be filled automatically if there is only one suitable suffix based on the lookup table. If there is more than one, manual selection is required.
If a route number and route suffix are provided, the user will see a list of selectable county names. If there is only one, it will be filled automatically with corresponding "Milepost from" and "Milepost to" and County2 and County3 files will be disabled, since only one county is available.
If more than one county can be selected, the user can add additional County2 and County3 information, or, the user should click the Clear button if additional county information is not needed.
39

The From/To information for all counties will always be filled automatically once the user selects the county name. By default, it will be 0 for "from" and a positive number for "to." If the user is conducting a survey from a negative direction, the user may click the reverse symbol to reverse the from/to information. FIGURE 3.7 shows all the fields for road information. The RC Info button needs to be clicked before typing in any information. It will search the RC lookup table and try to fill the form with available information. Then, a user can edit it if any field is incorrect or missed. Direction is decided by milepost from/to information in the project location part that has been just filled in.
FIGURE 3.7: Road Information
40

Once project location and road information are filled in, the user can click Save Project to save the current project or "Edit Seg Info" to save and directly jump into the segment page on the bottom bar (FIGURE 3.5). 2.4 Creating New Segments The segment survey page is divided into two parts, as shown in FIGURE 3.8. The left part is used for segment location information, while the right part is for distress survey information that contains an overview of all the distress values and the editor of each distress. The red rating box is updated once a distress or severity level is updated. On the right of the rating box, users can see the county and the starting and ending milepoints of the current project. For multiple segments, users can use buttons at the bottom to navigate between different segments in a current project, add new segments, or delete segments.
FIGURE 3.8: Segment Survey Page
41

FIGURE 3.9 shows all the fields for segment location information. When a user creates a new segment, the county and starting and ending milepoints of this segment will be automatically filled in ascending order. The value of "Seg To" will be the next integer of the "Seg From" value. If the project direction is negative, the starting milepoint will be greater than the ending one. The green bar shows the relative location of the current segment in this project.
FIGURE 3.9: Segment Location Information
42

FIGURE 3.10 and FIGURE 3.11 show two examples (load cracking and rut) of the pavement distress survey. The distress editor will display once a user taps on the corresponding distress button, as shown in FIGURE 3.8. There are 10 types of distress that should be filled in if the corresponding types of distresses occur and once the segment information for the current segment is complete.
FIGURE 3.10: Distress Survey Example for Load Cracking The upper half of the page shows an overview of all the distress values, while the lower half functions as a distress editor. A user can tap on the corresponding distress button, and the editor panel will display. When editing, clicking on the input box, will display a green border, indicating this input is focused, and any value changes will reflect this distress. Two input methods are provided: number-board and slider. While slider can improve the speed of operation, number-board is more convenient for accurate data input.
43

When the user fills in the value and clicks OK, it will be updated to the distress value overview shown in the upper part of the page. Clicking Cancel will discard the input value. Once users click OK and change any value in this part of the page, they will notice an automatic update on the overall rating at the top of the page.
FIGURE 3.11: Distress Survey Example for Rutting Other than data input, there are several tools at the bottom of this page, as shown in FIGURE 3.12. The following is a brief list of their functions:
1) Home: Go directly to the Home Page; discard unsaved changes. 2) Back to ProjInfo: Back to the current project information page. 3) View List Seg: Jump to the new page showing all the segments of the current
project. 4) Previous Seg: Navigate to previous segment information and survey based on the
input order.
44

5) Previous Seg: Navigate to the next segment information and survey based on the input order.
6) Save Segment: Save or update the current project. 7) Add New Seg: Add a new segment after current segment; note that this new
segment is not saved until save button is clicked. 8) Reset Changes: Discard unsaved changes of the current project and load the last
saved information; if the information has never been saved, load default information. 9) Delete Seg: delete the current segment, and go back to the previous segment.
FIGURE 3.12: Segment Navigation Bar
2.5 Loading Data from Previous Year When using the previous version of COPACES, a rater often started the survey for a new fiscal year based on the previous year's data. Thus, a rater does not need to re-enter the project location and road information. In this new COPACES for Tablet version, this function is also available by loading data from previous fiscal years and is provided on the Load Data page, as shown in FIGURE 3.13.
The FY box contains a list of fiscal years covering all data on the local machine. Then, the user can choose the district, office, and/or rater to filter the loaded data. Once a search condition is set, the user may notice the checkmark is brighter. The unset condition checkmark is relatively dark.
45

The ten most recent loaded records will be shown in the list of Latest loads to remind users what data has been loaded before. Once data is loaded and before it is edited and saved, users can find it on the "open project" page as a "TO DO" item.
FIGURE 3.13: Load Data Page 2.6 Open Existing Project The Open Project function on the main page (FIGURE 3.4) is used for opening or editing any existing project and its corresponding segments and surveys. The first step is to search projects based on the customized search conditions, as shown in FIGURE 3.14. If a user wants to open a "TO DO" project, which is loaded from a previous year but has not been edited or saved yet, the TO DO button needs to be clicked. If the target project is a completed one, the Finished button should be clicked. Selecting other conditions
46

will narrow down the target list. The checkmark for the set condition will appear brighter, while the unset condition checkmark is relatively dark. Clicking Search will reveal the result shown in FIGURE 3.15. On the project list page, clicking on the target project enables a user to either go to the project information page to edit it or to delete it. Only 100 results are shown each time; users can use Show previous (if not on the first page) or Show next (if not on the last page) button to see all results.
FIGURE 3.14: Open Existing Project Page
47

FIGURE 3.15: List of Searched Projects
2.7 Export Data
As discussed in Chapter 2, COPACES for Tablet, as a Windows Store application, cannot directly store data in a Microsoft Access database file that will be used by COPADQA. Instead, COPACES for Tablet will export the internal data to csv files. Then, they will be converted to Access database files. The conversion function is implemented in COPACES for Laptop, which will be introduced in the next section.
On the main page (FIGURE 3.4), clicking Output CSV will open the page of Export projects to CSV files, as shown in FIGURE 3.16. Eight data-filtering conditions can be set to narrow down the target projects, which are fiscal year, district, office, rater, starting trip date, ending trip date, route number, and county name. The checkmark of the set condition will appear brighter, while an unset condition checkmark is relatively dark.
48

The latest 10 exported records will be shown in the list of Latest exported data to remind a user what data has been exported before. The filtered projects are shown on the page of Select projects to export (FIGURE 3.17) A user can choose to export all the projects or some of them. The exported files will be stored in the Downloads folder of a local computer. FIGURE 3.18 shows some sample of exported data. A user will not directly use the exported data but will use the converted Microsoft Access database file.
FIGURE 3.16: Export Data Page
49

FIGURE 3.17: Export Data List View
FIGURE 3.18: Export Result Example
3. Converting Survey Data to Access Database
As mentioned above, the exported data from COPACES for Tablet needs to be converted to Microsoft Access data files that can then be used by COPADQA for district-level quality checking and data combination ( FIGURE 2.1). The conversion function is implemented in the COPACES for Laptop.
50

This function can be accessed from the menu item Import Data from COPACES for Tablet, as shown in FIGURE 3.19, when COPACES for Laptop is launched. Clicking this menu item will display the data import form, as shown in FIGURE 3.20.
FIGURE 3.19: Menu Item for Importing Data from COPACES for Tablet The exported data from COPACES for Tablet is stored in the folder "COPACES for Tablet" in the Downloads folder. However, for safety concerns, the Windows operating system uses a special folder (see FIGURE 3.20) to represent "COPACES for Tablet," which is automatically generated by the operating system. Thus, the first time data is imported, COPACES for Laptop does not know where the physical folder is and needs a user to manually specify the folder location. This is done by, clicking Change Input Data Folder. The Browse For Folder form appears, as shown in FIGURE 3.21. A user can navigate to and select the "COPACES for Tablet" subfolder under the Downloads folder. After that, COPACES for Laptop remembers this location, which will be automatically used next time. The next step is to select the date of the exported data from COPACES for Tablet. For purposes of data safety, a user can periodically export data from COPACES for Tablet
51

and convert it to Microsoft Access data files. If several exporting events are found, the dates are listed in the list box shown in FIGURE 3.20. The top item is the newest one. Normally, a user will use the newest one for conversion because it contains all the new data and updates. After a date is selected, clicking Import Data will enable the user to proceed. The converted data will be stored and combined with the current Microsoft Access data file, which is similar to the data directly collected using COPACES for Laptop.
FIGURE 3.20: Data Import Form
52

FIGURE 3.21: Selecting Source Data Folder
4. Enhanced Field Data Quality Checking
Data quality is the highest priority in a data-driven pavement management system. Due to its importance, data quality checking has been rigorously implemented in the previous version of COPACES. Since COPACES is used for field data collection, and its data quality directly affects the effectiveness of pavement preservation, maintenance, and rehabilitation decision-making, stricter data quality checking is desired. Comprehensive field data quality checking can help improve data accuracy and save the re-survey effort because quality issues can be identified and immediately solved in the field. Based on the discussion with OM's Liaison Engineers, several data quality checking criteria were discussed and determined. Because COPACES for Tablet will be the major tool for field data collection, the enhanced data quality check procedures are implemented in this program. In the meantime, data conversion and management functions are implemented in COPACES for Laptop.
53

4.1 Quality Checking Criteria
Based on the systematic procedures suggested by GDOT Liaison Engineers, the following criteria for data quality checking are embedded in COPACES for Tablet.
Criterion #1: Pavement condition rating checking Due to the deterioration of pavement surface conditions, the historical pavement ratings can be used to evaluate the reasonableness of the current pavement rating. Using this criterion, after the pavement condition data on a pavement project and /or segment is completed, the automatically-calculated PACES rating will be compared with the ones in previous years, such as the previous 3 years. If the current rating falls within a 1% variance of the previous ones, the survey engineer should re-check the survey procedures and the selected sample section.
Criterion #2: Sample section location checking
Due to the limited resource, the PACES survey only rates the major pavement distresses, i.e., cracking distresses, on a selected 100-foot sample section for each pavement segment. Locations of the sample sections are subjectively determined by the rater in terms of their representativeness. Thus, the selected sample section locations vary year by year. Under this criterion, the sample section locations for each project will be compared with the ones in previous years. If more than 90% of the segments have the same sample section locations as the ones in previous years, the rater should re-check the survey procedures and make sure the selection of a sample location is not based on the previous survey results.
54

Criterion #3: Pavement distress data checking
Under this criterion, the surveyed distress data for each project will be checked against the ones in previous years. If 70% of the segments in one project have the same distress data (type and severity) as the ones in previous years, the rater should re-check the survey procedures and make sure the distresses are correctly rated.
Criterion #4: Pass/Fail test rules
Based on the above three levels of data quality checking, a rule will be set to determine if the survey on a project passes or fails. For example, if Criterion #1 and either Criteria #2 or #3 are triggered, the survey on this project will be considered failed and need to be done again.
4.2 Operations on Enhanced Data Quality Checking
Note that the enhanced data quality checking will use the previous years' COPACES survey data. However, in the FY 2017 COPACES survey, a new state route lookup table was used, as discussed in Chapter 2. Thus, all projects were surveyed from scratch without the use of any previous year's data. As a result, the enhanced data quality checking procedures were not used in FY 2017 data collection, though they have been implemented. The following discussion presents the functional operations.
The enhanced quality checking module is embedded in both COPACES for Tablet and COPACES for Laptop. Data is shared between these two programs through the data conversion procedure introduced in Section 3 of this chapter. The enhanced data quality checking module in COPACES for Tablet serves as instant feedback for raters, whereas
55

COPACES for Laptop summarizes all questionable data for district engineers and/or Liaison Engineers. Quality Checking in COPACES for Tablet
When a user finishes collecting data for a segment and attempts to save the results, the quality checking module will be triggered once the user hits the Home or Back to PrjInfo button to end the process. The module will check the data quality according to the criteria listed above. If the collected data does not pass the quality check, a message will display, as shown in FIGURE 3.22, suggesting a user return and check or redo the survey.
FIGURE 3.22: Collected Data Fails at Quality Checking in COPACES for Tablet However, the user can still choose to proceed and save the results, in which case the quality checking module will record this questionable survey in an additional table unless the issue has been resolved later. All questionable surveys, together with other useful information, can be exported to csv files.
56

Quality Checking in COPACES for Laptop After the exported data from COPACES for Tablet is converted to Microsoft Access database files (see Section 3 of this chapter), an additional function is added for error checking, as shown in FIGURE 3.23. The table of all questionable surveys is available in COPACES for Laptop, as shown in FIGURE 3.24. For district engineers and/or Liaison Engineers, the list of questionable surveys can be used to further verify the quality of the submitted data from raters in area offices. If the data are unacceptable, a re-survey can be requested.
FIGURE 3.23: Quality Checking Function in COPACES for Laptop
FIGURE 3.24: Table of All Questionable Surveys
57

5. Automatic Software Update
As discussed in Chapter 2, to improve the efficiency of software delivery and software update, a mechanism for automatic software update has been implemented for COPACES for Laptop. Similarly, COPACES for Tablet can also be automatically updated.
After the setup files of COPACES for Tablet are submitted to GDOT's OIT, they are stored in a web repository, http://software.dot.ga.gov/COPACESTablet/. During the first installation, a method of "sideloading" is used to install COPACES for Tablet on a tablet computer. The operating system should be Windows 8.1 or Windows 10. Though the best way is to publish COPACES for Tablet is in a Microsoft Store, GDOT has not purchased the service for establishing a Microsoft Store for Business. The public Store is not suitable for publishing COPACES for Tablet. Finally, based on the discussion with GDOT's OIT, COPACES for Tablet is installed using "sideloading."
To implement an automatic update, a separate program, AutoUpdateCOPACESTablet, was developed. The corresponding executable file, AutoUpdateCOPACESTablet.exe, needs to be copied and stored on a local computer. When a new software update is available, a user will be asked to update the program when COPACES for Tablet is launched.
Due to the difference between Windows 8.1 and Windows 10, the sideloading methods are also different. Appendix II and Appendix III include the procedures for installing COPACES for Tablet on Windows 8.1 and Windows 10, respectively.
58

CHAPTER 4 CONCLUSIONS AND RECOMMENDATIONS
Shortly after the Georgia Tech research team started this project, OM began to collect the FY 2017 COPACES data. As discussed in Chapter 1, the previous version of COPACES that was released in 2008 has compatibility issues with Windows 7, 8.1, and 10. Thus, COPACES for Laptop was upgraded from the previous COPACES using the newer programming language, Microsoft C#. In the meantime, the new COPACES for Tablet was also developed to improve data collection efficiency by using tablet computers. Note that COPACES for Laptop is not just a replica of the previous version but has new functions that were developed to work with COPACES for Tablet. Since time was very tight for this project, the Georgia Tech research team has closely worked with GDOT OM and OIT to deploy, test, and refine both COPACES for Laptop and COPACES for Tablet. A statewide training workshop was held in Macon on August 18, 2016.
OM's Liaison Engineers played an important role in implementing COPACES for FY 2017 data collection. Even though a statewide training workshop was held, not all raters fully understood the use of COPACES for Laptop or COPACES for Tablet. Constrained by resources, the Georgia Tech research team cannot directly communicate with all raters. Instead, intensive meetings were held between the Georgia Tech research team and OM's Liaison Engineers to test, refine, and improve the programs. In the meantime, the reported issues from individual end users were collected by Liaison Engineers and discussed/solved in the meetings.
59

When the COPACES data collection approached the end, district engineers started to collect the COPACES data from raters in area offices. After that, COPADQA was used to conduct district-level data quality checking and to combine all area office data in a district into a single database file. Then, the combined files were submitted to Liaison Engineers for transferring the data to the central COPACES database, which was done by the Upload program. As discussed in Chapter 1 and Chapter 2, the previous version of COPADQA and Upload have the compatibility issue with Windows 7, 8.1, and 10. Thus, they needed to be rewritten using C#. Though it was out of the scope of this project, the Georgia Tech research team rewrote these two programs to help OM complete the FY 2017 data collection. Since most of the functions are replicates of the previous versions, they are not presented in this final report. However, automatic updates were implemented for these two programs, like the one for COPACES for Laptop.

TABLE 4.1 summarizes the total numbers of projects and segments collected in 7 working districts.

TABLE 4.1: Summary of FY 2017 COPACES Data

Working District 1 2 3 4 5 6 7

# of Projects 536 671 630 631 761 542 238

# of Segments 3,818 4,666 4,215 4,423 5,157 3,291 1,380

The enhanced data quality checking model fully utilizes previous COPACES data and provides more rigorous in-field data quality checking. The improved data quality will further improve the accuracy of pavement condition deterioration modeling and also
60

improve the effectiveness of pavement preservation, maintenance, and rehabilitation decision-making. To prepare for the FY 2018 pavement condition data collection, a small-scale training session was conducted in GDOT OM on October 17, 2017. The Assistant State Maintenance Engineer, Liaison Engineers, and the Research Implementation Manager from the Office of Research attended the training. After that, a statewide training session was held in Macon on November 13, 2017, as shown in FIGURE 4.1. All field engineers in area offices and district offices attended this training.
FIGURE 4.1: COPACES Training in Macon The following points recommend future improvements and further implementation: The most convenient way for deploying a Windows Store application, e.g.,
COPACES for Tablet, is to use the Microsoft Store. Since more and more applications are used on tablet computers, it is suggested a Microsoft Store for Business in GDOT be implemented. Thus, all GDOT-owned applications can be
61

conveniently published in this store, and users in GDOT can also quickly download and update the applications. The current operation flow for COPACES data transfer and data integration is not very convenient or efficient due to the use of local database files. Currently, cloud computing has been widely used for mobile data collection; in it, field-collected data can be quickly transferred to cloud databases through a WiFi connection. If GDOTowned cloud services, e.g., cloud database and mobile services, are available, the COPACES data transfer and data integration process could be significantly simplified. In the meantime, the field-collected data could be transferred to OM's general office in real time.
62

APPENDIX I: LIST OF STATE ROUTES

District 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

CountyNo 011 011 011 011 011 011 011 011 011 011 011 011 011 013 013 013 013 013 013 013 013 013 013 013 059 059 059 059 059 059 059 059 085 085 085 085 085 085 085

CountyName BANKS BANKS BANKS BANKS BANKS BANKS BANKS BANKS BANKS BANKS BANKS BANKS BANKS
BARROW BARROW BARROW BARROW BARROW BARROW BARROW BARROW BARROW BARROW BARROW CLARKE CLARKE CLARKE CLARKE CLARKE CLARKE CLARKE CLARKE DAWSON DAWSON DAWSON DAWSON DAWSON DAWSON DAWSON

RouteNo 0015 0051 0052 0059 0063 0098 0105 0164 0184 0198 0323 0326 0403 0008 0011 0053 0081 0082 0124 0211 0316 0324 0330 0403 0008 0010 0010 0015 0015 0024 0072 0422 0009 0009 0052 0053 0053 0136 0183

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 LO 00 AL 00 00 00 00 WE 00 00 WE 00 00

Appendix - 1

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 19.2
18.56 5.12 6.85
10.61 6.22
10.02 6.87 2.39 7.26 4.81 5.95 6.47
18.35 12.88 12.98
6.37 10.63
3.48 24.47 15.79
0.76 1.52
2.4 10.27 17.32 15.08 11.79
8.03 0.67 2.65 15.08 10.34 0.11 10.12 18.15 0.09 26.81 10.42

District 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

CountyNo 085 105 105 105 105 105 105 105 117 117 117 117 117 117 117 117 117 117 119 119 119 119 119 119 119 119 119 119 119 119 119 119 119 119 119 119 119 119 135 135 135 135

CountyName DAWSON ELBERT ELBERT ELBERT ELBERT ELBERT ELBERT ELBERT FORSYTH FORSYTH FORSYTH FORSYTH FORSYTH FORSYTH FORSYTH FORSYTH FORSYTH FORSYTH FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN FRANKLIN GWINNETT GWINNETT GWINNETT GWINNETT

RouteNo 0400 0017 0072 0077 0077 0079 0172 0368 0009 0009 0020 0020 0053 0141 0306 0369 0371 0400 0008 0017 0017 0017 0051 0059 0063 0077 0105 0106 0145 0174 0184 0198 0281 0320 0326 0327 0328 0403 0008 0008 0010 0013

RouteSuffix 00 00 00 00 CO 00 00 00 00 SO 00 NO 00 00 00 00 00 00 00 00 00 BU 00 00 00 CO 00 00 00 00 00 00 00 00 00 00 00 00 00 WE 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
7.47 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 7.34
26.06 24.67 18.71
1.37 7.99 7.48 10.68 21.69 0.18 15.01 0.37 4.93 7.01 12.75 19.79 6.02 20.13 6.73 4.35 16.29 1.63 23.14 22.46
4 1.31 0.08 19.73 16.32 4.81 0.27 7.07 0.56 9.79 8.28 9.77 6.17 21.48 22.21 0.86 13.65 22.9

Appendix - 2

District 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

CountyNo 135 135 135 135 135 135 135 135 135 135 135 135 135 135 135 135 135 135 135 135 137 137 137 137 137 137 137 137 137 137 137 137 137 137 137 137 137 139 139 139 139 139

CountyName GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT GWINNETT HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM HABERSHAM
HALL HALL HALL HALL HALL

RouteNo 0020 0020 0084 0120 0120 0124 0124 0140 0141 0141 0211 0264 0316 0317 0324 0347 0365 0378 0403 0419 0015 0015 0015 0017 0017 0105 0115 0197 0197 0255 0255 0255 0356 0365 0384 0385 0419 0011 0011 0013 0051 0052

RouteSuffix 00 NO 00 00 WE 00 SO 00 00 CO 00 00 00 00 00 00 00 00 00 00 00 CO LO 00 AL 00 00 00 CO 00 00 AL 00 00 00 00 00 00 BU 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
10.17 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 25.97 0.73 3.56 12.61 0.45 29.15 0.27 5.24 6.05 0.58 0.52 2.71 16.56 2.25 8.86 1.1 7.42 6.45 27.87 7.42 22.13 0.72 1.2 17.04 10.24 12.98 7.08 20.85 0.09 4.48 14.12 3.29 2.57 17.91 4.26 11.62 17.8 27.04 3.17 14.54 1.49 25.54

Appendix - 3

District 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

CountyNo 139 139 139 139 139 139 139 139 139 139 139 139 139 139 139 139 147 147 147 147 147 147 147 147 147 147 147 147 147 147 147 147 157 157 157 157 157 157 157 157 157 157

CountyName HALL HALL HALL HALL HALL HALL HALL HALL HALL HALL HALL HALL HALL HALL HALL HALL HART HART HART HART HART HART HART HART HART HART HART HART HART HART HART HART
JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON

RouteNo 0053 0053 0060 0060 0082 0136 0211 0254 0283 0284 0323 0332 0347 0365 0369 0419 0008 0008 0017 0017 0017 0051 0051 0059 0077 0077 0077 0077 0172 0181 0281 0403 0011 0011 0011 0015 0015 0052 0053 0059 0060 0082

RouteSuffix 00 CO 00 CO 00 00 00 00 00 00 00 00 00 00 00 00 00 WE 00 00 BU 00 SO 00 00 CO EA SP 00 00 00 00 00 BU CO 00 AL 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
10.5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 21.4 3.73
22.94 0.2
3.99 7.59 8.05 2.01 15.69 14.48 9.28 10.28 11.27 29.76 11.1 29.76 19.53 0.55 6.17 13.61 0.53 19.19 0.15 0.68 20.69 3.87 0.45 7.06 9.95 2.94
0.8 2.26 17.4 5.36 3.15 16.75 23.63 4.63
8.8 0.2 5.4 21.54

Appendix - 4

District 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

CountyNo 157 157 157 157 157 157 157 157 157 157 187 187 187 187 187 187 187 187 187 187 187 187 195 195 195 195 195 195 195 195 195 195 219 219 219 219 219 219 219 219 219 219

CountyName JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON JACKSON LUMPKIN LUMPKIN LUMPKIN LUMPKIN LUMPKIN LUMPKIN LUMPKIN LUMPKIN LUMPKIN LUMPKIN LUMPKIN LUMPKIN MADISON MADISON MADISON MADISON MADISON MADISON MADISON MADISON MADISON MADISON OCONEE OCONEE OCONEE OCONEE OCONEE OCONEE OCONEE OCONEE OCONEE OCONEE

RouteNo 0082 0098 0098 0124 0326 0330 0332 0334 0335 0403 0009 0009 0009 0011 0052 0052 0052 0060 0060 0060 0115 0400 0008 0008 0022 0072 0098 0106 0172 0174 0191 0281 0008 0010 0010 0015 0024 0024 0053 0186 0316 0422

RouteSuffix CO 00 WE 00 00 00 00 00 00 00 00 BU SO 00 00 BU SO 00 BU SB 00 00 00 SO 00 00 00 00 00 00 00 00 00 00 LO 00 00 BU 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 4.71
12.08 1.66
11.87 2.18 4.56
13.77 12.36
8.4 21.68 24.48
1.21 0.06 9.64 24.69 1.21 0.06 21.09 4.74 0.06 9.65 3.75 18.34
0.1 1.24 19.45 18.3 16.1 10.68 7.81 6.67 10.55 10.34 6.37
4 15.38 14.62
2.98 13.44
4.37 7.67
4

Appendix - 5

District 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

CountyNo 241 241 241 241 241 257 257 257 257 257 257 257 257 257 257 257 281 281 281 281 281 281 281 281 281 291 291 291 291 291 291 291 291 297 297 297 297 297 297 297 297 297

CountyName RABUN RABUN RABUN RABUN RABUN
STEPHENS STEPHENS STEPHENS STEPHENS STEPHENS STEPHENS STEPHENS STEPHENS STEPHENS STEPHENS STEPHENS
TOWNS TOWNS TOWNS TOWNS TOWNS TOWNS TOWNS TOWNS TOWNS UNION UNION UNION UNION UNION UNION UNION UNION WALTON WALTON WALTON WALTON WALTON WALTON WALTON WALTON WALTON

RouteNo 0002 0015 0028 0197 0246 0017 0017 0063 0105 0106 0145 0184 0320 0328 0365 0419 0002 0017 0066 0075 0180 0180 0288 0339 0515 0002 0011 0011 0060 0180 0325 0348 0515 0010 0010 0011 0012 0020 0081 0083 0138 0138

RouteSuffix 00 00 00 00 00 00 AL 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SP 00 00 00 00 00 SO 00 00 00 00 00 00 BU 00 00 00 00 00 00 WE

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 24.39 19.95 7.91 8.29 3.84 17.33 9.19 8.41 0.03 9.25 8 16.66 0.07 3.62 14.52 14.52 20.56 17.39 4.8 15.59 5.29 2.45 5.76 3.54 6.42 15.66 24.22 0.05 10.59 20.81 11.14 7 15.66 21.19 4.07 19.29 2.2 7.16 19.88 8.95 10.44 0.7

Appendix - 6

District 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

CountyNo 297 297 311 311 311 311 311 311 311 311 311 311 311 311 311 009 009 009 009 009 009 009 023 023 023 023 023 023 023 023 023 033 033 033 033 033 033 033 033 033 033 033

CountyName WALTON WALTON WHITE WHITE WHITE WHITE WHITE WHITE WHITE WHITE WHITE WHITE WHITE WHITE WHITE BALDWIN BALDWIN BALDWIN BALDWIN BALDWIN BALDWIN BALDWIN BLECKLEY BLECKLEY BLECKLEY BLECKLEY BLECKLEY BLECKLEY BLECKLEY BLECKLEY BLECKLEY BURKE BURKE BURKE BURKE BURKE BURKE BURKE BURKE BURKE BURKE BURKE

RouteNo 0186 0402 0011 0011 0017 0075 0075 0115 0254 0255 0255 0284 0348 0356 0384 0022 0024 0029 0049 0112 0212 0243 0026 0087 0087 0087 0112 0126 0257 0278 0404 0017 0023 0024 0056 0056 0078 0080 0088 0121 0121 0305

RouteSuffix 00 00 00 SO 00 00 AL 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 BU 00 00 00 00 00 00 00 00 00 SP 00 00 00 00 BY 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0
9.98 0 0 0 0 0 0 0 0 0 0 0 0 0
1.76 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 6.81 1.46
15.01 0.04
15.25 17.82 11.13 15.58
8.81 5.54 15.68 2.52 7.03 8.13 11.3 22.38 23.14 10.27 11.23
8.3 11.05 10.92 18.63
0.87 15.15
4.16 22.69
7.47 5.79 7.93 1.63 11.3 29.36 37.29 36.36 6.68 0.74 29.76 4.27 22.56 5.67 29.06

Appendix - 7

District 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

CountyNo 073 073 073 073 073 073 073 073 073 073 091 091 091 091 091 091 091 091 091 091 091 091 091 091 107 107 107 107 107 107 107 107 107 107 107 107 107 107 107 107 107 107

CountyName COLUMBIA COLUMBIA COLUMBIA COLUMBIA COLUMBIA COLUMBIA COLUMBIA COLUMBIA COLUMBIA COLUMBIA
DODGE DODGE DODGE DODGE DODGE DODGE DODGE DODGE DODGE DODGE DODGE DODGE DODGE DODGE EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL EMANUEL

RouteNo 0010 0028 0047 0104 0150 0223 0232 0383 0388 0402 0027 0027 0030 0031 0046 0046 0087 0087 0117 0126 0165 0165 0230 0257 0004 0004 0015 0023 0023 0026 0026 0046 0056 0057 0078 0086 0121 0171 0171 0192 0297 0297

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 BU 00 00 00 CO 00 00 00 00 00 00 00 00 00 BU 00 00 SP 00 00 00 00 00 00 00 00 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
28.18 0 0 0
27.99 0 0 0 0 0 0 0 0
1.78 0 0 0 0 0 0 0
9.65 0 0
6.43

MilepostTo 6.89 6.49
24.54 14.95 14.37 14.05 13.79
4.83 4.54 16.94 23.57 3.92 13.1 2.05 10.93 0.08 27.31 29.07 29.39 7.99 26.71 29.42 4.95 12.26 40.05 7.87 1.66 12.59 0.09 0.44 35.38 12.34 28.19 27.11 1.66
11 5.22 9.53 10.43 30.23 0.76 14.69

Appendix - 8

District 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

CountyNo 107 125 125 125 125 125 133 133 133 133 133 141 141 141 141 141 141 141 141 159 159 159 159 159 159 159 159 159 159 159 159 163 163 163 163 163 163 163 163 163 163 163

CountyName EMANUEL GLASCOCK GLASCOCK GLASCOCK GLASCOCK GLASCOCK GREENE GREENE GREENE GREENE GREENE HANCOCK HANCOCK HANCOCK HANCOCK HANCOCK HANCOCK HANCOCK HANCOCK
JASPER JASPER JASPER JASPER JASPER JASPER JASPER JASPER JASPER JASPER JASPER JASPER JEFFERSON JEFFERSON JEFFERSON JEFFERSON JEFFERSON JEFFERSON JEFFERSON JEFFERSON JEFFERSON JEFFERSON JEFFERSON

RouteNo 0404 0080 0102 0123 0171 0296 0012 0015 0044 0077 0402 0015 0015 0016 0016 0016 0022 0022 0077 0011 0011 0016 0016 0083 0083 0142 0212 0212 0212 0212 0380 0004 0004 0004 0017 0024 0047 0078 0080 0088 0102 0171

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 00 SO 00 SO WE 00 SO 00 00 SO 00 WE 00 SO 00 00 00 00 WE 00 00 BN BU 00 00 00 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0.7 1.71
0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 10.07 7.78 15.15 4.14 13.83 0.13 22.82 27.75 27.28 20.15 16.35 22.95 0.09 24.23 0.09 0.05 26.71 0.05 9.79 25.78 0.1 18.15 0.1 26.73 0.1 13.85 0.5 1.15 22.93 0.1 5.81 35.62 0.1 12.72 31.03 16.22 6.61 15.92 14.4 27.55 10 30.3

Appendix - 9

District 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

CountyNo 163 163 165 165 165 165 165 165 167 167 167 167 167 167 167 167 167 175 175 175 175 175 175 175 175 175 175 175 175 175 175 175 175 175 175 181 181 181 181 181 181 189

CountyName JEFFERSON JEFFERSON
JENKINS JENKINS JENKINS JENKINS JENKINS JENKINS JOHNSON JOHNSON JOHNSON JOHNSON JOHNSON JOHNSON JOHNSON JOHNSON JOHNSON LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LAURENS LINCOLN LINCOLN LINCOLN LINCOLN LINCOLN LINCOLN MCDUFFIE

RouteNo 0242 0296 0017 0017 0021 0023 0067 0121 0015 0026 0026 0031 0057 0078 0086 0171 0171 0019 0026 0026 0029 0029 0029 0031 0046 0046 0086 0117 0126 0165 0199 0257 0278 0338 0404 0043 0043 0044 0047 0079 0220 0010

RouteSuffix 00 00 00 BY 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 WE 00 SO WE 00 00 00 00 00 00 00 00 00 00 00 00 00 CO 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0
5.11 0 0 0 0 0
0.9 0 0 0 0 0 0 0 0 16 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 2.39
15.86 21.11
1.52 8.19 25.09 16.27 22.84 21.19 4.67 6.45 7.02 25.89 31.07 1.67 0.12 13.33 40.21 32.33 0.13 27.9 0.13 0.11 36.59 15.4 16.35 9.65 25.25 21.64 1.27 14.22 16.59
3 22.29 31.82
18.3 1.91 1.33 16.73 18.71 18.73 25.39

Appendix - 10

District 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

CountyNo 189 189 189 189 189 189 189 189 189 189 211 211 211 211 211 211 211 217 217 217 217 217 217 217 217 217 217 217 217 217 217 217 221 221 221 237 237 237 237 237 237 245

CountyName MCDUFFIE MCDUFFIE MCDUFFIE MCDUFFIE MCDUFFIE MCDUFFIE MCDUFFIE MCDUFFIE MCDUFFIE MCDUFFIE MORGAN MORGAN MORGAN MORGAN MORGAN MORGAN MORGAN NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON NEWTON OGLETHORPE OGLETHORPE OGLETHORPE PUTNAM PUTNAM PUTNAM PUTNAM PUTNAM PUTNAM RICHMOND

RouteNo 0012 0017 0017 0043 0047 0080 0080 0150 0223 0402 0012 0024 0024 0024 0083 0186 0402 0011 0012 0012 0020 0036 0036 0081 0138 0142 0162 0162 0212 0212 0212 0402 0010 0022 0077 0016 0024 0024 0044 0142 0212 0004

RouteSuffix 00 00 BY 00 00 00 00 00 00 00 00 00 BY SP 00 00 00 00 00 WE 00 00 SO 00 00 00 00 CO 00 00 00 00 00 00 00 00 00 BU 00 00 00 00

MilepostFrom 0 0 0 0 0 0
0.92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
15.46 16.11
0 0 0 0 0 0 0 0 0 0 0

MilepostTo 5.93
23.09 7.39 7.4 6.19 0.87 1.69
10.95 6.85 11.9
19.93 20.51
4.22 0.38 26.21 0.65 24.36 13.06 16.31 0.73 3.32 16.19 0.39 18.44 1.79 16.49 16.25 1.46 14.96 15.66 16.67 15.09 18.55 27.89 33.27 23.64 23.8
3.8 22.39
5.89 9.07 25.31

Appendix - 11

District 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

CountyNo 245 245 245 245 245 245 245 245 245 245 245 245 245 245 245 265 265 265 265 265 283 283 283 283 283 283 283 283 283 283 283 283 283 301 301 301 301 301 301 301 301 301

CountyName RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND RICHMOND TALIAFERRO TALIAFERRO TALIAFERRO TALIAFERRO TALIAFERRO TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN TREUTLEN
WARREN WARREN WARREN WARREN WARREN WARREN WARREN WARREN WARREN

RouteNo 0010 0028 0056 0056 0088 0088 0104 0104 0104 0121 0223 0232 0383 0402 0415 0012 0022 0044 0047 0402 0015 0029 0046 0056 0078 0086 0171 0199 0199 0227 0297 0298 0404 0012 0012 0016 0017 0017 0080 0080 0080 0123

RouteSuffix 00 00 00 SP 00 CO 00 CO EA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SP 00 00 00 00 00 BY 00 00 CO 00 00 AL 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
24.13 0 0

MilepostTo 18.12 11.29 14.6 6.58 10.85 0.04 7.34 0.66 0.66 19.24 0.25 0.72 2.61 6.6 15.4 12.47 21.94 2.52 10.89 10.16 13.21 11.33 20.72 15.76 10.19 17.72 2.57 7.75 3.52 2.17 5.67 4.36 18.43 19.13 1.61 10.97 4.67 7.31 23.27 24.87 1.99 3.43

Appendix - 12

District 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3

CountyNo 301 301 301 301 303 303 303 303 303 303 303 303 303 303 303 317 317 317 317 317 317 317 317 317 319 319 319 319 319 319 319 319 319 021 021 021 021 021 021 021 021 021

CountyName WARREN WARREN WARREN WARREN
WASHINGTON WASHINGTON WASHINGTON WASHINGTON WASHINGTON WASHINGTON WASHINGTON WASHINGTON WASHINGTON WASHINGTON WASHINGTON
WILKES WILKES WILKES WILKES WILKES WILKES WILKES WILKES WILKES WILKINSON WILKINSON WILKINSON WILKINSON WILKINSON WILKINSON WILKINSON WILKINSON WILKINSON
BIBB BIBB BIBB BIBB BIBB BIBB BIBB BIBB BIBB

RouteNo 0171 0223 0296 0402 0015 0024 0024 0057 0068 0088 0102 0231 0242 0242 0272 0010 0010 0017 0017 0044 0044 0047 0047 0080 0018 0018 0019 0029 0057 0096 0112 0243 1085 0011 0019 0019 0022 0049 0057 0074 0087 0087

RouteSuffix 00 00 00 00 00 00 SP 00 00 00 00 00 00 SP 00 00 BU 00 BU 00 SP 00 CO 00 00 SP 00 00 00 00 00 00 00 00 00 EA 00 00 00 00 00 CO

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 7.17 0.7 0.33
13.05 30.81 32.87
2.7 2.95 18.69 10.57
6.8 20.56 22.69
2.45 15.39 26.81
4.58 28.42
2.75 26.68
2.03 19.9 0.11 6.97 11.78 0.65 1.03 25.94 28.22 9.37 37.6 10.2
6.5 16.76 19.43
1.03 19.78 18.07
1.32 13.36 19.68
0.18

Appendix - 13

District 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

CountyNo 021 021 021 021 035 035 035 035 035 053 053 053 053 077 077 077 077 077 077 077 077 077 077 077 077 077 077 077 077 079 079 079 079 079 079 079 093 093 093 093 093 093

CountyName BIBB BIBB BIBB BIBB BUTTS BUTTS BUTTS BUTTS BUTTS
CHATTAHOOCHEE CHATTAHOOCHEE CHATTAHOOCHEE CHATTAHOOCHEE
COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA COWETA CRAWFORD CRAWFORD CRAWFORD CRAWFORD CRAWFORD CRAWFORD CRAWFORD DOOLY DOOLY DOOLY DOOLY DOOLY DOOLY

RouteNo 0247 0401 0404 0408 0016 0036 0042 0087 0401 0001 0026 0355 0520 0014 0014 0016 0016 0016 0034 0034 0034 0041 0054 0070 0074 0085 0100 0154 0403 0007 0022 0042 0096 0096 0128 0401 0007 0027 0090 0215 0230 0230

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SO 00 NO SO 00 BY WE 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CO

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3.45 0 0 0 0 0 0 0 0

MilepostTo 15.68 21.24 9.02 11.99 17.43 18.29 15.43 5.94 5.43 14.83 8.35 0.8 16.13 27.74 0.63 32.2 0.63 0.63 23.09 6.04 0.06 3.97 15.83 8.46 7.65 7.65 0.47 13.15 23.3 21.06 20.8 24.74 2.75 4.19 6.21 0.14 19.79 25.14 19.83 11.4 28.86 0.33

Appendix - 14

District 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

CountyNo 093 093 093 113 113 113 113 113 113 113 113 145 145 145 145 145 145 145 145 145 145 145 145 145 145 145 149 149 149 149 151 151 151 151 151 151 151 151 151 151 151 151

CountyName DOOLY DOOLY DOOLY FAYETTE FAYETTE FAYETTE FAYETTE FAYETTE FAYETTE FAYETTE FAYETTE HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HARRIS HEARD HEARD HEARD HEARD HENRY HENRY HENRY HENRY HENRY HENRY HENRY HENRY HENRY HENRY HENRY HENRY

RouteNo 0257 0329 0401 0054 0054 0074 0085 0092 0138 0279 0314 0001 0018 0018 0036 0085 0085 0103 0116 0190 0208 0219 0315 0354 0403 0411 0001 0034 0100 0219 0003 0020 0020 0020 0042 0042 0081 0081 0138 0138 0155 0155

RouteSuffix 00 00 00 00 WE 00 00 00 00 00 00 00 00 00 00 00 AL 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 DU EA 00 SO 00 WE 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0
0.41 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1.98 0
21.01

MilepostTo 7.26 6.47
18.28 15.33
0.98 17.32 15.32 19.64
1.13 3.75 5.99 20.86 0.41 12.69 0.05 16.48 3.94 13.58 23.41 8.71 9.69 20.08 24.25 6.93
1.5 20.7 18.59 20.56 26.29 6.52 5.49 19.87 0.05 0.54 23.49 1.22 24.29 0.79 1.19 10.75 19.16 23.83

Appendix - 15

District 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

CountyNo 151 151 151 151 151 151 153 153 153 153 153 153 153 153 153 153 153 153 153 153 153 169 169 169 169 169 169 171 171 171 171 171 193 193 193 193 193 193 193 193 193 197

CountyName HENRY HENRY HENRY HENRY HENRY HENRY
HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON HOUSTON
JONES JONES JONES JONES JONES JONES LAMAR LAMAR LAMAR LAMAR LAMAR MACON MACON MACON MACON MACON MACON MACON MACON MACON MARION

RouteNo 0155 0401 0413 0920 0920 0921 0007 0007 0011 0011 0011 0026 0049 0096 0127 0224 0247 0247 0247 0329 0401 0011 0018 0022 0044 0049 0057 0007 0018 0036 0109 0401 0026 0049 0090 0127 0128 0128 0224 0240 0329 0026

RouteSuffix SO 00 00 CO WE CO 00 SP 00 BU CO 00 00 00 00 00 00 CO SP 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 BY 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 0.57
20.62 0.63 0.2 0.27 0.05
18.21 0.33
29.14 4.62 2.8
14.91 1.48
11.12 15.38 14.07 21.99
7.01 3.17 0.99 16.9 24.09 25.07 18.51 14.62 14.11 2.37 19.06 13.93 19.28 0.78 2.68 24.72 28.91 20.7 21.05 17.84 1.86 16.1 7.74 2.96 16.43

Appendix - 16

District 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

CountyNo 197 197 197 197 197 197 197 197 197 197 197 197 197 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 207 207 207 207 207 207 207 207

CountyName MARION MARION MARION MARION MARION MARION MARION MARION MARION MARION MARION MARION MARION
MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER MERIWETHER
MONROE MONROE MONROE MONROE MONROE MONROE MONROE MONROE

RouteNo 0030 0041 0041 0127 0137 0137 0153 0240 0240 0240 0352 0355 0355 0018 0018 0041 0041 0054 0054 0074 0085 0085 0085 0100 0100 0109 0109 0109 0173 0190 0190 0194 0362 0403 0007 0018 0019 0042 0074 0083 0087 0401

RouteSuffix 00 00 CO 00 00 SP 00 00 00 CO 00 00 00 00 SO 00 SO 00 SP 00 00 AL SP 00 SO 00 SP WE 00 00 00 00 00 00 00 00 00 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0
0.64 0 0 0
2.17 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
7.78 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 6.1
27.87 0.17 8.76
19.79 1.64 0.86 0.17
18.54 1.94 9.78 1.37
17.67 27.66
0.15 30.21
0.15 8.9
0.16 19.99 28.18
14.1 0.81 13.29 0.12 21.5 9.05 0.08 4.98 3.66
8 5.4 16.42 4.44 6.26 19.9 13.11 27.03 17.82 24.62 18.67 24.89

Appendix - 17

District 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

CountyNo 207 215 215 215 215 215 215 215 215 225 225 225 225 225 225 225 225 225 225 225 231 231 231 231 231 231 231 235 235 235 235 235 235 235 235 235 235 235 235 235 235 249

CountyName MONROE
MUSCOGEE MUSCOGEE MUSCOGEE MUSCOGEE MUSCOGEE MUSCOGEE MUSCOGEE MUSCOGEE
PEACH PEACH PEACH PEACH PEACH PEACH PEACH PEACH PEACH PEACH PEACH
PIKE PIKE PIKE PIKE PIKE PIKE PIKE PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI PULASKI SCHLEY

RouteNo 0408 0001 0022 0022 0022 0085 0219 0411 0520 0007 0007 0011 0042 0049 0049 0096 0096 0127 0247 0401 0003 0003 0007 0018 0074 0109 0362 0011 0011 0011 0026 0026 0027 0027 0112 0112 0230 0230 0247 0257 0257 0003

RouteSuffix 00 00 00 CO SP 00 00 00 00 00 CO 00 00 00 CO 00 00 00 CO 00 00 SO 00 00 00 00 00 00 BU EA 00 WE 00 WE 00 WE 00 WE 00 00 WE 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1.44 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 3.94 19.7
21.79 0.73
10.31 14.71
8.65 14.94
7.74 11.34
0.17 0.1
3.52 17.96
4.73 0.7
15.07 0.52 4.56 11.1
15.28 0.87 3.32
22.02 2.09 18.9 9.44
19.52 1.3
0.28 13.19
0.77 22.81
0.85 17.43
0.85 25.43
0.85 5.78 18.81 0.85 0.47

Appendix - 18

District 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

CountyNo 249 249 249 249 249 249 255 255 255 255 255 255 255 259 259 259 259 259 259 259 259 261 261 261 261 261 261 261 261 261 261 261 261 261 261 261 263 263 263 263 263 263

CountyName SCHLEY SCHLEY SCHLEY SCHLEY SCHLEY SCHLEY
SPALDING SPALDING SPALDING SPALDING SPALDING SPALDING SPALDING STEWART STEWART STEWART STEWART STEWART STEWART STEWART STEWART SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER SUMTER TALBOT TALBOT TALBOT TALBOT TALBOT TALBOT

RouteNo 0003 0026 0153 0228 0240 0271 0003 0007 0016 0092 0155 0362 0401 0001 0001 0001 0027 0039 0039 0039 0520 0003 0027 0027 0030 0030 0045 0049 0049 0118 0153 0195 0228 0271 0308 0377 0022 0036 0041 0085 0085 0090

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CO 00 00 CO SP 00 00 00 WE 00 WE 00 00 WE 00 00 00 00 00 00 00 00 00 00 00 AL 00

MilepostFrom 0.47 0 0 0 0 0 0 0 0 0 0 0 0 0 0.62 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 15.7
12.33 8.43 6.49 8.75 5.16
11.68 0.61
23.41 8.54
12.99 4.62 1.88 0.54
23.12 0.72
23.26 24.15 15.71
1.48 17.04 18.48 28.98
2.15 36.18
2.15 6.06 26.59 1.53
4.8 2.18 23.82 3.74 2.42 11.39 11.31 29.04 22.24 25.25 6.48 4.63 11.04

Appendix - 19

District 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

CountyNo 263 263 263 263 263 263 263 263 269 269 269 269 269 269 269 269 269 269 269 285 285 285 285 285 285 285 285 285 285 285 285 289 289 289 289 289 289 289 289 293 293 293

CountyName TALBOT TALBOT TALBOT TALBOT TALBOT TALBOT TALBOT TALBOT TAYLOR TAYLOR TAYLOR TAYLOR TAYLOR TAYLOR TAYLOR TAYLOR TAYLOR TAYLOR TAYLOR TROUP TROUP TROUP TROUP TROUP TROUP TROUP TROUP TROUP TROUP TROUP TROUP TWIGGS TWIGGS TWIGGS TWIGGS TWIGGS TWIGGS TWIGGS TWIGGS UPSON UPSON UPSON

RouteNo 0096 0116 0190 0208 0240 0240 0315 0355 0003 0003 0022 0090 0090 0096 0127 0128 0137 0137 0208 0001 0014 0014 0014 0018 0054 0100 0103 0109 0219 0403 0411 0018 0019 0057 0087 0096 0112 0358 0404 0003 0003 0022

RouteSuffix 00 00 00 00 00 00 00 00 00 SO 00 00 CO 00 00 00 00 WE 00 00 00 CO SP 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SO 00

MilepostFrom 0 0 0 0 0
2.73 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 9.59 7.27 4.12
21.42 2.55 3.2 5.61 2.14
26.78 1.05 5.94
22.42 0.07
24.96 20.51 11.13 27.46
0.14 12.15 27.91 34.47
1.12 4.98 8.05 10.74 7.28 0.37 21.54 23.55 27.92 14.35 6.28 23.28 6.58 20.23 22.1 0.73 6.38 22.76 22.67 1.83 4.54

Appendix - 20

District 3 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

CountyNo 293 293 293 293 293 307 307 307 307 307 003 003 003 003 003 003 007 007 007 007 007 017 017 017 017 017 017 017 017 017 017 019 019 019 019 019 019 019 019 019 019 019

CountyName UPSON UPSON UPSON UPSON UPSON
WEBSTER WEBSTER WEBSTER WEBSTER WEBSTER ATKINSON ATKINSON ATKINSON ATKINSON ATKINSON ATKINSON
BAKER BAKER BAKER BAKER BAKER BEN HILL BEN HILL BEN HILL BEN HILL BEN HILL BEN HILL BEN HILL BEN HILL BEN HILL BEN HILL BERRIEN BERRIEN BERRIEN BERRIEN BERRIEN BERRIEN BERRIEN BERRIEN BERRIEN BERRIEN BERRIEN

RouteNo 0036 0036 0074 0074 0074 0027 0041 0045 0153 0520 0031 0064 0089 0090 0135 0520 0037 0091 0200 0216 0253 0011 0011 0090 0090 0107 0125 0182 0206 0215 0233 0011 0037 0064 0064 0076 0076 0125 0135 0158 0168 0520

RouteSuffix 00 WE 00 AL WE 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SO 00 SO 00 00 00 00 00 00 00 00 00 00 00 CO 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
9.23 0 0 0 0 0 0 0

MilepostTo 19.1 0.32
26.57 1.49 0.32 13.5
19.32 2.14 7.55 9.06 16.7 24.3 6.1 7
11.77 24.78 15.13 25.71
18.7 10.05
7.76 14.73
1.53 24.31
1.35 23.3 1.45 8.68 9.88 1.11 1.09 31.29 10.07
3.1 13.34 15.99
0.11 26.85 11.08
5.43 13.22 16.68

Appendix - 21

District 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

CountyNo 027 027 027 027 027 027 027 037 037 037 037 037 037 037 037 037 037 061 061 061 061 061 061 069 069 069 069 069 069 069 069 069 069 069 069 071 071 071 071 071 071 071

CountyName BROOKS BROOKS BROOKS BROOKS BROOKS BROOKS BROOKS CALHOUN CALHOUN CALHOUN CALHOUN CALHOUN CALHOUN CALHOUN CALHOUN CALHOUN CALHOUN CLAY CLAY CLAY CLAY CLAY CLAY COFFEE COFFEE COFFEE COFFEE COFFEE COFFEE COFFEE COFFEE COFFEE COFFEE COFFEE COFFEE COLQUITT COLQUITT COLQUITT COLQUITT COLQUITT COLQUITT COLQUITT

RouteNo 0031 0033 0038 0076 0122 0133 0333 0037 0037 0041 0041 0045 0045 0055 0062 0216 0234 0001 0037 0037 0039 0266 0266 0031 0031 0032 0032 0064 0090 0107 0135 0158 0206 0206 0268 0033 0033 0035 0037 0037 0111 0133

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 00 AL 00 00 00 00 00 00 00 00 00 00 00 SO 00 WE 00 00 00 00 00 00 CO 00 00 SO 00 00 WE 00 00

MilepostFrom 0 0 0 0 0 0 0 0
0.68 0
5.69 0 0 0 0 0 0 0 0
14.25 0 0
6.92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 0.07 3.06
17.17 30.46 17.28
20.1 29.16
0.38 25.75
5.15 5.81 20.38 0.38 10.08 18.52 14.44
5.7 8.53 13.87 14.55 22.98 6.62 7.58
29 2.64 28.96 1.11 3.46 3.85 11.33 24.37 35.19 15.83 4.46 14.83 22.36 1.68 26.84 29.93 0.82 15.58 30.43

Appendix - 22

District 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

CountyNo 071 071 071 071 075 075 075 075 081 081 081 081 081 081 081 081 081 087 087 087 087 087 087 087 087 087 087 087 087 087 087 087 087 087 095 095 095 095 095 095 095 095

CountyName COLQUITT COLQUITT COLQUITT COLQUITT
COOK COOK COOK COOK CRISP CRISP CRISP CRISP CRISP CRISP CRISP CRISP CRISP DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DECATUR DOUGHERTY DOUGHERTY DOUGHERTY DOUGHERTY DOUGHERTY DOUGHERTY DOUGHERTY DOUGHERTY

RouteNo 0202 0256 0270 0270 0007 0037 0076 0401 0007 0030 0033 0033 0090 0257 0300 0300 0401 0001 0001 0038 0038 0097 0097 0097 0241 0253 0253 0262 0285 0302 0302 0309 0310 0311 0003 0062 0091 0133 0234 0300 0520 0520

RouteSuffix 00 00 00 SP 00 00 00 00 00 00 00 CO 00 00 00 CO 00 00 BU 00 BU 00 CO SP 00 00 SP 00 00 00 SP 00 00 00 00 00 00 00 00 00 00 BU

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 6.03 3.59
10.43 0.35
21.62 13.86
15.9 21.31 17.02 19.62
7.78 1.78 18.26 4.99 13.87 3.31 15.93 32.87 16.34 25.4 2.82 38.53 1.51 3.41 5.56 24.74 1.04 31.71 0.24 4.56 1.11 26.78 14.36 12.39 14.68 16.71 16.18 16.01 22.9 17.97 16.67 11.9

Appendix - 23

District 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

CountyNo 099 099 099 099 099 099 099 099 099 099 099 099 099 101 101 101 101 101 101 101 131 131 131 131 131 131 131 131 131 155 155 155 155 155 155 155 155 173 173 173 173 173

CountyName EARLY EARLY EARLY EARLY EARLY EARLY EARLY EARLY EARLY EARLY EARLY EARLY EARLY ECHOLS ECHOLS ECHOLS ECHOLS ECHOLS ECHOLS ECHOLS GRADY GRADY GRADY GRADY GRADY GRADY GRADY GRADY GRADY IRWIN IRWIN IRWIN IRWIN IRWIN IRWIN IRWIN IRWIN LANIER LANIER LANIER LANIER LANIER

RouteNo 0001 0001 0001 0038 0039 0045 0062 0062 0200 0216 0273 0273 0370 0007 0011 0089 0094 0135 0187 0376 0035 0038 0038 0038 0093 0111 0112 0188 0262 0011 0032 0035 0090 0107 0125 0158 0206 0011 0011 0011 0031 0031

RouteSuffix 00 BU SB 00 00 00 00 BY 00 00 00 SP 00 00 00 00 00 00 00 00 00 00 CO SP 00 00 00 00 00 00 00 00 00 00 00 00 00 00 BY CO 00 CO

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 21.32 4.31 0.12 6.86 28.79 12.95 26.95 4.53 19.81 6.85 9.15 0.75 12.61 1.61 17.04 5.98 35.48 17.29 9.9 4.49 7.63 19.02 0.45 0.85 26.9 31.84 12.84 9.9 7.53 12.55 27.7 9.51 16.32 7.72 14.06 5.43 2.07 21.89 0.6 0.06 17.74 0.38

Appendix - 24

District 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

CountyNo 173 173 173 173 173 173 173 173 173 173 173 173 177 177 177 177 177 177 177 177 177 177 185 185 185 185 185 185 185 185 185 185 185 185 185 185 185 185 185 201 201 201

CountyName LANIER LANIER LANIER LANIER LANIER LANIER LANIER LANIER LANIER LANIER LANIER LANIER LEE LEE LEE LEE LEE LEE LEE LEE LEE LEE
LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES LOWNDES
MILLER MILLER MILLER

RouteNo 0037 0037 0038 0038 0064 0064 0122 0122 0125 0135 0135 0168 0003 0003 0032 0091 0118 0133 0195 0377 0520 0520 0007 0007 0007 0007 0007 0031 0031 0038 0038 0094 0094 0122 0125 0133 0135 0376 0401 0001 0039 0045

RouteSuffix 00 CO 00 WE 00 00 00 CO 00 00 BY 00 00 BY 00 00 00 00 00 00 00 00 00 AL BU SB SO 00 SO 00 WE 00 WE 00 00 00 00 00 00 00 00 00

MilepostFrom 0 0 0 0 0
10.24 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1.38 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 12.06 0.04 4.35 1.29 6.13 15 14.76 0.65 2.53 14.31 1.59 4.44 21.65 1.83 18.62 8.86 11.78 2.62 14.44 8.64 0.61 6.7 38 2.92 6.99 0.45 0.45 26.23 0.48 26.75 0.91 6.54 0.73 17.08 11.04 3.38 7.61 11.47 31.28 16.11 4.27 14.72

Appendix - 25

District 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

CountyNo 201 201 201 201 201 201 201 205 205 205 205 205 205 205 205 205 205 205 205 239 239 239 243 243 243 243 243 243 243 243 243 243 243 253 253 253 253 253 253 253 253 273

CountyName MILLER MILLER MILLER MILLER MILLER MILLER MILLER
MITCHELL MITCHELL MITCHELL MITCHELL MITCHELL MITCHELL MITCHELL MITCHELL MITCHELL MITCHELL MITCHELL MITCHELL QUITMAN QUITMAN QUITMAN RANDOLPH RANDOLPH RANDOLPH RANDOLPH RANDOLPH RANDOLPH RANDOLPH RANDOLPH RANDOLPH RANDOLPH RANDOLPH SEMINOLE SEMINOLE SEMINOLE SEMINOLE SEMINOLE SEMINOLE SEMINOLE SEMINOLE TERRELL

RouteNo 0045 0045 0091 0091 0091 0273 0310 0003 0037 0037 0065 0093 0097 0111 0112 0262 0270 0300 0311 0027 0039 0050 0001 0001 0001 0001 0041 0041 0050 0050 0216 0266 0266 0038 0039 0045 0091 0091 0253 0285 0374 0032

RouteSuffix CO SO 00 SO SP 00 00 00 00 CO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 BU SB 00 00 00 WE 00 00 00 00 00 00 00 AL 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
23.22 0 0 0
0.67 0 0 0 0
0.97 0 0 0 0 0 0 0 0 0

MilepostTo 0.1
0.14 23.56
0.14 0.33 8.11 7.36 29.17 22.58 0.28 17.28 33.94 18.73 3.81 28.39 12.74 2.27 29.17 11.44 10.05 16.66 15.49 22.72 23.34 3.33 0.09 0.55 22.38 21.17 0.09 9.01
0.3 11.63
13.8 20.96
4.54 11.36
1.85 10.7 13.74 7.89 9.69

Appendix - 26

District 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

CountyNo 273 273 273 273 273 273 273 273 275 275 275 275 275 275 275 275 275 275 275 275 275 277 277 277 277 277 287 287 287 287 287 287 287 287 315 315 315 315 315 315 315 315

CountyName TERRELL TERRELL TERRELL TERRELL TERRELL TERRELL TERRELL TERRELL THOMAS THOMAS THOMAS THOMAS THOMAS THOMAS THOMAS THOMAS THOMAS THOMAS THOMAS THOMAS THOMAS TIFT TIFT TIFT TIFT TIFT TURNER TURNER TURNER TURNER TURNER TURNER TURNER TURNER WILCOX WILCOX WILCOX WILCOX WILCOX WILCOX WILCOX WILCOX

RouteNo 0041 0045 0049 0050 0055 0118 0520 0520 0003 0003 0033 0035 0035 0035 0038 0038 0111 0122 0188 0202 0300 0007 0035 0125 0401 0520 0007 0032 0032 0090 0107 0112 0159 0401 0011 0030 0090 0112 0159 0215 0233 0257

RouteSuffix 00 00 00 00 00 00 00 00 00 AL 00 00 BU CO 00 BU 00 00 00 00 00 00 00 00 00 00 00 00 CO 00 00 00 00 00 00 00 00 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0
23.04 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 2.4
27.24 4.25 9.34
10.86 10.4
22.43 23.81 31.58 18.87 18.12 26.71
5.51 1.15 26.15 4.88 3.45 14.95 24.57 9.53 31.58 20.99 20.99 16.52 20.08 18.67 16.76 21.11 0.03 9.53 10.86 23.41 12.35 16.82 23.53 20.55
1.6 20.39
6.59 26.04 18.26
3.43

Appendix - 27

District 4 4 4 4 4 4 4 4 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5

CountyNo 321 321 321 321 321 321 321 321 001 001 001 001 001 001 001 001 001 005 005 005 005 005 025 025 025 025 025 025 029 029 029 029 029 029 029 029 029 029 031 031 031 031

CountyName WORTH WORTH WORTH WORTH WORTH WORTH WORTH WORTH APPLING APPLING APPLING APPLING APPLING APPLING APPLING APPLING APPLING BACON BACON BACON BACON BACON
BRANTLEY BRANTLEY BRANTLEY BRANTLEY BRANTLEY BRANTLEY
BRYAN BRYAN BRYAN BRYAN BRYAN BRYAN BRYAN BRYAN BRYAN BRYAN BULLOCH BULLOCH BULLOCH BULLOCH

RouteNo 0032 0033 0112 0133 0256 0300 0313 0520 0004 0015 0019 0019 0027 0121 0144 0169 0203 0004 0004 0019 0032 0203 0015 0023 0032 0110 0121 0520 0025 0026 0030 0067 0119 0144 0144 0204 0404 0405 0024 0026 0046 0067

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 AL 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SP 00 00 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0
2.04 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 14.33 33.1 23.45 10.32 17.35 15.02 22.23 20.2 21.14 32.86 0.3 3.05 24.78 26.26 15.56 2.69 10.79 17.89 1.6 6.67 19.34 12.8 14.89 20.11 18.68 16.17 14.89 27 9.18 5.85 23.25 7.48 12.44 24.24 3.98 11.12 9.06 11.49 14.65 42.64 16.11 35.42

Appendix - 28

District 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5

CountyNo 031 031 031 031 031 031 031 039 039 039 039 039 039 039 043 043 043 043 043 043 049 049 049 049 049 049 049 049 049 049 049 049 051 051 051 051 051 051 051 051 051 051

CountyName BULLOCH BULLOCH BULLOCH BULLOCH BULLOCH BULLOCH BULLOCH CAMDEN CAMDEN CAMDEN CAMDEN CAMDEN CAMDEN CAMDEN CANDLER CANDLER CANDLER CANDLER CANDLER CANDLER CHARLTON CHARLTON CHARLTON CHARLTON CHARLTON CHARLTON CHARLTON CHARLTON CHARLTON CHARLTON CHARLTON CHARLTON CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM

RouteNo 0067 0073 0073 0119 0119 0119 0404 0025 0025 0040 0040 0110 0252 0405 0023 0046 0057 0121 0129 0404 0004 0004 0015 0023 0023 0040 0040 0094 0121 0177 0185 0252 0017 0021 0021 0025 0025 0025 0026 0026 0026 0030

RouteSuffix BY 00 BY 00 CO SP 00 00 SP 00 SP 00 00 00 00 00 00 00 00 00 00 SO 00 00 WE 00 CO 00 00 00 00 00 00 00 SP 00 CO EC 00 CO WE 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 7.24
24.12 6.82
11.23 5.99 0.24
26.09 31.65
2.7 23.86
6.55 29.97 12.76 27.67 18.43 17.78
8.69 18.88
9.03 17.39
19.5 1.46 19.42 52.3 1.74 6.62 1.33 12.92 51.25
2.6 12.96 10.63
4.73 17.74
1.22 21.27
3.12 0.6
36.54 0.2
0.94 7.61

Appendix - 29

District 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5

CountyNo 051 051 051 051 051 051 051 065 065 065 065 065 065 065 065 065 065 103 103 103 103 103 103 103 103 103 103 109 109 109 109 109 109 127 127 127 127 127 127 127 127 127

CountyName CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM CHATHAM
CLINCH CLINCH CLINCH CLINCH CLINCH CLINCH CLINCH CLINCH CLINCH CLINCH EFFINGHAM EFFINGHAM EFFINGHAM EFFINGHAM EFFINGHAM EFFINGHAM EFFINGHAM EFFINGHAM EFFINGHAM EFFINGHAM EVANS EVANS EVANS EVANS EVANS EVANS GLYNN GLYNN GLYNN GLYNN GLYNN GLYNN GLYNN GLYNN GLYNN

RouteNo 0204 0204 0307 0404 0404 0405 0421 0031 0037 0038 0038 0089 0094 0122 0168 0177 0187 0017 0021 0021 0021 0026 0030 0119 0275 0404 0405 0030 0073 0129 0169 0169 0292 0025 0025 0025 0025 0027 0032 0099 0303 0405

RouteSuffix 00 SP 00 00 SP 00 00 00 00 00 WE 00 00 00 00 00 00 00 00 BU SP 00 00 00 00 00 00 00 00 00 00 SP 00 00 CO SE SP 00 00 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 24.87 7.17 8.49 16.53 3.07 20.07 6.68 3.82 10.75 22.92 1.39 44.77 10.4 19.04 10.7 10.86 17.1 29.3 27.89 2.1 0.51 6.38 17.02 21.98 5.55 2.91 0.63 12.84 14.86 17.14 14.37 0.54 1.92 25.56 1.12 4.11 7.45 22.79 11.57 18.52 9.13 16.87

Appendix - 30

District 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5

CountyNo 127 161 161 161 161 161 161 161 161 161 179 179 179 179 179 179 179 179 183 183 183 183 183 191 191 191 191 191 209 209 209 209 209 209 209 209 209 209 229 229 229 229

CountyName GLYNN
JEFF DAVIS JEFF DAVIS JEFF DAVIS JEFF DAVIS JEFF DAVIS JEFF DAVIS JEFF DAVIS JEFF DAVIS JEFF DAVIS
LIBERTY LIBERTY LIBERTY LIBERTY LIBERTY LIBERTY LIBERTY LIBERTY
LONG LONG LONG LONG LONG MCINTOSH MCINTOSH MCINTOSH MCINTOSH MCINTOSH MONTGOMERY MONTGOMERY MONTGOMERY MONTGOMERY MONTGOMERY MONTGOMERY MONTGOMERY MONTGOMERY MONTGOMERY MONTGOMERY PIERCE PIERCE PIERCE PIERCE

RouteNo 0520 0019 0019 0019 0027 0107 0135 0135 0135 0268 0025 0038 0038 0119 0119 0144 0196 0405 0023 0038 0057 0144 0196 0025 0057 0099 0251 0405 0015 0029 0030 0056 0056 0130 0135 0199 0292 0298 0015 0032 0038 0121

RouteSuffix 00 00 00 CO 00 00 00 CO SO 00 00 00 CO 00 SO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SO 00 00 00 00 00 00 00 00 00

MilepostFrom 0 0
2.74 0 0 0 0 0 0 0 0 0 0 0
1.73 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 25.07 1.73 18.36 0.17 11.29 8.8 24.33 0.73 0.9 8.09 18.25 21.48 1.72 35.65 2.93 19.83 26.98 13.12 21.02 13.57 29.04 8.19 9.99 22.85 8.59 20.5 13.48 21.92 11.57 11.57 12.28 23.83 0.12 1.29 18.67 4.95 1.9 1.64 21.98 18.91 21.91 21.98

Appendix - 31

District 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5

CountyNo 229 251 251 251 251 251 251 251 251 251 267 267 267 267 267 267 267 267 267 267 267 267 267 267 271 271 271 271 271 271 271 271 271 271 279 279 279 279 279 279 279 279

CountyName PIERCE
SCREVEN SCREVEN SCREVEN SCREVEN SCREVEN SCREVEN SCREVEN SCREVEN SCREVEN TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TATTNALL TELFAIR TELFAIR TELFAIR TELFAIR TELFAIR TELFAIR TELFAIR TELFAIR TELFAIR TELFAIR TOOMBS TOOMBS TOOMBS TOOMBS TOOMBS TOOMBS TOOMBS TOOMBS

RouteNo 0203 0017 0021 0021 0021 0021 0024 0073 0073 0073 0023 0030 0056 0057 0073 0121 0129 0144 0147 0152 0169 0178 0196 0292 0019 0027 0027 0030 0031 0117 0132 0149 0149 0165 0004 0015 0015 0029 0029 0030 0030 0056

RouteSuffix 00 00 00 BU CO SB 00 00 LO SO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 WE 00 00 00 00 00 CO 00 00 00 EA 00 EA 00 WE 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 12.1
24.05 30.56 16.32
0.03 0.1
41.25 30.57
3.02 0.11 36.83 14.28
4.4 36.91
8.41 34.7 0.61 15.49 9.48 5.51 18.95 14.28 2.62 11.83 1.37 22.16 1.01 12.31 21.43 34.58 18.6 18.51 3.17 8.07 26.03 23.27 0.72 11.28 0.72 16.88 1.31 17.27

Appendix - 32

District 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 6 6 6 6 6 6 6 6 6 6 6 6 6

CountyNo 279 279 279 279 279 279 279 279 299 299 299 299 299 299 299 299 305 305 305 305 305 305 309 309 309 309 309 309 309 015 015 015 015 015 015 015 015 015 015 015 015 045

CountyName TOOMBS TOOMBS TOOMBS TOOMBS TOOMBS TOOMBS TOOMBS TOOMBS WARE WARE WARE WARE WARE WARE WARE WARE WAYNE WAYNE WAYNE WAYNE WAYNE WAYNE WHEELER WHEELER WHEELER WHEELER WHEELER WHEELER WHEELER BARTOW BARTOW BARTOW BARTOW BARTOW BARTOW BARTOW BARTOW BARTOW BARTOW BARTOW BARTOW CARROLL

RouteNo 0086 0130 0147 0152 0178 0292 0297 0298 0004 0004 0038 0122 0158 0177 0177 0520 0023 0027 0038 0038 0169 0203 0019 0030 0031 0046 0046 0126 0149 0003 0003 0020 0020 0061 0113 0113 0140 0293 0293 0401 1000 0001

RouteSuffix 00 00 00 00 00 00 00 00 00 BU 00 00 00 00 00 00 00 00 00 WE 00 00 00 00 00 00 00 00 00 00 CO 00 SP 00 00 CO 00 00 CO 00 00 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0
6.88 0 0 0 0 0 0 0 0 0 0 0
0.95 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 13.16 10.95 9.71 8.26 15.14 15.33 9.04 0.58 38.76 9.63 21.87 15.16 9.87 4.27 18.57 31.82 23.38 35.8 20.72 2.08 19.35 11 27.95 17.56 5.71 0.6 5.76 17.84 5.18 27.96 4.77 23.73 4.25 26.82 15.17 0.35 22.6 21.27 0.39 29.94 3.3 21.52

Appendix - 33

District 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6

CountyNo 045 045 045 045 045 045 045 045 045 045 045 045 045 047 047 047 047 047 047 047 047 055 055 055 055 055 055 057 057 057 057 057 057 057 057 057 057 057 083 083 083 083

CountyName CARROLL CARROLL CARROLL CARROLL CARROLL CARROLL CARROLL CARROLL CARROLL CARROLL CARROLL CARROLL CARROLL CATOOSA CATOOSA CATOOSA CATOOSA CATOOSA CATOOSA CATOOSA CATOOSA CHATTOOGA CHATTOOGA CHATTOOGA CHATTOOGA CHATTOOGA CHATTOOGA CHEROKEE CHEROKEE CHEROKEE CHEROKEE CHEROKEE CHEROKEE CHEROKEE CHEROKEE CHEROKEE CHEROKEE CHEROKEE
DADE DADE DADE DADE

RouteNo 0001 0005 0008 0016 0061 0100 0101 0113 0113 0166 0166 0274 0402 0001 0001 0002 0003 0146 0151 0151 0401 0001 0048 0100 0114 0157 0337 0005 0005 0005 0020 0092 0108 0140 0369 0372 0401 0417 0058 0058 0136 0157

RouteSuffix BU 00 00 00 00 00 00 00 00 00 CO 00 00 00 00 00 00 00 00 SP 00 00 00 00 00 00 00 00 BU CO 00 00 00 00 00 00 00 00 00 SO 00 00

MilepostFrom 0 0 0 0 0 0 0 0
17.07 0 0 0 0 0
8.23 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 0.79
32.28 8.39
27.62 13.11 17.85
6.32 13.44 17.25 27.81
3.75 1.17 15.9 1.36 9.65 16.04 13.49 5.11 16.83 0.23 13.41 18.67 12.61 14.84 12.74 6.71 12.78 23.91 15.68 1.42 25.89 14.56 15.7 26.83 4.76 17.87 2.12 23.91 22.75 0.07 14.12 1.52

Appendix - 34

District 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6

CountyNo 083 083 083 083 083 083 083 083 083 111 111 111 111 111 115 115 115 115 115 115 115 115 115 123 123 123 123 123 123 123 123 129 129 129 129 129 129 129 129 129 143 143

CountyName DADE DADE DADE DADE DADE DADE DADE DADE DADE
FANNIN FANNIN FANNIN FANNIN FANNIN FLOYD FLOYD FLOYD FLOYD FLOYD FLOYD FLOYD FLOYD FLOYD GILMER GILMER GILMER GILMER GILMER GILMER GILMER GILMER GORDON GORDON GORDON GORDON GORDON GORDON GORDON GORDON GORDON HARALSON HARALSON

RouteNo 0157 0157 0189 0189 0299 0301 0406 0406 0409 0002 0005 0060 0060 0515 0001 0001 0020 0053 0100 0101 0140 0156 0293 0002 0002 0005 0052 0136 0282 0382 0515 0003 0053 0053 0061 0136 0136 0156 0225 0401 0001 0001

RouteSuffix 00 00 00 00 00 00 00 CO 00 00 00 00 SP 00 00 LO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SP 00 00 CO 00 00 00 00 BU

MilepostFrom 16.36 20.27 0 2.75 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.57 0.89 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 20.05 20.34 2.22 15.03 3.48 10.31 20.13 0.85 4.1 17.1 14.38 30.07 7.55 17.1 26.39 11.76 27.36 34.86 18.33 12.51 10.3 6.82 8.46 0.75 26.25 22.29 28.02 5.18 13.06 11.64 22.29 15.73 27.48 2.93 13.26 24 9.78 27.54 8.35 15.65 16 9

Appendix - 35

District 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6

CountyNo 143 143 143 143 143 143 143 143 213 213 213 213 213 213 213 213 213 213 223 223 223 223 223 223 223 223 223 223 227 227 227 227 227 227 227 227 227 227 233 233 233 233

CountyName HARALSON HARALSON HARALSON HARALSON HARALSON HARALSON HARALSON HARALSON
MURRAY MURRAY MURRAY MURRAY MURRAY MURRAY MURRAY MURRAY MURRAY MURRAY PAULDING PAULDING PAULDING PAULDING PAULDING PAULDING PAULDING PAULDING PAULDING PAULDING PICKENS PICKENS PICKENS PICKENS PICKENS PICKENS PICKENS PICKENS PICKENS PICKENS
POLK POLK POLK POLK

RouteNo 0008 0016 0100 0100 0113 0113 0120 0402 0002 0002 0002 0052 0052 0061 0136 0225 0282 0286 0006 0006 0061 0092 0092 0101 0113 0120 0120 0360 0005 0005 0053 0053 0108 0136 0136 0372 0417 0515 0001 0001 0006 0006

RouteSuffix 00 00 00 SP 00 00 00 00 00 00 00 00 AL 00 00 00 00 00 00 BU 00 00 00 00 00 00 CO 00 00 BU 00 BU 00 00 CO 00 00 00 00 BU 00 BU

MilepostFrom 0 0 0 0 0
3.81 0 0 0
32.08 32.63
0 0 0 0 0 0 0 0 0 0 0 13.89 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 19.16 0.98 18.1 0.9 3.63 5.37 17.07 9.6 31.88 32.48 32.73 19.69 5.36 28.31 2.79 27.77 6.85 5.05 16.7 6.03 24.3 11.77 18.35 11.47 11.67 22.06 7.39 4.04 15.22 0.47 30.02 6.43 6.53 19.66 2.65 0.47 0.83 14.39 16.35 4.22 29.32 3.22

Appendix - 36

District 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 7 7 7 7

CountyNo 233 233 233 295 295 295 295 295 295 295 295 295 295 295 295 295 295 295 295 295 295 313 313 313 313 313 313 313 313 063 063 063 063 063 063 063 063 063 063 063 063 063

CountyName POLK POLK POLK
WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WALKER WHITFIELD WHITFIELD WHITFIELD WHITFIELD WHITFIELD WHITFIELD WHITFIELD WHITFIELD CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON

RouteNo 0100 0101 0113 0001 0001 0001 0001 0002 0095 0136 0151 0157 0157 0157 0157 0189 0189 0193 0201 0337 0341 0002 0003 0003 0052 0071 0201 0286 0401 0003 0003 0006 0014 0042 0054 0054 0085 0138 0138 0138 0139 0314

RouteSuffix 00 00 00 00 00 00 BU 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CO 00 00 00 00 00 00 CO 00 00 00 00 CO 00 00 00 SP 00 00

MilepostFrom 0 0 0 0
20.46 28.75
0 0 0 0 0 0 12.62 31.19 31.47 0 12.81 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11.78 0 0 0

MilepostTo 19.71 13.25 10.91 19.1 27.33 30.64 3.34 4.33 7.78 36.25 14.74 11.1 27.5 31.4 33.28 0.52 13.43 27.14 3.24 9.94 15.49 10.92 27.27 0.67 8.11 13.56 17.67 5 18.6 16.2 1.15 0.32 0.4 6.95 13.38 1.15 7.65 10.56 12.66 0.53 6.28 4.76

Appendix - 37

District 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7

CountyNo 063 063 063 063 063 063 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 067 089 089 089 089 089 089 089 089 089 089 089 089 089

CountyName CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON CLAYTON
COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB COBB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB

RouteNo 0331 0401 0403 0403 0407 0413 0003 0003 0005 0005 0005 0005 0006 0006 0008 0092 0092 0092 0120 0120 0120 0139 0176 0280 0360 0401 0402 0407 0417 0008 0010 0012 0013 0013 0042 0042 0054 0124 0141 0154 0154 0155

RouteSuffix 00 00 00 00 00 00 00 CO 00 CO SO SP 00 SP 00 00 00 00 00 AL LO 00 00 00 00 00 00 00 00 00 00 00 00 CO 00 00 CO 00 00 00 SP 00

MilepostFrom 0 0 0
1.79 0 0 0 0 0 0 0 0 0 0 0 0
6.57 28.56
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9.12 0 0 0 0 0 0

MilepostTo 3.28 10.8 1.36 2.03 5.95 7.58
22.75 1.65
25.09 2.07 0.81 2.33 7.37 0.84 8.55 2.12
14.01 29.63 22.21
4.06 8.61 3.86 14.95 13.53 11.45 17.83 3.61 7.61 6.29 12.15 15.11 12.72 8.23 1.05 3.08 13.92 1.05 6.58 7.25 6.67 0.68 20.24

Appendix - 38

District 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7

CountyNo 089 089 089 089 089 089 089 089 097 097 097 097 097 097 097 097 097 097 097 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121

CountyName DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DEKALB DOUGLAS DOUGLAS DOUGLAS DOUGLAS DOUGLAS DOUGLAS DOUGLAS DOUGLAS DOUGLAS DOUGLAS DOUGLAS FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON

RouteNo 0212 0236 0260 0402 0403 0407 0410 0413 0005 0006 0008 0008 0061 0070 0092 0154 0166 0166 0402 0003 0003 0006 0006 0008 0008 0009 0009 0010 0013 0014 0014 0014 0014 0014 0014 0014 0042 0042 0042 0054 0054 0070

RouteSuffix 00 00 00 00 00 00 00 00 00 00 00 CO 00 00 00 00 00 WE 00 00 CO 00 00 00 WE 00 SO 00 00 00 00 AL CO CW SO SP 00 CO SP 00 CO 00

MilepostFrom 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
11.83 0 0 0 0 0 0 0
16.64 0 0 0 0 0 0 0 0 0 0 0

MilepostTo 6.38
14.28 1.19
17.56 8.65
26.34 7.25 2.9
24.15 6.58
18.02 0.39 1.2 5.64
13.92 5.64
20.72 0.23
18.81 17.83
0.17 11.51 12.06 10.03
0.17 29.85
0.74 2.6
3.79 16.26 25.09 13.72
2.01 1.92 0.76 2.42 6.04 0.62 2.38 6.31 0.73 16.97

Appendix - 39

District 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7

CountyNo 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 121 247 247 247 247 247 247 247

CountyName FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON FULTON
ROCKDALE ROCKDALE ROCKDALE ROCKDALE ROCKDALE ROCKDALE ROCKDALE

RouteNo 0070 0074 0092 0092 0120 0138 0139 0139 0140 0141 0141 0141 0154 0154 0154 0166 0236 0236 0237 0279 0280 0372 0400 0401 0402 0403 0403 0403 0407 0407 0407 0407 0012 0020 0138 0155 0162 0212 0402

RouteSuffix 00 00 00 00 00 00 00 SO 00 00 00 CO 00 00 CO 00 00 WE 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

MilepostFrom 22.63 0 0 69.88 0 0 0 0 0 0 15.61 0 0 17.13 0 0 0 0 0 0 0 0 0 0 0 0 14.75 15.41 0 20.82 53.03 60.62 0 0 0 0 0 0 0

MilepostTo 33.47 3.07 14.2 74.87 17.25 8.42 17.5 0.76 13.83 2.32 21 0.86 9.9 36.28 0.26 15.06 1.14 0.15 3.26 5.76 4.76 8.83 22.51 17.81 11.59 13.39 15.17 31.16 13.22 26.71 54.69 62.66 8.58 17.65 17.71 1.85 2.16 8.22 8.58

Appendix - 40

APPENDIX II: USER'S GUIDE FOR INSTALLING COPACES FOR TABLET ON WINDOWS 8.1
Preparation: Please register for a free Hotmail email account if you don't have one. You need the administrator credential to install the software. 1. Uninstall any previous COPACES for Tablet 2. Install COPACES for Tablet: Step 1: Right-click Add-AppDevPackage.ps1 (note: the file extension might not be shown on your tablet) and click Run with PowerShell
Run Add-AppDevPackage.ps1 with
Appendix - 41

Step 2: Type Y to answer the first question
Type Y to answer the question. Step 3: Press Enter to continue...
You will acquire a developer license and install the signing certificate. This step is not always needed if you have done it before. Step 4: Click I Agree to continue...
Appendix - 42

Click here to continue. Step 5: Type your email and password and click Sign in
Use your own email.
Appendix - 43

This is a confirmation. Click Step 6: Type Y to install certificate
Type Y to continue.
The installation is successful. Press Enter to finish
Appendix - 44

APPENDIX II: USER'S GUIDE FOR INSTALLING COPACES FOR TABLET ON WINDOWS 10
Prerequisite: Turn on the developer mode in the system setting.
1. Open Settings in start menu
2. Open Update & Security in Settings
Appendix - 45

3. In the "For Developers" section, select "Developer mode." You will need to click "Yes" in the pop-up dialog window.
Appendix - 46

4. Uninstall previous copies of COPACES for Tablet. Installation Procedure: Step 1: Open the installation package and right-click Add-AppDevPackage.ps1 (note: the file extension might not be shown on your tablet), and click Run with PowerShell.
Appendix - 47

Step 2: Press "Enter" button to close the PowerShell window after installation is complete.
Step 3 (not required): You may reset your developer feature in Figure 3 to "Windows Store apps" for security purposes.
Appendix - 48