shrug-l: Parcel Data issue assistance

Mayo, Michele Michele.Mayo@dep.state.fl.us
Tue, 4 May 2004 10:51:43 -0400


This is a multi-part message in MIME format.

------_=_NextPart_001_01C431E7.5090D488
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

=20

Brian,

=20

My experiences with a similar issue may be helpful.  I provide GIS =
support
for a program that also has a need to integrate historical spatial data =
with
newer data that has improved coordinate accuracy.  Its an issue of =
supporting
a system of processes which are dependent on a data set that is =
essentially
still in development.  The tricky part is that you're dealing with =
multiple
records for the same real-world feature.

=20

The solution was to design a GDB that models the interdependent parts of =
the
composite data set and enables me to maintain data integrity among =
multiple
sources, as well as the lineage of the data, within the GDB schema.  The
central concept of the design, courtesy of Linc Clay, is the use of a =
core
feature class that is a composite of it's sources with relationships to =
each
of the original sources.  The key points are:

=20

            Create separate feature classes for each of the original =
data
sources.

=20

Create a core feature class that contains one and only one record of all
features (a "record of record").  The criteria for choosing the source =
of
each record are up to you.

=20

            Create a system of keys that enable relationality between =
the
core FC and the source FCs.

=20

Create subtypes within each source FC that distinguish features having
membership in the core FC from those that don't.

=20

Create subtypes within the core FC that denote the source.

=20

Create a system of relationship classes between the core FC and the =
source
FCs with relationship rules that use the subtypes to constrain the
relationship to that subset of each FC to which you want the =
relationship to
apply.  Allow notifications to pass in both directions for flexibility =
when
validating edits.

=20

Give some careful thought to how you want to structure the attribute =
data.
You may want to maintain any attributes with fixed values in a =
standalone
table that will be independent of spatial edits.

=20

I also like to use a layer file to filter features that have pending QA
issues from the working data set.

=20

=20

Your situation is a bit more challenging than mine because I am dealing
primarily with point features.  To do this with polygons, you'll need to
create some topology rules as well.

=20

I hope this helps.  Let me know if you can use more detailed =
information.

=20

=20

Michele

=20

=20

Michele Mayo,  ES III - GIS Analyst

Florida DEP, Groundwater Regulatory Section

2600 Blair Stone Road MS 3580

Tallahassee, FL 32399

(850) 245-8658

michele.mayo@dep.state.fl.us

=20

=20

           =20

=20

-----Original Message-----
From: Pierce, Brian [mailto:pierceb@doacs.state.fl.us]=20
Sent: Tuesday, May 04, 2004 9:01 AM
To: shrug-l@lists.dep.state.fl.us
Subject: shrug-l: Parcel Data issue assistance

=20

I have been asked to distribute the following request for assistance.  =
Please
contact me if you can assist or point us to the right direction.

=20

Parcel data (polygon shapes with attribute data) were originally =
acquired
from multiple sources (different scales and projections) and "massaged" =
to
overlay on county boundaries, roads, hydrography, PLSS and other primary
layers.  The parcel files were merged into one ArcSDE feature class.

=20

Parcel shapes and attribute data (including parcel number and owner
information) was modified by the program area for some parcel shapes =
since
originally obtained.

=20

Regulatory action has been taken on some properties based on the parcel
shape, its relationship to other shapes, and attributes as they are =
currently
in the database.

=20

The program area must maintain the historical data on which these =
previous
regulatory actions were based.

=20

New parcel data is available from various sources (not all are the =
original
source).

=20

The program area is looking for sources that may have dealt with these =
issues
of maintaining historical GIS data while also updating the data for =
future
decision making.

=20

The program area seeks assistance with:

=20

1. Is there methodology/best practices to compare and integrate newer =
data
sets into an application as described above while retaining historical =
data
sets supporting prior actions?

2. What factors need to be considered in preparing the new data set for
integration into the application?

3. Is there methodology for incorporate parcel data from multiple =
sources
into a single data set at a more generalized scale (1:24000)?

=20

Thanks;

Brian

***********************************************************

Brian D. Pierce

GIS Project Manager

Florida Dept. of Agriculture & Consumer Services

(850) 245-1061

Fax: (850) 245-1076

pierceb@doacs.state.fl.us

************************************************************

=20


