Reference Documents 1.pdf

PMG Maintained Software Descriptions www.pmgpro.com

P a g e | 1

RIMS/Inventory Manager

RIMS is a client/server-based software application written in PowerBuilder and distributed department wide on users’ computers. Inventory Manager is the eventual replacement to RIMS and is a web-based .NET application. These applications are an enterprise-wide transportation information management system that provides users the ability to manage and report roadway information including intersections, roadway characteristics, and route feature data. This system allows users to view a graphic representation of a “cross-section” of roadway by retrieving data from multiple data sources and displaying this data within one window for a quick view of the roadway section. Both applications utilize the same Oracle database. RIMS uses a version of the Integrated Transportation Management System (ITMS) GeoMedia map for spatial representation of queries. Inventory Manager uses an Esri ArcGIS Server based mapping interface.

System Capabilities Overview

• Data maintenance tools for adding, updating, and maintaining road inventory data

• Query and reporting engines

• System administration

• Photolog

• Highway Performance Monitoring System (HPMS) Reporting

• Standard Reports

• Route Modification and Re-designation with automatic update of event tables

• Integration with Pavement Management

• Highway Performance Monitoring System (HPMS) Field Application

• Information spatially enabled

• All queries output to report and map

• Additional capability for reporting and ad-hoc querying

Traffic Data Management Analysis (TDMA)

The TDMA system provides users with the ability to view and edit coverage and non-coverage count traffic data. Other data maintained within TDMA include factors used to calculate the Annual Average Daily Traffic (AADT) for coverage counts. These factors include AADT growth factors, axle and seasonal factors, K and directional factors, and truck factors. Various traffic reports are also provided from TDMA.

The TDMA homepage contains a Google-based map for mapping counter image information.

System Capabilities Overview

• Manage Permanent Sites

• Manage Special Events

• On-Demand Imports

• Manage Portable Sites

• Import Site Specific Factors

P a g e | 2

• Import Ramp Counts

• Manage Traffic Data

• Manage Factor Group Data

• Manage AADT Growth Factors

• Manage Year End Data

• Manage Counter Images

• Map Counter locations

• View Counter images

HPMS Manager

HPMS Manager allows transportation agencies to take advantage of an easy to use set of tools to correlate and validate data prior to upload to the FHWA’s HPMS site. The HPMS submittal process is a time-consuming effort involving data cleanup, formatting, upload, validation, and rework; at the same time competing with other agencies for FHWA resources. Fully compatible with Esri’s Roads and Highways, HPMS Manager will allow the HPMS Coordinator to execute the same quality control validations run by FHWA within the DOT environment. This allows the user to cleanse data prior to upload and provide better validation results. HPMS Manager uses an Esri ArcGIS Server based mapping interface.

System Capabilities Overview

• Designed to work in conjunction with Esri’s Roads and Highways (R&H)

• User can easily define source data mapping for each HPMS item

• Full suite of validations based on FHWA specifications

• Ability to edit validation rules

• Source data residing in versioned R&H geodatabase can be directly edited from within application

• Submittal file creation

• Advanced, ad-hoc reporting capability

• Certified Mileage report creation

EGIS Viewer

EGIS Viewer allows transportation agencies to seamlessly collate a multitude of data from across the enterprise into a single view. The Viewer provides the ability for average users to create dynamic, ad-hoc queries, reports and maps to support daily responsibilities and decision making without possessing expert GIS knowledge. Having easy access to a host of Department data available 24/7 increases productivity and efficiency. EGIS Viewer data is updated nightly and includes information for Projects, Road Inventory, Pavement, Traffic, Bridges, and location based information. EGIS Viewer also provides the capability to launch the Pavement Viewer, Photolog Viewer, SLD Manager, and Google Street View.

Reports and various map functionality are also available. EGIS Viewer uses an Esri ArcGIS Server based mapping interface.

P a g e | 3

SLD Manager

The SLD Manager is an interactive Straight Line Diagraming tool where users can view roadway attributes, assets, and map information related to a route in one intuitive interface. SLD Manager has two versions; one for data editors, which is launched from Inventory Manager, and one for viewers, which can be accessed from a browser within the SCDOT network. SLD Manager uses an Esri ArcGIS Server based mapping interface.

System Capabilities Overview

• Query Tool – Users must query for a location. At a minimum, users will select County, Route Type, Route Number. Additionally, users can query for a beginning and ending milepoint.

• Google-Based Map – The SLD map interface will utilize a Google based map. All Google features, such as street view, will be available from the map and will work based on existing Google functionality.

• Point on Map – This point will represent the area which is currently being viewed. When the user traverses down the road, the point will move accordingly.

• Legend – The Legend will consist of the attributes available for the queried route. Therefore, the legend will not be populated until a query is submitted. The user can turn attributes on/off in the attribute area by selecting/de-selecting each attribute in the Legend region.

• Plan Region – The plan region will display features such as routes, crossing routes, bridges and railroads. These features will be shown at the appropriate location in the plan view.

• Attribute Region – The attribute region will show the various attributes in a linear manner for the attributes selected in the Legend region. Each attribute will break at the appropriate point based on the data being viewed. The various attributes will be color coded.

Project Programming System (P2)

P2S is designed to provide all agency users with a quick and reliable source for gathering, maintaining, and reporting all pertinent project information from inception to completion. P2S accomplishes this goal by integrating with other agency applications that exist on both MSSQL and Oracle platforms. These applications include Integrated Transportation Management System, (ITMS), Primavera, Contract Bid Estimating System (CBES), Webtransport, and SiteManager. P2S also leverages the current capabilities of SCDOT's Roadway Inventory Management System (RIMS/Inventory Manger, Oracle based) to provide route validation so that project managers can be automatically notified when routes overlap with projects. The application is designed to be user-friendly and web-based to allow users to spend less time inputting and researching project information and more time focused on the advancement of transportation projects. P2S also contains a Professional Services module which is used to manage the solicitation process for professional services contracts. This module is also integrated with ProjectWise.

P2S uses a Google-based map to display GeoMedia generated events.

P a g e | 4

Roadway Information System (RIS)

RIS is a public facing website which provides users the capability to query, view, and report on various SCDOT information. Users can query for Road Conditions and Load Restricted Bridge information, Roadway information, or Street Finder information. Additionally, RIS provides the ability to perform a Map Query. Users perform map queries by selecting a point on a road. The query returns specific information about the route(s) for that location. Users can also perform a “Locate Me” query to determine their approximate location. RIS includes hyperlinks to the South Carolina Traffic Advisories website as well as the SCDOT homepage. RIS uses a Google-based map to display GeoMedia generated events.

