Process document for updating ICC Centerline and MilePosts MileExits

07/26/2011

Introduction

This process document is to describe what the new ICC centerline, milepost and mile-exits about, how we processed the new data to matching the existing data attributes, how we updated the chartcenterline by appending the new ICC centerline, what methods we used in the whole process.

1. Identify the database update requirements and target

The Intercounty Connctor or ICC (MD 200) route is a partially completed toll freeway which will link existing and proposed development areas between the I-270/I-370 .

In review of exiting ArcGIS service map file ChartBG.mxd (on the “chartdevgis” server C:\arcgisserver\MapDocument\) – a Chart interactive background map, we can know that there is a miss for the ICC route.

To make the background map with a complete required feature route present in the map, we need to update the existing ChartBG geodatabase to make up the missed ICC route (MD 200) by using the new data provided by SHA.

The update requires the three feature classes are available in the existing ChartBG map service file. That means the existing interstates feature classes will be required to append new features from the data below.

1. ICC centerline (MD 200)

2. ICC Milepost

3. ICC MileExits

In brief, the purpose of the geodatabase update is to add the ICC related features into the existing geodatabase by appending them to the corresponding feature class.

2. Describing the new data source about ICC centerline and mileposts and mile-exits

a. Roads (Centerline with ICC)

The SHA provided ICC centerline data is come from the “roads” shape file which is located in the folder called “D:\ICC_Original_DataSource” on the server of “chartdevgis”, the “roads” there are total 328348 features.

The projected coordinate system name for the “roads” is NAD_1983_HARN_StatePlane_Maryland_FIPS_1900 and geograhic coordinate system name is GCS_North_American_1983_HARN.

The Planar Distance Units: meters.

[pic]

MD 200 (ICC) route with label on it

b. Milepost (MD200_INT_FEATURES_LOC)

The milepost feature class (points) on the MD200 (ICC) comes from a personal geodatabase – MD200.mdb which is located in the folder called “D:\ICC_Original_DataSource” on the server of “chartdevgis”, the feature class MD_200INT_FEATURES_LOC has total 62 features

The projected coordinate system name for the “roads” is NAD_1983_HARN_StatePlane_Maryland_FIPS_1900 and geograhic coordinate system name is GCS_North_American_1983_HARN.

The Plana Distance Units: feet

[pic]

Milepost features show on the MD 200 (ICC)

c. Mile Exits (MD200_INT_ROADS_LOC)

The mile exits feature class (points) on the MD200 (ICC) also comes from the same personal geodatabase as above which is located in the folder called “D:\ICC_Original_DataSource” on the server of “chartdevgis”, there are 16 features in the feature class, the mile exits features should be extracted from this feature class.

The projected coordinate system name for the “roads” is NAD_1983_HARN_StatePlane_Maryland_FIPS_1900 and geograhic coordinate system name is GCS_North_American_1983_HARN.

The Plana Distance Units: survey feet

[pic]

Mile Exits features show on the MD 200 (ICC)

[pic]

Highlighted folder for ICC data source location on the CHARTDEVGIS

3. Identify which layers need to be updated

By reviewing the existing ChartBG.mxd service map, you can find there is no an ICC route (MD 200) on the map, the background map file is composed of total 25 feature layers from US roads to States roads and county and state boundary polygons.

MD 200 location

[pic]

After a thorough study of the these feature layers, just the four feature layers related to ICC (MD 200) update, that means we have to update the four feature layers by appending new ICC data. They are as below and data sources are from server: distnode1chart or 10.2.110.10.

Layer Name Layer Source in CHARTBG on server

1. SHA GRID Centerlines (Details) GD_SHAGRIDCENTERLINE

2. MD Interstates (Inventory Direction) GG_MDINTERSTATESINVDIR

3. MD Interstates (Detailed) GD_MDINTERSTATES

4. MD Interstates (Gen) GG_MDINTERSTATESTEST

The corresponding map file is located on the server “Chartdevgis” in folders:

1. C:\arcgisserver\MapDocument\ MD_200_ICC\ChartBG.mxd

2. C:\arcgisserver\MapDocument\DISTNODE1CHART\ChartBG.mxd

4. Comparison between the exiting data attributes and the new data source attributes

a. ChartCenterLine compares to Roads

