1 / 11

Cadastral Data Exchange Standard version 2.0

Proposal to include Map Index boundary as optional shapefile in Cadastral Exchange Standard, a major amendment to enhance GIS data standards forum. Process involves group discussions, revisions, and community feedback for approval and adoption by OGIC.

hixon
Download Presentation

Cadastral Data Exchange Standard version 2.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cadastral Data Exchange Standard version 2.0 11th Annual GIS Standards Forum March 10, 2009

  2. Proposal by the Tax Lots Workgroup: Add Map Index Boundary as an optionalitem to the exchange standard Map Index: Polygon boundaries that represent the map area that is the boundary of a group of tax lots. The deliverable is an optional shapefile provided as part of the Cadastral Exchange Standard.

  3. Major Amendment to the Standard • Determined that this addition to the CDE Standard represented a “Major” amendment to the standard. • Examples cited in the “Procedures for Amending Standards” include: • Making significant changes to the data model • Adding to the list of minimum attributes • Or changing optional items to required items Adding Map Index Polygons was determined to be a “significant” change to the data model.

  4. Why include Map Index as part of the Standard? Many Counties already have this as a layer in their GIS; or can generate them by merging tax lots Map Index polygons aid DOR in the assembly of ORMAP Goal 2 data Map Index polygons can be merged to create an outer County Boundary – facilitate future county edgematching efforts

  5. Amendment Process • Discuss changes with Tax Lot workgroup • Incorporate changes into the existing standard (v 1.4) • Publish to GEO’s web page – 45 day review • Comments/Suggestions brought to FIT group for review • Updated standard presented to GIS community for approval Revised Standard posted to GEO’s web page on December 3, 2008 Received comments from 6 parties.

  6. Revision Posted to Web Site:

  7. Revision Posted to Web Site: • Feedback: • CVD ambiguous • Please list valid attributes • “Auto” fields not part of current standard, can we remove them? • - Use a standard naming convention for the mapindex shapefile • Comment on format for taxlot field in tax lot polygon attributes

  8. Revisions to the first Amendment:

  9. Amendments to the first Revision: • defined domain values • defined valid attribute values • included shapefile naming standard • removed “auto” fields from standard • - Reviewed tax lot polygon “Taxlot” field – seems to be OK

  10. Next Steps: • Repost to GEO’s GIS Data Standards web site for second 45-day review and comment process • Tech Group Review – possibly at the second ORMAP Grant review meeting on April 16, 2009 • Notification of intent to adopt the standard presented to GIS Community – email notification • Adoption by OGIC at appropriate quarterly meeting

More Related