Right of Way Data Management System (RWDMS)

RWDMS is used to address the capture, query, reporting, and analysis of information for the Rights of Way Office. The web based RWDMS includes interfaces for each R/W area, or activity. These include Appraisal, Acquisition, Relocation, Quality Control, Claims, Railroads, Utilities, Agent Information, and the Grantor Index. Additionally, there are modules for Reports, System Administration, and Code List Maintenance. Each of the areas/activities above has a separate, unique interface which is accessed from the main R/W application. For each area/activity, users have the ability to add, modify, and delete records. RWDMS is tightly coupled with the Project Programming System (P2S) and any changes to either system must include consideration for the other. RWDMS uses a Google-based map to display GeoMedia generated events.

STIP Manager

With STIP Manager, transportation agencies can take advantage of an easy to use web-based solution to create, amend and report the STIP. All applicable funding and budget information is available in one place ready for querying and reporting. Users are able to add new STIP entries or modify existing ones, view budget and expenditure information for various projects, and generate reports which are easy to understand. STIP items are easily mapped increasing the understanding of how the projects relate to each other. STIP Manager uses a Google-based map to display GeoMedia generated events.

System Capabilities Overview

• Electronically manage, amend and publish the STIP

• View STIP projects on a map

• Create “What if” scenarios

• Manage multiple revisions simultaneously

• Report budgets and expenditures

• Create Ad-hoc reports

• Integrated with P2S

P a g e | 5

Photolog Viewer

Photolog Viewer allows users to query for images along various South Carolina Routes. Users query by County, Route, Route Number, Auxiliary, Milepoint and Direction. For routes with multiple years of imagery available, users can select the image year which they want to view. Users also have the ability to show two images at once so that differences from one year to another can be observed. The images are “tagged” to the LRS so that the correct image is displayed based on the route queried. Once the result has been displayed, users can “ride” the route by viewing consecutive images as if they are driving the route. Photolog Viewer is available via EGIS Viewer and Inventory Manager or it can be launched from any browser within the SCDOT network.

Pavement Viewer

Pavement Viewer is similar to Photolog Viewer although there are some differences between the two interfaces. The Pavement Viewer interface contains frames for (1) the image, (2) pavement data, and (3) a Google-based map. Users query for pavement data and images by County, Route, Route Number, Auxiliary, Milepoint and Direction. Once the query has run, the user is presented with a table that contains various pavement specific information. When the user presses play, the location, represented by a dot, on the map is updated so that the user has a real-time view of where they are on the route.

The associated image advances as if the user is “riding” the route. This is accomplished displaying consecutive images. Pavement Viewer is available via EGIS Viewer and Inventory Manager or it can be launched from any browser within the SCDOT network.

Integrated Transportation Management System (ITMS)

An intranet web-based solution, ITMS provides a spatially enabled query and reporting mechanism that spans across many departments and mines information from various databases.

The ITMS web viewer combines and collates information from multiple sources in response to a user query without the user having to specifically define the location of the data. It is a tool that integrates information and displays the results on a map and in a report. The databases are not warehoused;

instead, the data is accessed live giving the SCDOT the most up-to-date information possible. ITMS was developed with .NET, GeoMedia WebMap, Oracle, and SQL Server applications.

Currently, ITMS is capable of integrating information from these systems:

• Roadway Inventory (RIMS)

• Construction (Site Manager)

• Maintenance Management

• Pre-Construction (P2S)

• Pavement Management

• Traffic Signals

• SharePoint

P a g e | 6

• Program Management including financial information

• Right of Way (RWDMS)

Area Query Tool

Overview The area analysis tool provides SCDOT GIS users with the ability to extract the line work that fall within an area feature. The tool will work much like a cookie cutter to ‘cut-out’ the specific area the user wants to work with. It will be used to retrieve the list of roadway segments that fall within the selected area of interest i.e. engineering districts, counties, cities. The results of the area analysis will be extracted, transformed and loaded into a new Microsoft Access database (warehouse) with appropriate formatting compatible with loading specifications by RIMS.

Tool Requirements

a. Tool must be able to take any given South Carolina area feature with valid geometry and then return all of the HIGHWAYS and/or OTHER_ROADS features contained within it.

b. The tool should work regardless of whether the area feature contains holes or not. However, this will increase the chance of failure if the holes are described with anomalous geometry.

c. HIGHWAYS and OTHER_ROADS features that are partially contained within the selected area must be cropped at the outer edge of the area feature.

d. Partial segments must be converted to individually-measured LRS features with accurate beginning and ending mile points recalculated base on the original BMP and EMP of the segment proportionally to the geometric length of the segment.

e. The tool must account for null LRS key values, LRS features that failed to calculate valid mile points, and reversed mile points.

f. The tool should account for Looped Routes

g. The calculated beginning and ending mile points will be rounded to the third decimal place.

L:\MAP_PRODUCTION\CITY\City_2016\CITY_MAP_Instructions1March2017.docx

CITY MAP PRODUCTION

PART 1: SET UP

PART 2: REVIEW QUERIES, CREATE ANALYTIC MERGE, OUTPUT TO FEATURE CLASS

PART 3: UPDATE DATA

PART 4: SYMBOLIZING FEATURES

PART 5: LABELING

PART 6: LABEL POSITIONING AND ADJUSTMENT

PART 7: LAYOUT WINDOW

PART 8: FINAL PRODUCTION

P a g e | 2

If while using these instructions, there is a need for an addition, revision, or correction, please communicate with Thomas or Emily for further adjustments and or clarifications.

City Map Production (2016-2017 Revision)

ANALYST INSTRUCTIONS

PART 1: SET UP

1. Locate previous CITY Map

a. Print a copy of the previous map off the SCDOT web site.

b. Use the old city map for correct labels and general comparison.

c. If additional reference needed go to the file cabinets by GIS Manager’s (Emily) desk and locate old City Map (not Annexation maps)

2. Create new Access Warehouse.

a. Copy and rename an access database for the specified city

i. Copy L:\MAP_PRODUCTION\City_2016\XCity_warehouse.mdb

ii. Paste in WAREHOUSES

iii. Rename to Current CITYNAME_2017

L:\MAP_PRODUCTION\City_2016\WAREHOUSES\CITYNAME_2017 e.g.

3. Set Up City Map GeoWorkspace

OPEN CITY MAP TEMPLATE FROM