------_=_NextPart_001_01C431E7.5090D488
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">
<title>Message</title>

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Tahoma;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>Brian,</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>My experiences with a similar =
issue may
be helpful.&nbsp; I provide GIS support for a program that also has a =
need to
integrate historical spatial data with newer data that has improved =
coordinate
accuracy. &nbsp;Its an issue of supporting a system of processes which =
are
dependent on a data set that is essentially still in development.&nbsp; =
The
tricky part is that you&#8217;re dealing with multiple records for the =
same
real-world feature.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>The solution was to design a GDB =
that
models the interdependent parts of the composite data set and enables me =
to
maintain data integrity among multiple sources, as well as the lineage =
of the
data, within the GDB schema.&nbsp; The central concept of the design, =
courtesy
of Linc Clay, is the use of a core feature class that is a composite of =
it&#8217;s
sources with relationships to each of the original sources.&nbsp; The =
key
points are:</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Create
separate feature classes for each of the original data =
sources.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>Create
a core feature class that contains one and only one record of all =
features (a &#8220;record
of record&#8221;).&nbsp; The criteria for choosing the source of each =
record
are up to you.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Create
a system of keys that enable relationality between the core FC and the =
source FCs.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>Create
subtypes within each source FC that distinguish features having =
membership in
the core FC from those that don&#8217;t.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></f=
ont></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>Create
subtypes within the core FC that denote the source.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>Create
a system of relationship classes between the core FC and the source FCs =
with
relationship rules that use the subtypes to constrain the relationship =
to that
subset of each FC to which you want the relationship to apply.&nbsp; =
Allow
notifications to pass in both directions for flexibility when validating =
edits.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></f=
ont></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>Give
some careful thought to how you want to structure the attribute =
data.&nbsp; You
may want to maintain any attributes with fixed values in a standalone =
table
that will be independent of spatial edits.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></f=
ont></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>I also
like to use a layer file to filter features that have pending QA issues =
from
the working data set.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>Your situation is a bit more =
challenging
than mine because I am dealing primarily with point features.&nbsp; To =
do this
with polygons, you&#8217;ll need to create some topology rules as =
well.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>I hope this helps.&nbsp; Let me =
know if
you can use more detailed information.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>Michele</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><b><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue;
font-weight:bold'>Michele Mayo</span></font></b><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>,&nbsp;
ES III - GIS Analyst</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
color=3Dblue
  face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>Florida</span></=
font><font
size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:blue'> DEP, Groundwater Regulatory </span></font><font size=3D2 =
color=3Dblue
 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>Section</span></=
font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
color=3Dblue
  face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>2600
  Blair Stone Road</span></font><font size=3D2 color=3Dblue =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'> MS =
3580</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
color=3Dblue
  face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>Tallahassee</spa=
n></font><font
 size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
 color:blue'>, </span></font><font size=3D2 color=3Dblue =
face=3DTahoma><span
  =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>FL</span></font>=
<font
 size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
 color:blue'> </span></font><font size=3D2 color=3Dblue =
face=3DTahoma><span
  =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>32399</span></fo=
nt></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>(850)
245-8658</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
color=3Dblue
face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:blue'>michele.mayo@dep=
.state.fl.us</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DTahoma><span =
style=3D'font-size:
10.0pt;font-family:Tahoma;color:blue'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Pierce, Brian
[mailto:pierceb@doacs.state.fl.us] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, May 04, =
2004 9:01
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
shrug-l@lists.dep.state.fl.us<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> shrug-l: Parcel =
Data
issue assistance</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>I have been asked to =
distribute the
following request for assistance.&nbsp; Please contact me if you can =
assist or
point us to the right direction.</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:blue'>Parcel data
(polygon shapes with attribute data) were</span></font><font =
color=3Dnavy><span
style=3D'color:navy'> </span></font><font color=3Dblue><span =
style=3D'color:blue'>originally
acquired from multiple sources (different scales and projections) and
&quot;massaged&quot; to overlay on county boundaries, roads, =
hydrography, PLSS
and other primary layers.&nbsp; The parcel files were merged into one =
ArcSDE
feature class.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:blue'>Parcel shapes
and attribute data (including parcel number and owner information) was =
modified
by the program area</span></font><font color=3Dnavy><span =
style=3D'color:navy'> </span></font><font
color=3Dblue><span style=3D'color:blue'>for some parcel shapes since =
originally
obtained.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:blue'>Regulatory</span></font><font
color=3Dnavy><span style=3D'color:navy'> </span></font><font =
color=3Dblue><span
style=3D'color:blue'>action has been taken on some properties based on =
the parcel
shape, its relationship to other shapes, and attributes as they are =
currently
in the database.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:blue'>The =
program
area must maintain the historical data on which these previous =
regulatory
actions were based.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:blue'>New =
parcel
data is available from various sources (not all are the original =
source).</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:blue'>The =
program
area is looking for sources that may have dealt with these issues of
maintaining historical GIS data while also updating the data for future
decision making.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:blue'>The =
program
area seeks assistance with:</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:blue'>1. =
Is there
methodology</span></font><u><font color=3Dnavy><span =
style=3D'color:navy'>/</span></font></u><font
color=3Dblue><span style=3D'color:blue'>best practices to compare and =
integrate
newer data sets into an application as described =
above</span></font><font
color=3Dnavy><span style=3D'color:navy'> </span></font><font =
color=3Dblue><span
style=3D'color:blue'>while retaining historical data sets supporting =
prior
actions?</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:blue'>2. =
What
factors need to be considered in preparing the new data set for =
integration
into the application?</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
color=3Dblue
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:blue'>3. =
Is there
methodology for incorporate parcel data from multiple sources into a =
single
data set at a more generalized scale (1:24000)?</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Thanks;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Brian</span></font></p>

</div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>****************************=
*******************************</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Brian D. =
Pierce</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>GIS Project =
Manager</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Florida Dept. of =
Agriculture &amp;
Consumer Services</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>(850) =
245-1061</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Fax: (850) =
245-1076</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><a
href=3D"mailto:pierceb@doacs.state.fl.us">pierceb@doacs.state.fl.us</a></=
span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>****************************=
********************************</span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C431E7.5090D488--