NJTPA Enterprise GIS (EGIS) User Manual

Transcription

COLLECT
COORDINATE
DATA
DISTRIBUTE
PRODUCE
MAINTAIN
ANALYZE
Quick
Reference
EGIS
User
Manuals
Support
Documents
Appendices
About the EGIS
The NJTPA has embarked upon a year-long project to centrally locate a
wealth of the data at the NJTPA. Some of the data items originate at the
NJTPA but many are generated by partner agencies. To regularize how
data items are stored, updated, and exchanged, a new enterprise-class
geospatial database has been designed. This application will assist users
in accessing, maintaining and exchanging data housed in the NJTPA
Geodatabase.
The database will help to ensure that data are current, accurate and
suitable for particular uses - by NJTPA staff, NJTPA subregions, partner
agencies and the general public. Authorized users will be able to draw
directly from the EGIS database to produce tables, maps, and conduct
their own analyses via websites and map service links.
Quick
Reference
EGIS
User
Manuals
Support
Documents
Appendices
About the Quick Reference Outline
The Quick Reference Outline serves as an at-a-glance document to orient
users with multiple resource documents and resources available in the
enterprise GIS database and the NJTPA Geoportal. The outline describes
the data inventory, how to accessing and working with the data, how to
use the Geoportal and general maintenance.
The outline provides narrative descriptions of highlighted training topic,
step-by-step directions for key tasks, and reference bookmarks for users
that desire more detail.
EGIS User’s Training
I. Introduction to EGIS – What is it?
a. Multi-User access to a dynamically updated Geodatabase
i. A spatially enabled database composed of over 250 tables, GIS
layers and data views generated by NJTPA and partner agencies
b. NJTPA Geoportal
i. A public-facing website containing a catalog of NJTPA and
partner agency data inventory, documentation, contact information,
downloadable data (ArcGIS shapefiles and Excel Tables), map
services (pre-made maps) and other GIS resources
II. Data Inventory
a. Spatial and Non-spatial data generated by NJTPA and partner agencies
i. All data contained in one production database, direct connect
available via authorized access only
b. Using EGIS Database Inventory
i. The EGIS dynamically updated inventory can be viewed on the
NJTPA Geoportal web site:
http://geoportal.njtpa.org:8080/geoportal/catalog/inventory/invento
ry.page
ii. Database naming conventions and representation standardsArcCatalog
Reference: EGIS User Manual pg.-6, Sec. 2
Standards and Representations
Naming Conventions: Database Name vs. Name
⇒ lp_SE2Place vs. Strategy Evaluation 2 Places (l = layer, p=planning, both
letter categories)
How to Read the Database Name and Data Model
The logical data model contains a set of standards and representations as follows.
⇒ Blue tables are business / non-GIS tables, and begin with the letter “t”
⇒ White table are GIS tables, and begin with the letter “l,” followed by a
second letter that denotes the NJTPA GIS data category. The data
framework categories are as follows:
¾
¾
¾
¾
¾
¾
¾
c = Cadastral
d = Design Plans
e = Environmental
f = Facilities
g = General
p = Planning
pb = Political Boundaries
¾ t = Transportation
¾ u = Utilities
1
iii. To organize the data model and to help manage associated with
specific NJTPA tasks, tables are grouped into 14-subject areas.
Reference: EGIS User Manual pg.-7, Sec. 2
#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Name
Capital Program
Strategy Evaluation/Refinement Area
Regional Planning Studies
Air Quality Conformity
NJ Congestion Management System
Transit
Freight Assessment
Census
Safety
New Jersey Regional Travel Model Enhanced (NJRTME)
Socio Economic Forecasting
Land Use
Regional Household Travel Surveys
NJDOT Management Systems
III. Accessing the EGIS Geodatabase
a. Authorized Database Connection – ArcCatalog
Reference: EGIS User Manual, pg.-7, Sec. 3.1
Connecting to Geodatabase
1.
2.
3.
4.
Open ArcCatalog
Double Click “Database Connections” in the left navigation tree window.
Double click “Add Spatial Database Connection”
Enter the information as depicted below included your given password.
2
IV. Working with the Data
a. Adding layers from Geodatabase with authorized access
Reference: EGIS User Manual, pg.-7, Sec. 3.1 (Authorized
Connection)
Adding data from Geodatabase
1. Click ‘Add Data’ button
2. ‘Look in:’ the Database Connections folder locate User connection
to EGIS database (must be create previously in ArcCatalog)
3. Add layers from EGIS database
b. Adding map services available on NJTPA Geoportal to ArcMap
i. Access via NJTPA Geoportal
Opening Map Services from Geoportal
1. Go to:
2.
3.
4.
5.
http://geoportal.njtpa.org:8080/geoportal/catalog/main/home.page
Click the ‘Map Services’ tab
Choose the desired map service by clicking the ‘ArcMap’ link
under the description
Click ‘Open’ button to launch ArcMap automatically.
Expand service and layers as appropriate
ii. Access via ArcCatalog
Connecting to Map Services in ArcCatalog
1.
2.
3.
4.
Go to and expand ‘GIS Server’
Double click ‘Add ArcGIS Server’
Select ‘Use GIS Services’ and click ‘Next>’
Select Internet Server URL:
http://geoportal.njtpa.org/ArcGIS/services and click ‘Finish’
5. Expand service and layers as appropriate in ArcCatalog
3
iii. Access via CS-W Client
Connecting to Map Services in ArcCatalog
1. Download CSW client from
http://www.njtpa.org/DataMap/GIS/Enterpr_GIS/NJTPA_Enterpris
e_GIS.aspx or request the file from zfields@njtpa.org and install it
2. Add CSW Client to Toolbar by going to ‘Tools’ – ‘Customize..’
and typing “CSW Client” in the command box.
3. Drag and drop icon on menu bar and click to launch CSW Client
4. Go to the ‘Configure’ tab and click the “New” icon
5. Enter NJTPA Geoportal in the ‘Display Name’ and enter the
‘Catalog Service URL’as:
http://geoportal.njtpa.org:8080/geoportal/csw/discovery?Request
=GetCapabilities&Service=CSW&Version=2.0.2
6. In the Find tab, choose the NJTPA Geoportal from ‘In Catalog’
7. Select ‘Live Data and Maps Only’
8. Search the NJTPA Geoportal content the “Results” box
4
c. Replicating Database and Map Services
i. Replication options will be explored on an individual agency basis
Reference: EGIS Data Replication and Extraction
d. Extracting Data – ArcMap and NJTPA Geoportal
i. Users must have ArcGIS 9.3.1 or later to extract data directly from
the geodatabase
In ArcMap
1. Add the “Distributed Geodatabase” toolbar, by going to ‘View,’
‘Toolbars,’ ‘Distributed Geodatabase’
2. Select the Extract Data tool on the far right as shown
3. Select a destination for your personal geodatabase
4. Once all the steps of the “Post Data Extraction Options” wizard are
finished, the personal geodatabase will contain the items of initially
chosen map services
From Geoportal: Extract Data and Receive via Email
1.
2.
3.
4.
5.
Click ‘Extract Data’ tab
Click the “Draw desired area” icon:
Draw a polygon around the area of interest
Check the desires data layers in the selection box to the right
Enter a destination e-mail address and click “Extract Data” button
From Geoportal: Download from Dynamic Inventory
1. Click ‘Inventory’ tab
2. Navigate through data available for download by sorting through
pages or “Subject Area” links
3. Click desired ‘Table’ or ‘GIS Layer’
4. Open or save file
e. Using Model Building clipping tool – By NJTPA region or Subregion
Reference: Clip Model Documentation
5
V. Using NJTPA Geoportal
a. The NJTPA Geoportal attempts to centrally locate a wealth of the data
suitable for particular uses - by NJTPA staff, NJTPA subregions, partner
agencies and the general public. This site is intended to orient users on
how to:
i. View the contents of the Geodatabase inventory (Extract Data,
Map Services and Inventory tabs)
ii. Search for items of interest (Home, Search and Inventory tabs)
iii. Link to NJTPA map services and other data resources (Map
Services and Links tabs)
b. Description of the Geoportal
Reference: NJTPA Geoportal User Manual
Header Link
Login
Register
Help
About
Feedback
Tab/Web Page
Home
Search
Extract Data
Map Services
Inventory
Links
Description
Registered users login to geoportal on this page.
Users are able to register for site use by entering organization
and contact information. User group types and privileges are
defined as follows:
¾ Public – Search for data
¾ Registered User – Public privileges plus able to save
search, validate metadata
¾ Publisher – Registered User privileges plus able to
create/upload metadata
¾ Administrator – Publisher privileges plus able to
approve metadata and set restrictions
Administrator assigns users to groups once registration has been
completed.
Launches vendor (ESRI) supported help center site.
Describes available resources and functions of site.
Send feedback to geoportal administrator via email.
Description
Welcome page contains quick links for searching by Framework
Category or Subject Area, as well as links to several other GIS
Resources that may be of interest to the user.
Allows the user to enter keywords to search, use pre-defined
searches based on four NJTPA categories (Subject Area,
Framework, NJTPA Goals, and Legacy).
Allows users to draw a polygon around an area of interest, select
spatial layers to download and send as shapefiles or personal
geodatabase to an email address specified by the user.
Shows an inventory of live map services available to use in
ArcMap, ArcExplorer or Google Earth.
Shows a dynamic table with a complete list of all layers
included in the current version of the NJTPA EGIS. The data
table layers can be downloaded to Excel format while the GIS
layers can be downloaded in ESRI shape format.
Provides the user with many useful web links related to the
planning process.
6
VI. General Maintenance
a. Maintenance Plan – Overview of EGIS User Responsibility
Reference: EGIS User Manual, pg.-5, Table-1
b. Maintenance Schedule (For identified contributors only)
i. First Quarter: July 1st to July 15th
ii. Second Quarter: October 1st to October 15th
iii. Third Quarter: January 1st to January 15th
iv. Fourth Quarter: April 1st to April 15th
c. XML Metadata Maintenance Standards (For identified contributors only)
Reference: Metadata Reference Guide for NJTPA Geoportal
d. Review User Manuals, Support Document and Appendices
i. EGIS User Manual
ii. NJTPA Geoportal User Manual
iii. Support Documents
1. EGIS Data Replication and Extraction
2. Clip Model Documentation
iv. Appendices
1. EGIS Data Model
2. EGIS Data Inventory
3. EGIS Quality Assurance Program
4. Metadata Reference Guide for NJTPA Geoportal
7
Quick
Reference
EGIS
User
Manuals
Support
Documents
Appendices
About the User Manuals
There are two user manuals for the NJTPA Enterprise GIS: 1) the EGIS
User Manual and 2) the NJTPA Geoportal User Manual. These two
document comprehensively explain how to navigate the database and the
Geoportal. Information about the data inventory, how to accessing and
working with the data, how to use the Geoportal and general
maintenance is detail in these two documents with references to support
documents and appendices.
North Jersey Transportation Planning Authority
Enterprise-Class Geodatabase Development
EGIS User Manual
Prepared for:
North Jersey Transportation Planning Authority (NJTPA)
One Newark Center, 17th Floor
Newark, New Jersey 07102-1982
Prepared by:
AECOM USA Inc.
570 Broad Street, 5th Floor
Newark, New Jersey 07102
May 12, 2010
AECOM Project No. 6009942
Enterprise-Class Geospatial Database Development
EGIS User Manual
_______________________________________________________________________
Document Revision History
Version
Version 1 –
Outline Draft
Version 2 – Draft
1
Version 2 – Draft
2
6/8/2010
Date
April 16th,
2010
May 3rd, 2010
May 12th,
2010
File Name
EGIS User Manual – Guidelines Outline Draft – 04.16.2010
EGIS User Manual - Guidelines Draft 1 - 05.03.2010.doc
EGIS User Manual - Guidelines Draft 2 - 05.12.2010
2
Comments
First Draft; Submitted
via email
Submitted via FTP
Submitted via FTP;
Incorporates NJTPA
comments from
5.11.2010
EGIS User Manual
_______________________________________________________________________
Table of Contents
1. 2. INTRODUCTION ...................................................................................................... 4 USING EGIS DATABASE INVENTORY................................................................ 6 Naming Standards........................................................................................................... 6 Subject Areas .................................................................................................................. 6 3. EGIS ACCESS ........................................................................................................... 7 3.1 Geodatabase Access ............................................................................................. 7 3.2 Geoportal Access.................................................................................................. 8 4. WORK FLOW ............................................................................................................ 9 4.1 Exchange Mechanism .......................................................................................... 9 4.2 Map Services ...................................................................................................... 10 4.3 Exchange Schedule ............................................................................................ 10 5. METADATA MAINTENANCE.............................................................................. 10 6. DATA SECURITY................................................................................................... 10 6.1 Custodian Contact Information .......................................................................... 10 6.2 Data Use Constraints.......................................................................................... 11 6.3 Distribution Liability.......................................................................................... 12 TABLES
Table 1 - EGIS User Responsibility Overview................................................................... 5 Table 2 - Data Model Subject Areas................................................................................... 7 Table 3 - Geoportal Users ................................................................................................... 8 Table 4 - Geoportal Functions ............................................................................................ 9 Table 5 - EGIS Agency Contacts...................................................................................... 11 FIGURES
Figure 1 - Direct Connection to EGIS Databases ............................................................... 8 Appendix U1 – EGIS ER Data Model
Appendix U2 – EGIS Data Inventory
Appendix U3 – EGIS Quality Assurance Program
Appendix U4 – NJTPA Geoportal User Manual
Appendix U5 – EGIS Data Exchange Schedule
Appendix U6 – Metadata Reference Guide for NJTPA Geoportal
6/8/2010
3
EGIS User Manual
_______________________________________________________________________
1.
INTRODUCTION
The North Jersey Transportation Planning Authority (NJTPA) has undertaken the Enterprise
Geographic Information System database (EGIS) project, contained in the agency’s Unified
Planning Work Program (UPWP) for 2009. The goal of the project is to consolidate the agency’s
data into a single, web-enabled platform and to improve information sharing among the project
EGIS participants.
The database will help to ensure that data are current, accurate and suitable for particular uses by
participants: NJTPA staff, NJTPA subregions, partner agencies and the general public.
Authorized users will be able to draw directly from the EGIS database to produce tables, maps,
and conduct their own analyses via websites and map service links.
This manual details the following EGIS user functions: navigating the database inventory,
accessing the data, coordinating data workflow, maintaining proper metadata and verifying data
validity. Table 1 provides an overall user guide to the NJTPA EGIS.
6/8/2010
4
Table 1 - EGIS User Responsibility Overview
#
1
What
Inventory
•
•
2
3
Access
Workflow
•
•
•
•
Who
Maintained by
NJTPA
Contributed to by sub
regions and other
EGIS partner
agencies
NJTPA Central Staff
Non-NJTPA Central
Staff
•
•
•
•
•
Scheduled Data
Exchange:
Data consumption
via:
- Geoportal
- Map Services
•
•
4
Metadata
Maintenance
All EGIS participants
5
Data Security
All EGIS participants
•
How
Geodatabase storage
FTP drop-off in year
one
Direct geodatabases
transfer in year two
•
•
When
Data maintained
continuously by
NJTPA
Quarterly data
submissions by sub
regions and other
EGIS partner
agencies
Public web access to
Geoportal and GIS
application
Credentialed access to
Geodatabase
Continuous
FTP Drop-off in year
one
Direct geodatabase
transfer in year two
Quarterly
Credentialed access accounts are
provided by Zenobia Fields,
Principal Planner, at NJTPA:
zfields@njtpa.org
URL Web Site
Create metadata in
ArcCatalog for ESRI
objects
• Equivalent for non
ESRI objects e.g.
spreadsheets
Data release/use form
Notes
All data submissions to NJTPA
should conform to its quality
assurance requirements, detailed
in this document and Appendix
U3 – EGIS Quality Assurance
Program.
As required
As required
Geoportal Website is:
http://geoportal.njtpa.org:8080/ge
oportal/
Map Services can be accessed via
both Geoportal and ArcCatalog
methods
• All EGIS metadata conforms
to FGDC standards
• Non ESRI data items should
be provided to NJTPA with a
suitable metadata sheet
Forms are provided by NJTPA
2.
USING EGIS DATABASE INVENTORY
The NJTPA maintains an inventory of over 250 tables (GIS layers and views) within its
Geodatabase. It also maintains map services to graphically depict these items. Some of the data
items originate at the NJTPA but many are generated by partner agencies. The EGIS Geodatabase
will serve as a mechanism to regularize how data items are stored, updated, and exchanged
through a compulsory set of data storage standards. Before a data item is checked into the
Geodatabase and made part of the official inventory, it is reviewed against NJTPA’s quality
assurance program.
The Geodatabase was developed around a relational database model. The Data Model and Data
Inventory table are available for review in Appendix U1 – EGIS ER Data Model and Appendix
U2 – EGIS Data Inventory respectively. The EGIS inventory can also be viewed on the NJTPA
Geoportal web site.
http://geoportal.njtpa.org:8080/geoportal/catalog/inventory/inventory.page
The table naming and organizational standards are presented below.
Naming Standards
•
•
Regular tables are depicted as white in the data model and begin with “t_” e.g. t_Project
Spatial layers are depicted as blue in the data model and begin with the letter “l” followed
by a second letter that denotes the NJTPA GIS data category, referred to as data
framework categories:
¾
¾
¾
¾
¾
¾
¾
¾
¾
c = Cadastral
d = Design Plans
e = Environmental
f = Facilities
g = General
p = Planning
pb = Political Boundaries
t = Transportation
u = Utilities
e.g. lp_SE2Place
•
For table naming conventions beyond the table and layer prefixes, refer to Appendix U3
– EGIS Quality Assurance Program, Table 7.
Subject Areas
To facilitate organization of the data model and to help NJTPA manage specific areas of its
business processes, the tables are grouped into 14 sub-subject areas enumerated in Table 1.
EGIS User Manual
_______________________________________________________________________
#
Table 2 - Data Model Subject Areas
Description
Main
Composite of all tables and subject areas
Capital Program
Tables associated with the NJTPA’s Capital Program
Strategy
Tables associated with the NJTPA’s strategy evaluation areas
Evaluation/Refinement Area
Tables associated with the NJTPA’s regional planning studies
Tables associated with the NJTPA’s air quality conformity
process
NJ Congestion Management
Tables associated with the NJTPA’s congestion management
System
process
Transit
Tables associated with New Jersey’s transit operations and
ridership
Freight Assessment
Tables associated with New Jersey’s freight quintiles and
movements
Census
Tables associated with the federal census bureau
Safety
Tables associated with NJDOT’s traffic accident database
New Jersey Regional Travel
Tables associated with the NJTPA’s regional travel demand
Model Enhanced (NJRTME)
model
Tables associated with the NJTPA’s socioeconomic data
Land Use
Tables associated with land use and environmental screening
Regional Household Travel
Tables associated with Census-based household surveys
Surveys
NJDOT Management
Tables associated with the NJDOT’s management systems data
Systems
Name
1
2
3
4
5
6
7
8
9
10
11
12
13
14
3.
EGIS ACCESS
Access to EGIS resources is either through direct Geodatabase access via ArcGIS or through
indirect access via the internet or through.
3.1
Geodatabase Access
Direct access to the NJTPA Geodatabase is provided by NJTPA central staff in the form of a user
login account. Each account will have a specific set of permissions that determine which tables
and GIS layers are viewable and which are restricted. Restrictions are at the discretion of the data
custodian. A list of the EGIS tables, their permissions levels, and their custodians is provided in
Appendix U2 – EGIS Data Inventory. The contact information for each custodian can be found
in section 6, should a user have interest in a restricted item.
Connecting to Geodatabase
1.
2.
3.
4.
Open ArcCatalog
Double Click “Database Connections” in the left navigation tree window.
Double click “Add Spatial Database Connection”
Enter the information as depicted below included your given password.
6/8/2010
7
EGIS User Manual
_______________________________________________________________________
Figure 1 - Direct Connection to EGIS Databases
3.2
Geoportal Access
The URL address for the NJTPA Geoportal is http://geoportal.njtpa.org:8080/geoportal/
The Geoportal is governed by user a hierarchy presented in Table 3.
Table 3 - Geoportal Users
User Type
Public
Registered User
Publisher
Administrator
Search
for
Data
√
√
√
√
Save
Search
Validate
Metadata
Create/
Upload
Metadata
Approve
Metadata
Set Access
√
√
√
√
√
√
√
√
√
√
A summary of Geoportal functions is listed in Table 4.
6/8/2010
8
EGIS User Manual
_______________________________________________________________________
Table 4 - Geoportal Functions
Geoportal Page
HOME
SEARCH
EXTRACT
DATA
MAP SERVICES
INVENTORY
LINKS
Description
Welcome page for the NJTPA Geoportal. Contains quick links for
searching by Framework Category or Subject Area, as well as links to
several other GIS Resources that may be of interest to the user.
The Search Page allows the user to enter text to search, as well as predefined searches well as the four NJTPA categories (Framework, Legacy,
Subject Area and Goals). Additional search parameters allow users to filter
by content type, date, or ISO category or to arrange your search results by
relevance, type, date or alphabetical order.
The Extract Data page allows users to draw a polygon around an area of
interest, select spatial layers to download and a map projection and the
application will clip out those layers and send as shapefiles to an email
address specified by the user.
The Map Services page shows an inventory of live map services available
via the NJTPA Geoportal. For each service, users have the option of
previewing the map service in a web page or opening the map service in
The Inventory page shows a dynamic table with a complete list of all
layers included in the current version of the NJTPA EGIS. The data table
layers can be downloaded to Excel format while the GIS layers can be
downloaded in ESRI shape format.
The Links page provides the user with many useful web links related to the
NJTPA Planning Process.
Appendix U4 – NJTPA Geoportal User Manual describes the Geoportal user interface.
4.
WORK FLOW
4.1
Exchange Mechanism
FTP – For year one of the EGIS project, an EGIS FTP site will be the repository for incoming
data. The FTP site is ftp://apps.NJTPA.org/egis. Login credentials to the FTP site are available
from the NJTPA. Once data items are placed on the FTP site, the NJTPA reviews them for
quality assurance based on its Quality Assurance program and subsequently places the items in its
GDB_PROD production database where it is available for use in other applications, and is added
to the EGIS Dynamic Inventory Table via the process described above. These items are than
available for public use via download.
Geodataservice – For year two of the EGIS development, participating agencies will have the
option to push their data directly from ArcCatalog into an EGIS Geodatabase, avoiding the need
to place information on an FTP site. This process entails geodatabase to geodatabase data
transfer.
6/8/2010
9
EGIS User Manual
_______________________________________________________________________
4.2
Map Services
The NJTPA also distributes its data by placing a collection of data sets inside a map file and
publishes it in the form of a map services on its Geoportal web site, on the Map Services tab.
Map services can also be consumed in ArcGIS by connecting to
http://geoportal.njtpa.org/arcgis/services through the GIS Server node in ArcCatalog.
Initial map services will include:
1. Subregion Package (Land Use, Zoning, County Projects, Traffic Counts, Parcels, Trials
and other layers where available)
2. NJTPA’s Six Agency Goals
a. Accessibility (Transit Ridership with Transit layers including PATH)
b. Environmental Screening (Pollutant Tables and Various Environmental
Evaluation layers)
c. Economic Activity (Census per Capita Income, Rail Freight, Truck Corridors,
Airport Freight by Municipality and County)
d. Intermodal Connectivity (Average Travel Time to Work, Congestions Delay by
County and Roadway Network)
e. Safety and Maintenance (Roadway Network, Safety layers, Bridge
Management and Pavement Management)
f. Land Use and Transportation Systems (VMT Results, Density of Settled Land,
2000 US Census Population by County, Demographic Projections,
3. NJTPA Projects (TIP, PDWP, Strategy Evaluation/Refinement, and Confirmity)
4. Transit (NJ Transit and PANYNJ)
5. NJDEP Package
6. NJDOT Package
4.3
Exchange Schedule
EGIS data sharing participants conform to a quarterly data submission process with NJTPA. See
Appendix U5 – EGIS Data Exchange Schedule for the agency data sharing schedule.
5.
METADATA MAINTENANCE
Metadata is the responsibility of the data custodian. Before it publishes metadata to the
Geoportal, NJTPA ensures that all information complies with FGDC metadata standards. NJTPA
requests that all data items submitted to the EGIS contain proper metadata as part of any ESRI
object (GIS layers and tables). Data items submitted in other formats should contain equivalent
descriptions. Appendix U6 – Metadata Reference Guide for NJTPA Geoportal, contains a stepby step guide for creating proper metadata in ArcCatalog.
6.
DATA SECURITY
6.1
Custodian Contact Information
Table 5 lists the EGIS agency participants and their corresponding contact information. Any
issue related to proprietary or use-restrictions should be addressed through these individuals.
6/8/2010
10
EGIS User Manual
_______________________________________________________________________
Table 5 - EGIS Agency Contacts
#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
Agency
NJTPA (Systems Planning)
NJTPA (Information Technology)
NJTPA (Finance & Administration)
NJTPA (Freight Planning)
NJTPA (Regional Planning)
NJTPA (Capital Programming)
NJTPA (External Affairs)
NJTPA (Public Affairs)
Morris County
Sussex County
Warren County
Warren County
Passaic County
DVRPC
PANYNJ
NYMTC
NJDOT
NJOGIS/NJOIT
NJDEP
NJ TRANSIT
6.2
Contact
Zenobia Fields
Veronica Alcon
Keith Miller
Brian Fineman
Chris Roche
Igor Sorin
David Colon
Beth Johnson
Jakub Rowinski
Hamou Meghdir
Zhen Liu
Ted Ritter
Mark Solof
John Hayes
David Kunz, GISP
Brian Appezzato
Albert Krouse
Michael Lysicatos
Will Stevens
Kevin Maddox
Munnesh Patel
Gary Zayas
Edith Konopka
John Bocchino
Glenn Newman
e-mail
zfields@njtpa.org
valcon@njtpa.org
kmiller@njtpa.org
fineman@njtpa.org
rochecc@njtpa.org
sorin@njtpa.org
dcolon@njtpa.org
ejohnson@njtpa.org
jrowinski@njtpa.org
hmeghdir@njtpa.org
zliu@njtpa.org
tritter@njtpa.org
solof@njtpa.org
JHayes@co.morris.nj.us
dkunz@sussex,nj.us
bappezzato@co.warren.nj.us
akrouse@co.warren.nj.us
mlysicatos@passaiccountynj.org
wstevens@dvrpc.org
kmaddox@panynj.gov
mpatel@dot.state.ny.us
Gary.Zayas@dot.state.nj.us
edith.konopka@oit.state.nj.us
john.bocchino@dep.state.nj.us
GNewman@njtransit.com
Data Use Constraints
The North Jersey Transportation Planning Authority ("NJTPA") Data Distribution Agreement
requires users to abide by the following terms and conditions:
Terms of Agreement
1. Use:
The information provided here was compiled by the NJTPA. Redistribution or any other
use is prohibited. Upon completion of the Project, Licensee will return this Data to
NJTPA and delete any copies on Licensee's computers or networks.
2. Data Sources:
Licensee agrees to list NJTPA as the data source on any product of which this Data is a
part such as NJDOT and NJ Transit.
3. Use Restrictions:
There are no use restrictions on the data provided/List use restrictions.
6/8/2010
11
EGIS User Manual
_______________________________________________________________________
4. Disclaimer
No warranties or representations are expressed or implied regarding this Data.
5. Confidentiality
Users agree to hold all information concerning the Data in trust, to take all reasonable
steps to safeguard the Data, and to prevent unauthorized disclosure thereof.
6.3
Distribution Liability
Information contained herein is provided for informational purposes only. The North Jersey
Transportation Planning Authority provides geographic information systems (GIS) data and
metadata with no claim as to the completeness, usefulness, or accuracy of its content, positional
or otherwise. The agency and employees make no warranty, express or implied, and assume no
legal liability or responsibility for the ability of users to fulfill their intended purposes in
accessing or using GIS data or metadata or for omissions in content regarding such data. The data
on this site could include technical inaccuracies and typographical errors. The data on this site is
presented "as is," without warranty of any kind, including, but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement. Your use and
browsing of information on this site is at your own risk. In providing this data or access to it, the
agency assumes no obligation to assist the user in the use of such data or in the development, use,
or maintenance of any applications applied to or associated with the data or metadata.
You are encouraged to contact citation agency directly to verify data validity. Data last updated
Februray 2010.
6/8/2010
12
Table of Contents
1.
2.
3.
4.
INTRODUCTION ...................................................................................................... 2
NJTPA GEOPORTAL SECURITY ........................................................................... 2
NJTPA GEOPORTAL USER GUIDE ....................................................................... 3
METADATA AND XML........................................................................................... 9
TABLES
Table 1 - Geoportal Security Hierarchy .............................................................................. 3
Table 2 - NJTPA Geoportal Summary................................................................................ 3
Table 3 - Metadata Search Results...................................................................................... 7
FIGURES
Figure 1 - ESRI® Geoportal Technology White Paper, October 2009 .............................. 2
Figure 2 - NJTPA Geoportal Welcome Page ...................................................................... 4
Figure 3 - Downloading a GIS Layer to a Zip File. ............................................................ 6
Figure 4 - NJTPA Geoportal Search Page .......................................................................... 6
Figure 5 - Google Earth showing NJTPA Geoportal search results ................................... 9
_______________________________________________________________________
1.
INTRODUCTION
The NJTPA Geoportal provides a public interface to the Enterprise Geographic Information
Systems (EGIS) project by allowing users to search metadata and to find out what GIS data is
available for use in the planning process. The NJTPA Geoportal will allow NJTPA staff,
subregions and other interested parties to discover what data NJTPA and other agencies have
available and how that data can be acquired.
The NJTPA Geoportal is a web browser based application that can be accessed by anyone over
the internet to search metadata that has been uploaded to the site and approved as complete by the
NJTPA Geoportal Administrator. Figure 1 Shows the Geoportal concept.
Figure 1 - ESRI® Geoportal Technology White Paper, October 2009
2.
NJTPA GEOPORTAL SECURITY
The NJTPA Geoportal contains four levels of access (Public, Registered Users, Publishers and
Administrators). The NJTPA Geoportal allows anyone to search for metadata to find out what
data is available and who to contact to gain access to the data. The access to the data itself is
determined by the policy of the owner agency of the data. Additionally, metadata records can be
restricted so that they will not appear in search results for users other than Publisher or
Administrator level users.
Anyone can become a registered user with the NJTPA Geoportal by filling out a short form and
entering a valid email address. Registered users can save searches and validate metadata but
7/22/2010
2
_______________________________________________________________________
cannot publish new metadata to the Geoportal. In order to publish metadata to the NJTPA
Geoportal, a registered user must be added to the Publisher group by the NJTPA Geoportal
Administrator. Members of the Publisher group have the ability to create or upload new metadata
to the site to add it to the Administrator’s queue. Before the uploaded metadata can be seen in the
search results by other users, it must be reviewed and approved by the NJTPA Geoportal
Administrator. Table 1 below shows the matrix of user types and the privileges assigned to each
type:
Table 1 - Geoportal Security Hierarchy
User Type
Public
Registered User
Publisher
Administrator
3.
Search
for
Data
√
√
√
√
Save
Search
Validate
Metadata
Create/
Upload
Metadata
Approve
Metadata
Set Access
√
√
√
√
√
√
√
√
√
√
NJTPA GEOPORTAL USER GUIDE
The NJTPA Geoportal is a web browser application used to search metadata for GIS and other
data that is relevant to the NJTPA planning process. This section of the documentation will
provide a guide to using the NJTPA Geoportal application to search and publish metadata. Figure
2 shows the NJTPA Geoporatal website. Table 2 provides a summary of the Geoportal functions.
Table 2 - NJTPA Geoportal Summary
Geoportal Page
HOME
SEARCH
EXTRACT
DATA
MAP SERVICES
INVENTORY
7/22/2010
Description
Welcome page for the NJTPA Geoportal. Contains quick links for
searching by Framework Category or Subject Area, as well as links to
several other GIS Resources that may be of interest to the user.
The Search Page allows the user to enter text to search, as well as predefined searches well as the four NJTPA categories (Framework, Legacy,
Subject Area and Goals). Additional search parameters allow users to filter
by content type, date, or ISO category or to arrange your search results by
relevance, type, date or alphabetical order.
The Extract Data page allows users to draw a polygon around an area of
interest, select spatial layers to download and a map projection and the
application will clip out those layers and send as shapefiles to an email
address specified by the user.
The Map Services page shows an inventory of live map services available
via the NJTPA Geoportal. For each service, users have the option of
previewing the map service in a web page or opening the map service in
The Inventory page shows a dynamic table with a complete list of all
layers and tables included in the current inventory of the NJTPA EGIS.
The data table layers can be downloaded to Excel format while the GIS
layers can be downloaded in ESRI shape format.
3
_______________________________________________________________________
LINKS
The Links page provides the user with many useful web links related to the
NJTPA Planning Process.
Figure 2 - NJTPA Geoportal Welcome Page
Home Page
Upon opening the NJTPA Geoportal web application in your web browser, you will be greeted by
the home page as in Figure 2. Below the welcome message, there are two boxes that contain
some links and pre-defined search filters that can provide a quick way for users to find what they
are looking for.
In the left box, the NJTPA Framework Categories are listed. Clicking on one of the categories
takes the user to the Search page with the search results for that category displayed. Similarly, the
7/22/2010
4
_______________________________________________________________________
Subject Areas in the right box provide pre-defined search filters that will take the user to the
search page with the results for that subject area shown. Also in the right box are some links to
other resources that may be of use to the end user.
On the home page, there are several links that will take you to various sections of the application.
The links in the top right of the page will be visible on any page of the NJTPA Geoportal. These
links have the following functions:
Login: This link will allow you to enter your username and password to gain privileges assigned
to your account.
Register: The NJTPA Geoportal allows users to register and create a username and password for
logging in to the site. Once a user has registered, NJTPA can determine whether to give them
Publisher or Administrator privileges.
Help: The NJTPA Geoportal has targeted help that opens in a new browser window, and gives
you information based on the page you are looking at. For example, if you clicked the Help link
while on the Register page, it would open to the help section that describes how to register with
the Geoportal.
About: This link tells the user some basic information about NJTPA and the NJTPA Geoportal.
Feedback: Clicking on the Feedback link opens up a form where the user can fill out their email
address and submit feedback to the NJTPA Geoportal Administrator. The user will get a
confirmation email and their feedback will be sent to the geoportal@njtpa.org email address.
Home: Returns user to the Welcome Screen shown in Figure 2.
Search: The Search page that contains some more options for searching (Figure 3).
Download: The Download page contains an application that allows the user to draw a polygon on
a map and select the layers that they want to download. The NJTPA Geoportal will clip the data
to the polygon selected, compile the data into a zip file and then email it to the user.
Map Services: The Map Services page shows the live web map services available from the
NJTPA Geoportal, and has links for users to consume these services in ArcMap, Google Earth or
a web browser.
Inventory: The Inventory page contains a table that shows all the tables and feature classes that
make up the NJTPA EGIS. Anyone of these items can be downloaded by placing your mouse on
the item. Figure 3 shows the ability to download a GIS Layer.
7/22/2010
5
_______________________________________________________________________
Figure 3 - Downloading a GIS Layer to a Zip File.
Links: The Links page contains many links relevant to the NJTPA EGIS project and the NJTPA
planning process.
Search Page
On the Search page as shown in Figure 3, there are several options for searching metadata. Most
prominently, there is a search bar where you can enter text parameters on which to search for
metadata. For example, if you entered “boundaries” into the search box, the results would include
any metadata that has the word boundaries in the title, abstract or other text fields.
Figure 4 - NJTPA Geoportal Search Page
7/22/2010
6
_______________________________________________________________________
On the right side of the Search page, there are Search Filters defined for each Framework
Category, Legacy Category, Subject Area and NJTPA Goal. Clicking on one of these Search
Filters automatically returns all metadata items that fall into that category. This is a quick way to
find all data relevant to a particular subject or planning process.
Below the main search bar there is a drop-down for Content Type. This drop-down can be used to
filter the search results by one of several content types, including Downloadable Data, Live Map
Services, Offline Data, etc.
Just below the Content Type drop-down are links for a directed search (Search In), detailed
search (Search Criteria) and Clear. If you click the “Search In” link, a window will pop up that
allows you to choose whether you want to search the NJTPA Geoportal, ESRI’s ArcGIS Online
content, or the Geospatial One Stop GIS Portal. If you select an option besides the NJTPA
Geoportal, the search results will be formatted the same, but the content will actually be coming
from another source.
The “Search Criteria” link also opens a pop up window, which will allow the user to adjust the
search criteria by ISO data category (Administrative and Political Boundaries, Cadastral, etc) or
by date range. Also, the user can select how to sort the search results, either by relevance to the
search term, title (alphabetical), content type, date, or the area of the bounding box. The Clear
button will clear out any of the Search In or Search Criteria options you have previously selected.
The metadata search results can contain some or all of the links below the metadata title and
abstract text. These items are listed in Table
Table 3 - Metadata Search Results
Link
Open
Preview
Globe (.kml)
Globe (.nmf)
ArcMap
7/22/2010
Action
If the search result is a live web map service, then clicking on the Open link
will open the ArcGIS Server map service information page in a new
browser window. This page shows the parameters of the ArcGIS Server
map service, including the layer information, bounding box, and also links
to view the service in a simple Javascript (web browser) viewer, Google
Earth or ArcMap. If the search result is for downloadable data, the Open
link will open the URL where the user can download the data. If the search
result is for offline data, the Open link will not be shown.
The Preview link is available for live web map services only. Clicking on
the Preview link opens a new window that shows a preview of the web map
service along with some metadata information.
The Globe (.kml) link is available for live web map services only. Clicking
on Globe (.kml) gives you the option to open or save a KML file. The KML
file can be viewed in Google Earth, as long as it has been installed on the
user’s computer.
The Globe (.nmf) link is available for live web map services only. Clicking
on Globe (.nmf) gives you the option to open or save a NMF file. The NMF
file can be viewed in ArcGIS Explorer, as long as it has been installed on
the user’s computer.
The ArcMap link is available for live web map services only. Clicking on
7
_______________________________________________________________________
Details
Metadata
Zoom To
ArcMap opens a MXD file in ArcMap, complete with layers in the Table of
Contents that can be turned on and off. This is a very quick and direct way
to bring web map services into the GIS desktop environment.
Clicking on the Details link opens a new page with full metadata details in
an easy to read format including bounding box, live map preview (if
available), and contact information for acquiring the data.
Clicking on the Metadata link opens the XML version of the full metadata,
without formatting.
Clicking on Zoom To causes the map viewer on the Search Page to zoom to
the extents of the selected metadata record.
Also shown on the search page is a live map service that shows the geographic extents of each
search result. As you put the mouse over an item in the search results, it highlights the result text
and the corresponding bounding box in the map viewer. If you click on a search result, the item
expands and shows the metadata abstract as well as several new links such as Details, Metadata,
Zoom To, and others, based on whether it is a live web map service, downloadable data or offline
data.
The other available functions on the search page include the ability to save your search
parameters for future use (if logged in as a registered user). After entering the search parameters
and clicking the search button, click on My Saved Searches, give the search a descriptive name
and click Save. Next time, clicking on My Saved Searches will show a list of all the previously
saved searches. Clicking on a saved search will automatically enter all the search parameters that
were entered prior to saving and naming the search. This is especially useful if the user will often
be searching for similar data.
Additionally, you can save the search results as an RSS feed, which can be viewed in a RSS
Reader such as Google Reader or Apple Mail. There are several formats available to save the
RSS feeds (GEORSS, ATOM, HTML, etc), making it useful for almost every possible type of
reader application. When new metadata is added to the Geoportal that matches your search
results, the RSS feed will be immediately updated to reflect the new results. You can even open
the search results in Google Earth by clicking on the KML link.
7/22/2010
8
_______________________________________________________________________
Figure 5 - Google Earth showing NJTPA Geoportal search results
4.
METADATA AND XML
Creating metadata in ArcCatalog is the foundation of populating the Geoportal with
content. After a metadata item is created, an XML document is published to the
Geoportal. After it is approved, it is processed and made available on the NJTPA
Geoportal web site where it is searchable, can be previewed, and downloaded from the
Inventory tab. Quality metadata is essential for the success of the Geoportal. Please refer
to Appendix U6 - Metadata Reference Guide for NJTPA Geoportal for creating
geoportal-ready metadata items in ArcCatalog. FGDC compliant metadata is a
prerequisite for submitting data items to the NJTPA Geoportal.
7/22/2010
9
Quick
Reference
EGIS
User
Manuals
Support
Documents
Appendices
About the Support Documents
For general users, the main support documents of concern are the EGIS
Replication and Extraction and the Clip Model Documentation
documents. The Data Replication and Extraction document explains how
to automate the maintenance of the most current NJTPA database on
user’s local computer or network. The document also describes how to
extract individual data layers from the database and geoportal. The Clip
Model Documentation details the procedure for clipping GIS layers by
geographic areas, in this case by the NJTPA region or individual
counties.
EGIS - Data Replication and Extraction
Prepared for:
Prepared by:
AECOM USA Inc.
June 7th, 2010
EGIS - Data Replication and
Extraction
_______________________________________________________________________
Document Revision History
Version
Version 1 – Draft
Date
June 3rd, 2010
Version 2 – Draft
June 7th, 2010
7/22/2010
File Name
EGIS Data Replication - Draft 1 06.03.2010
EGIS Data Replication and
Extraction - Final - 06.07.2010
2
Comments
Submitted via FTP
Submitted via email
Extraction
_______________________________________________________________________
Table of Contents
1.
2.
INTRODUCTION ................................................................................................... 4
DATA REPLICATION AND EXTRACTION STEPS ............................................ 5
2.1 Publish Geodata Service .................................................................................... 5
2.2 Consume Geodata Service ................................................................................. 7
3. DATA REPLICATION AUTOMATION .............................................................. 10
3.1 Deploy Python Script ...................................................................................... 10
3.2 Windows Task Scheduler ................................................................................ 12
4
INTERAGENCY WORK-FLOW .......................................................................... 14
TABLES
Table 1 - Replication versus Extraction ........................................................................... 4
Table 2 - Python Script Variables .................................................................................. 12
FIGURES
Figure 1 - Sample Data Transfer Work-flow .................................................................... 5
Figure 2 - Data Replication Process Detail....................................................................... 9
Figure 3 - Python Shell and Sample Script ..................................................................... 11
Figure 4 - Windows Task Scheduler .............................................................................. 13
Figure 5 - Data Transfer Decision Path .......................................................................... 14
7/22/2010
3
Extraction
_______________________________________________________________________
1.
INTRODUCTION
The information below describes two alternative methods of transferring data from one
geodatabase, such as an NJTPA sub-region geodatabase, to another geodatabase, such as an
NJTPA EGIS geodatadatabase like GDB_STAGE.
1.1
Replication – The process of transferring data from a source geodatabase to a
destination geodatabase where the source is the parent and the destination is the child.
The child replica is dependent on the parent replica through synchronization.
Replication is a good strategy for scheduled data transfer. Data replication offers the
benefit of data transfer automation, in relation to other methods such as FTP transfer.
1.2
Extraction – The one-time process of transferring data from one geodatabase to another,
akin to copy and paste. Extraction enables one-time downloading of data through
ArcMap into a personal geodatabase format from a map/geodata service.
These processes can overlap, be used in conjunction with each other, or be used separate of each
other, depending on the data transfer requirements. Both processes are implemented by
publishing a geodata service in the ESRI ArcGIS Server software.
Some of the differences between Replication and Extraction are highlighted in Table 1.
Table 1 - Replication versus Extraction
#
1
2
3
4
Replication
Advantages
Disadvantages
Allows for
Requires replica
dynamic
maintenance
synchronization
No need for FTP Requires version
maintenance
Extraction
Advantages
Disadvantages
Does not require
Can not be scripted
replica maintenance
Can be used with
map services
Does not allow for
dynamic data
synchronization
Can be scripted
Can be used with
map services
This document describes 1) the two data transfer methods and 2) data replication automation.
The document presents generic data transfer alternatives. Implementation will require close
collaboration with EGIS partner agencies to select a specific process. However, NJTPA can
implement data extraction as a way to provide an additional data download option to EGIS
partner agencies and the public.
7/22/2010
4
Extraction
_______________________________________________________________________
2.
DATA REPLICATION AND EXTRACTION STEPS
Data replication and extraction occurs in two phases 1) publishing a geodata service by a host
source e.g. NJTPA EGIS partner agency and 2) consuming the geodata service at a destination
location e.g. NJTPA or through a web browser in conjunction with ArcMap. Figure 1 presents a
sample work-flow where a sub region publishes a geodata service to be consumed by NJTPA.
This example uses the ArcGIS Server Manager as the tool to illustrate how to create a geodata
service. ArcCatalog can also be used.
Figure 1 - Sample Data Transfer Work-flow
2.1
Publish Geodata Service
The following steps make data available for replication into an EGIS Geodatabase and for
extraction into a personal geodatabase. These steps are carried out by the organization that is
hosting the data to be replicated or extracted. Note that creating a geodata service with a map
service is the preferred method.
2.1.1 Prepare data for replication and or extraction (ArcCatalog)
Replication:
7/22/2010
5
Extraction
_______________________________________________________________________
Connect to a data source with a user account that has write permissions
Register the data set(s) to be replicated as versioned
Make sure the data sets(s) to be replicated are versioned without the option to
move edits to base
Each data set must have a GlobalID column
All spatial data must be stored in high precision
Extraction:
No preparation is required for data extraction
2.1.2 Create map file of data to be replicated or extracted (ArcMap)
Consider the intended beneficiary of the data that is being prepared for
consumption.
Add the data items that were prepared in step 2.1.1 to an ArcMap session
Save the map file (*.mxd) where it can be accessed by ArcGIS Server
2.1.3 Publish map service (ArcGIS Server)
Log into ArcGIS Server Manager and select the Services tab on the left
Choose ‘Publish a GIS Resource’ at the top of the page
Choose the mxd file created in step 2.1.2 as the basis for the GIS map
resource
In the next page, click the Geodata capability to associate the map service
with a geodata service. This steps points the map file to a data source, in the
form of a geodata service and enables a user to access the data content via the
service. This step, by default, enables data extraction through the map
service in ArcMap.
In the services list, the map service is now coupled with a geodata service. These services work
together, but can also be utilized independently. The map service can be published to the NJTPA
Ggeoportal. When a user opens this map service in ArcMap, the service can be downloaded in a
personal geodatabase format.
2.1.4 Add Replication capability to the geodata service
To enable data replication, one additional step is necessary.
In the Manage Resources page, edit the geodata service created in step 2.1.3
Select the Capabilities tab and click the Replication option at the bottom of
the page
7/22/2010
6
Extraction
_______________________________________________________________________
Note that the Extraction capability is enabled by default when the geodata service is created while
the replication needs to be added proactively.
2.2
Consume Geodata Service
This document describes two ways to consume the geodata service.
1.
Data Replication
The following steps allow NJTPA to transfer the remote data eligible for replication to an EGIS
geodatabase. This can be achieved in several ways. The sample process below executes the data
transfer in ArcMap. The same process can be carried using the ‘Crate Replica From Server’
procedure in the Distributed Geodatabase tool kit in ArcCatalog. The option to implement data
replication automatically is described in Section 3.
2.2.1 Connect to the remote data source
In ArcCatalog, navigate to the GIS Servers node
Double-click on the Add ArcGIS Server sub node and select Use GIS
Services
In the next dialogue box, select Internet and enter the Server URL address of
the remote data source (provided by EGIS partner agency)
The map service and geodata service generated in step 2.1 is now exposed
2.2.2 Add map service to ArcMap
Open ArcMap and add the map service generated in 2.1 to the session
2.2.3 Run Data Replication Wizard
In the ArcMap session, add the Distributed Geodatabase tool set to the map
session
Select the first tool, ‘Create Replica Wizard’ using the parameters in 2.2.4
2.2.4 Select the following data replication parameters
Replica Type: One way replica. Note that if synchronization is to
be used, select two way.
What do you want to replicate: Data
Geodatabase to replicate to: GDB_STAGE
Replica Name: <DataSource_Date_DataSetName>
7/22/2010
7
Extraction
_______________________________________________________________________
In the final page, select No further action
Data replicas are managed in ArcCatalog by right-clicking on the geodatbase where replicas exist,
and selecting Distributed Geodatabase/Manage Replicas. When a replica has been created, the
replica name is inserted into the replica manager in both the parent and the child geodatabases.
The details of the manual data replication process are summarized in Figure 2.
After the replica has been created, the data can be updated in the child by using the
synchronization tool in the Distributed Geodatabase tool set. If a one-time data replication
instance is required, the data replicas in both the parent and child geodatabases must be deleted in
the Data Replication Manager. Initial coordination with the parent EGIS partner organization is
essential for replication success.
7/22/2010
8
Data Source / Sub region / Publish Geodata Service / Parent
Destination / NJTPA / Consume Geodata Service / Child
Prepare Data for Replication
(ArcCatalog)
Data
(Re)Source
1. Data user must have write access
2. Data set must be registered as
versioned
3. The data can not be versioned
with the option to move edits to
base
4. Each data set must have a
Globalid column.
5. All spatial data must be stored in
a high precision spatial reference
Create Replica from Geodata service
Connect to Data Source
Publish Map service Using Map File
In ArcGIS Server (with Geodata
Capibility)
1. GIS Servers in ArcCatalog
2. e.g. http://geoportal.njtpa.org/
arcgis/services
1. In ArcMap, load the Map Service from the
remote source
2. In ArcMap run the Data Replication Wizard or
Extract Data Wizard (from Distributed
Geodatabase Tools)
3. Use the one way replica; Data options
4. Choose GDB_DEV or GDB_STAGE as
geodatabase destination
Add Replication Capability to the
Geodata Service
Create Map File of Data to be
Replicated (ArcMap)
1. Add data layers to ArcMap
2. Save Map file where it can be
accessed by ArcGIS Server
GDB_STAGE
Figure 2 - Data Replication Process Detail
2.
Data Extraction
Data extraction requires less preparation time and is generally useful for generic purposes, like
enabling data copying from map services. Any map service that is coupled with a geodataservice
can be used for download in ArcMap. Map services can be added into an ArcMap session from
several locations.
http://geoportal.njtpa.org/ArcGIS/rest/services/MapServices
http://geoportal.njtpa.org:8080/geoportal/catalog/main/home.page (Map Services)
ArcCatalog\GIS Servers\ http://geoportal.njtpa.org/arcgis/services
Once the map services is added to ArcMap, select the Extract Data tool from the Distributed Data
tool set and select a destination for your personal geodatabase. After the download process, the
personal geodatabase will contain the items in the map services.
3.
DATA REPLICATION AUTOMATION
As an alternative to Section 2.2, data replication can also be scheduled to run using the Windows
Task Scheduler. In this process, a task is scheduled in the Task Scheduler to run a Python script.
This script executes the same data replication steps as in the Create Replica From Server tool in
ArcCatalog.
One scheduled job created in the Task Scheduler corresponds to one map / geodata service to be
replicated. For example, if Warren County has built a geodata service to replicate parcels and
projects per quarter, one job in Windows Scheduler needs to be created to execute the data
transfer. If synchronization is the desired update method, a script can be built based on the
synchronization tool.
3.1
Deploy Python Script
A Python script can be created from an ArcGIS model, which in turn can used to automate the
data replication process. The sample python script NJTPA_Replication.py can be used as a
starting point for future automated data replications.
The scripts can be placed and run from any location where it has access to ArcCatalog and the
geodatabase connections within it. To edit the script, right-click on the file and choose ‘Edit with
IDLE’. Figure 3 shows the Python Shell and the sample script. This script automates the Create
Replication From Server steps.
Extraction
_______________________________________________________________________
Figure 3 - Python Shell and Sample Script
Table 2 describes the variables that are in the sample script.
7/22/2010
11
Extraction
_______________________________________________________________________
Table 2 - Python Script Variables
Variable
#
Variable Name
1
GeoDataServer
2
Replica_Type
3
Geodatabase to where the
child replica will be written to
(left side of the = sign)
Name of the replica created by
the NJTPA staff that is
creating the replica.
4
5
3.2
Data layers / items
Notes
This is the remote ArcGIS Server URL where the
geodata service that can be replicated is exposed.
This location is accessed through the GIS Servers
node in ArcCatalog. The URL address should be
provided by the EGIS partner agency.
Use one-way replication. Check-out and Two-way
replications can be implemented but require the
consideration of other work flows.
Same as the geodatabase to where the child replica
will be written to, but includes the “.sde” extension”
(right side of the = sign)
The same replica name will be added to the parent
geodatabase. The recommended standard for
naming replicas is
<DataSource_Date_DataSetName >
These are the data items that are contained in the
geodata service created in 2.1 above, and are eligible
for replication. These items can also be previewed
in ArcMap using the map service. In practice, these
items will be coordinated with the partner EGIS
agency. These items will be entered into the script
using the same names as the source data set and are
separated by a semicolon.
Windows Task Scheduler
The python script(s) can be run on a scheduled basis. They can also be executed manually within
Python through the Python Shell. The steps below describe how to run one or more data
replication scripts.
7/22/2010
12
Extraction
_______________________________________________________________________
3.2.1 Go to Programs / Accessories / System Tools / Task Scheduler to open the
application, depicted in Figure 4
Figure 4 - Windows Task Scheduler
3.2.2 Go to Create Task on the right side of the screen
3.2.3 General Tab: Create a task name. A long term strategy and naming convention
for data replication tasks should be developed
3.2.4 Trigger Tab: Set desired times e.g. quarterly for this particular replication
3.2.5 Actions Tab: Go to New and browse to the Python script for this particular
replication
7/22/2010
13
Extraction
_______________________________________________________________________
4
INTERAGENCY WORK-FLOW
Transferring data between two agencies requires a coordinated effort with an EGIS partner
agency. Data replication should be viewed as a cycle and each step requires planning. Figure 5
depicts the high-level decisions to be addressed at the planning stage of the data transfer process.
Figure 5 - Data Transfer Decision Path
The geodata service can be updated and refreshed indefinitely and thus reduce the number of
steps required to transfer data from a remote location to an EGIS geodatabase.
7/22/2010
14
4.4 – ArcGIS Clip Model
Prepared for:
Prepared by:
AECOM USA Inc.
April 29, 2010
The information below describes the ArcGIS models built to clip any GIS features based on two features
(NJTPA region and NJTPA Counties). To use the model, copy the files into a desirable folder where they
can be accessed by ArcCatalog.
1. NJTPA Clip Model (NJTPA_ClipModel.tbx) contains two models: County_ClipModel_GDB_PROD
and NJTPA_ClipModel_GDB_PROD. A generic clip model is also provided.
I.
Model Environment & Geoprocessing Features
a. Created in ArcGIS 9.3.1 environment using ArcGIS Model Builder
b. Geoprocessing Features:
i. Selection Tool: Selects NJTPA border from Regional MPO Borders (Database
Connections\to GDB_PROD.sde\GDB_PROD.EGIS_ADMIN.lpb_MPO)
ii. Clip Tool: Clips user-specified input to NJTPA border (Using selection from
section 1.b.i.)
1. Output: User-specified feature class
II. Model Procedure
a. Open NJTPA_ClipModel
b. Input Features: Enter user-specified file into Model (e.g. New Jersey Statewide Census
Tracts)
i. Feature to be Clipped
c. Output Feature Class: Enter user-specified output geodatabase and feature class data.
III. Model Stipulations:
a. Input features are scripted to automatically clip to NJTPA border
b. Imbedded within the clip tool is a selection procedure. The selection procedure references
“Database Connections\to GDB_PROD.sde\GDB_PROD.EGIS_ADMIN.lpb_MPO” (see
1.b.i.). If the database connection does not match gdb_prod.sde, then user must manually
edit the selection procedure.
c. Output Feature Class must be feature class within a Geodatabase
i. Provided geodatabase within “\models” folder (EGIS_Models.mdb)
2. County Clip Model (County_ClipModel) clips a user-specified input file to a user-specified New
Jersey County (e.g. New Jersey Schools to Morris County Border Æ Morris County Schools)
Note: The County_Clip model needs to generate temporary files to a personal geodatabase. These files
will be generated within the personal geodatabase delivered as a part of this tool kit. To ensure that the
files are generated correctly, you need to map the location of the personal geodatabase in the model itself.
To do this, follow the instructions below:
1. Right-click on the Count_ClipModel and select edit
2. Double-click on the temp circle
3. In the temp path, insert the file path of the location of the EGIS_Models.mdb personal
geodatabase
The instructions to the use the model are as follows.
I.
b. Geoprocessing:
i. Select Tool: Selects user-specified County from NJ Counties (Database
Connections\to GDB_PROD.sde\GDB_PROD.EGIS_ADMIN.lpb_County)
ii. Clip Tool: Clips user-specified input to Selected County (Using selection from
section 1.b.i.)
II. Model Procedure
a. Open County_ClipModel
b. Input Features: Enter user-specified input file into Model (e.g. New Jersey Schools)
c. Specify “Which County?”: Using SQL expression, specify which county to clip input
features
d. Clip Features: Enter user-specified output geodatabase and feature class data
a. When specifying which County to clip to, you must enter the expression using SQL
syntax. Use the ArcGIS expression builder for an intuitive process (e.g. COUNTY =
'BERGEN'). If clipping to two or more counties, use the OR logical separater (e.g.
COUNTY = 'BERGEN' OR COUNTY = 'ESSEX').
b. Imbedded within the clip tool is a selection procedure. The selection procedure references
“Database Connections\to GDB_PROD.sde\GDB_PROD.EGIS_ADMIN.lpb_County”
(see 1.b.i.). If the database connection does not match gdb_prod.sde, then user must
manually edit the selection procedure.
c. Output Feature Class must be feature class within Geodatabase
Generic Clip Model (Generic_ClipModel) clips a user-specified input file to a user-specified clip feature
(e.g. Survey Respondents to NJTransit Bus Station Buffer Æ Survey Respondents within NJTransit
Bus Station Buffer)
I.
b. Geoprocessing:
i. Clip Tool: Clips user-specified input to user-specified clip feature
II. Model Procedure
a. Open Generic_ClipModel
b. Input Features: Enter user-specified input file into Model (e.g. NJTPA Census Tracts)
i. Feature to be Clipped
c. Clip Features: Enter user-specified clip file into Model (e.g. Bergen County Border).
Feature
i. Feature used to Clip
d. Output Feature Class: Enter user-specified output geodatabase and feature class data.
a. Output Feature Class must be feature class within a Geodatabase
Quick
Reference
EGIS
User
Manuals
Support
Documents
Appendices
About the Appendices
The appendices provide more background information for the items
contained in the EGIS and how the system was conceptualized. The
appendices are comprised of the Data Model, Data Inventory, Quality
Assurance Program and Metadata Reference Guide for the NJTPA
Geoportal. The Data Model is a diagram of the how the tables and GIS
layers relate in the database. The Data Inventory is a list of all the items in
the database. The Quality Assurance Program describes the standards
and guidelines all users need to abide. The Metadata Reference Guide
for the NJTPA Geoportal describe each item in the database is
documented and cataloged.
NJTPA_v6 -- Display1 / 02. StrategyEvaluationArea
Subject Area 2 - Strategy
Evaluation
lp_SE2Place
lpb_County
t_SE_PROJECT_CONCEPT_COUNTY
CNTY_CODE
SE2ID
County
FIPSSTCO
County_Label
MPO
GNIS
STFID (FK)
CNTY_CODE (FK)
MPO
NJTPAccd00
NJTPAAccd_1
NJTPAAccd_2
PlaceName
NJTPAccd_4
CreateBy
CreateDate
UpdateBy
UpdateDate
MCD_CODE (FK)
t_SE_STRATEGY_AREA_COUNTY
SE_ConceptCountyID
StrategyAreaCountyID
SE_ConceptID (FK)
CNTY_CODE (FK)
StrategyAreaID (FK)
CNTY_CODE (FK)
t_PeformanceTarget_BikePed
t_SE_REFINEMENT_AREA_COUNTY
t_SE_RefinementArea
RefinementAreaID
RefinmentAreaCountyID
StrategyCategoryID (FK)
RefinementArea
RefinementAreaID (FK)
CNTY_CODE (FK)
SE2ID (FK)
County
Municipality
Bikepedshr
t_PeformanceTarget_HotSpot
t_SE_REFINEMENT_AREA_DETAILED_STRATEGY
SE2ID (FK)
County
Municipality
INHOTDLY
RefinementAreaDetail_ID
DetailedStrategyID (FK)
t_PerformanceTarget_RoutDly
t_SE_StrategyCategoryGroup
lp_StrategyArea
StrategyCategoryID
StrategyCategory
Description
StrategyAreaID
t_SE_DetailedStrategy
DetailedStrategyID
t_SE_Concept
SE_ConceptID
ProjectId (FK)
Description
dbnum
ProjectID
StrategyCategoryID (FK)
Description
Name
t_Project
ProjectId
Name
Category
Area
Description
Strategy
Year
OldStratID
CategoryID
CreateBy
CreateDate
UpdateBy
UpdateDate
ProjectPhaseId (FK)
ParentProjectID
DBNUM
REVISION
ProjectName
Description
NJTSTIPDesc
PIPESTAT
IsStateProgram
FiscalYear
MultiYear
PipelineNO
Jurisdiction
Sponsor
PavementRank
DrainageRank
Initiation
ROD_Date
Award_Date
LocationDescription
FilesSource
AQ_Code
UPC
ContractNo
DBSort
Section
DemoLead
Limits
M_POSTS
Lead
UpdateReason
1, 1 / 1, 1 -- 6:19:43 PM , 4/6/2010
SE2ID (FK)
County
INROUT
Municipality
t_PerformanceTarget_TransitIn
SE2ID (FK)
County
Municipality
TRSHRIN
t_PerformanceTarget_TransitNYC2
SE2ID (FK)
County
Municipality
TRSHRNYC
t_PerformanceTarget_TransitOut
SE2ID (FK)
County
Municipality
TRSHROUT
t_PerformanceTarget_TripLgthOut
SE2ID (FK)
County
Municipality
AVGTRPLG
t_PerformanceTarget_UnexpDly
SE2ID (FK)
Municipality
INCRASH
County
NJTPA_v6 -- Display1 / 03. RegionalPlanningStudies
Subject Area 3 - Regional
Planning Studies
lpb_County
t_REGIONAL_STUDIES_COUNTY
RegionalStudies_CountID
CNTY_CODE (FK)
RegionalPanningID (FK)
CNTY_CODE
County
FIPSSTCO
County_Label
MPO
GNIS
t_REGIONAL_STUDIES_MUN
lp_RegionalPlanningStudy
RegionalPlanningID
Name
Description
Type
Lead
SubName
DateStart
DateEnd
LeadAgency
Status
PDWP_No
CreateBy
CreateDate
UpdateBy
UpdateDate
RegionalStudies_Mun_ID
RegionalPlanningID (FK)
Mun_Code (FK)
MCD_CODE (FK)
lpb_Municipality
Mun_Code
MCD_CODE (FK)
MUN_KEY
MUN
TYPE
TAZ
COUNTY
NAME
STFID
1, 1 / 1, 1 -- 6:20:20 PM , 4/6/2010
NJTPA_v6 -- Display1 / 04. AirQualityConformity
Subject Area 4 - Air
Quality Conformity
t_Project
ProjectId
ProjectPhaseId (FK)
ParentProjectID
DBNUM
REVISION
ProjectName
Description
NJTSTIPDesc
PIPESTAT
IsStateProgram
FiscalYear
MultiYear
PipelineNO
Jurisdiction
Sponsor
PavementRank
DrainageRank
Initiation
ROD_Date
Award_Date
LocationDescription
FilesSource
AQ_Code
UPC
ContractNo
DBSort
Section
DemoLead
Limits
M_POSTS
Lead
UpdateReason
DESCPTSTIP
DESCPTNJTPA
DESCPTDVRPC
DESCPTSJTPO
CISProgramCategory
CISSubcategory
ReceiveDate
Submitted
CreateDate
CreateBy
UpdateDate
UpdateBy
Desc_Update
t_BudgetSet
t_ConformityProject
ConformityProjectID
ConformityRunID (FK)
ConformityScenarioYrID (FK)
Exempt
ExemptCat
RegSig
CompletionDate
Modeled
Comments
New
ConsultantComments
ProjectId (FK)
ProjectID
ModelComments
dbnum
t_Budget
ConformityBudgetSetID
ConformityBudgetID
Comments (FK)
SIPID (FK)
NAAreaID (FK)
PollutantID (FK)
ConformityBudgetSetID (FK)
BudgetYr
Budget
Comments
t_ScenarioYr
ConformityScenarioYrID
ScenarioYr (FK)
ConformityRunID (FK)
Comments
t_VehicleType
VehicleTypeID
t_ConformityRun
AnalysisStartDate
TIP_FY
RTP_Yr
AnalysisReason
ConformityBudgetSetID
t_VMTCredit
VMTCreditID
ConformityProjectID (FK)
ProjectName
VMTCredit
Comments
lpb_County
CNTY_CODE
County
FIPSSTCO
County_Label
MPO
GNIS
PollutantID
NAAreaID
PollutantName
Units
Abbreviation
NAAreaName
Comments
Description
Comments
ConformityRunID
t_VMTCreditBreakdown
t_SIP
SIPID
SIPName
SIPReason
SubmissionDate
AdequacyDate
Comments
t_VMTResult
VMTResultID
VehicleTypeID (FK)
SeasonID (FK)
RoadTypeID (FK)
CNTY_CODE (FK)
VMT_Type
VMT
t_RoadType
VMTCreditBreakdownID
RoadTypeID
CNTY_CODE (FK)
VMTCreditID (FK)
CreditPercent
Type
Description
Comment
t_NAArea
t_Pollutant
t_EmissionsResult
EmissionResultID
VehicleTypeID (FK)
SeasonID (FK)
CNTY_CODE (FK)
PollutantID (FK)
Conformity
RoadTypeID
Emissions
t_Season
SeasonID
SeasonName
Description
t_NACounty
NAAreaCountyID
CNTY_CODE (FK)
NAAreaID (FK)
1, 1 / 1, 1 -- 6:20:51 PM , 4/6/2010
NJTPA_v6 -- Display1 / 05. Congestion Management Systems
Subject Area 5 - NJ Congestion
Management System
t_CMS_Scenario_index_i
BNODE
t_CMS_Scenario_xy
CMSNUM (FK)
X
Y
MILEPOST
POSTLVE1
CMSNUM (FK)
ANODE
BNODE
ABKEY
SRI (FK)
SLD_Name
BEGIN_MP
END_MP
ROUTE
CMSNUM
SIAP-based Data
Not part of CMS
proper
t_CMS_Scenario_NRec_i
t_CMS_Scenario_geom_i4
CMSNUM (FK)
LINKID
ANODE
RECUR_SPD
NRCUR_SPD
CMSNUM (FK)
RT_LTR
BEGIN_MP
END_MP
FUNC_CLASS
ACT_FUNC
TRK_PROHIB
DISTANCE
AB_NUM_LAN
BA_NUM_LAN
t_CMS_Scenario_LLOS_i
CMSNUM (FK)
LINKID
ANODE
DIST
NETVOL24
NETVOLAM
NETVOLPM
t_CMS_Scenario_capspd_i
t_CMS_Scenario_Corr_i
t_CMS_Scenario_NLOS_i
CMSNUM (FK)
t_CMS_vol_i
CMSNUM (FK)
RT_LTR
BEGIN_MP
END_MP
ONEWAY_ADT
ADT_06_SOU
ADT_YEAR
ABTRUCKPCT
BATRUCKPCT
TRK_SOURCE
TRK_YEAR
AB_AM_MOV
AB_PM_MOV
CMSNUM (FK)
RT_LTR
BEGIN_MP
END_MP
NJTPA_C1
NJTPA_C2
NJTPA_C3
lt_NJ_Roadway_Network
CDEV
VOLTAM
VOLTMD
VOLTPM
VOLTNT
t_CMS_Scenario_Appr_i
SRI
MP
Q_LEVEL
QUALITY
VC
STATUSAM
CRITX_AM
STATUSPM
CRTX_PM
t_CMS_Scenario_Route
BNODE
SOURCEID
LANES
CDEV
CTRLCAP
LINKID__10377
CMSNUM (FK)
t_CMS_Scenario_Link_i
CMSNUM (FK)
t_CMS_Linkdata_2way
CMSNUM
ANODE
BNODE
ABVOLAM
BAVOLAM
BTH_VOLAM
RT_LTR
SALNAME
BEGIN_MP
END_MP
TPK
I78
I80
NJ17
NJTPK
TURNPIKE
LINKID
AGROUP (FK)
LINKID
ANODE
DIST
FTYPE
ATYPE
FGROUP
RGROUP
t_CMS_Bottleneck
CMSNUM (FK)
RANK
SCORE
SRI
FROM_MP
TO_MP
FC
JURISDICTION
ABAMBROKEN
ABPMBROKEN
t_CMS_Intersection
SRI
MP_START
MP_END
DIRECTION
SLD_NAME
ID
CMSNUM (FK)
CMSNUM (FK)
RT_LTR
BEGIN_MP
END_MP
AB_LCAP_AM
AB_LCAP_PM
lt_CMS_IntersectionAnalys
t_CMS_Scenario_VMTVHT_i
AGROUP
FGROUP
VMTTOTAL
VMT01
VMT02
1, 1 / 1, 1 -- 6:23:45 PM , 4/6/2010
t_CMS_Interchange
KEY_A
InterchID
VolumeScore
VC_Score
FC_Score
FuncClass
MagnVolume
IntensityVC
RANK
SCORE
SRI
MAIN_MP
MP
COUNTY
TWNSHP
VOL_AM
VOL_PM
IntCode
sri
mp
lat
long
Rank
TotalScore
FuncClass
SIScore
SMVolume
SMScore
SevCongestion
SevScore
CountyID
CountyName
NJTPA_v6 -- Display1 / 06. Transit
Subject Area 6 Transit
lt_BusStop
t_RidershipBusTransit
RecordID
t_RidershipFerry
ID (FK)
Value1
RidershipFerryID
Line (FK)
Year
Month
Ridership
ID
LINE (FK)
LATITUDE
LONGITUDE
STOP_TYPE
ON_STREET
AT_STREET
LEG
t_RidershipBusGroup
RidershipBusGroupID
BusGroup
Year
Quarter
Weekday
Saturday
Sunday
lt_BusLine
LINE
lt_Ferry
Line
Operator
Comment
t_PR_SubLot
FacID
ParentLot (FK)
UrbitranID
NameUrbitran
NameNJDOT
LocalName
t_RidershipRailPATH
RidershipRailPathID
Station_ID (FK)
Value1
CreateDate
CreateBy
UpdateDate
UpdateBy
ID
BUS_ROUTE_ID
BUS_ROUTE
TYPE
BUS_VAR
DIRECTION
lt_RailStation
Station_ID
t_RidershipRailStation
t_PR_Facility
FacID (FK)
lf_PR_Location
FacID
POINTX
POINTY
CNTY_CODE
MPO
UrbitranID
NameUrbitran
NameNJDOT
ContainsSubLot
LocalName
StationName
StationID
Confirmed
CNTY_CODE
Mun
RidershipRailStationID
Station_ID (FK)
Rail_ID
Year
Quarter
AvgWeekdayBoard
AvgSaturdayBoard
AvgSundayBoard
t_RidershipRailLine
RidershipRailLineID
Rail_ID (FK)
Year
Quarter
AvgWeekdayTrips
AvgSaturdayTrips
AvgSundayTrips
TicketType_OPRT
TicketType_SC
TicketType_MP
TicketType_OWTTWK
t_PR_FACILITY_RAILINE
FacilitiesTransitID
FacID (FK)
Rail_ID (FK)
t_PR_FACILITY_PR_TRANSITBUS
FacilitiesTransitBusID
FacID (FK)
RouteID (FK)
1, 1 / 1, 1 -- 6:25:01 PM , 4/6/2010
Municipality
County
RailId
lt_RailTransitLine
Rail_ID
Rail_Line
MSLINK
Owner
RailLineCode
ServiceType
Operator
Service
t_PR_TransitBus
RouteID
ServiceType
RouteName
Operator
Ownership
CodeName
NJTPA_v6 -- Display1 / 07. FreightAssessment
Subject Area 7 - Freight
Assessment
lt_TruckCorridors_NJTPA
TruckCorridorID
CorridorName
CorridorLength
lt_RailAbandoned_NJTPA
t_TruckFreight
TruckFreightID
Tonage
FreigthLink
lt_TruckStop_NJTPA
lf_BusinessLocation
ID
STOP_NAME
ADDRESS
CNTY_CODE
MPO
lt_RailFreightLine
RailFreightLineID
Length
Owner
INFOUSA
CONAME
CITY
STATE_ABV
ZIP_CODE
SIC_EXT
FRN_CODE
IS_CODE
NUMBER_EMP
SALES_VOL
LineName
PreviousOwner
CurrentOwner
Contiguous
Trail
Plans
Line_ID
New_ID
lt_FAF2
lt_AtGradeCrossing
ID
CROSSING
LENGTH
DIR
VERSION
RECID
STATE
SIGN1
SOURCE
TYPEOS
HIGHWAY
STREET
LAT
LON
lt_FreightLocator
RecordID
CompanyName
PrimaryAddress
PrimaryCity
PrimaryState
PrimaryZipCode
ContactName
Phone
County
Latitiude
Latidute
SelectedSIC_Code
SelectedSIC_Desc
EstimatedInboundTons
EstimatedOutboundTons
EstimateTotalTones
Based on "Arizona"
Table Structure
1, 1 / 1, 1 -- 6:25:51 PM , 4/6/2010
NJTPA_v5.5 -- Display1 / 08. Census
Subject Area 8 Census
lpb_CensusBlockGroup_2000
STFID (FK)
MCD_CODE (FK)
TRACTID (FK)
MPO
CNTY_CODE
lpb_CensusBlock_2000
lpb_CensusTract_2000
TRACTID
MCD2000
CNTY_CODE
MPO
POPULATION
STFID (FK)
MCD_CODE (FK)
t_Journey_to_Work
ODID
STFID (FK)
MCD_CODE (FK)
FIPSSTCO
TRACT2000
BLOCK2000
MPO
lt_Street_TIGER
TLID
FENAME
FNODE
TNODE
MPO
ResState
ResCounty
ResMCD
ResCMSA
ResPMSA
Year
lp_SE2Place
SE2ID
t_AmericanCommunitySurvey
AC_Survey_ID
CNTY_CODE (FK)
County
B01003_1_EST
B01003_1_MOE
B01002_1_EST
B01002_1_MOE
Year
STFID (FK)
CNTY_CODE (FK)
MPO
NJTPAccd00
NJTPAAccd_1
NJTPAAccd_2
PlaceName
NJTPAccd_4
CreateBy
CreateDate
UpdateBy
UpdateDate
MCD_CODE (FK)
lpb_County
CNTY_CODE
County
FIPSSTCO
County_Label
MPO
GNIS
1, 1 / 1, 1 -- 12:48:35 PM , 2/18/2010
NJTPA_v6 -- Display1 / 09. Safety
Subject Area 9 - Safety
lt_Street_TIGER
FENAME
FNODE
TNODE
MPO
SRI
MP_START
MP_END
DIRECTION
SLD_NAME
t_SMS_Accidents_NJTPA
CrashID
SRI (FK)
CountyName
MunicipalityName
MilePost
CrashDate
Street
County
Street_County_Munic
t_SMS_Drivers_NJTPA
CrashID (FK)
DriverCity
DriverSate
t_SMS_Vehicles_NJTPA
VehicleNumber
CrashID (FK)
InsuranceCompanyCode
Make of Vehicle
Model of Vehicle
t_SMS_Pedestrians_NJTPA
t_SMS_Occupants_NJTPA
t_SMS_DeerCrashes_NJTPA_2006
PedestrianNumber
CrashID (FK)
PhysicalCondition
Address Zip
CrashID (FK)
FIRSTSEQUE
SECONDSQUE
1, 1 / 1, 1 -- 6:27:32 PM , 4/6/2010
OccupantNumber
CrashID (FK)
VehicleCondition
NJTPA_v6 -- Display1 / 10. NJRTME
Subject Area 10 - NJRTM-E
lt_TAZ_Boundary
ZONE
lpb_County
CNTY_CODE
County
FIPSSTCO
County_Label
MPO
GNIS
lt_NJRTM_yrPeriodMode
AREA
AT
STATE_CODE
STATE_NAME
CNTY_CODE
COUTNY_NAME
TRACT
FIPSSTCO (FK)
BLKGROUP
STFID
MCD_CODE
GEOGRAPHY
NJRTM_ZONE
ID
SRI
SRI (FK)
Year
COUNTY (FK)
A
B
BEGIN_MP
END_MP
DISTANCE
CAPACITY
FT
AT
LANESAM
LANESPM
LINKTYPE
TERTYPE
NLTLANE
NJRTLANE
MP_START
MP_END
DIRECTION
SLD_NAME
'COUNTY' values correspond to
FIPSSTCO in lpb_County
1, 1 / 1, 1 -- 6:28:11 PM , 4/6/2010
NJTPA_v6 -- Display1 / 11. Socio Economic Forecasting
Subject Area 11 - Socio
Economic Forecasting
lt_TAZ_SED_NYMTC
TAZ
FIPSCO
PopTot05
PopHH05
PopGQ05
lt_TAZ_Boundary
ZONE
AREA
AT
STATE_CODE
STATE_NAME
CNTY_CODE
COUTNY_NAME
TRACT
FIPSSTCO (FK)
BLKGROUP
STFID
MCD_CODE
GEOGRAPHY
NJRTM_ZONE
lpb_County
CNTY_CODE
County
FIPSSTCO
County_Label
MPO
GNIS
t_SED
SED_ID
ZONE (FK)
CNTY_CODE (FK)
MCD_CODE (FK)
DISTRICT
YEAR
AREA
DEVAREA
AT6
ATYPE
CINDEX
POP
HH
INCOME
AMINE
CONST
MFG
TRANS
WHLS
RETAIL
FIRE
SERVICE
GOV
MILITARY
TOTAL
t_SED_ForecastMCD2035
MCD_CODE
County
MCD
2010Pop
2015Pop
lpb_Municipality
Mun_Code
MCD_CODE (FK)
MUN_KEY
MUN
TYPE
TAZ
COUNTY
NAME
STFID
TRACTID
MCD2000
CNTY_CODE
MPO
POPULATION
STFID (FK)
MCD_CODE (FK)
1, 1 / 1, 1 -- 6:29:05 PM , 4/6/2010
NJTPA_v6 -- Display1 / 12. Landuse
Subject Area 12 Landuse
Includes environmental
screening,
wetlands, pinelands
le_Landuse_DEP
LanduseID
Cover
le_Landuse_Rutgers
LanduseID
Cover
lpb_County
CNTY_CODE
County
FIPSSTCO
County_Label
MPO
GNIS
1, 1 / 1, 1 -- 6:30:03 PM , 4/6/2010
NJTPA_v6 -- Display1 / 13. Regional Household Travel Surveys
Household Travel Surveys
t_HH_PUD
SAMPNO
HH_ADDR (FK)
QUEST
ADVLT
ATHOME
TOTVEH
DWELL
t_PER_PUD
t_VEH_PUD
t_LOC_PUD
LOCNO
LOCTYPE
TRACT
AV_STATU
ID
PERSNO
W2_LOC (FK)
W1_LOC (FK)
S_LOC (FK)
SAMPNO (FK)
GENDER
AGE
LIC
RELATE
t_PLAC_PUD
VEHNO
SAMPNO (FK)
PLACENO
NOSTOP
INTP
PDIARY
PNOPREP
t_TRIP_PUD
PLACENO
SAMPNO (FK)
PL_LOC (FK)
NOSTOP
INTP
PDIARY
PNOPREP
PERSNO
SAMPNO (FK)
PERSNO
NOSTOP
INTP
PDIARY
PNOPREP
1, 1 / 1, 1 -- 6:30:57 PM , 4/6/2010
NJTPA_v6 -- Display1 / 14. DOT Management Systems
Subject Area 14 - DOT
Management Systems
t_SLD_FederalAid
SRI
MP_START
MP_END
DIRECTION
SLD_NAME
t_SLD_NHS_type
id
sri
mp_start
mp_end
nhs_type
type_code
nhs_type
descr
t_SLD_FederalAid_Type
t_DMS_FloodClosureSite
ID
type_code
descr
SRI (FK)
RouteID
ROAD_CLOSURE_RC_FROM_7_1_04
County
SiteID
MPO
From_MP
To_MP
Town
ADT
UPC
ADT_X_RC
FloodClosureSite
Location
Original_Rank_Value
Year_Screened
RouteID__8646
t_SLD_FunctionalClass
id
sri
mp_start
mp_end
type_code
t_SLD_FunctionalClass_Type
type_code
descr
t_SLD_Jurisdiction
id
sri
mp_start
mp_end
type_code
t_SLD_LaneCount
id
sri
mp_start
mp_end
descr
t_SLD_Jurisdiction_Type
type_code
descr
t_SLD_ShoulderInWidth
id
t_PMS
ID
sri
mp_start
mp_end
descr
id__11815
t_SLD_MedianType
id
sri
mp_start
mp_end
type_code
t_SLD_MedianWidth
t_SLD_Median_Type
Type_Code
Descr
t_SLD_ShoulderWidth
id
id
sri
mp_start
mp_end
descr
sri
mp_start
mp_end
descr
t_SLD_PavementWidth
t_TMS
SRI (FK)
MP_End
MP_Start
PaveType
AADT
Lanes
Med
County
SpdLim
IRI
Bridge
SDI
NHS
t_BMS_2009
stnum
route
strucname
nbi_001a
nbi_001b
t_SLD_Speed
id
id
sri
mp_start
mp_end
descr
sri
mp_start
mp_end
descr
SRI & MP Values Mapped to
NJ_Roadway_Network
1, 1 / 1, 1 -- 6:31:39 PM , 4/6/2010
ID
SRI (FK)
CO_NAME
MUN_NAME
STATION_ID
ROUTE_PRFX
ROUTE
SOUTE_SFX
MP
STREET_NAME
LOCATION
AADT
DATE_COUNTED
CLASS
Subject Area 1 - Capital
Program
Name of Data Resource
Database Name
Data Source
Download File
Capital Program - Historical Project
Attributes
t_Historical_Project_Attributes
NJTPA
Table
Capital Program - Historical Project Finance
Attributes
t_Historical_ProjectFinance_Attributes
NJTPA
Table
Capital Program - Historical Project
Finances
t_Historical_ProjectFinance
NJTPA
Table
Capital Program - Historical Projects
t_Historical_Project
NJTPA
Table
Capital Program Category Types
Capital Program Funds
t_Category
t_Fund
NJDOT
NJTPA
Table
Table
Capital Program Project Category ID Codes t_Project_Category
NJTPA
Table
Capital Program Project Change Type
t_ProjectChangeType
NJTPA
Table
Capital Program Project Contacts
t_Contact
NJDOT
Table
Capital Program Project Financials
t_ProjectFinance
NJDOT/NJTRANSIT
Table
Capital Program Project Phase
t_ProjectPhase
NJTPA
Table
Capital Program Project Change
t_ProjectChange
NJTPA
Table
Capital Program Project Role
t_ProjectRole
NJTPA
Table
Capital Program Project Role
t_ProjectRoute
NJTPA
Table
Capital Program Project Score
t_ProjectScore
NJTPA
Table
Capital Program Projects by Members
t_Project_Members
NJDOT
Table
Capital Program Reference Code
t_ReferenceCode
NJTPA
Table
Capital Program Reference Type
t_ReferenceType
NJTPA
Table
Capital Program Revision Phase
t_RevisionPhase
NJTPA
Table
Capital Program Revisions
t_Revision
NJTPA
Table
Capital Program Score Type
t_ScoreType
NJTPA
Table
Capital Program Structure
t_Structure
NJTPA
Table
Capital Program TIP Modification and
Amendment Package
t_Package
NJTPA
Table
Capital Program Transportation
Improvement Program Approval Level
t_ApprovalLevel
NJTPA
Table
Capital Program Transportation
Improvement Program Reference ID Codes t_TIP_Reference
NJTPA
Table
Capital Program Work Phase
t_WorkPhase
NJTPA
Table
Capital Program Work Phase Type
t_WorkPhaseType
NJDOT/NJTRANSIT
Table
Congressional Districts
lpb_CongressionalDistrict
NJDEP
GIS Layer
Legislative Districts
lpb_LegislativeDistrict
NJDEP
GIS Layer
Metropolitan Planning Organizations
Capital Program Project Routes
lpb_MPO
t_Route
NJOIT
NJTPA
GIS Layer
Table
NJTPA Projects - Polygons
lp_Project_poly
NJTPA
GIS Layer
NJ Municipalities
lpb_Municipality
NJOIT
GIS Layer
NJTPA Projects
t_Project
NJTPA
Table
NJ Counties
lpb_County
NJOIT
GIS Layer
NJ Roadway Network
NJDOT
GIS Layer
Subject Area 2 - Strategy
Evaluation/ Strategy
Refinement
Database Name
Data Source
Download File
Detailed Strategy Evaluation Areas
t_SE_DetailedStrategy
NJTPA
Table
Performance Target for Bike & Ped
t_PerformanceTarget_BikePed
NJTPA
Table
Performance Target for Hotspots
t_PerformanceTarget_Hotspot
NJTPA
Table
Performance Target for Routine Delays
t_PerformanceTarget_RoutDly
NJTPA
Table
Performance Target for Transit into Places
Performance Target for Transit out of
Places
t_PerformanceTarget_TransitIn
NJTPA
Table
t_PerformanceTarget_TransitOut
NJTPA
Table
Performance Target for Transit to NYC
t_PerformanceTarget_TransitNYC2
NJTPA
Table
Performance Target for Trip Length Out
t_PerformanceTarget_TripLgthOut
NJTPA
Table
Performance Target for Unexpected Delays t_PerformanceTarget_UnexpDly
NJTPA
Table
Strategy Category Group ID Codes
t_SE_StrategyCategoryGroup
NJTPA
Table
Strategy Evaluation 2 Places
lp_SE2Place
NJTPA
GIS Layer
Strategy Evaluation Areas
lp_StrategyArea
NJTPA
GIS Layer
Strategy Evaluation Concepts
t_SE_Concept
NJTPA
Table
NJTPA Projects
t_Project
NJTPA
Table
NJ Counties
lpb_County
NJOIT
GIS Layer
Planning Studies
Database Name
Data Source
Download File
lp_RegionalPlanningStudy
NJTPA
GIS Layer
Regional Planning Studies by County
t_REGIONAL_STUDIES_COUNTY
NJTPA
Table
Regional Planning Studies by Municipality
t_REGIONAL_STUDIES_MUNCIPALITY
NJTPA
Table
NJ Municipalities
lpb_Municipality
NJOIT
GIS Layer
NJ Counties
lpb_County
NJOIT
GIS Layer
Subject Area 4 - Air Quality
Conformity
Database Name
Data Source
Download File
NJTPA Audit
t_AUDIT
NJTPA
Table
Air Quality Conformity Budget
t_Budget
NJTPA
Table
Air Quality Conformity Budget Set ID of
Time
t_BudgetSet
NJTPA
Table
Air Quality Conformity Pollutant
t_Pollutant
NJTPA
Table
Air Quality Conformity Projects
Air Quality Conformity Roadway Type
Classifications
t_ConformityProject
NJTPA
Table
t_RoadType
NJDOT
Table
Air Quality Conformity Runs
t_ConformityRun
NJTPA
Table
Air Quality Conformity Scenario Year
t_ScenarioYr
NJTPA
Table
Air Quality Conformity Season
t_Season
NJTPA
Table
Air Quality Conformity Vehicle Miles
Traveled Credit Breakdowns
t_VMTCreditBreakdown
NJTPA
Table
Traveled Credits
t_VMTCredit
NJTPA
Table
Traveled Results
Air Quality Conformity Vehicle Type
Emissions Results
t_VMTResult
t_VehicleType
t_EmissionsResult
NJTPA
NJTPA
NJTPA
Table
Table
Table
Non-Attainment Areas
t_NAArea
US EPA
Table
Non-Attainment Areas: Carbon Monoxide
le_NAA_CarbonMonoxide
US EPA
GIS Layer
Non-Attainment Areas: Ozone
le_NAA_Ozone
US EPA
GIS Layer
Non-Attainment Areas: Particulate Matter
10
le_NAA_ParticulateMatter10
US EPA
GIS Layer
Non-Attainment Areas: Particulate Matter
2.5
le_NAA_ParticulateMatter25
US EPA
GIS Layer
Non-Attainment Areas: Sulfur Oxides
le_NAA_SulfurDioxide
US EPA
GIS Layer
Non-Attainment by County
t_NACounty
NJTPA
Table
State Implementation Plan
t_SIP
NJDOT
Table
NJ Counties
lpb_County
NJOIT
GIS Layer
Subject Area 5 - NJ Congestion
Management System
Database Name
Data Source
Download File
Congestion Management Intersection
Analysis
lt_CMS_IntersectionAnalysis
NJDOT
GIS Layer
NJDOT Congestion Management System
Bottlenecks
t_CMS_Bottleneck
NJDOT
Table
Input Capacity, Speed, Incidents
t_CMS_TA_06_capspd_i
NJDOT
Table
Input Corridor File
t_CMS_TA_06_Corr_i
NJDOT
Table
Input Geometry File
t_CMS_TA_06_geom_i4
NJDOT
Table
Input Index ID File
t_CMS_TA_06_index_i
NJDOT
Table
Input Link File
t_CMS_TA_06_Link_i
NJDOT
Table
Input Route File
t_CMS_TA_06_Route
NJDOT
Table
Input Two-Way Link Data File
t_CMS_Linkdata_2way
NJDOT
Table
Input Volume
t_CMS_TA_06_vol_i
NJDOT
Table
Interchanges
t_CMS_Interchange
NJDOT
Table
Intersections
t_CMS_Intersecton
NJDOT
Table
Output Approach Operations File
t_CMS_TA_06_Appr_i
NJDOT
Table
Output Link LOS File
t_CMS_TA_06_LLOS_i
NJDOT
Table
Output Node LOS File
t_CMS_TA_06_NLOS_i
NJDOT
Table
Output Non-Recurring Delay File
t_CMS_TA_06_NRec_i
NJDOT
Table
Output Vehicle Hours of Travel & Vehicle
Mile Traveled File
t_CMS_TA_06_VMTVHT_i
NJDOT
Table
Output XY Coordinates File
t_CMS_TA_06_XY_i
NJDOT
Table
NJ Roadway Network
NJDOT
GIS Layer
Subject Area 6 - Transit
Database Name
Data Source
Download File
Ferries
Ferry Ridership
lt_Ferry
t_RidershipFerry
Various
NJTRANSIT
GIS Layer
Table
NJ Transit Bus Lines
lt_BusLine
NJ Transit
GIS Layer
NJ Transit Bus Ridership
t_RidershipBusTransit
NJ Transit
Table
NJ Transit Bus Stops
lt_BusStop
NJ Transit
GIS Layer
NJ Transit On Time Performance
t_OnTimePerformance
NJDOT/NJTRANSIT
Table
NJ Transit Rail Lines
lt_RailTransitLine
NJ Transit
GIS Layer
NJ Transit Rail Stations
lt_RailStation
US Census Bureau
GIS Layer
Park & Ride Facilities
t_PR_Facility
NJDOT/NJTRANSIT
Table
Park & Ride Locations
lf_PR_Location
NJDOT
GIS Layer
Park & Ride Sublots
t_PR_SubLot
NJDOT/NJTRANSIT
Table
Park & Rides Facilities along Transit Bus
Routes
t_PR_FACILITY_PR_TRANSITBUS
NJDOT/NJTRANSIT
Table
Park & Rides for at Rail Stations
t_PR_FACILITY_RAILINE
NJDOT/NJTRANSIT
Table
Park & Rides for Transit Bus
PATH Ridership for Rail
t_PR_TransitBus
t_RidershipRailPATH
NJDOT/NJTRANSIT
PATH
Table
Table
Ridership by Rail Line
t_RidershipRailLine
NJ Transit
Table
Ridership by Rail Station
t_RidershipRailStation
NJ Transit
Table
Subject Area 7 - Freight
Assessment
Database Name
Data Source
Download File
Abandoned Rail Lines within NJTPA Region
lt_RailAbandoned_NJTPA
Various
GIS Layer
At Grade Crossings
lt_AtGradeCrossing
NJTPA
GIS Layer
ESRI Business Locations
Freight Rail Lines
lf_BusinessLocation
lt_RailFreightLine
GIS Layer
GIS Layer
Freight Analysis Framework 2
lt_FAF2
ESRI
Various
Bureau of
Transportation
Statistics (BTS)
Freight Locator
NJDOT Truck Corridors within NJTPA
Region
lt_FreightLocator
TranSearch
GIS Layer
lt_TruckCorridor_NJTPA
NJDOT
GIS Layer
NJDOT Truck Stops within NJTPA Region
lt_TruckStop_NJTPA
NJDOT
GIS Layer
Subject Area 8 - Census
Database Name
Data Source
Download File
Census American Community Survey
t_AmericanCommunitySurvey
Journey to Work
t_Journey_to_Work
Cenus
Table
US Census Block Groups, 2000
lpb_CensusBlockGroup_2000
US Census Bureau
GIS Layer
US Census Blocks, 2000
lpb_CensusBlock_2000
US Census Bureau
GIS Layer
US Census Tracts, 2000
TIGER Streets
lt_Street_TIGER
US Census Bureau
US Census Bureau
GIS Layer
GIS Layer
NJ Counties
lpb_County
NJOIT
GIS Layer
GIS Layer
Table
Strategy Evaluation 2 Places
lp_SE2Place
NJTPA
GIS Layer
Subject Area 9 - Safety
Database Name
Data Source
Download File
Drivers in Crashes within NJTPA Region
t_SMS_Drivers_NJTPA
NJTPA
Table
NJDOT Safety Management System Deer
Crashes within NJTPA Region, 2006
t_SMS_DeerCrashes_NJTPA_2006
NJDOT
Table
NJDOT
Table
NJDOT Safety Management System Vehicle
Crashes within NJTPA Region
t_SMS_Accidents_NJTPA
NJDOT Safety Management System Vehicle
Occupants in Crashes within NJTPA Region t_SMS_Occupants_NJTPA
NJDOT Safety Management System
Vehicles Involved in Crashes within NJTPA
Region
t_SMS_Vehicles_NJTPA
NJDOT
Table
NJDOT
Table
Pedestrians in Crashes within NJTPA Region t_SMS_Pedestrians_NJTPA
NJDOT
Table
NJ Roadway Network
TIGER Streets
lt_Street_TIGER
NJDOT
US Census Bureau
GIS Layer
GIS Layer
Subject Area 10 - NJRTM-E
Database Name
Data Source
Download File
North Jersey Model Run for 2010 Evening
lt_NJRTM_2010PMHWY
NJTPA
GIS Layer
North Jersey Model Run for 2010 Midday
lt_NJRTM_2010MDHWY
NJTPA
GIS Layer
North Jersey Model Run for 2010 Morning
lt_NJRTM_2010AMHWY
NJTPA
GIS Layer
North Jersey Model Run for 2010 Night
lt_NJRTM_2010NTHWY
NJTPA
GIS Layer
North Jersey Model Run for 2035 Evening
lt_NJRTM_2035PMHWY
NJTPA
GIS Layer
North Jersey Model Run for 2035 Midday
lt_NJRTM_2035MDHWY
NJTPA
GIS Layer
North Jersey Model Run for 2035 Morning
lt_NJRTM_2035AMHWY
NJTPA
GIS Layer
North Jersey Model Run for 2035 Night
lt_NJRTM_2035NTHWY
NJTPA
GIS Layer
Traffic Analysis Zone Boundaries
lt_TAZ_Boundary
US Census Bureau
GIS Layer
NJ Counties
lpb_County
NJOIT
GIS Layer
NJ Roadway Network
NJDOT
GIS Layer
Subject Area 11 - Socio
Economic Forecasting
Database Name
Data Source
Download File
NJTPA 2035 Demographic Projections by
Municipality
t_SED_ForecastMCD2035
NJTPA
Table
NYMTC Demographic Projections by TAZ
lt_TAZ_SED_NYMTC
NYMTC
GIS Layer (Restricted)
NJ Counties
lpb_County
NJOIT
GIS Layer
NJ Municipalities
lpb_Municipality
NJOIT
GIS Layer
Traffic Analysis Zone Boundaries
lt_TAZ_Boundary
US Census Bureau
GIS Layer
US Census Tracts, 2000
US Census Bureau
GIS Layer
Subject Area 12 - Land Use
Database Name
Data Source
Download File
NJDEP Land Use Land Cover 2007
le_LandUse_NJDEP07
NJDEP
GIS Layer
NJDEP Land Use Land Cover
le_LandUse_DEP
NJDEP
GIS Layer
Rutgers Land Use
le_LandUse_Rutgers
Rutgers
GIS Layer
NJ Counties
lpb_County
NJOIT
GIS Layer
Household Travel Surveys
Database Name
Data Source
Download File
Regional Travel – Household Interview
Survey: Results by Household
t_HH_PUD
NJTPA/NYMTC
Table
Survey: Results by Location
t_LOC_PUD
NJTPA/NYMTC
Table
Survey: Results by Person
t_PER_PUD
NJTPA/NYMTC
Table
Survey: Results by Place
t_PLAC_PUD
NJTPA/NYMTC
Table
Survey: Results by Trip
t_TRIP_PUD
NJTPA/NYMTC
Table
Survey: Results by Vehicle
t_VEH_PUD
NJTPA/NYMTC
Table
Subject Area 14 - NJDOT
Management Systems
Database Name
Data Source
Download File
NJ Roadway Network
NJDOT
GIS Layer
Bridge Management System 2009
t_BMS_2009
NJDOT
Table
NJDOT Bicycle Compatibility Index
t_BicycleCompatibilityIndex
NJDOT
Table
NJDOT Drainage Management System
Flood Closure Sites
t_DMS_FloodClosureSites
NJDOT
Table
NJDOT Straight Line Diagram Access Level t_SLD_AccessLevel
NJDOT
Table
NJDOT Straight Line Diagram Federal Aid
t_SLD_FederalAid
NJDOT
Table
NJDOT Straight Line Diagram Federal Aid
Type
t_SLD_FederalAid_Type
NJDOT
Table
NJDOT Straight Line Diagram Functional
Class
t_SLD_FunctionalClass
NJDOT
Table
NJDOT Straight Line Diagram Functional
Class Type
t_SLD_FunctionalClass_Type
NJDOT
Table
NJDOT Straight Line Diagram Jurisdiction
t_SLD_Jurisdiction
NJDOT
Table
NJDOT Straight Line Diagram Jurisdiction
Type
t_SLD_Jurisdiction_Type
NJDOT
Table
NJDOT Straight Line Diagram Lane Count
t_SLD_LaneCount
NJDOT
Table
NJDOT Straight Line Diagram Left Path
t_SLD_LeftPath
NJDOT
Table
NJDOT Straight Line Diagram Left Path
Inside
t_SLD_LeftPathInside
NJDOT
Table
NJDOT
Table
NJDOT Straight Line Diagram Left Shoulder t_SLD_LeftShoulder
NJDOT Straight Line Diagram Left Shoulder
Inside
t_SLD_LeftShoulderInside
NJDOT Straight Line Diagram Median Type
Description Codes
t_SLD_Median_Type
NJDOT
Table
NJDOT
Table
NJDOT Straight Line Diagram Median Type t_SLD_MedianType
NJDOT
Table
NJDOT Straight Line Diagram Median Width t_SLD_MedianWidth
NJDOT
Table
NJDOT Straight Line Diagram National
Highway System Type
t_SLD_NHS_type
NJDOT
Table
NJDOT Straight Line Diagram Pavement
Width
t_SLD_PavementWidth
NJDOT
Table
NJDOT Straight Line Diagram Pedestrian
Facility
t_SLD_PedestrianFacility
NJDOT
Table
NJDOT Straight Line Diagram Pedestrian
Sign
t_SLD_PedestrianSign
NJDOT
Table
NJDOT Straight Line Diagram Right Path
t_SLD_RightPath
NJDOT
Table
NJDOT Straight Line Diagram Right Path
Inside
t_SLD_RightPathInside
NJDOT
Table
NJDOT Straight Line Diagram Right
Shoulder
t_SLD_RightShoulder
NJDOT
Table
NJDOT Straight Line Diagram Right
Shoulder Inside
t_SLD_RightShoulderInside
NJDOT
Table
NJDOT Straight Line Diagram Shoulder In
Width
t_SLD_ShoulderInWidth
NJDOT
Table
NJDOT Straight Line Diagram Shoulder
Width
t_SLD_ShoulderWidth
NJDOT
Table
NJDOT Straight Line Diagram Speed
t_SLD_Speed
NJDOT
Table
NJDOT Traffic Monitoring System
t_TMS
NJDOT
Table
NJDOT Pavement Management System
t_PMS
NJDOT
Table
Appendix U3 – EGIS Quality Assurance program
Table of Contents
1.
2.
INTRODUCTION ...................................................................................................... 2
GOVERNANCE AND POLICY ................................................................................ 2
Governance ..................................................................................................................... 2
Policy .............................................................................................................................. 2
3. TECHNOLOGY PLATFORMS................................................................................. 2
3.1 Hardware and Software Standards ....................................................................... 3
3.2 Geodatabases Standards ....................................................................................... 4
3.2 Data Management ................................................................................................ 9
4. INTERAGENCY STANDARDS ............................................................................. 12
TABLES
Table 1 - Server-Side: Database and Application ............................................................... 3
Table 2 - Server-Side: Application ..................................................................................... 3
Table 3 - Client-Side: Application ...................................................................................... 4
Table 4- EGIS Geodatabases Description........................................................................... 5
Table 5 - NJTPA Quality Assurance Program .................................................................... 6
Table 6 - NJTPA Framework Categories............................................................................ 7
Table 7 - SQL Server 2008 and ArcSDE Table Naming Conventions............................... 8
Table 8 - EGIS Data Exchange Method ........................................................................... 12
FIGURES
Figure 1 - EGIS Hardware .................................................................................................. 3
Figure 2 - EGIS Data-Flow Process.................................................................................... 4
Figure 3 - EGIS Geodatabase Sequence ............................................................................. 4
Figure 4 - Dynamic Data Inventory Process ..................................................................... 10
Figure 5 – The NJTPA EGIS Geoportal ........................................................................... 12
Task 3.4 – EGIS Standards
_______________________________________________________________________
1.
INTRODUCTION
The North Jersey Transportation Planning Authority (NJTPA) has undertaken the Enterprise
Geographic Information System database (EGIS) project, contained in the agency’s Unified
Planning Work Program (UPWP) for 2009. The goal of the project is to consolidate the agency’s
data into a single, web-enabled platform and to improve information sharing among the project
EGIS participants. The document System Requirements, developed in Task 1, details the overall
design and strategy of the EGIS. This document summarizes the EGIS’s policy, technology, and
operating standards and describes its overall quality assurance and data management programs.
2.
GOVERNANCE AND POLICY
Governance
The NJTPA EGIS is governed and overseen by a data management team referred to as the NJTPA
Data Management Group (NJTPA-DMG). The NJTPA-DMG sets and enforces policies, guides
decision-making related to technology, and oversees the agencies Quality Assurance, Data
Inventory, and Data Exchange programs. At its core, the EGIS is a network of people, data, and
technology resources. The NJTPA-DMG mission is to ensure that these resources are used to
best serve the transportation goals of the region.
Policy
The NJTPA-DMG has implemented a set of comprehensive, high-level policies that serve to
guide the overall administration of the NJTPA’s EGIS.
•
•
•
•
3.
Commitment to a creating a framework for the open exchange of GIS and other digital
products
Commitment to providing user-friendly and internet-based public access to GIS and other
digital products
Commitment to the use of state-of-the-art data management tools to support data
development and data exchange programs
Enforcement of a Quality Assurance program to establish trust in the data products
published by NJTPA
TECHNOLOGY PLATFORMS
Implementation of the EGIS, as a data sharing network, relies on several technology components.
Data exchange standards among and within NJTPA partner agencies requires a basic
understanding of the hardware and software platforms used to build the EGIS. These components
make up the EGIS infrastructure and are part of the overall EGIS standards.
7/22/2010
2
_______________________________________________________________________
3.1
Hardware and Software Standards
The EGIS is built, operated, and maintained using an array of IT components. These components
can be divided into three groups; 1) Server-Side: Database and Application, 2) Server-Side:
Application, and 3) Client-Side: Application. These components are supported by NJTPA’s local
area network which consists of a Citrix – IP Centrex/Primary ISP run on a 50 mb per second
back-bone. Figure 1 depicts the overall EGIS hardware configuration.
Figure 1 - EGIS Hardware
Tables 1, 2, and 3 enumerate the software elements that reside within in the hardware profile.
Table 1 - Server-Side: Database and Application
#
1
2
Software Element
Operating System
Database server
3
4
GIS Gateway
Data Management
Applications
5
Web Server for Data
Management
Applications
Description
Microsoft Windows Server Standard 2008
Relational Database Management System Microsoft SQL Server 2008; Version 10.0.1600.22
ESRI ArcSDE 9.3.1; Release 93004
Microsoft SQL Server Business Intelligence
Development Studio with ASP.NET. C## is the
programming language. Note that initial EGIS data
management applications are run from the database
server.
Microsoft IIS
Table 2 - Server-Side: Application
#
1
2
Software Element
Operating System
Server GIS
3
Web Server for ArcGIS
Server
GIS internet Metadata
portal
4
7/22/2010
Description
Microsoft Windows Server Standard 2008
ESRI ArcGIS Server for the Microsoft .NET
Framework, Version 9.3.1 R 3000
Microsoft IIS
ESRI ArcGIS Server Geoportal Extension Version
9.3.1
3
_______________________________________________________________________
5
6
Web server Geoportal
Extension
Servlet for the
Geoportal
7
Geoportal Extension
developer platform
#
1
2
Software Element
GIS connection
Database connection
Apache, Version 6.0
Apache Tomcat Version 6.0 /Apache Directory
Server Version 1.5, Apache Directory Studio
Version 1.5
Java SE Runtime Engine (JRE) 6 Update 16 / Java
SE Development Kit (JDK) Update 16
Table 3 - Client-Side: Application
3.2
Description
ESRI ArcGIS 9.3.1
Microsoft SQL Server Management Studio and
Access 2007
Geodatabases Standards
The EGIS is implemented through an ESRI ArcSDE geodatbase platform to support the
development and distribution of quality data sets. A geodatabase is a database that has been
spatially enabled through the ArcSDE software. For further detail related to its design, refer to
EGIS documents 3.1 and 3.2. The contents of the EGIS geodatabases are made available through
other ESRI software components, such as ArgGIS and ArcGIS Server. Together, these
components make up the EGIS data-flow, available for use by EGIS participants. The data flow
process for GIS oriented data is depicted in Figure 2.
Figure 2 - EGIS Data-Flow Process
The geodabase is the cornerstone of the EGIS. A series of standards have been developed to
govern its use and associated data distribution. These standards serve to guide all aspects of data
development, submission, storage, and distribution. These standards, in their aggregate, are one
part of the overall EGIS Quality Assurance Program. The program is based on a work-flow that
develops spatial and non-spatial data through four stages. Each stage represents one physical
geodatabase. Data sets are progressively developed and reviewed before they are checked into
subsequent geodatabases. Figure 3 depicts the sequence of the geodatabase as data is developed
through each stage.
Figure 3 - EGIS Geodatabase Sequence
Table 4 describes the four geodatabases at the physical database level.
7/22/2010
4
_______________________________________________________________________
Table 4- EGIS Geodatabases Description
#
1
Database
GDB_DEV
2
GDB_STAGE
3
GDB_PROD
4
GDB_HIST
5
GDB_REP_AgencyX
Purpose
Development database that contains ArcSDE GIS layers
and other data items that are in development and subject
to a QA/QC process before they are checked into the
GDB_STAGE database. This database is used to initiate
datasets, develop their overall structure, and populate the
structure with record values.
Staging database that contains ArcSDE GIS layers and
other data items. These items can come from the
GDB_DEV database or potentially from other agencies.
All data items in this geodatabsae are subject to NJTPADMG quality assurance guidelines. After the items are
in conformance with the quality assurance program, they
can be placed in the GDB_PROD database.
Production database that contains the active, day-to-day
ArcSDE GIS layers and non-GIS database items. These
items have been reviewed by the NJTPA_DMG group
and its quality assurance program. No GIS editing will
occur in this database; standard SQL data transactions
on business tables will occur in this database.
Database that stores time-stamped, ArcSDE GIS layers.
These items come from the GDB_PROD database.
Geodatabases that will participate in a distributed data
replication process, between NJTPA and other
participants. Note that the databases that will be set up
for replication do not currently have the requisite details
needed to support the replication process.
Quality Assurance
As data is developed through the four geodatabases, standards are imposed on each item to ensure
quality and conformace with the underlying technology. The process should begin at the
GDB_DEV stage, but is essential at the GDB_STAGE level. Table 5 describes the quality
assurance items for which EGIS data sets will be subject to during the data development process.
7/22/2010
5
_______________________________________________________________________
Table 5 - NJTPA Quality Assurance Program
#
1
QA/QC Item
Each layer must have a responsible
party from an NJTPA division to
maintain the layer.
2
3
Each layer must use the
NAD_1983_StatePlane_New_Jersey
XY Coordinate System
Each layer must conform to NJTPA
naming conventions
4
Each layer must contain a spatial index
5
Each layer must contain complete
metadata
6
Each layer must be checked for quality
assurance by the NJTPA database team
against the quality assurance items
7
Each NJTPA owned layer must contain
the Create Date, CreateBy, Updatedate,
UpdateBy fields
Each layer must conform to the schema
established in the NJTPA EGIS data
model. Some important fields are:
• Data sets that will grow over
time must contain a Date field
to facilitate data exchange
processes.
8
7/22/2010
Description
Each layer must have a custodian and a
sponsoring department.
Each layer must contain a proper spatial
reference.
Refer to the document EGIS – Logical
Geodatabase Design for a an explanation of
layer naming conventions and Table 6 for SQL
Server 2008 and ArcSDE Table Naming
Conventions
Spatial indexes improve the efficiency of data
queries and retrieval
Meta data, to varying degrees, should be
maintained for all EGIS data objects. Meta is
catalogued in two places.
1. In ArcCatalog where it is stored in the SQL
Server Geoportal931 database and
available for wider use through the
Geoportal web application
2. In the NJTPA Data Management
application (Data Dictionary / Adaptive
Data Inventory Template) where it is
stored in the t_DataItems and
t_SubjectArea tables.
3. NJTPA follows all FGDC and ISO
standards related to information about the
data sets for which it owns and is
responsible.
NJTPA has established a Database Group
whose tasks consists of, among other task,
running through the agencies Quality
Assurance Program check-list, before data is
checked into the GDB_PROD geodatabase
These fields enable NJTPA staff to track the
changes of an ArcSDE layer.
Generally, layers and tables for which NJTPA
is not the custodian, the layer/table schema will
be established by the custodian agency. For
layers/tables where NJTPA is the custodian,
table definitions should be observed. Note that
some tables or layers could be considered
hybrid, in the sense that NJTPA has taken data
6
_______________________________________________________________________
•
9
Each layer, where possible,
should contain County and
MPO fields with values.
• Join fields must be consistent to
maintain the integrity of
underlying views and
relationship classes.
Each layer must be aggregated, at a
minimum, up to the regional level.
Layers aggregated at the municipality
and county level should be avoided.
from an outside source, and redesigned the
schema to facilitate data storage.
Layers, if possible, should be entered into the
EGIS as complete regional data sets. One
notable exception is county-level cadastral data
sets, denoted by lc_County.
The data items themselves are stored in the GDB_PROD geodatabase according to Framework
Categories, depicted in Table 6.
Table 6 - NJTPA Framework Categories
7/22/2010
#
1
Suffix
c
Framework Category
Cadastral
2
d
Design Plans
3
e
Environmental
4
f
Facilities
5
g
General
6
p
Planning
7
pb
Political Boundaries
8
t
Transportation
9
u
Utilities
7
Description
Includes legal,
block and lot data
sets
Includes CAD-type
data sets
Includes data sets
that are
environmentally
related
Includes data sets
that are related to
buildings
Includes data sets
that do not fit into
any of the formal
data categories
Includes data sets
that relate to the
planning process
Includes data sets
that denote
artificial
boundaries created
by humans
Includes data sets
that are
transportation
related
Includes data sets
that are related to
utilities
_______________________________________________________________________
Data items are also subject to a set of nomenclature standards. Table 7 provides a list of
guidelines to consider when naming database tables and GIS layers.
Table 7 - SQL Server 2008 and ArcSDE Table Naming Conventions
#
1
2
3
Convention
Table names should, as clearly as
possible, describe the data
contained in the table, keeping in
mind the 32 character limitation for
SQL Server database object names.
Words in table names should
follow three basic conventions:
• Base tables should be
separated by a capital with
no spaces or underscores.
•
Join tables should be
capitalized, and separated
with underscores
•
Where two capitalized
words meet, they can be
separated by underscores
Table names should avoid the use
of abbreviations.
Example
•
le_UrbanArea
•
t_PR_FACILITY_RAILLINE
•
t_HH_PUD
Exceptions include:
• CMS: Congestion Management
System
•
SLD: Straight Line Diagram
•
SMS: Safety Management
System
•
4
5
Names of database objects (tables,
feature classes, etc.) should be
singular.
Only use words like
‘BOUNDARY, ‘ZONE’, ‘LINE’,
‘POINT’ when they are necessary
to clarify the data contained by the
table. Logical, non-technical
7/22/2010
8
_______________________________________________________________________
descriptors are preferred over
technical jargon that may make
sense to technical staff only.
6 Column names should be singular
where possible. Avoid using dates
• lt_BusLine_12282009
or years as part of the table name in
a production database. Historical
data sets, with their time-stamped
suffix, should be stored in the
GDB_HIST geodatabase. This
process, in effect, represents
NJTPA’s change management
system.
7 In general, the first word in the
table’s name should reflect the data
• Streams_MOA instead of
content while additional words will
MOA_Stream
refine the description. This makes
it easier for users to find data that is
• BuildingMyNeighborhood
most often listed alphabetically or
instead of
when using search engines.
MyNeighborhoodBuilding
3.2
Data Management
Data management is a fundamental part of the EGIS. In addition to the underlying ArcSDE and
ArcGIS Server software platforms, the management of NJTPA’s data resources is supported
through two external facing environments.
Data Inventory
The EGIS contains a dynamic data inventory process, maintained within the Geoportal931 SQL
Server database and on the NJTPA Geoportal site on the Inventory page. The process consists of
SQL Server and .NET tools. Figure 4 depicts the data inventory process.
7/22/2010
9
XML content (and other
information) inserted into
Geoportal931 databases
i.e GPT_ADMIN,
GPT_METADATA, others
Create/Update
Metadata in
ArcCatalog
Export to FGDC
*.XML format
Post XML
metadata file to
Geoportal
(using gptadmin
account)
Set as Approved in
Geoportal931.GPT_ADMIN
Fire
Trigger:
tr_exec_sp_metainfo
_admin
For Insert, Update,
Delete
XML files can be
imported into ArcCatlog
Execute Stored
Procedure:
sp_metainfo
Decompose XML from
GPT_METADATA.XML
into t_MetaInfo
(61 fields from xml file) –
XPATH/TSQL
v_TableInventory
(Subset of t_MetaInfo
is published to
Geoportal.Inventory
Page)
Figure 4 - Dynamic Data Inventory Process
.NET application
(InventoryDownload)
Makes objects available
for download via mouseclick in NJTPA Geoportal
The Data Inventory process starts with ArcCatalog where XML files are created that contain
information about each EGIS data object. These xml files are than published to the Geoportal
where they are processed and placed within the Geoportal/Inventory web page and made
available for download to the public.
Geoportal
The NJTPA Geoportal provides a public interface to the EGIS by allowing users to search the
agencies metadata (data about data). The Geoportal will allow NJTPA staff, subregions, state
agencies, MPO’s and the public to discover what data NJTPA and other agencies have available
and how that data can be acquired. The Geoportal is a web browser based application that can be
accessed by anyone over the internet to search metadata that has been uploaded to the site and
approved as complete by the NJTPA Geoportal Administrator. In this way, the NJTPA Geoportal
site is key component of the agencies overall data management and quality assurance program.
Figure 5 present the home-page of the Geoportal. For a full discussion of the NJTPA’s
Geoportal, refer to the EGIS Admin and User manuals.
_______________________________________________________________________
Figure 5 - NJTPA EGIS Geoportal
4.
INTERAGENCY STANDARDS
The EGIS is a data repository for spatial and non-spatial data. Exchanging data in and out of the
repository is also subject to a series of standards. Table 8 summarizes the access and exchange
methods available to EGIS participating agencies.
Table 8 - EGIS Data Exchange Method
#
1
2
Method
Direct access to
geodatabase content
Access to published
ArcGIS Server map
7/22/2010
Description
via credentialed login
through ArcGIS Desktop
• via ArcGIS Server web
Applications
12
Agency
• NJTPA Central Staff
• Subregions
All map services can be
exposed as either restricted
_______________________________________________________________________
services
•
•
•
(credentialed and non
credentialed)
via ArcGIS Desktop
(credentialed)
via NJTPA EGIS Data
Management web page
and link to geoportal
(credentialed and non
credentialed)
via NJTPA Geoportal
(non credentialed)
or non restricted to any
individual or organization
•
•
•
•
•
•
•
•
Map Services
embedded in an
ArcGIS Server
application can be
restricted at the login
level
Map Service available
through ArcGIS are
restricted at the
connection level
Map services available
through the Data
Inventory are
restricted at the login
level
Map Services via the
NJTPA Geoportal are
not restricted
NJTPA Central Staff
Subregions
State Agencies
MPO’s
Public
NJTPA Central Staff
Any NJ agency
•
•
NJTPA Central Staff
Any NJ agency
•
•
•
3
Access to meta data
and associated map
services
via the EGIS Geoportal
4
Replication to and
from EGIS
geodatabases
via ESRI geodatabase
service:
•
•
5
ftp
7/22/2010
Extraction – data can
be copied from a
geodatabase (Checkout/check-in)
Replication – Edits can
be synchronized with
another geodatabase
(with ArcSDE only) –
Both one-way and
two-way
File transfer
13
Appendix U6:
Metadata Reference Guide for NJTPA Geoportal
This document serves as a guide for creating and updating metadata so that it can be uploaded to the
NJTPA Geoportal. The layout of the document takes you through the ArcCatalog metadata editor
screens tab by tab, and describes the minimum fields that are required and validated by the NJTPA
Geoportal. The pages below start from the Identification menu at the top-left and work from left to right
in the Metadata Editor through the Metadata Reference menu at top-right. If you populate all of the
fields listed in the document below with valid metadata, then export the metadata in the “FGDC CSDGM
(XML)” format, you will be able to upload the XML file to the NJTPA Geoportal without errors.
Additionally, if the Theme Keywords are populated correctly, the search functions on the NJTPA
Geoportal for NJTPA Framework Categories, Subject Areas, Legacy Categories and NJTPA Goals will work
properly.
Each ArcCatalog Metadata Editor screen has a separate page below. The heading at the top of the page
gives the navigation instructions within ArcCatalog. For example, to get to the Bounding Coordinates
page, you would first select the “Identification” menu at the top of the ArcCatalog Metadata Editor, then
select the “Spatial Domain” tab, then the “Bounding Coordinates and G-Polygon” sub-tab. This string of
actions is depicted with the following text at the top of the page:
Identification→ Spatial Domain→ Bounding Coordinates and G-Polygon
Once you have finished populating all required metadata fields, click the Save button in the metadata
editor to save your changes. Next, click the Export Metadata button, select FGDC CSDGM (XML) and give
the file a unique name (ie- MPOBoundaries.xml). Finally, log into the NJTPA Geoportal as a Publisher and
use the upload function to upload the XML file.
1
Identification→ General
Field Name
Abstract
Purpose
Type
Text
Text
Req’d
Yes
Yes
Text
Yes
Use
Constraints
Text
Yes
Native Data
Set Format
Text
No
Supplemental
Information
Access
Constraints
Text
No
Notes
A brief narrative summary of the data set.
A summary of the intentions with which the data set
was developed.
Other descriptive information about the data set.
Restrictions and legal prerequisites for accessing the
metadata. These include any access constraints
applied to assure the protection of privacy or
intellectual property, and any special restrictions or
limitations on obtaining the metadata.
Restrictions and legal prerequisites for using the
metadata after access is granted. These include any
metadata use constraints applied to assure the
protection of privacy or intellectual property, and any
special restrictions or limitations on using the
metadata.
While this field should be populated automatically by
ArcCatalog, it is a good idea to verify the format type
is correct. In the case of the NJTPA EGIS data, the
format will be SDE Feature Class.
2
Identification→ Contact→ Point of Contact (Details button)→ General
Field Name
Primary
Contact
Person
Organization
Position
Contact Voice
Telephone
Contact Fax
Number
Contact Email
Address
Contact
Instructions
Type
Radio
Button
Text
Text
Text
Phone
Number
Phone
Number
Email
Address
Text
Req’d
Yes
No
Yes
No
Yes
No
No
No
Notes
Select ‘Organization’. The NJTPA Geoportal will give
you an error if you have selected ‘Person’.
Contact person’s name
Name of the organization responsible for the creation
and maintenance of the data set.
Title of the contact person
The telephone number by which individuals can
speak to the organization or individual.
The telephone number of a facsimile machine of the
organization or individual.
The address of the electronic mailbox of the
Supplemental instructions on how or when to contact
the individual or organization.
3
Identification→ Contact→ Point of Contact (Details button)→ Address
Field Name
Primary
Contact
Person
Organization
Position
Address Type
Address
City
State or
Province
Postal Code
Country
Type
Radio
Button
Text
Text
Req’d
Yes
Zip Code
Text
Yes
Yes
Text
Drop-Down
Text
Text
Text
No
Yes
No
Yes
Yes
Yes
Yes
Notes
Contact person’s name
Name of the organization responsible for the creation
and maintenance of the data set.
The information provided by the address.
An address line for the address.
The city of the address.
The state or province of the address.
The ZIP or other postal code of the address.
The country of the address.
4
Identification→ Citation→ Citation Information (Details button)→
General
Field Name
Title
Originator
Type
Text
Text
Req’d
Yes
Yes
Publication
Date
Online
Linkage
Date
(YYYYMMDD)
URL
Yes
Yes
Notes
The name by which the data set is known.
The name of an organization or individual that
developed the data set. If the name of editors or
compilers are provided, the name
The date when the data set is published or otherwise
made available for release.
URL to organization listed in “Originator” field.
Alternatively, you may enter a URL to a website
where the data can be downloaded. There can be 1 or
2 values entered for this field; use the ‘+’ button
under the field to add a second URL. If you wish to
leave this field blank, you must enter a single space
character in the field.
5
Identification→ Citation→ Citation Information (Details button)→
Series/Publication Information
Field Name
Publication
Place
Type
Text
Req’d
Yes
Publisher
Text
Yes
Notes
The name of the city (and state or province, and
country, if needed to identify the city) where the data
set was published or released.
The name of the individual or organization that
published the data set.
6
Identification→ Time Period
Field Name
Currentness
Reference
Type
Text
Req’d
Yes
Single Date/Time;
Multiple Dates/Times;
Range of Dates/Times
Radio Button
Yes
Calendar Date
Date
(YYYYMMDD)
Date
(YYYYMMDD)
Date
(YYYYMMDD)
Yes
Beginning Date
End Date
Yes
Yes
7
Notes
The basis on which the source time
period of content information of the
source data set is determined. Select
either “ground condition” or
“publication date”.
Means of encoding a single date and
time;
means of encoding multiple individual
dates and times; means of encoding a
range of dates and times.
The year (and optionally month, or
month and day).
The first year (and optionally month,
or month and day) of the event.
The last year (and optionally month, or
month and day) for the event.
Identification→ Status
Field Name
Progress
Update
Frequency
Type
Drop-down
Drop-down
Req’d
Yes
Yes
Notes
The state of the data set. Options are “Complete”, “In
work” or “Planned”.
The frequency with which changes and additions are
made to the data set after the initial data set is
completed. Options are "Continually", "Daily",
"Weekly", "Monthly", "Annually", "Unknown", "As
needed", "Irregular" or "None planned”.
8
Identification→ Spatial Domain→ Bounding Coordinates and G-Polygon
Field Name
North
South
East
West
Type
Decimal Degrees
Req’d
Yes
Decimal Degrees
Yes
Decimal Degrees
Decimal Degrees
Yes
Yes
Notes
Northern-most coordinate of the limit of coverage
expressed in latitude.
Southern-most coordinate of the limit of coverage
expressed in latitude.
Eastern-most coordinate of the limit of coverage
expressed in longitude.
Western-most coordinate of the limit of coverage
expressed in longitude.
9
Identification→ Keywords
Field Name
Theme Keyword
Type
Text
Req’d
Yes
Theme Thesaurus
Text
Yes
Notes
These keywords should be populated from the list
on the following pages of NJTPA keywords that
refer to the NJTPA Framework Categories, Subject
Areas, Legacy Categories and NJTPA Goals.
Entering these keywords will allow the links on the
search page of the NJTPA Geoportal to return the
dataset in the results for the associated category.
A thesaurus defines a set of keywords. There is no
limit to the amount of keywords in a single
thesaurus, however the NJTPA Geoportal only
reads the first and second Thesaurus. Therefore
you must put the NJTPA keywords in the first or
second Thesaurus listed. If creating a new
Thesaurus containing NJTPA keywords, you should
call the Thesaurus ‘NJTPA’.
10
Framework Categories
Category
Cadastral
Design Plans
Environmental
Facilities
General
Planning
Political Boundaries
Transportation
Utilities
Metadata Keyword
CadastralFramework
DesignPlansFramework
EnvironmentalFramework
FacilitiesFramework
GeneralFramework
PlanningFramework
PoliticalBoundariesFramework
TransportationFramework
UtilitiesFramework
Legacy Categories
Category
Census
Demographics
Land Use
Management Systems
Measures
National Environmental Protection Agency
Metadata Keyword
CensusLegacy
DemographicsLegacy
LandUseLegacy
ManagementSystemsLegacy
MeasuresLegacy
NEPALegacy
North Jersey Regional Transportation Model
NJRTMLegacy
Office of Smart Growth
Project Pipeline
Regional Indicators
Regional Travel-Household Interview Survey
OSGLegacy
ProjectPipelineLegacy
RegionalIndicatorsLegacy
SurveyLegacy
Regional Transportation Plan Corridors
Studies
Subregions GIS
Tele Atlas
Transportation Network
RTPCorridorsLegacy
StudiesLegacy
SubregionsGISLegacy
TeleAtlasLegacy
TransportationNetworkLegacy
11
Subject Area
Category
Capital Program
Strategy Evaluation/Refinement Area
NJ Congestion Management System
Transit
Freight Assessment
Census
Safety
New Jersey Regional Travel Model
Enhanced (NJRTME)
Metadata Keyword
CapitalProgramSubjectArea
StrategyEvaluationSubjectArea
StudiesSubjectArea
ConformitySubjectArea
CMSSubjectArea
TransitSubjectArea
FreightSubjectArea
CensusSubjectArea
SafetySubjectArea
NJRTMESubjectArea
Land Use
Regional Household Travel Surveys
NJDOT Management Systems
Other
ForecastingSubjectArea
LandUseSubjectArea
SurveySubjectArea
NJDOTManagementSystemsSubjectArea
OtherSubjectArea
NJTPA Goals
Category
Environmental Screening
Accessibility
Economic Activity
Intermodal Connectivity
Safety
Land Use & Transportation Systems
Metadata Keyword
EnvironmentalScreeningGoals
AccessibilityGoals
EconomicActivityGoals
IntermodalConnectivityGoals
SafetyGoals
LandUseGoals
12
Identification→ Browse Graphic
Field Name
Filename
Type
URL
Req’d
No
Description
File Type
Text
Drop-down
No
No
Notes
This field should only be populated if you have
a valid URL to a thumbnail image file that is
hosted on the web. Otherwise, leave this field
blank.
A text description of the illustration.
Graphic file type of the thumbnail specified in
the Filename field.
13
Data Quality→ General
Field Name
Logical
Consistency
Report
Completeness
Report
Type
Text
Req’d
Yes
Text
Yes
Notes
An explanation of the fidelity of relationships in the
data set and tests used.
Information about omissions, selection criteria,
generalization, definitions used, and other rules
used to derive the data set.
14
Data Quality→ Process Step
Field Name
Process
Description
Type
Text
Req’d
Yes
Process Date
Date
(YYYYMMDD)
Yes
Notes
Information about the events, parameters, and
source data which constructed the data set, and
information about the responsible parties. An
explanation of the event and related parameters
or tolerances.
The date when the event was completed.
15
Spatial Reference→ General
Field Name
Geographic
Coordinate System
Name
Projected
Coordinate System
Name
Horizontal Datum
Name
Type
Text
Req’d
No
Text
No
Text
No
Ellipsoid Name
Text
Yes
Numeric
Yes
Semi-major Axis
Denominator of
Flattening Ratio
Numeric
Yes
Notes
Geographic Coordinate System (Datum) that the
dataset is assigned. ArcCatalog should provide this
information by default.
Projected Coordinate System (Projection) that the
dataset is projected to. ArcCatalog should provide
this information by default.
Horizontal Datum that the dataset is assigned.
ArcCatalog should provide this information by
default.
Ellipsoid that corresponds to the Geographic
Coordinate System. ArcCatalog should provide this
information by default.
default.
default.
16
Distribution→ General
Field Name
Resource
Description
Distribution
Liability
Type
Text
Text
Req’d
Yes
Yes
Notes
The Content Type of the data should be entered
here. This field determines the Content Type that
the NJTPA will assign to the metadata for the
Content Type searches (drop-down) and also for
the icon that is displayed in the search results. The
following Content Type options are available:
Live Data and Maps
Downloadable Data
Offline Data
Map Files
Static Map Images
Other Documents
Applications
Geographic Services
Clearinghouses
Geographic Activities
Statement of the liability assumed by the
distributor.
17
Distribution→ Distributor→ Contact Information (Details button)→
General
Field Name
Primary
Contact
Person
Organization
Position
Contact Voice
Telephone
Contact Fax
Number
Contact Email
Address
Contact
Instructions
Type
Radio
Button
Text
Req’d
Yes
Text
Phone
Number
Phone
Number
Email
Address
Text
No
Yes
Text
No
Yes
No
No
No
Notes
Contact person’s name from whom the data set may
be obtained.
Name of the organization from whom the data set
may be obtained.
The telephone number by which individuals can
speak to the organization or individual.
The telephone number of a facsimile machine of the
The address of the electronic mailbox of the
Supplemental instructions on how or when to contact
the individual or organization.
18
Distribution→ Distributor→ Contact Information (Details button)→
Address
Field Name
Primary
Contact
Person
Organization
Position
Address Type
Address
City
State or
Province
Postal Code
Country
Type
Radio
Button
Text
Req’d
Yes
Text
Drop-Down
Text
Text
Text
No
Yes
Yes
Yes
Yes
No
Text
Yes
Zip Code
Text
Yes
Yes
Notes
Contact person’s name from whom the data set may
be obtained.
Name of the organization from whom the data set
may be obtained.
The information provided by the address.
An address line for the address.
The city of the address.
The state or province of the address.
The ZIP or other postal code of the address.
The country of the address.
19
Distribution→ Standard Order Process→ General
Field Name
Digital Form;
Non-digital Form
Fees
Turnaround
Ordering
Instructions
Type
Radio
Button
Text
Text
Text
Req’d
No
No
No
No
Notes
Option for obtaining the data set on computercompatible media or non-computer-compatible
media. Always use Digital Form for GIS data.
The fees and terms for retrieving the data set.
Typical turnaround time for the filling of an order.
General instructions and advice about, and special
terms and services provided for, the data set by the
distributor.
20

NJTPA Enterprise GIS (EGIS) User Manual

Transcription

Similar documents

Strategic Plan, Strategic Progress

Textiles and Apparel

NJTPA Region

Port lotniczy Kraków

200 DPI

Your global partner for every mining project

Shoreh Elhami - Center for Urban and Regional Analysis

Télécharger - Egis group

railwayengineering