L:\MAP_PRODUCTION\City_2016\Geoworkspaces\CITY_Template_March1.gwt Save as NAME_2017.gws in L:\MAP_PRODUCTION\CITY_2016\Geoworkspaces\CITYNAME_2017.gws

P a g e | 3

4. Set Up and Verify Warehouse Connections

a. Connect to new city warehouse (just created)

i. Go to Warehouse from the toolbar menu and select “Connections”

Opens Connections box

ii. Highlight the XCity_Warehouse database connection and select “Properties”

iii. Re-direct the Access Database file Browse to L:\MAP_PRODUCTION\City_2016\WAREHOUSES

iv. Open the .mdb file of the specified city (CITYNAME_2017.mdb)

v. Select OK in the Properties box

b. Connect to old city warehouse from ~2010.

i. Select “New’

ii. Connection Type: Access

iii. Connection name: OLD_cityname

iv. Browse to to L:\MAP_PRODUCTION\CITY\Warehouse

File Name: City Name Access Database file .mdb

v. OPEN

c. Close the Connections box SAVE Geoworkspace

ii. Close and reopen file and verify all is set up and opening properly

5. SET UP: Confirm Coordinate System: State_Coordinate_M_SEED

OLD CITY NAME

P a g e | 4

If it needs to be changed, select ‘Load…’ and open L:\CoordinateSEED\State_Coordinate_M_SEED

OK

Save GeoWorkspace from the File toolbar

6. SET ‘LIMITS of MAP AREA’

Set LIMITS_OF_MAP_AREA for your city by updating the Query in the map template.

This query update will also update all the city map features in the template (e.g., map point symbols, highways, other roads, public and military property, railroads, hydro features, etc…)

a. Change the LIMITS_OF_MAP_AREA_selection query to display the specified city attributes

Updated by selecting Analysis Tab Queries LIMITS_OF_MAP_AREA_selection ‘Properties’ then filter for your city.

P a g e | 5

“Save GeoWorkspace” from the File toolbar

b. Research and Adjust ‘LIMITS’ Should be done

c. Check Queries in Template to be sure they have updated.

AIRPORTS_and_LIMITS_SQ ARMORIES and LIMITS_SQ BRIDGE_LINE_over_150_SQ_RW BRIDGE_LINE_under_150_SQ_RW Buffer_on_LIMIT CEMETERIES_and_LIMITS_SQ CHURCH_CEMETERY_and_LIMITS_SQ CHURCHES_and_LIMITS_SQ COUNTY_LINES and Buffer_SQ COURTHOUSE_and_LIMITS_SQ EXIT_NUMBERS_and_LIMITS_SQ

P a g e | 6

HIGHWAYS_and_Buffer_SQ HIGHWAYS SQ for DISPLAY HIGHWAYS SQ for LABELS HIGHWAYS SQ for SHIELDS HOSPITAL and LIMITS_SQ LAKEOVER5 and LIMITS_SQ LAKEUNDER5 and LIMITS_SQ LIMITS_OF_MAP_AREA_selection MILITARY and LIMITS_SQ MILITARY and LIMITS_SQ_buffer300 MUNICIPALinLIMITS_SQ MUNICIPALinLIMITS_SQbuffer300 OTHER_ROADS PROPOSED in LIMITS AREA OTHER_ROADS SQ for DISPLAY OTHER_ROADS SQ for LABELS OVERLAPS in LIMITS AREA POINT_OF_INTEREST and LIMITS_SQ PRIVATE_SCHOOLS and LIMITS_SQ PUBLIC_PROP and LIMITS_SQ_buffer300 PUBLIC_PROPERTY and LIMITS_SQ RAILROADS_and_Buffer_SQ RIVER_STREAM_and_LIMITS_SQ SCDOT_BUILDINGS_and_LIMITS_SQ SCHOOLS and LIMITS_SQ STATE_LINE_and_Buffer_SQ STREAMS and LIMITS_SQ WELCOME_REST_AREA_and_LIMITS_SQ WETLANDS and LIMITS_SQ

7. CUTTING MASKS

Using the State shape (one feature), a hole will be cut in it with the LIMITS AREA shape, (creating two features).

The hole will be deleted, creating a mask.

a. How to Create STATE_BUFFER_HOLE (800 ft buffer mask) around city.

Fit the Map Window to show the STATE_BUFFER_HOLE feature.

i. In the Map Window legend make only STATE_BUFFER_HOLE and BUFFER_on_LIMIT “Locatable On”

ii. Select STATE_BUFFER_HOLE Vector Tab SPLIT SPLIT BY

EXISTING FEATURE (bottom left)

iii. Select BUFFER_on_LIMIT right click Perform Split ;OK; OK

iv. Delete the inside polygon generated from the split.

Eventually, the STATE_BUFFER_HOLE will be white fill with white boundary.

P a g e | 7

May color fill now to view for working purposes.

v. Move up STATE_BUFFER_HOLE to display over bridges and roads, but under point symbols.

b. Create STATE_LIMIT_HOLE

i. In the Map Window legend make only STATE_LIMIT_HOLE and

LIMITS_OF_MAP_AREA_selection “Locatable ON”

ii. In the Map Window select STATE_LIMIT_HOLE Vector Tab SPLIT

SPLIT BY EXISTING FEATURE

iii. select LIMITS_OF_MAP_AREA_selection right click (anywhere in the map window) ‘Perform Split’ ;OK; OK

iv. Delete the small polygon (the inside polygon generated from the split).

v. Move up STATE_LIMIT_HOLE to display just under ‘Limits’ feature, below boundary line features, above area and hydro features.

Eventually, the STATE_LIMIT_HOLE will all be white masks, but may be left various colors or translucencies while working.

SAVE

c. Buffer Feature (BUFFER_on_LIMIT) may be turned off. (will be used briefly while inserting map into layout window)

Check with Annexations if there is anything that we need to be alerted to

P a g e | 8

PART 2: Review Queries, create Analytical Merge, and Output to Feature Classes

1. Review OTHER_ROADS_PROPOSED in LIMITS AREA.

a. If there are no proposed roads (ROUTE_AUX: “PRO”), turn off feature in legend and skip.

b. If there are proposed roads touching the area, a previously created query will have been updated by the ‘Limits’.

i. Appearing in the MapWindow legend as:

ii. An example of proposed roads appearing in the template:

c. Output OTHER_ROADS SQ for DISPLAY to a new Feature Class and save it in the new City

Warehouse (CITYNAME_2017).

d. Output OTHER_ROADS SQ for DISPLAY to a Feature Class OTHER_ROADS for

DISPLAY_FC allowing the feature to be edited (removal of PROPOSED roads) for this map without affecting the oracle database.

