applying the nsdi framework transportation standard for data exchange
DESCRIPTION
Applying the NSDI Framework Transportation Standard for Data Exchange. Facts and Fallacies. Facts. The NSDI Framework Transportation Feature Identification Standard is intended to support data exchange. Proposes a method of identifying transportation features. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/1.jpg)
Applying the NSDI Framework Transportation Standard for Data Exchange
Facts and Fallacies
![Page 2: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/2.jpg)
Facts
The NSDI Framework Transportation Feature Identification Standard is intended to support data exchange.Proposes a method of identifying transportation features.Includes a means of transferring data about those features.
![Page 3: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/3.jpg)
Files, Not Tables
The standard is expressed as a set of feature “naming” rules and file formats.The standard is NOT a data model for production databases.The files are transactional in design to support chronological updates.Does not define a topological network.
![Page 4: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/4.jpg)
Transactional Files
Authority ID and the record’s creation date are always part of the “primary key.”No records are ever removed.Updates consist of extracting records written since a defined date, such as the last update for the user.
![Page 5: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/5.jpg)
Problems with Previous Draft
Readers tried to use the file structures as a data model for production systems.Many reviewers thought the graphic conventions used in the standard had to be adopted internally.Too much emphasis on feature segmentation methods.
![Page 6: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/6.jpg)
Other Issues
Color graphics didn’t photocopy well.No guidance on moving between the exchange files and production databases.Lack of clear description of transactional nature.Confusing references to networks and topology.
![Page 7: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/7.jpg)
“Authority” Defined
“Any organization that takes responsibility for proposing, designating, or working in partnership with other organizations to define FTRPs and FTSegs.” [Sec. 2.3.1]
![Page 8: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/8.jpg)
Characteristics of an Authority
Create or update transportation databases (or plan to do so), and Share those databases or related attribute sets with others (or plan to do so), and Conform data exchange practices to this standard. [Sec. 2.3.1]
![Page 9: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/9.jpg)
Authority ID
Five characters in length.Starts with two-character FIPS code for the state or “00” for federal and multi-state entities.Last three characters are sequentially defined for each authority.Requires an authority registrar.
![Page 10: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/10.jpg)
Transportation Features
Framework Transportation Segments (FTSegs).Framework Transportation Reference Points (FTRPs).FTRPs are placed at the end of each FTSeg.Co-terminus FTSegs share a common FTRP.No topology required, but can be constructed using FTRP types.
![Page 11: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/11.jpg)
FTSeg Defined
“A specified directed path between two Framework Transportation Reference Points (FTRPs) along a physical transportation feature that identifies a unique linear element of that feature.” [Sec. 2.3.7]
![Page 12: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/12.jpg)
FTRP Defined
“The specified location of a (required) endpoint of a Framework Transportation Segment (FTSeg), an (optional) intermediate point along an FTSeg defined by an offset distance from the origin of the FTSeg, or a (optional) location off the linear system defined by FTSegs.” [Sec. 2.3.3]
![Page 13: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/13.jpg)
Example Data Sets
PoliticalBoundary
FTSeg
FTRP
Not anFTSeg
TerminalFTRP Multi-path
FTSegs
Not anFTSeg
IntermediateFTRP
![Page 14: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/14.jpg)
Multiple Segmentation
Different Authorities can segment the same set of transportation features to meet different application needs: State DOT segments break at State Road
intersections and state line. County segments break at major roads and
county line. City segments break at all street crossings.
Reconciled using Equivalency File.
![Page 15: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/15.jpg)
Feature IDs
Basic form is AAAAA.F.XXXXXXXX.“AAAAA” is the Authority ID.“F” is the type of feature (FTRP=‘P’, FTSeg=‘S’).“XXXXXXXX” is a sequence number defined by the Authority.Decimals are explicit; i.e., include them.
![Page 16: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/16.jpg)
How to Get Started
Segment the transportation network into discrete linear elements.Place connection/termini points at the end of segments.Place other points at locations of special interest (along or off segments).Apply naming conventions.Publish initial set of segments and points.
![Page 17: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/17.jpg)
The File Structure
One header record that contains file name.One or more body records.Each data record uses ASCII character string fields separated by tab characters (ASCII 9) and terminated by a carriage return (ASCII 13) and a line feed (ASCII 11).All fields must be included; null values (ASCII 0) must be explicit.
![Page 18: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/18.jpg)
Caveat
The following slides are based on discussions to date and do not reflect an adopted standard. Final details may differ slightly from those shown here.
![Page 19: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/19.jpg)
Authority File
Authorities are involved in data development and maintenance.Authority creating the record need not be the one that created the identifiers.Status = ‘P’, ‘A’, or ‘R’.
Authority File
authority-IDdateauthority-namecontact-person-primarycontact-voice-telephonecontact-fax-telephonecontact-email-addresscontact-URLcontact-instructionsauthority-addressauthority-cityauthority-stateauthority-zipauthority-countyauthority-access-infoauthority-infostatus
![Page 20: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/20.jpg)
FTRP File
Describes where it is and how the location was determined.Location stated using WGS 84 datum.Supported by FTRP feature type and measurement method files (look-up tables).
FTRP File
authority-IDFTRP-IDdatelocation-descriptionFTRP-feature-typelatitudelongitudehorizontal-measure-methodhorizontal-accuracyelevationvertical-measure-methodvertical-accuracystatus
FTRP Type File
authority-IDFTRP-feature-typedatemeaning
![Page 21: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/21.jpg)
FTSeg File
States terminal FTRPs, what path it follows, and how the segment length was determined.Length stated in meters.Supported by FTSeg feature type and measurement method files (look-up tables).
FTSeg File
authority-IDFTSeg-IDdatefrom-endpointto-endpointpath-descriptionintermediate-point-IDFTSeg-feature-typestatelengthlength-measure-methodstatus
FTSeg Type File
authority-IDFTSeg-feature-typedatemeaning
![Page 22: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/22.jpg)
Intermediate FTRP File
Indicates the FTSeg upon which the intermediate point exists.States the distance offset from FTSeg origin in %.Supported by offset measurement method file (look-up table).
Intermediate FTRPFile
authority-IDFTRP-IDdateFTSeg-IDFTSeg-offsetoffset-measure-methodstatus
![Page 23: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/23.jpg)
Equivalency File
Indicates relationship between one set of features and another.Supports FTRP:FTRP, FTRP:FTSeg, and FTSeg:FTSeg equivalencies.Supports direction differences between FTSegs.
Equivalency File
authority-IDdatereference-FTRP-FTSeg-IDfrom-reference-offsetend-reference-offsetequivalent-FTRP-FTSeg-IDfrom-equivalent-offsetto-equivalent-offsetstatus
![Page 24: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/24.jpg)
Attribute File
The “real” data exchange mechanism.Some Authorities may only define and share attribute data.Supports linear LRS.Use SDTS for cartographic data.
Attribute File
authority-IDFTRP-FTSeg-IDdatefrom-offsetend-offsetattribute-nameattribute-value
Attribute Type File
authority-IDattribute-namedatemeaningunit of measure
![Page 25: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/25.jpg)
Example of Integration
TransportationFeature Table
tranfeatureIDstartonenteredonenteredbyretiredontranfeattypeID (FK)externalkey (PK)latestFLGbeginmilepointendmilepointdirectionID (FK)length
Event Table
tranfeatureID (FK)eventIDstartonenteredonenteredbyeventtypeID (FK)beginmilepointendmilepointsidelateraloffsetvaluelatestFLGdescriptionscheduledtimeactualtime
FTSeg Table
ftsegIDstartonenteredonenteredbytranfeatureID (FK)authorityIDfwtransegIDdatefromendpointtoendpointpathdescriptionintermediatepointftsegfeaturetypestatelengthlengthmeasuremethodstatus
FTRP Table
ftrpIDstartonenteredonenteredbytranfeatureID (FK)authorityIDfwtransegrefptIDdatelocationdescriptionftrpfeaturetypelatitudelongitudehorizmeasuremethodhorizaccuracyelevationvertmeasuremethodvertaccuracystatus
Attribute Table
attributeIDstartonenteredonenteredbytranfeatureID (FK)eventIDauthorityIDfwtranfeatureIDdatestartoffsetendoffsetattributenameattributevalue
IntermediateFTRP Table
connIDstartonenteredonenteredbyauthorityIDfwtransegrefptIDdateftsegIDftsegoffsetoffsetmeasuremethodstatus
Is onBegins
Ends
![Page 26: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/26.jpg)
Close Up - FTSegsTransportationFeature Table
tranfeatureIDstartonenteredonenteredbyretiredontranfeattypeID (FK)externalkey (PK)latestFLGbeginmilepointendmilepointdirectionID (FK)length
FTSeg Table
ftsegIDstartonenteredonenteredbytranfeatureID (FK)authorityIDfwtransegIDdatefromendpointtoendpointpathdescriptionintermediatepointftsegfeaturetypestatelengthlengthmeasuremethodstatus
FTSeg Table derived from legacy transportation feature table.Extra FTSeg data stored in FTSeg Table.FTSeg File records are created as updates to FTSeg Table occur.
![Page 27: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/27.jpg)
Close Up - AttributesAttribute Table derived from legacy Event Table.Attribute File records are created as updates to Event Table occur.
Event Table
tranfeatureID (FK)eventIDstartonenteredonenteredbyeventtypeID (FK)beginmilepointendmilepointsidelateraloffsetvaluelatestFLGdescriptionscheduledtimeactualtime
Attribute Table
attributeIDstartonenteredonenteredbytranfeatureID (FK)eventIDauthorityIDfwtranfeatureIDdatestartoffsetendoffsetattributenameattributevalue
![Page 28: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/28.jpg)
Final Draft Changes
Emphasize transactional nature.Reduce segmentation content.Show how to migrate/integrate with existing databases.Illustrate how to use the standard with multiple examples.Use monochrome graphics conventions.
![Page 29: Applying the NSDI Framework Transportation Standard for Data Exchange](https://reader034.vdocuments.us/reader034/viewer/2022052401/568147f6550346895db52ccb/html5/thumbnails/29.jpg)
Contact the Author
Al Butler, GIS DirectorOrange County, [email protected]; 407-836-5514
Mark Bradford is Chair of the FGDC Ground Transportation Committee; [email protected].