WPC 2 BU Z-0pt (TA)#|d2cpi (M)Helv 14pt Bold (AD)Helv 12pt Bold (AD)Prestige Elite 12cpi (M)^,,4Xp,44P,4,TXXXXXXXXXX,,Hddp|PHx|00dL|\\XX|h\Xd4T4XP,T\P\T0T\$(T(\\\\8D4\P|LPPXPLHP LaserJet Series II (Additional)HLSEIIAD.PRSd6X@C,t0u'm@2%- #|[Prestige Elite 12cpi (M)Helv 14pt Bold (AD).PRSd6X@C,t0qD@2 WY_/Prestige Elite 12cpi (M)Helv 14pt Bold (AD)Helv 12pt Bold (AD)Prestige Elite 12cpi Bold (M)Courier 10cpi BoldTmsRmn 12pt Bold (AD)* /tC4,-Xt2pQX.uSddd,A9dp,`NQ.Prestige Elite 12cpi (M)Helv 14pt Bold (AD)Helv 12pt Bold (AD)Prestige Elite 12cpi Bold (M)dTdd4hlXpX@`p<@lYo'BVq3D\r2. 1e"m,^4@@d4LLd0@0ddddddddddd88`ĀxPd|t|TdTdd4hlXpX@`p<@l ( ) | | ( ?????? ) | | ( ???????? ) | | ( ?? ?? ) \/ ********** ( ?? ) ********** * * ( ??? ) * * * Production * ( ??? ) * ISO 8211 * * Systems * ( ??? ) * DDF * * Databases * ( ??? ) * (Transfer * * * ( ) * Fileset)* ********** ( ??? ) ********** ^ ( ??? ) | | ( ) | | ( ) | | ( ) <  uSH  Components of a Spatial Data Transfer Processor#2p;׼#у@ Any transferprocessing system would have to start from the production systems databases and produce ISO 8211 files. The amount of expertise needed is too great to combine in one component. Think of the system with a component for each area of expertise... 0*&& @ Addxx addxx @ @  ? #x `w;5X# | \ ..... / \. ./ . . CONCEPTUAL LEVEL SDTS Conceptual SDTS Part 1, Sect 1,2,3,4.1 . . SDTS Part 2 / ..... \ / | \ =================== SDTS Specifications LOGICAL LEVEL SDTS Part 1, Sect 4.2,5 =================== ISO 8211 Encoding IMPLEMENTATION LEVEL SDTS Part 3 =================== ISO 8211 "Specification for a Data Descriptive File for =================== Information Interchange" MediaDependent * MEDIA (Physical) LEVEL | Standards | Tape, Disk, CD ROM | . * . | . . | | Cartridges, etc. |:| |:| |:| |:| |:| #2p;׼# A reminder of the wide range of knowledge needed to use the SDTS. You wouldn't expect a single person to be proficient in all of these areas. So, why would you expect a single program to be? ,0*&& @ addxx ddxx @  x  uS #d `w;9# | SDTS | | ISO 8211 | |>| EXPORTER | >| ENCODER || | | | | | | | | | \/ | \/ ********** ********** ********** * * * * * * * Production * * Transfer * * ISO 8211 * * Systems * * Repository * * DDF * * Databases * * * * (Transfer * * * * * * Fileset)* ********** ********** ********** ^ | ^ | | | | | | | SDTS | | | | ISO 8211 | | || IMPORTER |< | DECODER |<  uS  Components of a Spatial Data Transfer Processor#2p;׼#уx#Xl4  p ;X# An implementation of SDTS requires expertise in SDTS, profiles, ISO 8211, and user data mappings. Any transferprocessing system would have to start from the production systems databases and produce ISO 8211 files. The components in between these two are based on the concept of 'isolation of expertise'. Each component has expertise in a certain area. E ddxx  ddx  E x  ComponentQ Area of Expertiseq SDTS Exporter maps from user data model to SDTS logical modelqqQ SDTS Importer !3 maps from SDTS logical model to user data modelsqq ISO 8211 Encoder creates SDTS/Profile ISO 8211 filesqq3 ISO 8211 Decoder interprets SDTS/Profile ISO 8211 filesq Transfer Repository understands SDTS/Profile content and requirements  Overview of the System Repository will be populated with data from the production systems and/or from data received via spatial data transfers. The ISO 8211 Encoder and Decoder functions will handle processing the data into and out of SDTS/Profilecompliant file format,C%0*&& respectively. The SDTS Export function will provide data from production systems to the Repository. Likewise, the SDTS Import function will take data from the Repository and  X place it in the production systems. #2p;׼#0*&& E ddx   ddxx E   %Component: Production Systems /Databases oXrefers collectively to all of the data used or generated in the production of spatial products(# oXa subset of the information will be required to fulfill the content requirements of a transfer(# ======================================== Now, let's take a closer look at the responsibilities of each component. First the components on the encoding operation path will be covered (Prod. Dbs, SDTS Exporter, Transfer Repository, ISO 8211 Encoder, ISO 8211 DDF). Then the remaining components concerned with the decoding operation (ISO 8211 Decoder, SDTS Importer) will be covered. The Production Systems Databases refers collectively to all of the data used or generated in the production of spatial products. This includes map separates (analog), digital files, technical instructions (text), points used for accuracy testing, control information, etc. A subset of this information will be needed to satisfy the content requirements of the SDTS. (These are the collective data of your existing processing systems.) 0*&& @ ddxx  ddxx @   'Component: SDTS Exporter oXTakes data from the production systems and sends it to the Transfer Repository(# oXKnows the mapping of the user data model to the logical structure of SDTS (# XExample: Knows that a DLG3 "area point" is equivalent to an SDTS "area point" and must occur in a PointNode module(# ======================================== The SDTS Exporter will take data from the production systems and send it to the Transfer Repository. This function will require many interfaces to existing systems on a wide variety of platforms. The Exporter will need to: XoX` ` respond to requests from the Transfer Repository for data(#` XoX` ` capture data (scan or data entry) not in digital form (i.e. map collar information)(#` XoX` ` allow module crossreferences to be defined(#` XoX` ` know the mapping of the user data model into the logical structure of a transfer (e.g., knows that a DLG3 "area point" is equivalent to an SDTS "area point" and must occur in a PointNode module)(#`  0*&& @ ddxx  ddx x @   $Component: Transfer Repository oXmanages all of the data required by the SDTS modules(# oXenforces rules and restrictions involving module/transfer content(# XExample: If subfield 'External' in Catalog/Directory has value Y, then subfield Module Version must also be valued.(# ======================================== The Transfer Repository manages all of the data required by the SDTS modules. Any rules and restrictions involving module/transfer content will be enforced by the Transfer Repository. Some of the tasks related to data management are: XoX` ` generating unique record ids within the modules(#` XoX` ` generating unique module names within a transfer, enforcing any applicable naming conventions(#` XoX` ` generating the contents of the Transfer Statistics Module(#` XoX` ` knowing what data is required for a module(#` XoX` ` knowing what data is required for a transfer based on transfer content and applicable profile(#` XoX` ` insuring module crossreferences and foreign ids are valid(#` XoX` ` reporting the status of a transfer what is present and what is missing(#` XoX` ` enforcing any restrictions (dealing with other than ISO 8211 implementation constructs) imposed by profiles (#` 6% 0*&& @ ddx x  !ddx x @  9 &Component: ISO 8211 Encoder oXreceives the information from the Transfer Repository and creates a SDTS transfer fileset (# oXknows the mapping of SDTS to ISO 8211(# XExample: Global modules must not share an ISO 8211 file(# ======================================== The ISO 8211 Encoder will receive the information from the Transfer Repository and create a SDTScompliant ISO 8211format transfer. Some of the tasks that this will involve are: XoX` ` calculate field widths and byte counts in the leaders and directories(#` XoX` ` order the records in a file to maximize the use of dropped leaders(#` XoX` ` enforce any file naming conventions(#` XoX` ` supply the module location information in the Catalog/Directory module(#` XoX` ` use the appropriate medialevel standard(#` XoX` ` enforce any restrictions (dealing with ISO 8211 or media standards) imposed by profiles(#` " 0*&& @ !ddx x  Addx x @  y #Component: SDTS Transfer Fileset oXconsists of one or more ISO 8211 files, on one or more media volumes(# oXreceived from and sent to other organizations (# ======================================== The SDTS Files are the complete set of files on one or more media volumes that constitute a transfer. These are sent to/received from other agencies. These files are in the ISO 8211 format, and are physically encoded on the media using a mediadependent standard. Z 0*&& @ Addx x  addx x @  7 &Component: ISO 8211 Decoder oXtakes the information from a SDTS transfer fileset and sends it to the Repository(# oXknows how to interpret ISO 8211 files(# XExample: Can recover module records from ISO 8211 files(# ======================================== ISO 8211 Decoder will do things like: XoX` ` verify correct ISO 8211 format(#` XoX` ` use appropriate medialevel standard (#` XoX` ` use the data descriptive information to process the transfer files(#` XoX` ` use SDTS knowledge to parse out modules and module records(#` XoX` ` handle files spanning media volumes(#`  0*&& @ addx x  ddx x @   'Component: SDTS Importer oXtakes the data from the Repository and sends it to the appropriate production system(# oXknows the mapping of SDTS to the production systems(# XExample: Information from PointNode modules that are entity points will become 'degenerate lines' (DLG3 terminology).(# ======================================== The SDTS Importer will take the data from the Repository and ship it to the appropriate production system. Because SDTS is so general, there is a large number of possibilities when receiving transfers. The Importer will need to: XoX` ` know the mapping of the SDTS constructs into the user data model(#` XoX` ` detect transfers in a format it is not programmed to handle (i.e., transfer contains an arc, and your systems cannot work with these.)(#` XoX` ` generate reports to aid the user in determining how data should be shipped to production systems(#`  0*&& @ ddx x  ddxx @  +The System Design oXprovides a common basis for communication (# oXguides the formulation of projects(# oXassists in making managerial decisions concerning resources (# ======================================== This system design is intended to aid in communications by providing a common basis of discussion. It is also intended to guide the formulation of projects. It would be possible to identify manageable tasks with clearlydefined goals, which is critical to the success of large systems development. Also, the system design could be used to guide managerial decisions concerning where resources should be concentrated. The system design is intended as a framework to guide discussions, project proposals, and managerial resource decisions. 0*&& @ ddxx  ddxx @   $Software Development Guidelines oXUse the system design as a guide, i.e. don't try to include too much expertise in a single routine (# oXFormulate objectbased designs, viewing data and processes as a whole (# oXKeep the interface between components minimal and welldefined(#