e. Roads output to Feature Class (see pictures below).

f. Proposed Roads should be deleted from the Feature Class road files.

Then this feature should be used for the Analytical Merge of Other Roads.

P a g e | 9

Create Analytical Merge of the roads for visual continuity.

a. Analysis Tab Analytical Merge of OTHER_ROADS SQ for DISPLAY Merge criteria is “By attribute and touching”, and Attribute is “FEATURE_TYPE”.

Query name : OTHER_ROADS AM for DISPLAY

P a g e | 10

b. Then Symbolize. Under Legend Entry Properties – “Unique Value Thematic” and classify by

FEATURE_TYPE

c. HIGHWAYS should be done and set up (as there are no proposed roads in HWY feature) If it does need to be redone, create Analytical Merge of the HIGHWAYS SQ for DISPLAY

d. Turn off HIGHWAYS SQ for DISPLAY

OTHER_ROADS SQ for DISPLAY or FC

P a g e | 11

Use OTHER_ROADS AM for DISPLAY and HIGHWAYS AM for Display for Display on map.

3. Review Highway OVERLAPS in LIMITS AREA to determine if your city has overlaps.

PART 3:

UPDATE DATA

(prior to labeling)

1. STREAMS

a. Streams (STREAMS and LIMITS_SQ) should be unbroken at lakes. No need to pursue examining each one’s location, but as they are encountered, check, and, if there is a break, then connect.

P a g e | 12

b. If the lake does not exist and there is no sign of any lake in the surrounding area, delete the feature (If aerial image verifies it) Broken dams following 2015 flood have caused some changes.

c. The streams should continue through the lake (displayed underneath). If streams are gapped at lakes, edit geometry and connect stream feature.

2. Add Names to all Rivers

RIVER_STREAM_and_LIMITS_SQ

a. Change Contents of Data Window to display the STREAMS feature class

In the Data Window, right click and select “Change Contents” Select STREAMS_SQ from Queries

b. Check to see if a name has been assigned to each river by looking at its attributes

i. If there is no name, use the old city map or insert topographic map to locate the name of the river using CURRENT IMAGERY per Yelena Go to Apollo & Google earth Change Feature class name

c. Break the river where necessary to change the name

3. Add Names to all Railroads

a. Change Contents of Data Window to display the RAILROADS feature class

i. In the Data Window, right click and select “Change Contents”

1. Select RAILROADS_and_BUFFER_SQ from Queries

ii. Check to see if a name has been assigned to each railroad by looking at its attributes

b. If there is no name, use the old city map or the topographic map to locate the name of the

Railroad Paul Newman is go-to person when it comes to anything ‘railroads’ NewmanPK@scdot.org

4. Review all symbols (for map features)

a. Set Nominal Scale to 15,840

i. Go to “View” and select “Display Properties”

ii. Nominal scale: 15,840

b. Zoom to Nominal Scale

c. Review all map symbols and ensure symbols are rotated accurately

i. All symbols should be rotated according to the road they come off of in the map (Short sentence; big project) e.g. Schools, churches, cemeteries, armories, points of interest, etc.

ii. Features touching roads should be moved back.

d. Use “Output to Feature Class” in Manage Data toolbar to create new feature class of any feature you will rotate or adjust on the map or remove from the map. (E.g., schools, churches, hospitals, SCDOT bldgs.)

Select Queried Features to be Output to Feature Class if there is a need to ‘turn off’ features or rotate them. SAVE Target connection “XCity_warehouse”

Select Advanced table to change the output name (Target Feature Class) Sample screen:

mailto:NewmanPK@scdot.org

P a g e | 13

NOTE: (Sometimes tacking an ‘FC” on the name helps to indicate it has been saved as a new Feature Class.)

e. Output as a Feature Class, then turn off original queried feature.

f. Move Feature example:

Note: School symbol here has been moved and rotated to match the general location and orientation of the building (as found on GoogleMaps)

g. Features to check:

P a g e | 14

Point Features Rotate to face roadways.

Check attributes for address Or consult photo.

If symbol touches road feature may be moved slightly to accommodate an improved display.

Keep point on property.

If unable to correct, it may need to be turned off.

NOTE: MAKE SURE READ WRITE CONNECTIONS ARE CLOSED!!!

P a g e | 15

PART 4: SYMBOLIZING FEATURES

1. For more details on symbolizing features consult file

L:\MAP_PRODUCTION\City_2016\ City_Map_instructions_for_SYMBOLS. Most point features are symbolized correctly in the template. However use the SCDOT Black White Symbols to adjust any symbols on the map. The hydro features and boundarys should be symbolized correctly.

2. Use following Table as a guide for HIGHWAYS and OTHER_ROADS.

SCDOT Black White City Transportation

HIGHWAYS AM for DISPLAY Symbology Feature Type Symbol Type Interstate Interstate Pri_Div Divided Pri_Multi Primary Multilane Pri_TwoLane Primary Twolane Sec_Div Divided Paved_Sec Paved Secondary Unpaved_Sec Unpaved Secondary City_Paved_Sec City Paved Secondary City_Sec_Div Divided City_Unpaved_Sec City Unpaved Secondary Directional Ramps (Black 1pt) I_Ramp Ramps P_Ramp Ramps Ramp_Spur Ramps S_Ramp Ramps City_Paved_CoRd Paved County Road

OTHER_ROADS_AM_for DISPLAY Symbology SCDOT Black White - City Transportation Feature Type Symbol Type Paved_CoRd Paved County Road Unpaved_CoRd Unpaved County Road L_DIV Divided Private Private Directional Ramps (Black 1pt) City_L_Div Divided City_Paved_CoRd Paved County Road City_Unpaved_CoRd Unpaved County Road City_Paved_Sec City Paved Secondary

P a g e | 16

PART 5: LABELING

1. Verify Scale

2. LAYOUT ORIENTATION

a. Study current map being developed

b. Consult previous City Map to determine orientation

c. Determine if it will be produced in Landscape or Portrait, and if a rotation will be required to fit.

d. Rotation must be completed before labeling is started. (Do we rotate ever? Not yet)

3. GENERATE LABELS

a. Go to ‘Labeling’ tab Label Manager ‘Label Preferences’ Browse to L:\MAP_PRODUCTION\LabelRules

Select OK

c. Go to Label Manager – Verify that all the □ check boxes are cleared.

d. Add Labels using Labeling

NOTE: GENERATE NAMES BEFORE SHIELDS

4. Generate Name Labels

a. Generate HIGHWAY Name Labels