Before we were going to update the ICC route centerline features in the ArcSDE geodatabase, we have to compare how the data attribute column difference between the new ICC road and the existing chartcenterline. The purpose of the comparison is to match the two data has same attribute columns to help them append together.

We have created a XSL file on the Chardevgis Server the name of the XSL is called “Comprison_ICC_Roads_and_CHARTBG_RelatedLayers.xsl”, it described what different columns between “ChartCenterLine” and “roads”. From the compared result, we can know that there are several columns exist in “ChartCenterLine” without existing in the “Roads” shp file, so we need to add the following columns on the new roads shp file. For more details please refer to the XSL file in the directory:

D:\ICC_Geodatabase_Update_XSL\ on the chartdevgis server.

• CNTYDESC

• DISTRICT

• MP_CO

• MP_ROAD_NA

• STMP_CHART

• STMP_CHART_TO

• T_MEAS

• TEMP_

b. GG_MDINTERSTATESINVDIR compares to Roads

By comparing the “GG_MDINTERSTATESINVDIR” and “Road”, we can know that existing “GG_MDINTERSTATESINVDIR” just has “MP_RTE_NO” , “OBJECTID” and geometry column “Shape”, so we have delete those nonused columns from “Roads” and just keep the “ID_RTE_NO” column which can be mapped to “MP_RTE_NO” column. The details of the comparison can be found the same XSL file above.

Feature Layer GG_MDINTERSTATESINVDIR Roads

Column_Name MP_RTE_NO ========= ID_RTE_NO

c. GD_MDINTERSTATES compares to Roads

The comparison between GD_MDINTERSTATES and Roads has an identical result like the above, that is roads includes many nonused columns, it just needs to mapping the ID_RTE_NO column to the MP_RTE_NO in the GD_MDINTERSTATES.

Feature Layer GD_MDINTERSTATES Roads

Column_Name MP_RTE_NO ========= ID_RTE_NO

d. GG_MDINTERSTATESTEST compares to Roads

The comparison between GG_MDINTERSTATESTEST and Roads also has an identical result like above, that is roads includes many nonuses columns, it just needs to mapping the ID_RTE_NO column to the MP_RTE_NO in the GG_MDINTERSTATESTEST.

Feature Layer GD_MDINTERSTATESTEST Roads

Column_Name MP_RTE_NO ========= ID_RTE_NO

e. GD_SHAGRIDCENTERLINE compares to Roads

The comparison between GD_SHAGRIDCENTERLINE and Roads can be found that there is no attribute column can be matched to the Roads, since there is only one Column “TEXT” in the GD_SHAGRIDCENTERLINE, and Roads doesn’t have a corresponding column name, so we have create a new field name in the Roads

Feature Layer GD_SHAGRIDCENTERLINE Roads

Column_Name TEXT Create new field column (TEXT)

5. Data processing work flow and related major procedures

a. Update the “roads” Column Attributes with ArcGIS Catalog

From the above comparison between existing “ChartCenterline” and “roads”, we can know that the “roads” missing of several attribute columns, such as

• CNTYDESC

• DISTRICT

• MP_CO

• MP_ROAD_NA

• STMP_CHART

• STMP_CHART_TO

• T_MEAS

• TEMP_

So to match the field attributes with existing “ChartCenterline”, we need to add new field columns on the “Roads”, the work can be done from ArcGIS Desktop (ArcCatalog), the screenshots look like below:

[pic]

Firstly, highlighting the shp file “Roads” in the directory and click the “Preview” table tab, then click on the “Options” button on bottom of the table, click the “Add Field…”, you will see the pop-up “Add Field” floating box, entering the field name, and select the data type using the arrow down button, finally click the “OK” button, you will see the new field column is added into the table. Repeating this same process, the “roads” shape file will have identical attribute columns like existing “chartcenterLine”.

[pic]

b. Extracting the “ICC” (MD200) route from the “Roads” shape file

1. The purpose of the whole updating is to add the “ICC” (MD200) route into the existing feature classes, so the most important task is to extract the “ICC” (MD 200) route from the “roads” shape file, then append the extracted “ICC” to the feature layers below. We know that the “ICC” is not only compose of ID_RTE_NO = 200, but also compose of ID_RTE_NO = 370, because the part of 370 are those routes and ramps connected to 200, by putting the “Roads” shape file against the existing map file ChartBG.mxd (C:\arcgisserver\MapDocument\ MD_200_ICC\ChartBG.mxd), the highlighted route is the ICC which queried by using the ArcMap Layer Properties “Definition Query” Query Builder. After query the “roads” with the definition query:

