Technical Issues in NOAA's Nautical Chart Program (1996) / Chapter Skim
Currently Skimming:
3 Technical Considerations
3 Technical Considerations
Pages 18-24
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 18... ...
POPULATING THE VECTOR DATABASE To provide and support digital vector data products, nautical chart features will need to be captured and stored in a vector database rather than in raster chart images. While currently there is no legal requirement for NOAA to produce a complete vector digital data product, a demand exists for new products with some data themes captured in vector form.
|
From page 19... ...
The process of loading a vector database with all data currently contained in the paper chart suite is costly, but technically possible; contractors are currently doing similar work for the Defense Mapping Agency (DMA)
|
From page 20... ...
editions of chart products and the timely management and maintenance of large amounts of source data are among the main reasons for moving to a digital production system. DATA STANDARDS The two primary data formats used in international nautical applications are S-57 and VPF (see detailed discussion in appendix D)
|
From page 21... ...
Participation on the international technical committees that develop these specifications helps NOAA ensure that the standards evolve within an overall plan of change, thereby causing minimum impact on systems. NOAA could promote consistency by publicizing this position, alerting data users to be prepared for data within standard formats, and allowing software systems developers to be prepared to create and use this data.
|
From page 22... ...
In a marketplace where a high percentage of COTS solutions are applied, the federal government no longer will be able to dictate the use of specific standards, and commercial practice will frequently bypass federal standards. Consequently, although standards can be used effectively and are necessary to define data formats and content, a migration plan that attempts to plan data systems over more than a five-year period, or to foresee every contingency, is probably not realistic.
|
From page 23... ...
Because of the significant investment that other agencies of the federal mapping, charting, and geodesy community have made, it is possible for NOAA to reduce its overall system development costs by taking advantage of code that has already been developed and tested to perform similar tasks. Another key element in controlling software costs is to use as many standard COTS modules as possible and to modify requirements to avoid custom coding whenever possible.
|
From page 24... ...
These difficulties make it clear to the committee that in undertaking the development of future systems, it is worthwhile for NOAA management to pay critical attention to methods and management practices documented in the literature of systems engineering science, management science, technology development, and organizational change, and to benefit from the lessons learned by other federal government agencies that have undertaken similar modernization programs (DOD, 19954. The basic building blocks for improving the management of complex technological and engineering projects are qualified staff to manage the project, highlevel reporting and access of the project manager to senior management, stable assignment of the project manager and supporting staff, a team approach to implementation, timely decision making, and the enforcement of a systems engineering methodology.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.