i. Select HIGHWAYS_SQ for LABELS Symbol in Map Window Legend

iii. Move them to the bottom of the display. They will be used for the naming of roads, this will force the placement of names to be held off of the road line.

P a g e | 17

b. Repeat for OTHER_ROADS SQ for LABELS

c. Go to Labeling Tab in the toolbar and select “Label Manager”

i. Highlight the HIGHWAYS_SQ for LABELS feature

ii. Select “Properties” and under Style:

Text: STREET_NAME Font: Arial Style: Regular Size: 5.0

iii. Uncheck the box next to “Label with Symbol”

iv. Select OK

i. Check the “Label” box next to HIGHWAYS_SQ for LABELS

ii. Change the “Rule” to ROADS (Under ‘Rule’ heading, dropdown. NOT ‘Rule’ button with popup screen)

iii. Select OK to close the Label Manager window

iv. Zoom out to the full extent of the city boundary

v. Go to Labeling in the toolbar and select “Generate Static Labels”

“Output to” section, select “Warehouse” Connection box, select the specified city Access warehouse XCity_warehouse Output Name box, type in “HIGHWAY_NAMES” “Extent” section, select “Current View Extent” “Scale or Map Size” section, select “Nominal Scale” and set to 15,840

vi. Select OK

P a g e | 18

P a g e | 19

d. Generate OTHER ROAD Name Labels

i. Go to Labeling in the toolbar and select “Label Manager”

Through conflation there will be new local road names

ii. Clear checked boxes

iii. Highlight the OTHER_ROADS SQ for LABELS feature

iv. Select “Properties” and under Style:

Text: STREET_NAME Font: Arial Style: Regular Size: 5.0 Select OK

v. Check the “Label” box next to OTHER_ROADS SQ for LABELS

vi. Change the “Rule” to ROADS

vii. Select OK to close the Label Manager window

viii. Zoom out to the full extent of the city boundary

ix. Go to Labeling in the toolbar and select “Generate Static” labels “Output to” section, select “Warehouse” Connection box, select the specified city Access warehouse: XCity_warehouse Output Name box, type in “OTHER_ROADS_NAMES” “Extent” section, select “Current View Extent” “Scale or Map Size” section, select “Custom Scale” and set to 15,840

x. Select OK

P a g e | 20

NOTE: TURN DISPLAY OFF FOR HIGHWAY_NAMES AND OTHER_ROAD_NAMES WHILE

SHIELDS ARE BEING GENERATED

5. Generate Shield Labels

a. Set Highway Shield Properties Add Shields using Labeling Tool.

i. Go to Labeling in the toolbar and select “Label Manager”

ii. Clear check marks

iii. Check ‘Label” boxes next to I-, S-, SC, US and ‘HIGHWAYS SQ…’ will automatically check.

This will preserve settings imported through template

P a g e | 21

If settings need to be redone, follow the following steps:

iv. Highlight HIGHWAYS SQ for SHIELDS and set the ‘Rule’ to SHIELDS Check label box Message: “The value will be applied to all members of the group. Do you want to continue?”YES ‘Properties’ ‘Label Properties’ window ‘Text :’ copy and paste ROUTE_NUMBER \n ROUTE_AUX or enter by way of ‘Expression’ button.

Style:

Font: Arial, Bold Size: 7.0 pt

OK

vi. √Check the box next to ‘Label with Symbol’ Select first shield Uncheck D-, R-, RS

NOTE: Any road with “FS-“ please check with Anthony

vii. Highlight the I- feature within the HIGHWAYS_SQ_for_SHIELDS feature Check “Label”

Select “Properties…”

Select the black and white Interstate symbol At the bottom of the window, change the size to 20.0 pt

P a g e | 22

viii. Highlight the S- feature within the HIGHWAYS_SQ_for_SHIELDS feature

Select “Properties…”

Select the circle shaped Secondary symbol At the bottom of the window, change the size to 16.0 pt.

ix. Highlight the SC feature within the HIGHWAYS_SQ_for_SHIELDS feature

Select “Properties…”

Select the first SC symbol (with the darker edges) At the bottom of the window, change the size to 22.0 pt.

x. Highlight the US feature within the HIGHWAYS_SQ_for_SHIELDS feature

Select “Properties…”

Select the shield shaped US symbol At the bottom of the window, change the size to 18.0

OK

b. Generate Highway Shields

a. Zoom out to the full extent of the city boundary

b. Go to Labeling in the toolbar and select “Generate Static” labels

In the:

“Output to” section, select “Warehouse” Connection box, select the specified city warehouse: XCity_warehouse Output Name box, type in “HIGHWAY_SHIELDS” “Extent” section, select “Current View Extent”

“Scale or Map Size” section, select “Nominal Scale”

P a g e | 23

c. Adjust Shield Font Size This will reset fonts changed smaller automatically during generation.

i. Turn Shields – Locatable ON

ii. Make ONLY HIGHWAY_SHIELDS_TXT Locatable ON

iii. Expand to view entire city map area

iv. Select ALL by dragging box around county

v. Labeling Change Properties T to t

vi. Mark For ‘selected labels’

vii. Check ‘Apply Font Size:’ 7 pt

S- Shields text is 7 pt or 6 pt for 4 digit numbers SC- Shield text is 7 pt or 6.5 for 3 digit numbers US – Shield is 7 pt

Turn Display OFF HIGHWAYS SQ for SHIELDS display when done.

Turn Display ON for HIGHWAY_NAMES and OTHER_ROAD_ NAMES

P a g e | 24

d. EXIT NUMBERS (This only needs to be done in the areas that have Interstates)

i. Open Label Manager and clear all the check marks

ii. Highlight the EXIT_NUMBERS_and_LIMITS_SQ feature

iii. Select “Properties”

Text: Exit Font: Arial Style: Bold Size: 7.0

iv. Check the box next to “Label with Symbol”

v. ‘Browse’ to L:\CoordinateSEED\Symbols\Shields\SCDOTshields.lsf

vi. Select the oval shaped Exit Number shield

vii. At the bottom of the window, change the size to 18.0 pt

viii. Select OK

ix. Check the “Label” box next to EXIT_NUMBERS

x. Go to Rule and match the following – click CREATE

P a g e | 25

xi. Zoom out to the full extent of the city map area LIMITS boundary

xii. Go to Labeling and select ‘Generate Static’ In the ‘Output to’ section, select Warehouse ‘Connection’ box, select XCity_warehouse warehouse Output Name box, type in EXIT_SHIELDS

xiii. Select OK in the Label Manager window