“IDE_RTE_NO” = 200 or “ID_RTE_NO” = 370

Then highlight the query result from the roads table, the screenshot is like below.

[pic]

• GD_MDINTERSTATES

• GG_MDINTERSTATESTEST

• GG_MDINTERSTATESINVDIR

Even though ICC route is extracted from “roads” shp file, however, from the above comparison we can know that the above three feature classes have only one “MP_RTE_NO” field column that the “Roads” can be mapping with “ID_RTE_NO”, so we can shrink (remove) all of the other columns in the extracted “roads” and remain only the “ID_RTE_NO” column, then change the field name to be “MP_RTE_NO”.

As result the “roads” is updated to be a “MD_ICC_UPDATED” intermediate shp file with the only one attribute column and total 70 features. Noted is required that the actual ICC route is not need to have the “Ramps” in the added features, so we deleted those ramp features from the ICC and just keep the major ICC route. So the actual ICC features used to append to the existing feature layers above only 35 features. We will describe how to append the shp file (actual ICC route) to the existing feature classes in ArcSDE Geodatabase using ArcSDE command line in next section.

[pic]

To get the “GG_MDINTERSTATESINVDIR” route, we should query the “roads” to make the two attributes field name equal, “MP_DIRECTI = CAL_DIRECT”, that means the route direction should be same, and the route name should be “INTERCOUNTY CONNECTOR”, the queried result is showed here below, from ArcMap you can see the there is single direction route for the GG_MDINTERSTATESINVDIR.

[pic]

Since the GG_MDINTERSTATESTEST and GG_MDINTERSTATESINVDIR are required to show the route features by using one feature for each route, so we have to dissolve extracted ICC route feature layer with field name “MD_RTE_NO” .

[pic]

The dissolved result table shows here below.

[pic]

You must be notice that the GG_MDINTERSTATESTEST is the double route polyline and GG_MDINTERSTATESINVDIR is a single route polyline.

[pic]

• GD_SHAGRIDCENTERLINE

The similar procedure can be taken to process the “GD_SHAGRIDCENERLINE”, since the “GD_SHAGRIDCENTERLINE” includes all of the 70 ICC features such as ramps and route 370, we just need to create a new attribute column name “TEXT” and remove all of other original column name in the extracted “MD_ICC_Projected”, the result is like the screen shot below.

[pic]

c. Append the result updated to the exiting feature layers

After having the extracted ICC route and updated their attributes column, now we can use them to append to the existing feature layers in CHARTBG. That means the target feature layers to be appended are as below:

• GD_MDINTERSTATES

• GG_MDINTERSTATESTEST

• GG_MDINTERSTATESINVDIR

• GD_SHAGRIDCENTERLINE

The whole appending steps and ArcSDE command line are as following.

1. Uploading the created ICC route shp file to be SDE feature class in the geodatabase by using the command line.

shp2sde -o create -l MD_ICC_NO_RAMP,shape -f MD_ICC_NO_RAMP.shp -a all -c 2000 -v -D CHARTBG -i sde:sqlserver:10.2.110.10 -s 10.2.110.10_chartbg -u dba -p theforce

Here we used the “shp2sde” command line and upload a shape file “MD_ICC_NO_RMP” into ArcSDE geodatabase, the feature class name also called “MD_ICC_NO_RAMP”, the database is called “CHARTBG” in server “10.2.110.10”. The “MD_ICC_NO_RAMP” can be used to append the “GG_MDINTERSTATESTEST” feature class since it is double route feature layer.

Similar process for other ICC route shp file also can be uploaded into the ArcSDE geodatabase, as the result there are 4 feature classes are uploaded into the geodatabase for appending use.

• MD_ICC_INVENTORY a single ICC route – append to GG_MDINTERSTATESINVDIR

• MD_ICC_DISSOLVE a double ICC route – append to GG_MDINTERSTATESTEST

• MD_ICC_NO_RAMP a detailed ICC route – append to GD_MDINTERSTATES

• MD_ICC_SHAGRID a detailed ICC route (include ramps) – append to GD_SHAGRIDCENTERLINE

