# Presentation: 671728

## Spatial Data Transfer Standard Profiles:  The Key to Implementation

## SDTS is a mechanism for the transfer of spatial data

**10/01/93**

## SDTS is complex because :

**Addresses wide range of spatial data types**
**Addresses metadata necessary for complete information exchange**
**Is modular and allows user defined implementations****	**

**10/01/93**

## SDTS Spatial Data Types

**Vector - geometry and topology **
**Vector - geometry only **
**Vector - topology only**
**Raster - pixels**
**Raster - grid cells**
**Raster - n-dimensional**
**Composites**

**10/01/93**

## SDTS  Spatial Metadata Types

**Global “header” information**
**Data Quality**
**Attributes & Data Dictionary**
**Graphic Representation**
**Text**
**Symbology**
**Area fills**

**10/01/93**

## SDTS Modules

**GLOBAL**

**DATA QUALITY**

**SPATIAL**

**GRAPHIC REP**

**ATTRIBUTE**

**Lineage**
**Positional Accuracy**
**Attribute Accuracy**
**Logical Consistency**
**Completeness**

**Point - Node**
**Line**
**Arc**
**Ring**
**Polygon**
**Raster Defn.**
**Layer Defn.**
**Dimension Defn.**
**Cell**

**Identification**
**Catalog**
** ****/Directory**
** ****/Cross Ref.**
** ****/Spatial Domain**
**Security**
**Internal Spatial**
**  ****Reference**
**External Spatial**
**   ****Reference**
**Registration**
**Spatial Domain**
**Data Dictionary**
**  ****/Definition**
**  ****/Domain**
**  ****/Schema**
**Transfer Statistics**

**Text Representation**
**Line Representation**
**Symbol Representation**
**Area Fill Representation**
**Color Index**
**Font Index**

**OTHER**

**Composite**
**Coding**

**Attribute Primary**
**Attribute Secondary**

## A full implementation of all possibilities of the SDTS in a single software system is a monumental, if not impossible task.

**10/01/93**

## Profiles assist in the implementation of the SDTS.

**10/01/93**

## The SDTS contains limited pre-defined structures, and allows for defining new relationships.

**10/01/93**

## The SDTS does not specify:

**Organization**
**Structure of modules**
**Modules to be used**
**Structure and linkage of attribute data**
**Order of modules**
**Module names**
**Multiple uses of modules**
**Record order in modules**
**etc.**

**10/01/93**

## The SDTS can be used like a tool kit.

**Different users may use the tools differently.**
**Some tools may perform several tasks.**
**Some tasks may be done several ways.**
**Resulting data sets may be difficult  to decode.**

**10/01/93**

## Profiles make decisions about possibilities not addressed, left optional, or left with numerous choices in the SDTS.

**10/01/93**

## Profiles Provide Order

**Subset of SDTS**
**Not stand-alone**
**Address a specific data type**
**Structures choices allowed by SDTS**
**Extensions to the standard for well-defined cases**

**10/01/93**

## Profiles address all three levels of a transfer:

**Conceptual**
**like which family of data is permitted**
**Logical**
**like which modules are required/excluded**
**Format**
**like file names, module to file relationships**

**10/01/93**

## A profile can provide for:

**Module names**
**Attribute organization**
**Order of the transfer file set**
**Order of modules**
**Order of records within modules**
**Order of fields within modules**
**Creation of the transfer file set**
**File names**
**Location of files**
**Required contents**

**10/01/93**

## Profiles provide a key to the transfer file set’s organization and content.

**10/01/93**

## Software Development

**Software written to address a transfer file set created under a profile is easier to write and maintain.**

**10/01/93**

## Profile Philosophy

**Reduce the level of ambiguity in a transfer file set**
**Specify manageable subsets differentiated by spatial data model/structure**
**Restrict options as much as possible**
**Add mandatory specifications where useful**
**Restrict variations among profiles as much as possible**
**Existing profiles are used as a guide**

- 10/01/93

**10/01/93**

## Who Creates Profiles?

**Any agency/group wanting to implement SDTS**
**Profile development is coordinated by the SDTS Task Force**

**10/28/93**

## When should a Profile be Created?

**When aspects of a source data model have specific requirements not addressed or allowed in an existing profile.**
**Developers are encouraged to use an existing profile.**

**10/28/93**

## Formal Profiles

**These profiles are being submitted for ratification by a standards body**
**Topological Vector Profile**** **
**Part 4, Ratified FIPS 173b June 94**
**Point Profile**** **
**Part 6, FGDC review April 97**
**Raster Profile with BIIF Extension**
**Part 5, drafted by joint USGS, NIMA group May 97**

**10/28/93**