xiv. In the “Extent” section, select “Current View Extent”

In the “Scale or Map Size” section, select Nominal Scale.

xv. Select OK

In the Map Window Legend turn the EXIT_NUMBERS feature Display OFF.

e. SYMBOL FEATURES - BUILDINGS Go to Labeling in the toolbar and select “Label Manager” and Clear checks Highlight each individual SYMBOL features (i.e. churches, hospital, schools, etc.)

Feature Selected Rule Text Font Style Size ARMORIES (change from earlier instruction. NOT to be labeled) CHURCHES BUILDINGS CHURCH_NAM Arial Bold 6 CHURCH AND CEMETERY BUILDINGS CHURCH_NAME Arial Bold 6 COURT BUILDINGS COURT_NAME Arial Bold 6 HOSPITAL BUILDINGS NAME Arial Bold 6 SCHOOLS BUILDINGS SCHOOL_NAM Arial Bold 6 PRIVATESCHOOLS BUILDINGS SCHOOL_NAM Arial Bold 6 POINT OF INTEREST LANDMARKS LOCATION_NAME Arial Bold 6 WELCOME CENTER & REST AREA LANDMARKS WELCOME_NAME Arial Bold 6 AIRPORT BUILDINGS AIRPORT_NAME Arial Bold 6 CEMETERIES (No name attribute) SCDOT_BUILDINGS (Not included. No name other than county)

P a g e | 26

i. Select “Properties” and under Style:

Text: NAME Font: Arial Style: Bold Size: 6.0

ii. Select OK

iii. Check the “Label” box next to each feature you would like symbolized

iv. Change the “Rule” to BUILDINGS or LANDMARKS

v. Select OK to close the Label Manager window

vi. Zoom out to the full extent of the city boundary

vii. Go to Labeling in the toolbar and select “Generate Static Labels”

viii. In the “Output to” section, select “Warehouse” Connection box, select Xcity_warehouse Output Name box, type in “MAP_SYMBOL_LABELS”

ix. In the “Extent” section, select “Current View Extent”

x. In the “Scale or Map Size” section, select Nominal Scale

xi. Select OK

a. RAILROADS

i. Labeling tab Label Manager

ii. Open Label Manager and clear all the check marks

iii. Highlight the RAILROADS_and_Buffer_SQ

iv. Select ’Properties…’ Text: NAME Font: Arial Style: Regular Size: 6.5

(this is a reduction from earlier settings of Size: 8 pt)

v. Select OK

vi. Check the “Label” box next to RAILROADS

vii. Change the “Rule” to RAILROADS, OK

viii. Go to Labeling and select “Generate Static”

ix. In the “Output to” section, select “Warehouse”

Connection box, select XCity_warehouse

x. Output Name box, type in “RAILROADS_NAMES”

xi. Adjust the labels locations as needed.

P a g e | 27

b. PUBLIC PROPERTY

i. Open Label Manager and clear all the check marks

ii. Highlight the PUBLIC_PROPERTY feature

iii. Select ’Properties…’ Text: PROPERTY_NAME Font: Arial Style: Bold Size: 10.0

iv. Select OK

v. Check the “Label” box next to PUBLIC_PROPERTY

vi. Change the “Rule” to PROPERTY - OK

vii. Go to Labeling and select “Generate Static”

viii. In the “Output to” section, select “Warehouse” Connection box, select XCity_warehouse Output Name box, type in “PUBLIC_PROPERTY_NAMES”

ix. In the “Extent” section, select “Current View Extent”

x. In the “Scale or Map Size” section, select “Nominal Scale”

xi. Select OK

xii. Adjust the labels locations as needed.

Consulting the old map may show an area which is not appearing labeled.

CHECK: feature may be found in GISTRANS.STATE_NAT_PARK Names may need to be entered manually.

c. MILITARY INSTALLATIONS

xii. Open Label Manager and clear all the check marks

xiii. Highlight the MILITARY_INSTALLATIONS feature

xiv. Select “Style” ’Properties…’

Text: PROPERTY_NAME Font: Arial Style: Bold Size: 10.0

xv. Select OK

xvi. Check the “Label” box next to MILITARY_INSTALLATIONS features

xvii. Change the “Rule” to PROPERTY

xviii. Go to Labeling and select “Generate Static”

xix. In the “Output to” section, select “Warehouse”

xx. Connection box, select XCity_warehouse Output Name box, type in “MILITARY_INSTALLATIONS_NAMES”

xxi. Adjust the labels locations as needed.

d. HYDRO Feature Labels Adjust later to be smaller or larger – see the old map for guidance.

Add OCEAN (TNR Italic at 16 pt) and WETLANDs (TNR Italic at 11 pt), if appropriate.

Frequently a Halo is needed for Hydro Labels -- at 2 pt white

P a g e | 28

Change Rule to “Label Joined Feature”

a. Hightlight the STREAMs_and LIMITS_SQ feature

b. Select “Properties” and under Style:

Text: NAME Font: Times New Roman Style: Italic Size: 8.0

c. Select OK

d. Check the “Label” box next to STREAMS and LIMITS_SQ

e. Change the “Rule” to RIVERS

a. Highlight the RIVERS_STREAMS and LIMITS_SQ feature

b. Select “Properties” and under Style:

Text: NAME Font: Times New Roman Style: Italic Size: 11.0

c. Select OK

d. Check the “Label” box next to RIVERS_STREAMS and LIMITS_SQ

e. Change the “Rule” to LAKES

P a g e | 29

a. Highlight the LAKESOVER5K_SQ feature

b. Select “Properties” and under Style:

Text: NAME Font: Times New Roman Style: Italic Size: 8.0

c. Select OK

d. Check the “Label” box next to LAKESOVER5K_SQ

e. Change the “Rule” to LAKES

f. Select OK to close the Label Manager window

Zoom out to the full extent of the city boundary Go to Labeling and select “Generate Static” In the “Output to” section, select “Warehouse” Connection box, select XCity_warehouse Output Name box, type in ‘HYDRO_LABELS”

P a g e | 30

Some of the HYDRO Labels’ fonts will need to be adjusted and/or repositioned.

e.g.:

P a g e | 31

e. County Names Labels: If the city has a county or state boundary, the boundary must be labeled

i. Create Feature Manage Data Features Feature Class Definition - choose XCity_warehouse New General Tab Name: BORDERING_CO_LABELS Geometry Type: Text

YES; CLOSE

ii. Insert Text for County and State Boundary labels

iii. Vector Toolbox “Text and Labels” “ Insert Text” from the drop down box.

iv. In the “Insert Text” Dialog box:

Select “BORDERING_CO_LABELS” warehouse from XCity_ warehouse

v. Check the box next to “Override Style”

1. For county labels – Italic, 10, Arial (text should be capital letters)

2. For state labels – Italic, 16, Arial (text should be capital letters)

vi. Type in the correct label in the large white box

vii. Place the label in the correct area in the map

viii. If the label needs to be realigned, highlight the label and then go to Vector tool box and then “Geometry” and select “Spin”

ix. SAVE

P a g e | 32

PART 6: Labeling Positioning and Adjustment

This step seems most beneficial on larger maps with tight downtown areas, requiring extensive manipulation of labels to fit in the space. Using the previous label and symbol placement as a reference can speed up the process. It appears to be more efficient to skip this step on smaller maps.

1. Load Labels from the OLD CITY Map to the current City Map. Change all OLD Labels to red font

LABELINGDISPLAY LABELSChoose warehouse connection:OLD_CitywarehouseADD Labels

City_EXITS_TXT City_HIGHWAYS_TXT City_HYDROGRAPHY_TXT City_MISCELLANEOUS_TXT City_OTHER_ROADS_TXT City_SHIELDS_TXT City_SYMBOL_TXT

Map display Nominal Scale ALL Locatable OFF ALL features just created Locatable ON Select ALL

P a g e | 33

Change Font Color to Red

Adjust Shield placement using the old shields. You can now compare old and new labels and use the old labels to help place new labels.

Red SC-121 shows previous location of shield, which is now on a local road.

Red S-411 is placed where a road has a new name label.

Black S-411 will need a new placement Black S-105 can be placed at location of previous S-105

NOTE: When finished using the old labels remove (turn off or delete) all red features.

P a g e | 34

Miscellaneous Adjustments Adjust Hydro labels, Railroad labels, Map Symbol labels, Names of roads and shields

Do not merely follow this section step by step, but read over entire section to understand the variety of factors influencing placement labels. You may want to skip ahead and put most of display layers in order now. (page. 41)

NOTE: Zoom to “Nominal Scale” (15,840) when deciding what labels need to be moved

a. Basics:

- Label Priority is 1-Shield, 2-Street Label, 3-Symbol Label

- A road name label cannot be smaller than 4.5 pt. font, and a shield 5.0pt

- Symbols should not overlap

- When moving labels, use the “Reposition” tool

OR

- If a label needs to be on one line, use the “Compose Label” tool

- If a label needs to be on two lines, use the “Decompose Label” tool

- When changing properties of label, use the “Change Label Properties” tool

- If a word within the label needs to be split up, add spaces into the text within the Change Label - Properties dialog box

- An individual word may only be split once, creating two parts

P a g e | 35

b. Shields

- Shields with too many numerals, resulting in touching the shield edge, should reduce the font size.

- Where the route numbers overlap and multiple shields are to be displayed the order is I, US, SC, S, and numbering low to high.

- Whenever possible they should touch the road they identify. Only the ID road.

- Use the old map as a guide to move the shields around.

- Center on the line where possible.

- Set to the edge and touch less when the roads get short (< 2x length of shield)

- Don’t cover the end of road or transition of feature type.

- Leader Lines (if necessary) ‘Labeling’ ‘Labeling Options’ Arrow Style: 2 Width: 1 pts

This selection needs to be redefined following each time GeoMedia is closed and then reopened.

If at all possible, avoid crossing over a road. When adding leader lines, use the “Leader” tool. Only add leader lines for Shields

- Abbreviations for Auxiliary Roads.

• If the highway is an auxiliary (CON, ALT, MLC, BUC, BUS, BU1, BU2, SPR, SD1, SD2, CH1, CE1, etc.) the auxiliary label must be placed underneath the route number within the shield (often needs to be reversed).

• The abbreviation must be verified and the font size reduced to fit shield.

• If there is only one auxiliary, we may remove the suffix number: e.g. BU1 BUS

• If there are multiple auxiliaries, then we retain the suffix numbers: e.g. DR1, DR2, etc.

(Unlike county maps, we will not delete auxiliaries from shields.)

P a g e | 36

- Route Overlaps should be identified form the OVERLAPS in LIMITS_AREA feature in the template and labeled with both Shields.

NOTE: If there are adjustments to shield labels, adding or removing, these will be given following Systems review during final checks.

- For EXIT_RAMP Labels, use only one label per exit placed to the side of the interchange

c. Bridges Divided HWYS – some places they overlap and one may need to be turned off for a clear view on map.

d. Insert “false roads” if needed, unlikely. Reference County Map instructions if needed.

e. Insert Feature MASKs

i. Create MASK features (Line or Area) colors white or black in XCity_warehouse folder to meet your personal masking/editing style preference.

ii. Recommended: MASK_WHT area to cover areas in the buffer area or hydro features.

MASK_BLK line to cover roads that do not need to be displayed in buffer area.

iii. Analyst may create a mask feature in Xcity_warehouse or use old hydro masks

iv. The feature may still be imported from the OLD_city folder if needed

HYDRO_MASKs need to be inserted where RIVERS and LAKES meet to create a continuous feature. Locate areas where HYDRO_MASKS need to be inserted

P a g e | 37

3. Layers Priority Level LAYERS Display Order in Map Window (Legend)

Labels / Shields NAME of Feature Text of Neighboring County Names BORDERING_CO_LABELS Hydro Features Text HYDRO_LABELS_TXT

(all TXT listings will include FSM and LDR features) RR text RAILROADS_TXT Highway Shields HIGHWAY_SHIELDS_TXT Leader lines under all shields Exits Shields under all other shields EXIT_SHIELDS ROAD_NAMES Highways HIGHWAY_NAMES_TXT

Other Roads OTHER_ROADS_TXT Public Property label text PUBLIC_PROPERTY_TXT MILITARY Property label text MILITARY_INSTALLATION_NAMES Map Features label text MAP_SYMBOL_LABELS_TXT

Labeling Text above symbol feature

SYMBOLS

No order preference within group.

Anything that overlaps, we move or remove, so display level is irrelevant.

Armory ARMORIES and LIMITS_SQ Park and Ride included Church CHURCHES and LIMITS_SQ Church and Cemetery CHURCH_CEMETERY and LIMITS_SQ Hospital HOSPITAL and LIMITS_SQ School SCHOOLS and LIMITS_SQ Private School PRIVATE_SCHOOLS and LIMITS_SQ Point Of Interest POINT_OF_INTEREST and LIMITS_SQ Cemetery CEMETERIES and LIMITS_SQ Welcome Center and Rest Area WELCOME_REST_AREA and LIMITS_SQ Airport AIRPORTS_and LIMITS_SQ SCDOT Bldg SCDOT_BUILDINGS and LIMITS_SQ Courthouse COURTHOUSE and LIMITS_SQ