2. Appending process using ArcToolbox

From the ArcToolbox find the Data Management Tools, then inside of the toolset “General” there is a tool called “Append”, double click the tool “Append” the Append box appears, then browse to the above ICC route feature class for example, the MD_ICC_SHAGRID, then select the Target Dataset in the same geodatabase here is the GG_SHAGRIDCENTERLINE. Finally click “OK” button, the ICC can be appended to the GG_SHAGRIDCENTERLINE feature class. The screen shot can be look as the below.

[pic]

3. Export and import the SDX file for other Geodatabase update use. Since we have created the ICC route feature classes, and successfully append them into the ArcSDE geodatabase, we can use the result for other CHARTBG update in different server for example (distnode1chart and devchart). When we export the MD feature classes to SDX file, the ArcSDE command used here is:

sdeexport -o create -l MD_ICC_INVENTORY,shape -f GG_MDINTERSTATESINVDIR_ICC.sdx -D CHARTBG -i sde:sqlserver:10.2.110.10 -s 10.2.110.10_chartbg -u dba -p theforce

sdeexport -o create -l MC_ICC_SHAGRID,shape -f GD_SHAGRIDCENTERLINE_ICC.sdx -D CHARTBG -i sde:sqlserver:10.2.110.10 -s 10.2.110.10_chartbg -u dba -p theforce

sdeexport -o create -l MD_ICC_NO_RAMP,shape -f GD_MDINTERSTATES_ICC.sdx -D CHARTBG -i sde:sqlserver:10.2.110.10 -s 10.2.110.10_chartbg -u dba -p theforce

sdeexport -o create -l MD_ICC_DISSOLVE,shape -f GG_MDINTERSTATESTEST_ICC.sdx -D CHARTBG -i sde:sqlserver:10.2.110.10 -s 10.2.110.10_chartbg -u dba -p theforce

The exported SDX results are located in the directory D:\ICC_Shailesh\SDE_Export folder on the ChartDevGIS server.

[pic]

When we use these SDX file to append other CHARTBG geodatabase, we have to use the ArcSDE import command like the below:

sdeimport -o append -l GD_MDINTERSTATES,shape -f GD_MDINTERSTATES_ICC.sdx -D CHARTBG -i sde:sqlserver:distnode1chart -s distnode1chart -u dba -p theforce

sdeimport -o append -l GD_SHAGRIDCENTERLINE,shape -f GD_SHAGRIDCENTERLINE_ICC.sdx -D CHARTBG -i sde:sqlserver:distnode1chart -s distnode1chart -u dba -p theforce

sdeimport -o append -l GG_MDINTERSTATESINVDIR,shape -f GG_MDINTERSTATESINVDIR_ICC.sdx -D CHARTBG -i sde:sqlserver:distnode1chart -s distnode1chart -u dba -p theforce

sdeimport -o append -l GG_MDINTERSTATESTEST,shape -f GG_MDINTERSTATESTEST_ICC.sdx -D CHARTBG -i sde:sqlserver:distnode1chart -s distnode1chart -u dba -p theforce

6. Update the exiting Map document with ICC labeling shows in different scales

After the existing Feature Classes were updated with ICC route features, we have to update the existing ArcGIS service used Map file for example ChartBG.mxd. (C:\arcgisserver\MapDocument\ MD_200_ICC\ChartBG.mxd)

In the ChartBG.mxd, we need to update these feature class labeling to show the ICC route. [200]

[pic]

a. Update the MD Interstates (Inventory Direction) labeling by using the VB script, in the Label Expression, we check the “Advanced” expression box and fill the script below. Then the label will be show on the ICC route like the map here.

Function FindLabel ( [MP_RTE_NO] )

IF [MP_RTE_NO] = 200 then

FindLabel = [MP_RTE_NO]

End IF

End Function

[pic]

b. Update the MD Interstates (Gen) labeling by using VB script, like the process above, we add a VB script, the purpose of the VB script is to show other interstates route label without showing the MD 200. The screen shot can be presented below

Function FindLabel ( [MP_RTE_NO] )

IF [MP_RTE_NO] 200 then

FindLabel = [MP_RTE_NO]

END IF

End Function

[pic]

[pic]

6. Update ArcGIS Service cache based on the Map document updated feature layers and labeling

7. Test the whole geodatabase feature layer update in production application