Section 11 Washington State Cadastral Framework Project.doc
资源目录
压缩包内文档预览：
编号：19063078
类型：共享资源
大小：236.22KB
格式：RAR
上传时间：2019-05-09
上传人：hon****an
认证信息
个人认证
丁**（实名认证）
江苏
IP属地：江苏
6
积分
- 关 键 词：
-
测绘工程专业英语
测绘工程专业
- 资源描述：
-
测绘工程专业英语,测绘工程专业英语,测绘工程专业
- 内容简介：
-
Section 11 Washington State Cadastral Framework Project:Implementing the FGDC Cadastral Data Content Standardand Integrating Datafrom Multiple SourcesABSTRACT: The Washington Cadastral Framework Project is a National Spatial Data Infrastructure (NSDI) demonstration project intended to show the benefits of building partnerships, sharing costs and coordinating work, standardizing data and tools, speeding up application development, improving and documenting data, resolving data conflicts, and sharing data. The Washington Cadastral Framework Project is broken down into two phases which are pilot projects designed to implement a standard cadastral data set and to integrate cadastral data from multiple data sources. Phase 1 (September1997 to September 1998) involves extending and implementing the Federal Geographic Data Committee (FGDC) Cadastral Data Content Standard in SDE/Oracle, populating the database with initial data, developing metadata on the data, and distributing the data over the Internet to project partners. The Cadastral Data Content Standard was extended to work with other framework data content themes: Geodetic Control, Hydrography, Transportation, and Governmental Units. Phase 2 (September 1998 to September 1999) involves adapting the FGDC Cadastral Data Transfer Standard for data exchange, integrating data from several representative partner sources (federal, state, regional, county, city, and private organizations), developing update-locking procedures for long transactions over the Internet, and automating the integration process so that minimal intervention is required for enforcing standards and resolving conflicts.IntroductionCadastral data are the geographic extent of the past, current, and future rights and interests in real property. Rights and interests are the benefits or enjoyment in real property that can be conveyed, transferred, or otherwise allocated to another for economic remuneration (Federal Geographic Data Committee (FGDC), Cadastral Subcommittee 1996).Typically, cadastral records are kept by public and private surveyors, county recorders, county tax assessors, land title companies, private land management businesses, private land agents, and government agencies entrusted with public lands. Each organization keeps the records that are necessary to conduct its business. Surveyors measure and describe land; they keep records of their surveys and legal descriptions. Counties are responsible for publicly recording business transactions including conveyances, easements, leases, and sales from the land, and they keep these records. County tax assessors are interested in the value and usage of land as the basis of local government revenue. Land title companies duplicate the records of land transactions and add value by spatially indexing those transactions. Private land managers, such as timber, railroad, and mining companies, along with government agencies managing public lands, must track the extent of their large and dispersed holdings, and they must also track any encumbrances and restrictions placed on those holdings which limit the use of the land. Private land agents, such as developers and realtors, watch the transactions of land closely for investment and marketing. Each organization keeps a specific and detailed proprietary database of its business interests. All of these organizations conduct business among each other, and many are interested in communicating their land holdings and transactions to facilitate their business operations. The goals of the project described in this paper are to develop a basic information standard for communication about land holdings and transactions, create a common database of cadastral information, and implement a method of communicating cadastral information between organizations and the common database.The Washington Cadastral FrameworkThe Washington Department of Natural Resources (DNR) has many interests in cadastral information. Washington became a state in 1889, taking possession of all aquatic lands and a selection of non-private uplands. The DNR currently manages about 2,000,000 acres of aquatic lands and 3,000,00() acres of uplands held in trust for the public.The State land Survey Office of the DNR maintains a statewide data set of the Public Land Survey System network, corners, and state ownership parcels (Washington Department of Natural Resources 1997b). The Land Records Office maintains the documentation of state land ownership, easement, resource sale and lease transactions and is in the process of automating these records into a data set. The Resource .Mapping Section of the Department of Natural Resources collects ownership, administration, and management information from other public agencies and maintains a data set of major public lands inventory(Washington Department of Natural Resources 1997a). The Aquatic Land Ownership Unit is building a data set of the aquatic subdivisions of land and state ownership parcels.One of the Department of Natural Resources interests in the Cadastral Framework Project is the completion and integration of all the cadastral data sets with the framework cadastral database. The Department is also interested in converting its Arc/Info coverage database into a SDE/Oracle feature database (Arc/Info and SDE are proprietary geographic information system softwares developed by the Environmental Systems Research Institute).The Department of Natural Resources has a great interest in improving the quality of spatial data and developing standards for distributing spatial data in general. The Department has actively participated in many geographic information system cooperative initiatives to set standards of spatial data communication, integrate spatial data sets, and provide methods of accessing spatial data sets. As member of the Washington Geographic Information Council (VAGIC), the DNR has provided direction for improving government geographic information products and services.In the Data96 project initiated in 1994, the Department of Natural Resources worked with private, tribal, local, state and federal organizations to complete existing transportation, hydrography, land survey, and topography data sets. The data were put into a common format and distributed to the partners. The Washington Geographic Information Council was awarded an FGDG grant for the Washington Clearinghouse in 1995. The clearinghouse is a searchable national catalog of metadata allowing users to find existing data sets and their data sources. Metadata provided by DNR for six data sets are now available on the Washington Clearinghouse Node. An extension of the clearinghouse concept into searchable catalog of prospective projects would allow users to locate partners for developing data sets that do not exist.The Washington Framework Management Group (FMG) was initiated m 1996 to direct the implementation of the NSDI framework strategy within Washington State. The FMG was charged with coordinating and facilitating the statewide geospatial framework. In 1996, the Cadastral Framework Project and Hydrography Framework Project were identified as high-priority targets for Washington framework development. Later, the Washington Transportation Framework Project Was identified for development. The DNR created a framework coordination work unit in 1997 to support the FMG and facilitate and coordinate the framework projects. Coordination of framework efforts has allowed the DNR to participate at a national level as well as at: state level. In 1998, the FMG was recognized as a subcommittee of the WAGIC (WAGIC 1998).Playing a leadership role in supporting the Framework Management Group, the Department o Natural Resources focused on the Cadastral Framework Project. The Department began recruiting partners and scoping the project, and hired a project manager to plan and oversee the project development. A Framework Demonstration Project Program grant proposal was written for the project which was approved for $65,000 in 1997. After completion and approval of a project feasibility study by the DNRs Information Technology, Board, the project took off the ground. A follow-up grant proposal to help fund phase 2 of the project was submitted and approved for S99,000 in 1998.A cross-section of federal, state, county, regional, and private organizations have joined in the effort to develop and test an inter-organizational partnership approach to create, manage, and distribute base cadastral data for the state of Washington. The project partners include die U.S. Bureau of Land Management, U.S. Bureau of Reclamation, U.S. Forest Service, U.S. Geological Survey, Washington Department of Natural Resources, Washington Department of Revenue, Washington Interagency Committee for Outdoor Recreation, Washington Department of Transportation, Washington Department of Community Trade & Economic Development, Puget Sound Regional Council, Clark County, Douglas County, Spokane County, Stevens County Partnership, Thurston Regional Planning Council, Yakima County, Longview Fibre Inc., Weyerhaeuser Corporation, and the Environmental Systems Research Institute (ESRI).Some of the partners have highly developed GIS data and applications; others are just beginning. Partners have contributed funds, in-kind hours of service and input, or a combination thereof. A wide variety of business requirements and expectations of the Washington State Cadastral Framework have been discussed and identified. The partnership has developed a charter and a partnership agreement. The charter identifies tile goals and objectives of the partnership. The agreement specifies the benefits of joining the project partnership, and limits the use of the data and the application system during the development phase of the project.Framework Partners The National Spatial Data Infrastructure means the technology, policies, standards, and human resources necessary to acquire, process, store, distribute, and improve utilization of geospatial data. The framework is the core set of geospatial data that are significant to a broad variety of users and to the process of ongoing data maintenance. The framework data themes are geodetic control, ortho-imagery, elevation, transportation, hydrography, government units, and cadastral information. Subcommittees of the FGDC coordinate the development of these key data categories. Working groups of the FGDC address issues that transcend data categories, such as archives, clearinghouse, facilities, framework, and standards (FGDC 1998c).The Federal Geographic Data Committee coordinates the development of the National Spatial Data Infrastructure at a national level. The FGDC is using three major programs to generate interest and support the development of the framework. The Framework Demonstration Project Program (FDPP) helps fund projects that demonstrate the sustained ability to develop tile framework from local data sources. The Competitive Cooperative Agreements Program (CCAP) helps fund the testing of different framework aspects. The NSDI Benefits Program helps fund projects that demonstrate the benefits of sharing data between organizations (FGDC 1997).Development SummaryDeveloping an application to update a spatial data set over the Internet is an ambitious undertaking, so the project was broken down into two phases. The objective of the first phase was to develop and implement an FGDC-compliant data model, convert existing DNR statewide cadastral data coverages (POCA, PLS-PT, and MPI.), and serve the data over the Internet. During Phase 2 the objective is to develop data exchange and edit environments, and to integrate other internal and project partner data. As the database structure becomes more standardized and technology advances, a third phase may include the development of tools and utilities for automating the partner data integration process. That final phase was not planned at the time of writing this report. FGDC Cadastral Data Content Standard The FGDC Cadastral Data Content Standard models the business of tracking rights in land conveyed through transactions. The standard identifies the business components involved in land surveying and land recording as well as the relationships between them. The main components of the standard are legal descriptions, including boundaries and comers, parcels, transactions, rights, restrictions, agents, and document sources (FGDC, Cadastral Subcommittee 1996).In the cadastral data content model, the parcel is the focus of rights and interests in land. The extent of a parcel is compiled from legal description components that are individual Public Land Survey (PLS), mapped lots, metes and bounds, boundary, and strip descriptions (Wattles 1987). The descriptions may be associated to boundaries and corners which may also include direct references to ownership parcels. Transactions convey rights for parcels between agents. Restrictions are imposed on parcels by public agencies. Document sources index where to find legal descriptions, restrictions, transactions, boundaries, agents, corners, and coordinate measurements in the public record or in private files. Parcels and agents may be located by addresses. The standard also standardizes domains of allowable values for attributes of cadastral entities, and defines the cadastral entities and attributes. Educational materials on the standard are now on the Web (FGDC, Cadastral Subcommittee 1998b). Washington Cadastral Requirements Analysis Data analysis was approached from several directions: the FGDC Cadastral Data Content Standard, a partner requirements survey and review, existing DNR coverages, and by developing DNR projects. There are some areas of the FGDC Cadastral Data Content Standard that have been modified in the Washington Cadastral Framework Project. The modifications are a documentary clarification of the cadastral standard; a restructuring of the relationships between entities; and extensions to the content. A narrative of the intended use of the Cadastral Data Content Standard is not included in the standard itself. It took several months of data modeling and direct guidance from members of the Cadastral Subcommittee to establish and document how the Cadastral Framework Project would use the standard. Because of the technical and legal complexity of land surveying and land transaction, data analysts need extensive background to understand what they are working on. The entity, and attribute definitions of the standard are expanded, and domain value definitions are added. Supertypes/subtypes are identified and broken down. The meaning of relationships are defined and labeled on the standards diagram to assist in its use. A transition of DNR datasets from Arc/Info to Oracle/SDE was conducted simultaneously with the adoption of the Cadastral Data Content Standard. A complete transition required that content extensions be made to facilitate the conversion of these within the context of the whole data model. The extensions include the additional framework themes of governmental units and geodetic control. Monuments were separated from corner points in the model to include geodetic control.A project partner requirements survey was developed from the FGDC Cadastral Data Content Standard. The survey asked partners which of the entities and attributes they maintained, and of those, which were shareable on the framework. It also asked for information on the entities and attributes that were needed by each partner, but not maintained by them. From the trickle of partner requirement changes that came in later through review sessions it became apparent that some partner requirements were missed and that this should not have been the only approach. Metadata about partner proprietary cadastral systems should have been collected to identify existing partner requirements for the data that are used and provided or received in data exchanges. The partner metadata in the form of the FGDC Metadata Content Standard could also then be submitted to and used by the clearinghouse for search, query, and location of data sets (FGDC 1995). Additional partner requirements included relationships from record boundary to hydrography and transportation features, significant location as a coordinated point, attributing corners with Geographic Coordinate Database codes, and Federal information Processing Standard codes (Bureau of Land Management 1997). In the context of existing DNR data coverages, a technical analysis was performed to document the physical structure and the foreign key relates, and also to logically normalize the entities, attributes, and relationships. In terms of developing DNR projects, the Automated Tract Book Project and the Aquatic Land Ownership Project are included in the development data model. The complexity of this approach is apparent, and some of the logical modeling was reworked in physical prototyping. The structure of relationships between Parcel, Parcel Transaction, Transferred Right, and Agent was changed from the Cadastral Data Content Standard to allow for the collection of initial data. In most cases, GIS databases do not store land transaction data that would document a clear line of title. Without modification, the standard would not be able to accept data converted from existing databases. Therefore, the relationships were altered in the Washington model for Parcel Transaction to go between Parcel, Agent, and Document as a three-way relationship. Transferred Right was attached directly to Parcel. Some of the data provided to the Cadastral Framework database may not be thoroughly documented, but publishing the information with source documents over the Internet exposes challenges and forces recovery of transaction documentation. The accuracy of ownership and encumbrance information will increase over time.Several things were learned from the September 1998 National Spatial Data Infrastructure meeting. The data content standards are minimally attributed sets of data necessary to conduct the business of each FGDC theme. Extension of the data content standard should usually be limited to the business proprietary database, not the common partner database. However, data content standards for governmental units, geodetic control, hydrography, and transportation have not been developed yet. Theme extension from the perspective of the Cadastral Data Content Standard is the only option currently available. Prototyping and Physical Data Design The complexity of the logical data model required resolution of the many possible implementations of the model. Prototyping was used in several cases to force resolution of the supertype/subtype entities. Lack of data to fill in some of the relationships between tables is another problem worked out in the physical implementation. Being new to the object oriented feature model of SDE also made prototyping of implementation ideas necessary. At first individual extracts of data sets from coverages were made. However, it was apparent that these could not readily be converted back to an integrated coverage format for editing in a conventional Arc coverage environment-most of the tools for editing in a SDE/ArcView shape format have not been developed or have not had the time to mature. The approach we have taken is to extend the base coverage to a region format and then convert to SDE layers based on the region subclasses using the ArcPlot SDE utilities. These layers can be merged back together into a region coverage for editing. Metadata Development Metadata developed for the Washington Cadastral Framework Database have been on the Washington Clearinghouse Node of the Federal Geospatial Data Clearinghouse (Washington Cadastral Framework Partnership 1998b) since August 1998. The clearing- house metadata are a brief summary of the whole cadastral data set. Metadata for individual layers of the Washington Cadastral Framework Database are developed separately and are available from the project Web site (Washington Cadastral Framework Partnership 1998a). The intent is to Have the most general metadata searchable at the national level, then more detailed metadata available at the state level. Internet DistributionESRIs ArcView Internet Map Server (IMS) was chosen to serve the data over the Internet. ArcViews Database Access extension allows a direct connection to the SDE database. ArcViews IMS extension serves GIS data for map display and query through a customizable standard interface. The IMS offers several formats of standard interfaces as multiple frames. The layout and number of these frames is easily adjusted in the master, and the content of several frames may be modified by editing the HTML. JAVA enhancement of the standard Web page and the Map Cafe viewer are also possible. As each SDE layer was implemented, a database theme was created in ArcView to display the layer and allow queries. In some cases, a database query had to be constructed to filter the data from the layer. The activation scale was set for each of the themes so that they are displayed and can be queried at an appropriate level. Modifications were made to allow the Identify button to return query results from all active themes. The default only returned query results from the first active theme. One change to the Identify command was the retention of the defined database query because Identify was nullifying the defined query and producing unexpected results from the filtered theme.At the time of writing this paper, the legal area descriptions for Public Land Survey townships and sections were available to Framework Partners by county or state. Boundaries, corner points, state ownership, other public ownership, government units, and administrative subdivisions were expected be available by the date of publication. Interactive selection of data within a rectangular envelope was developed with JAVA. More tools for selecting data to download will be developed as needed. (Washington Cadastral Framework Partnership 1998a.) FGDC Cadastral Data Transfer Standard The FGDC cadastral Dam Transfer Standard exists as an Arc/Info regions export coverage. This standard is basically the same as the Cadastral Data Content Standard, except that at the time of writing this article it included only PLS legal area descriptions (FGDC, Cadastral Subcommittee 1998a). The data transfer standard has no coding scheme and may be difficult to use for data exchange.Washington cadastral framework partners decided that data contributed to the Standard needed to be validated before integrating them into the framework database. In order to increase the speed and accuracy of update transactions, values for many attributes were coded. Text string searches, which take time and can be inaccurate, were minimized. Database Integration The focus of the data integration process is to facilitate accurate and timely data integration to the Framework database while minimizing the effort that has to be spent by the Integrator on validating data and resolving errors. Additional cadastral data transfer standards will be developed to allow an exchange of data over the Internet using shape files, export coverages, and AutoCAD formats. The participants in the database integration process are data developers, data providers, database stewards, database integrators, database administrators, and data users. Data developers create proprietary databases which have data that could be shared in a framework database. Data providers are certified to provide data updates to the framework database. Data stewards are the business experts familiar with cadastral data who have been designated to certify data sets for integration, and resolve database conflicts. Data users are the public and private agencies who conduct cadastral business, and who are targeted for cadastral framework publicity and information. Database integrators review the results of integration validation and respond to problems and conflicts. Database administrators support the framework database operations, backup, and recovery. The developer, the data sets, and metadata must be certified by the database stewards for updating the database. The developer builds a procedure to convert data from the proprietary database to a data transfer standard with the assistance of the database integrator. Cadastral framework data sets include legal area descriptions, boundaries, corners, geodetic control points, parcel transactions, record documents, government units, and administrative areas. Data developers who are creating or revising their proprietary databases will have the opportunity to adopt the FGDC Cadastral Data Content Standard to make framework transactions easier. Once the developer has been certified as a data provider, the provider can check data out of tile database, make updates, and check data back into a staging area. Check-out is limited to the providers jurisdiction and authority. Updates are to be on a 30-day cycle; check-outs for updates that are expired will be canceled. The framework integration application will validate data by transaction, authority, jurisdiction, and history. Transactions are validated by the conformance with the data structure. Authority is validated by the data sets which have been certified for the provider. For example, the provider must have a land surveyor make updates of legal area descriptions, boundaries, or comers. Jurisdiction is validated by geographic area. History is validated against the existing records in the database. The database integrator must then review the validation reports and plots to decide whether to accept the database update from the staging area. If there are database integration problems, such as formatting or coding problems, then the integrator will return the update to the provider with the validation report. If there are data conflicts in the update, such as accepting a different monument as the representation of a corner, then the integrator must consult with the data steward and the provider to determine the intent of the update and decide whether to accept the update. Data older than those current in tile database should be retired on check-in (Hair et al. 1997).Next StepsFile next steps are to reexamine business events and processes. Events include data change, data integration problem, data conflicts, database failure, and data requirement change. Processes include data development, location of developed data through clearinghouse indexing, data provider certification, data editing, database update notification, database maintenance, database integration, database integration problem resolution, database conflict resolution, database backup and recovery and database change control. The procedural response to each event, and the details of each process, are being finalized with partners. Data stewards will draft quality control standards for data certification. The standards will determine the authority and jurisdiction of data providers. Data stewards will also examine data conflict situations. Data parameters identifying conflict situations will have to be developed to minimize database integrator intervention. It is envisaged that data stewards will have to work through conflict resolution processes to handle each situation. The project will construct an update and integration application. Database administrators will continue to evaluate data formats for editing and exchange. Partners will integrate framework data within the pilot geographic area of Snohornish County.
- 温馨提示:
1: 本站所有资源如无特殊说明，都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
2: 本站的文档不包含任何第三方提供的附件图纸等，如果需要附件，请联系上传者。文件的所有权益归上传用户所有。
3.本站RAR压缩包中若带图纸，网页内容里面会有图纸预览，若没有图纸预览就没有图纸。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 人人文库网仅提供信息存储空间，仅对用户上传内容的表现方式做保护处理，对用户上传分享的文档内容本身不做任何修改或编辑，并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容，请与我们联系，我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。
人人文库网所有资源均是用户自行上传分享，仅供网友学习交流，未经上传用户书面授权，请勿作他用。
|
2:不支持迅雷下载,请使用浏览器下载
3:不支持QQ浏览器下载,请用其他浏览器
4:下载后的文档和图纸-无水印
5:文档经过压缩，下载后原文更清晰
|
川公网安备: 51019002004831号