# Presentation: 262538

## Community Update and Transportation Data

- Donald Cooke, Founder
- Geographic Data Technology, Inc
- NATMEC 2000
- August 29, 2000
- ***USE “NOTES” VIEW IN POWERPOINT***

## GDT

- The “Dynamap” Company
- Founded in 1980; 448 employees
- Dominant supplier of spatial data for Business Geographics applications
- Dominant supplier of spatial data for WWW-mapping and locator services

**Notes:**
GDT is a company I founded in 1980, which has grown, as of this writing (Sept 15, 00) to 448 employees with no end in sight.  GDT seems to have figured out how to make money maintaining a “better TIGER file”.  One might argue that our Dynamap street database is the country’s defacto transportation data layer, based on our market penetration in business, web, and CD consumer markets.  

GDT takes seriously, understands, and values the USA’s policy that the citizens own the intellectual property generated by the Federal government.  It was only because of this policy that GDT even exists. The goal of the company has always been to take the best of public data, make it better and easier to use, and earn money in the process.  

We believe that this policy creates a unique, synergistic “co-evolutionary” state where GDT and the Census Bureau have a productive collegial relationship, and also purchase and use each other’s datasets.  When details of the relationship are examined, it is clear that everyone (Census, GDT, users, taxpayers) benefits from this dynamic created by Federal data policy.

The point of this presentation is to explain GDT’s new “Community Update” partnership and present it as a model for maintaining transportation datasets. 

## National Spatial Data Infrastructure: “NSDI”

- “The NSDI consists of spatial datasets with huge -- nearly universal -- utility, and such a high return-on-investment that they should be made available as a public good”
- (Spatial datasets are just computerized maps)

**Notes:**
Note that this is not the standard definition of the NSDI, which reads more like:
	“The NSDI is the means to assemble geographic information that describes the arrangements and attributes of features and phenomena on the Earth.  The infrastructure includes the materials, technology, and people necessary to acquire, process, store, and distribute such information to meet a wide variety of needs.”  NRC Mapping Science Committee,1993

I harbor a firm opinion that we made a mistake by adopting the “process” definition of NSDI.  The focus should be on the “thing”, to employ Mike Goodchild’s distinction.

“It’s the spatial datasets, stupid!”  (not the process)

## What constitutes the NSDI?

- Seven “framework” themes (NSGIC):
- Geodesy
- Orthoimagery
- Elevation
- Transportation
- Hydrography
- Governmental Units
- Cadastre

**Notes:**
This is an excellent starting taxonomy of important NSDI datasets.

We have two choices, both of which we should do:

1) Build the datasets

2) Discuss and refine this list.  

Though I am temperamentally better suited to choice #1, which is what my company is doing, I do have opinions on choice #2.  For example, I would leave off “Geodesy”, as it fails my definition of the NSDI (previous slide), as it is only of interest as a spatial dataset to GIS nerds (myself included!).  

But because of the past several decades of practice with these themes,  we know enough about them to forge ahead with NSDI implementation.

## Who is responsible for the NSDI?

- Traditionally the Federal Government
- (for some of the themes...)
- NGS does geodesy
- USGS/Agriculture/BLM make DOQs
- Census Bureau does transportation network(!)
- BLM & states/counties maintain land records
- What is the role of the private sector?
- Who owns the data?
- Is the NSDI a public good or not?

**Notes:**
When you look at who is responsible for various framework themes, a lot of interesting questions arise.

## History of Cartography

- First map (stone!) 2500BC
- Paper
- Printing Press
- Location determination/Surveying
- Aerial Photography
- Orthorectification
- Computer storage of spatial data
- Internet

**Notes:**
This is a distillation (no pictures) of one of my “stump speeches”, designed to get people to see that the advents of computers and the internet are the latest in a long string of cartographic technology.  

I used to think that the “big event” in the technology of cartography (map-making) was the computer; now I am realizing that the internet, and wireless access to it, is equally important.

## Slide 7

**Notes:**
Community Update is a public-private partnership between GDT and local governmental agencies (county or town) to maintain the transportation layer of the NSDI.  

As in true partnerships, no money changes hands.

## Public - Private Partnership

- Realizing the promise of the
- SCSD: Street Centerline Spatial Dataset
- (Transportation) component of the NSDI

**Notes:**
A sound-byte for C.U.!

Following slides show the C.U. conception as it was originally unveiled in July 1999: 

## COMMUNITY UPDATE

- Free Download of Local Dynamap Coverage

**COMMUNITY UPDATE**

**Notes:**
Using ESRI's ArcIMS, Community Update allows local knowledge providers to access GDT's database free of charge over the Internet.  These agencies can then provide updated information and data enhancements directly to GDT. GDT validates the information and may add additional attributes or enhancements. The revised data for the local area  is then available, at no cost via ArcData Online, to the local agencies that help improve the data. Community Update is the perfect public-private partnership, creating a dynamic and evolving nationwide spatial data infrastructure.

## Free Download Using ArcData Online

**Free Download Using ArcData Online**

**Notes:**
Data is posted on ESRI ArcData Online.  The Community Update partners use a special account to download the information for free.  

## COMMUNITY UPDATE

- Street Updates, Address Changes,
- New Boundaries

**Map Markup**

- Free Download of Local Dynamap Coverage

**COMMUNITY UPDATE**

**Notes:**
The ideal CU partner is the local official who is the first to know of new streets and addressing changes.