P a g e | 38

Other Features Buffer – (a masking buffer) STATE_BUFFER_HOLE fill white, border white .5 pt., translucency 0 near top Mask MASK (city folder) Bridges (Locatable OFF!) BRIDGE_LINE_under_150_SQ_RW (point)

(Locatable OFF!) BRIDGE_LINE_over_150_SQ_RW (line) above roads

“False Roads” FALSE_ROADS OVERLAPS display off Highways HIGHWAYS_AM for_DISPLAY OTHER_ROADS PROPOSED – display off Other Roads OTHER_ROADS_AM_for_DISPLAY

Other roads under Highways State Lines STATE_LINE_and Buffer_SQ County Lines COUNTY_LINES_and Buffer_SQ

GA_COUNTIES_DISPLAY

NC_COUNTIES_DISPLAY

Limits of Map Area LIMITS_OF_MAP_AREA_selection Buffer on Limit (display off) needed for Layout transfer . closelater Buffer Mask STATE_LIMIT_HOLE white fill; white boundary (.5) 0 translucency Public Property mask PUBLIC_PROP and LIMITS_SQ_buffer300 white white Public Property PUBLIC_PROPERTY and LIMITS_SQ

Military/ Government Property just below Public Property Military Mask MILITARY and LIMTS_SQ_buffer300 Military/ Government Property MILITARY and LIMTS_SQ RR below roads RAILROADS_and_Buffer_SQ

Lakes and Rivers LAKESUNDER5_and_LIMITS_SQ LAKESOVER5_and_LIMITS_SQ RIVER_STREAM and LIMITS_SQ Streams line symbol STREAMS and LIMITS_SQ

Streams below all other Hydrography except Wetlands Wetlands WETLANDS and LIMITS_SQ Municipal Hole MUNICIPALinLIMITS_SQbuffer300 Municipal area feature MUNICIPALinLIMITS_SQ HIGHWAYS SQ for LABELS display off OTHER ROADS_ SQ for LABELS display off

P a g e | 39

PART 7: LAYOUT WINDOW

1. Layout window formatting. Copy the old city map layout window marginalia and text and paste it into the new city map layout window so all pertinent information is transfered.

a. OPEN the “OLD” city file geoworksapce and go to the Layout Window.

b. Copy contents of the layout window and paste to layout window in new city geoworkspace layout window.

Legend contents will be lost.

Retains frames and layout and text on your city.

c. Close old Geoworkspace once successfully copied.

P a g e | 40

d. If the LIMITS have been changed: Adjust frame sizes if needed. Should a change in frame size create question about the sheet orientation, Landscape orientation is the preferred layout.

e. If the sheet is too small for the frame, select ‘Page Setup’ and increase the dimensions.

A-Size Landscape 11 x 8.5 inch B-Size Landscape 17 x 11 C-Size Landscape 22 x 17 D-Size Landscape 34 x 22 E-Size Landscape 44 x 34 Custom

2. Revise the Date (remember to reallign center)

3. Edit and realign broken word “particular”

TO

4. Change the GIS/Mapping phone number to (803) 737-3103 and the Room number to 122.

5. Insert Scale Bar

Verify that it is not in need of change of font scale and moved apart.

Scale Bar should be set in template, and reflect the following image.

Font set at Arial Bold 6 pt.

If not, consult separate file for instructions.

L:\MAP_PRODUCTION\City_2016\Scale_Bars_CityMap_Instructions

Check that color is BLACK and not dark gray.

Copying from old Layout Window has often resulted in a change to gray (unknown why?).

P a g e | 41

6. Display Reduce Display area size as needed to reduce ‘white space’.

Adjust frame size accordingly.

Delete blank old city map frame which was copied from the old layout

P a g e | 42

7. Insert MAP

a. Go to “Window” in the Home toolbar and select “Layout Window”

b. Execute a “Fit All” to zoom into the layout template

c. Highlight the inside Map Frame

d. Layout Window Layout tab Map and Maginalia Insert Map

Map window: MapWindow1 Geographic Extent: Existing Shape or Rectangle.

Plot Scale: 15,840 Mode: Dynamic

e. Select OK

f. In the Map Window legend, turn Display ON and Locatable ON for “Buffer_on_LIMIT”

g. In the map, select the blue line (Buffer_on_LIMIT)

h. Select the line again to “snap point on boundary”

i. Go to “Layout Window”

j. Position and click to place

k. Double click the map in the Layout Window “Map Properties” Dialog box opens

l. Select the “General” tab

m. Uncheck “Display Boundary”

n. Select OK

o. Adjust map position in Layout window to match existing Directional arrows (If not there, see next step).

p. In the Map Window legend, turn Display OFF “Buffer_on_LIMIT”

q. SAVE

P a g e | 43

8. Adjust Layout Window

a. In the Layout Window make sure toolbars are displayed. Go to “Drawing” toolbar and select Arrange tools. Tools that need to be selected:

Align, Distribute, Editing, Grouping, Layout, Ordering, Ribbon, Standard

The layout frames need to be 0.25 inches apart with an angle of 45, -45, 135, or -135 degrees

b. SCDOT website needs to be at the bottom left corner of the map

1. Align the name with the inner layout frame

2. SCDOT symbol needs to be centered with SCDOT website

c. Center all title and legend information

d. Make sure there is even “white-space” at the top of the title and the bottom of the legend

9. Change North Arrow to North Arrow with State Shield North arrow should be at the top left corner of the map.

a. Select North Arrow

b. Choose to view Properties (OK when get warning and the North Arrow Properties window will appear)

c. Select Browse Use the North Arrow with the SCDOT shield located in

L:\\CoordinateSEED\SCDOT_North_Arrows\SC_BLACK

P a g e | 44

North Arrow with State Shield

d. Size to 110 pt. – resize as needed

e. Reposition North Arrow if necessary

10. Directional Arrows

P a g e | 45

a. Verify Alignment. SHOULD be in place Standard: Arrow is .6 inches long with 1.0 pt width and a ‘Solid Triangle Small’ arrow at end.

Text is Tahoma 7 pt (First versions were done at 8 pt and needed to be adjusted down)

For I-, U.S. & S.C. routes:

Move arrows present in template.

Copy if needed Rotate to match trajectory of the road Edit contents of text (based on previous…