ROK Blog

Esri’s Parcel fabric offers a clean and efficient way to maintain and edit high quality land records. The fabric joins data into a cohesive structure allowing edits to apply across multiple features in a database. This creates easier workflows, increased data integrity, and reduced headaches for land record managers.

So how do land records transcend the old school’s messy data models into the fluid structure of Esri’s parcel fabric?

1.  Create and set up a staging geodatabase             

• Data clean up with topology rules
• Parcel line preparation

Creation of necessary source data attributes for migration
2.  Create and set up a future geodatabase that will contain the parcel fabric inside Esri’s Local Government Information Model  schema

• Tailor this geodatabase to original land records data (i.e. spatial reference, creation of structure to support migration of source attributes, etc.)

3.  Migrate the data

• This step is computer process intensive and could tie up a machine for a while
• Paramaterization of data migration tool

4.  Review the migration

• It is essential that a thorough review of the newly created parcel fabric is conducted for quality control purposes. There are a few known issues and fixes to employ if a parcel does not migrate into the fabric.

Check out this Esri whitepaper for more information.

For more information regarding the parcel fabric, check out the comprehensive parcel fabric training seminar co-hosted by ROK technologies and Panda Consulting at the college of Charleston March 13-15.

Today we have a guest entry from Steve Eakins, who is the GIS Manager at ETM, an engineering firm from Jacksonville, Florida. ROK and ETM have collaborated often on some large scale projects. Without further delay, here is Steve discussing a recent collaboration on Geodatabse replication.

Working with ROK we have been able to setup SDE geodatabase replication using the ESRI 9.2 Desktop product since ESRI added that function in their release last year.

Database replication gives us the ability, through a secure VPN connection, to maintain our data on the ROK SDE geodatabase. We can, on an automated regular schedule, synchronize only the changes thereby, minimizing network bandwidth utilization during peak hours while keeping our clients ROK hosted website up to date. Replication for us is enabled one way so that the ROK database is a child of our parent master.

Using replication reduces delays in mailing or oversights in forgetting to send all the changed data. This is a huge time saver and is truly a win-win scenario.

For more information see ESRI's website on database replication using ArcGIS 9.2 at http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=Understanding_distributed_data

Then talk to the ROK!

Jason Harris