A major purpose of C.U. is to remove the friction and time required for spatial knowledge (new streets) to get from the originators to the users.

An example of a demanding user is Sears Logistics, which has to dispatch and deliver appliances to a new house well before the occupants move in.

If more efficient dispatching is to take place, the GIS database -- or NSDI transportation data theme, must be continuously updated.

The public benefits from Sears, and others, using this NSDI dataset.  The customer is told exactly when the delivery will arrive.  The big delivery trucks drive fewer miles, consuming less fuel and creating less pollution and traffic congestion.  Sears saves money, which raises their profits, which raises their tax payments!  This is where the big ROI (return on investment) for spatial data kicks in.

## Community Update Edit Using arcIMS

**New** **Road** **Added**

**Community Update Edit Using arcIMS**

**Notes:**
The user is transferred to an arcIMS session showing their area of interest.   It is then possible to add new roads, change address ranges, remove roads, adjust politcal boundaries in addition to other changes. 

## COMMUNITY UPDATE

- Street Updates, Address Changes,
- New Boundaries

- Conversion to GDT
- Operational Format

**Map Markup**

- Free Download of Local Dynamap Coverage

**COMMUNITY UPDATE**

**Notes:**
Data returns to GDT -- the “steward” of the transportation theme -- for QC, spatial alignment, Postal currency, etc.

## GDT Mapping Tech Reviewing Updates

**GDT Mapping Tech Reviewing Updates**

**Notes:**
A GDT mapping technician quickly reviews the proposed chances and brings up whatever information we have to confirm the changes.  Our sources include digitized air photos, satellite imagery, postal records, and paper maps in addition to many other sources.

## Road Added to GDT Database before 

**Alignment with Orthorectified Image**

**Notes:**
Typically, new developments are entered freehand much smaller than they really are.  It is extremely useful to have a relatively accurate representation of the new street -- as above -- available for immediate use.  Most applications are not sensitive to spatial errors of even several hundred feet, as above.

GDT flags each segment with individual metadata codes which track the origin and accuracy of each data element.  This enables position-sensitive applications to use only those elements which meet application criteria, and also greatly streamline eventual positional realignment.  See next slide.

## Road Added to GDT Database after 

**Alignment with Raster Image**

**Notes:**
GDT has a huge positional accuracy effort underway.  We have made extensive DGPS field measurements, following the FGDC’s new NSSDA. (National Standard for Spatial Data Accuracy).  These tests show a consistent 4 to 6-meter RMSE (root-mean-square-error) accuracy for our dataset -- significantly better than 1:24,000 DLGs (digital line graphs.) and so-called “navigational-quality” databases.

GDT employs many terrabytes of SAN (storage area network) storage to house the nations DOQs (which are, incidentally, another of the seven framework themes).  These accurate, registered images are available to our DMTs (digital map technicians) to ensure and achieve 4-6 meter RMSE accuracy wherever possible.

Contact me if you want to know more about GDT’s accuracy program.

## COMMUNITY UPDATE

- Street Updates, Address Changes,
- New Boundaries

- Conversion to GDT
- Operational Format

**Map Markup**

- Free Download of Local Dynamap Coverage

- Updates Applied

**COMMUNITY UPDATE**

- Satellite
- Images

- Current
- USPS
- data

- Digital ortho-
- photo quads

- Paper Maps,
- GIS datasets

**Notes:**
This graphic simply underscores the added value of GDT’s ongoing processes.

Data is posted on ESRI arcData Online.  The Community Update users can then download the information for free.  The loop continues with the next update.

## Benefits

**COMMUNITY UPDATE**

**Benefits**
** ****Dynamap****®**** quality**
** ****Positional Accuracy: RMSE<8 meters**
** ****Rapid Updates - Postal currentness**
** ****Work on applications, not GIS update**
** ****Enhanced Data Layers**
** ****WWW Data Availability**

**Notes:**
Here is our “pitch” to potential C.U. partners:

“We recognize the local communities of the country have the best possible data available.  Using Community Update, you can have the most up-to-date data and accurate data available in digital form.  You won’t have to do the day to day maintenance of a complex spatial database.  You will be able to take advantage of GDT other layers such as water boundaries, railroads, etc. which are part of the standard GDT product.  The data that you help maintain will be available to regional emergency responders and companies interested in your area so that they too have the most accurate and current information available - improving both public safety and commerce.”

## Who owns the data?

- Public Domain ethic at Federal level
- “Tower of Babel” at the state level
- Private sector must “own” its data assets
- Can’t copyright “facts”
- Is there some subset of data that is public and some other that is proprietary?
- Rules of scale and convenience
- Aging of dataset relates to value

**Notes:**
No answers here:  just a list of the issues.  I would welcome a continuing dialogue on this subject.

........... I am convinced that the advent of the internet is a huge, positive, disruptive force to our thinking about how maps (spatial data) should be maintained.  The Community Update model is THE way to maintain an ongoing nationwide transportation framework data theme.  The technical design resonates positively with everyone who understands it. I don’t see a viable alternative to this model of spatial dataset maintenance.

The surprise to me, after 33 years of practice, is that this concept originates in a private sector company.  This imposes a huge burden and responsibility  on GDT to function as a trusted steward of this national resource.  We are challenged to maintain a public good without the authority to levy taxes.  

Many organizational issues remain unresolved, and some of them have been identified in the foregoing slides.  I welcome any comments on this presentation and its possible application to transportation databases.
		Donald Cooke, GDT, Sept 15, 2000