HomeMy WebLinkAboutRFP - P836Exhibit "1"
P-836: PLACEMENT OF FEATURE LINKED ADDRESS ANNOTATIONS
City of Fort Collins
Geocrarhic Infamdion Services
2 element(s) now selected
Arcedit:
list
Record
TYPE#
TYPE -ID SOILCOV AI ANNO ITEM
6
0 2
1
12
0 4
2
Arcedit:
calc ai_anno_item
='rel1/lattribute2'
Arcedit:
list
Record
TYPE#
TYPE -ID SOILCOV AI_ANNO_ITEM
6
0 2
1 rell//attribute2
12
0 4
2 rell//attribute2
6. To update the annotation text displayed using item values from the
feature attribute table.
Now that the annotation subclass, anno.type, is linked to soilcov's PAT by
AI_ANNO_ITEM, ARCEDIT will display the value of AI_ANNO_ITEM as
annotation text. When the PAT is updated, it will automatically update the
annotation text displayed. For example, if you update soilcov's item
ATTRIBUTE1's value to 'silty clay', the annotation will be updated after a draw is
issued and will display'silty clay' as text.
Arcedit: de poly anno.type
Arcedit: draw
Arcedit: of poly
Arcedit: select one
Arcedit: moveitem 'silty clay' to attribute1
Arcedit: draw
AI_ANNO_ITEM calculated to a blank value will display the default $TEXT value,
not a blank. You cannot calculate AI_ANNO_ITEM to display a blank.
Another way to use Al-ANNO_ITEM is to change the database table name of the
related file instead of changing the Relation Name//item as you did in the
previous example. In this example, you only need to change the Table Identifier
in the relate list.
1. To set up lookup tables.
In this example, you have two lookup tables, english.lut and swedish.lut
The lookup table, english.lut, has an item named ID with a definition of 4, 5, B
and an item named TEXT with a definition of 24, 24, C and the following records:
$RECNO ID TEXT
1 1 One
2 2 Two
3 3 Three
4 4 Four
5 5 Five
The lookup table, swedish.lut, has an item named ID with a definition of 4, 5, B
and an item named TEXT with a definition of 24, 24, C and the following records:
$RECNO ID TEXT
1
1
Ett
2
2
Tva
3
3
Tre
4
4
Fyra
5
5
Fern
2. To create an annotation attribute table (TAT).
Arcedit: ec langcov
Arcedit: createfeature anno.lang
Arcedit: createattributes
3. To add AI_ANNO_ITEM to the TAT.
Arcedit: additem ai_anno_item 32 32 c
Arcedit: items
Column ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED
1 LANG# 4 5 B -
5 LANG-ID 4 5 B -
9 AI ANNO ITEM 32 32 C -
4. To add annotation records.
Add five annotation records with text as 'TXT'. ($TEXT = TXT) For this example,
'TXT' is used as the default text to be displayed so that you know when you're not
using a relate. You can use any text as the default text.
5. To set up a relate between the lookup tables and the TAT.
The following aml will set up a relate between the two lookup tables, english.lut
and swedish.lut, and the TAT in ARCEDIT.
/*Iangrel.aml
/*Aml uses english.lut and swedish.lut. RH
&args lang
&if [null %tang%] &then
&s lang english /* default
/*using keyword allows you to abbreviate the argument
&s key = [keyword %fang% english swedish]
&if %key% < 1 &then
&s lang = english
&else
&s lang = swedish
relate add
lang
%lang%.lut
INFO
lang-id /* subclass
id
linear
ro
relate list
&return
6. To select all the annotation records and calculate the value -of
AI_ANNO_ITEM to equal the value of the related item.
Arcedit: select many
5 element(s) now selected
Arcedit: calc ai_anno_item ='lang//text'
7. To update the annotation text displayed by changing the database table
name of the related file.
Arcedit:
ec langcov anno.lang
Arcedit:
textset font
Arcedit:
draw /* displays $TEXT
Arcedit:
&r langrel.aml english
Arcedit:
draw /* displays English text
Arcedit:
&r langrel.aml swedish
Arcedit:
draw /* displays Swedish text
■ AI_ANNO_ITEM does not update $TEXT (actual text stored in the TXT); it
only replaces what is displayed during the current session.
0 AI_ANNO_ITEM is also recognized by ARCPLOT drawing commands.
■ The word AI_ANNO_ITEM can be typed all uppercase or all lowercase.
See also the RELATE command for information on RELATE ADD, RELATE
SAVE and RELATE RESTORE.
Attachment D: Annotation placement specifications figures 1 - 3.
1. General Rule for East, West and North South Streets
As a general rule annotations should be placed along an angle of 0 to 90 degrees as demonstrated in figure 1,
and centered within polygons allowing users to read the addresses from left to right. Deviation from this will
produce annotations that would be difficult to read. This rule applies primarily to streets that have a north to
south and east to
west direction
360
0
a
Streets with north to south direction of
7 7
116
travel.Address reads from left to right at angle
of 90° and the address is centered within the
111
1118
polygon.
h
�^
1000
1007
North
1008
1011
1002
1005
1009
1001
TOM
1 112
100
1010
,
South
1004
tOD
101,3
W (�D N l0
N N N O h
O
O
O
t00 � t0p
N
00� O
O
O
O
0
O O O
O
O
tND
p O O O O
(00
O O O O O O
O .!5
e7
O
West ^� o East
oro m M v n m r m rn o
0 0 o r o 0 0 0 0 0 0 0 0 0 0
O O j
mar
Streets with east to west direction of travel Address
reads from north to south at angle of 00 and the
address is centered within the polygon.
180
Figure 1. General rules for the placement of address annotations for East, West and North
South Streets.
2. General Rules for North South Facing Cul-de-sacs
Annotations within parcels that form a cul-de-sac will be centered with the
parcels so that they can easily be read from left to right. The annotations should at best follow
the inside boundary lines between parcels as shown.
360
South Facing Cul-de-sac I 0 I South Facing Cul-de-sac
Address reads from left to right at angles
between 270° and 360°. The address is
centered within the polygon and follows an
angle consistent with how the parcels
surround the cul-de-sac.
�,h I o� �
r n m n
O O O O O O
North Facina Cul-de-sac
Address reads from left to right at angles
between 180° and 270°. The address is
centered within the polygon and follows an
angle consistent with how the parcels
surround the cul-de-sac.
Scat
180
1
Address reads from left to right at angles
between 0° and 9V The address is
centered within the polygon and follows an
angle consistent with how the parcels
surround the cul-de-sac.
North Facing Cul-de-sac
Address reads from left to right at angles
between 90' and 180°. The address is
centered within the polygon and follows an
angle consistent with how the parcels
surround the cul-de-sac.
�r
Figure 2. General rules for the placement of address annotations for North and South
facing cul-de-sacs.
3. General rules for east and west facing cul-de-sacs.
Annotations within parcels that form a cul-de-sac will be centered
within the parcels so that
they can easily be read from left to right. The annotations should
at best follow the inside
boundary lines between parcels as show
360
East Facing Cul-de-sac
0
West Facing Cul-de-sac
Address reads from left to right at angles
Address reads from left to right at angles
between 270° and 360°. The address is
between 0° and 90". The address is
centered within the polygon and follows an
centered within the polygon and follows an
angle consistent with how the parcels
g
A",
angle consistent with how the parcels
surround the cul-de-sac.
^^
surround the cul-de-sac.
1
w
co 0
�O O O O !� f0 t0 tp N l0
O O O O O O O
r
0
0 0 t r m
O O O O O O O
East Facing Cul-de-sac
Address reads from left to right at angles
between 180' and 270°. The address Is
centered within the polygon and follows an
angle consistent with how the parcels
surround the cul-de-sac.
S2�
180
0
O I O I p I O t p I o O I pl
West Facing Cul-de-sac
Address reads from left to right at angles
between 90° and 180°. The address is
centered within the polygon and follows an
angle consistent with how the parcels
surround the cul-de-sac.
'4,1°
w�
y
Figure 3. General rules for the placement of address annotations for cul-de-sacs facing east and west.
Attachment E: Annotation placement and Building Designation instruction.
The address number for which you will create an annotation subclass will contain
a field with a unique identifier that will be used as a relate item to the address
database which contains the same unique identifier. Building annotations will be
included in the same annotation subclass as the number annotations. For
example a trailer park has an address number of 1200. However the address list
database has no records for the buildings/trailers. In this case you would do the
following.
1. Add the annotations for the buildings/trailers in the same annotation
subclass as the address numbers, assigning each building annotations a
unique id value. The method for assigning unique id values will follow the
cities assignment scheme.
2. Add additional records to the address list with unique id values that will
relate back to the building annotations unique id value.
Address number annotation
added and unique id value j'
assigned. 121 NUMBER TEXT
1200 122 BUILDING TEXT
123 TEXT
124 TEXT
125 TEXT
126 TEXT
Building number annotation 127 TEXT
added and unique id value 12$ TEXT
assigned.
129 TEXT
Address number currently in the
address list database, with its
unique id value.
Records added to the address list
database with unique id values
assigned to reflect what has been
added as annotations.
INUM
123456789
1200
4#,
121
123456789
1200
1
122
123456789
1200
2
123
123456789
1200
3
124
123456789
1200
4
125
123456789
1200
5
126
123456789
1200
6
127
123456789
1200
7
128
123456789
1200
8
129
913 9(
� 37C
93 93 371
371
37
j7 20 Ell 01020
Q 5
III 12 13 � i5 � G
\'S
to a
� 3�
o d C7 ®O 3:
`)
3651
Figure 4 Condominium complex
This figure shows an area from the PFA run book. The group of buildings in the
center is a condominium complex. The annotations collected for this area will be
One the address number "1020", and two The building numbers located within
the squares. There are many cases like this when condos have visible areas to
place the annotations. However in some cases these areas do not exist, for such
a case a building foot print feature will be provided as reference for annotation
placement.
THE P ESEPvE
02 RAINVEFF HIVE
I
NEST
Figure 5 Preserves apartment complex.
This figure shows an area from the PFA run book. The group of buildings in the
center is the Preserves apartment complex. The annotations collected for this
area will be one the address number "1212", and two the building numbers, in
this case they are letters. This example shows the actual unit numbers, in such
cases this area will be noted in the discrepancy report and referenced by the
parcel number. It is not necessary to collect any descriptive data such as
garages, clubhouse, tennis courts or parking as seen in this figure.
Section 1.0: Scope of Work.................................................................................
3
1. Address Annotations........................................................................................
8
1 a. Additions to the Arclnfo addresslist Database ................................................
8
2. Project Orientation............................................................................................
8
3. Pilot Project......................................................................................................
8
4. Pilot Deliverables..............................................................................................
9
5. Post Pilot Requirements...................................................................................
9
Section 2.0: Quality Control..................................................................................
9
1. Annotation Placement......................................................................................
9
2. QC for Number of Generated Annotations.....................................................
10
4. Timeline table..............................................................................................................10
Attachment A: Area of parcel data coverage................................................................6
Attachment B: A quarter section representing annotation placement .....................7
Attachment C: Methodolgy for creating featured linked annotations in ESRI
Arclnfoworkstation.................................................................................................13
Attachment D: Annotation placement specifications figures 1 - 3...........................19
Attachment E: Annotation placement and Building Designation instruction .......... 22
Figure 4 Condominium complex.......................................................................................24
Figure 5 Preserves appartment complex............................................................................25
Figure6 Trailer park............................................................................................................1
Table 1 Summary table of scale values...............................................................................2
NORTH COLLEGE MOBLE PLAZA.
801
VVV
a
`,a`�, •.
r1.
•5`,tl`8.tl 9`S\R1{`wR r\` x'.x F,.3'.t` F'.'s
..�'.
TO tCitEGE EVC.----y
;a.R,R;e;ist/R;
{
�•R� -
� �t:,�e, e. e. R•, s'. s`?ems
Figure 6 Trailer park
This figure shows an area from the PFA run book. The rows of numbers in this case are
trailers within a trailer park complex. A technician will not see any division lines on the
parcel and will have to use as reference the building footprint feature data as placement
reference. The annotations collected for this area will be one the address number
"1601", and two the trailer numbers. In the event that a technician comes across an
area that does not contain the appropriate lines or building foot prints that aid in
determining where to place building annotations a discrepancy report should be sent to
the City of Fort Collins and this data will be produced within 48 hours of notice.
It is not possible to anticipate every scenario that may occur during the data capture
process and any anomalies that may add a significant amount of work to the project.
However, it is our expectation that TGS will adapt to such cases, if this should increase
the scope of the project beyond the current contract, TGS and the City will have to
agree on any changes before work is conducted.
PSA 05/O1
Table 1 is a summary of individual scale values that the PFA run book will display map
pages at. Text size will have to be determined based on the varying scales that are
going to be used in the run book map pages. The annotation subclass will need to have
a field designating at what scale value it is used to be displayed at.
SCALE
LARGE
SMALL
NUMBER
IN SCALE
RANGE
450
4.0
3.0
1
650
5.5
4.5
1
700
6.0
5.0
1
800
6.5
5.5
1
900
7.5
6.5
3
1000
8.5
7.0
2
1100
9.0
8.0
1
1142
9.5
8.0
1
1200
10.0
8.5
1
1300
11.0
9.5
1
1400
11.5
10.0
2
1600
13.5
11.5
3
1650
14.0
12.0
1
1660
14.0
12.0
1
1800
15.0
13.0
1
1900
16.0
13.5
1
2000
16.5
14.5
5
2100
17.5
15.0
1
2150
18.0
15.5
1
2200
18.5
15.5
1
2300
19.0
16.5
3
3000
25.0
21.5
2
4000
33.5
28.5
1
4200
35.0
30.0
275
8400
70.0
60.0
65
TOTAL COUNT
376
Table 1 Summary table of scale values
PSA 05/O1
Section 1.0: Scope of Work
1. Address Annotations
The contractor will produce address annotations for all parcels within the City
of Fort Collins GIS maintenance area shown in attachment A. There are
approximately 58,000 parcels. The address annotations will be delivered as
an annotation subclass in the ESRI Arclnfo format, maintaining a unique link
to the city's address database. The contractor will receive an Arclnfo
database file containing all the current addresses for the City of Fort Collins
and an Arclnfo coverage containing all parcels as a region subclass.
Attachment B is a sample of the desired annotation results.
1a. Additions to the Arclnfo addresslist Database (addendum portion)
The Contractor will reference the Poudre Fire Authorities current map book
and edit the City of Fort Collins address database to reflect addresses that
contain building designations. The address database itself contains some of
this information however it is concatenated, meaning the building and unit
designations are in one field. The cities current updating procedures do not
allow us to distinguish between buildings and units. Consequently the unit
field may be populated with in accurate data that needs to be corrected. The
contractor will be required to QC the current entries in the address database
and make any needed corrections by capturing buildings in a separate field.
The contractor will use the Poudre Fire Authorities detailed run book maps to
add the building attributes that do not currently exist in the address database.
Also feature linked annotations will be created for the building designations
and placed relatively in the same locations as they are in the run book and at
the correct scale and size.
2. Project Orientation
A meeting will be scheduled to get TGS familiar with the data, answer
questions and discuss any technical issues that the GIS department or TGS
may have. The expected method for creating the data and performing QC/QA
must be submitted to the City of Fort Collins prior to starting the pilot project in
the form of a Microsoft word document. A revision to this document would
then be submitted before work starts on the entire data set.
3. Pilot Project
To determine further details, a pilot project will take place. Feature linked
annotation addresses will be created for 4 quarter sections at varying scales
and text sizes by TGS. The differences in scales represent subset areas
within the quarter sections. The contractor is required to use ESRI's Arclnfo
Workstation to create the annotations. The preferred method for creating the
feature linked annotations is documented in attachment C. The contractor will
define the method for creating the annotations and list the types of software
used in the required process/procedure document. A sample or pilot dataset
will be given to the contractor and then returned to the City of Fort Collins
within one week after data delivery for testing and quality control by the city.
The pilot work will include examples of both tasks 1 and 1.a as described
earlier. The submitted data will be tested to assure that it will migrate into the
city's current parcel data. Quality control is to be done on the pilot data so that
any additional parameters needed to complete the entire job can be given to
the contractor. The contractor will follow general rules for annotation
placement, and address table modifications, which are described in
attachments D and E.
4. Pilot Deliverables
Feature linked annotation will be delivered to the City of Fort Collins as
specified in the pilot project. A minimum of 90% of the annotation addresses
have to be placed according to the specifications outlined in attachment D
and 100% of the addresses must have an annotation.
5. Post Pilot Requirements
A discrepancy list would be submitted every three days so problems in the
data can be corrected by City of Fort Collins employees as they are found. In
the event that the number of discrepancies exceeds a total number of 25
documented occurrences a report will be submitted to the City of Fort Collins
either the same or next working day they are found, even if a scheduled
report was given as recently as 1 day prior to such an occurrence. Problems
might include items such as corner lots and other parcels with multiple
addresses. This reporting provision is extremely important to the city because
of our limited staff and resources. An extremely large list of discrepancy
delivered at one time could cause a back log of work for us. TGS has stated
in their proposal that they have a great deal of experience doing this type of
work, therefore it is our understanding that an experienced TGS technician
should be able to notice irregularities and log or track them for reporting
purposes. The methodology for tracking will be up to the TGS project
manager, but must be approved by the City of Fort Collins GIS project
manager prior to starting any work. This methodology can be established
during the pilot phase, but must be in place before starting work on the entire
data set.
Section 2.0: Quality Control
1. Annotation Placement
After delivery the City of Fort Collins will review 25 randomly chosen quarter
sections at the1:4250 scale for completeness and accuracy of annotation
placement. The selection will also include 1 area for all other scale values.
Table 1 is a summary of scales contained in the PFA grid system. The city is
sectioned out by 498 quarter sections, with an average of 120 addresses
within each section. We are expecting that at minimum 95% of the addresses
will be placed in their correct location. If more than 5% of the checked
addresses aren't placed correctly or any addresses are missing, the product
will be returned for correction. The QC process will be repeated only twice If
the City of Fort Collins at that point still finds an unacceptable number of
errors, the contract is void and the City has no further obligation. The
parameters used for the quality control will be based on the guidelines in
attachment D and E. The annotation size is important will vary depending on
scale requirements. This is because the desired result is to have the
annotations fill at least 75 — 80 percent of the parcel at varying scales with the
exception of parcels greater than 20,000 square feet.
2. QC for Number of Generated Annotations
The contractor must produce 100% of all the address annotations whether the
positions are correct or not. No margin of error is acceptable for this Item.
The annotations should use a coding scheme that the vendor would create.
The scheme should allow a person to query annotations that have been
placed as required and those that are not.
4. Timeline table
Project planning meeting
Day 1
Pilot data delivered to contractor
Day 2
Parcel data features (polygons and regions)
Address list database (info file)
Building footprint feature (polygons)
Updated PFA run book (hard copy )
Grid data features (polygons)
Evaluation and QC of pilot data delivered to the City of Fort
Day 13
Collins by contractor.
Deliverables:
Annotations
Address list
Discrepancy list
Process/procedure document
City of Fort Collins delivers address data for annotation
Day 25
production (pending acceptance of pilot data). This will include a
project update and evaluation meeting for the pilot work with the
TGS's project manager.
Mid project evaluation meeting
Day 37
Final product as outlined in the scope of work
Day 50
Quality control completed and the contractor is notified of
Day 71
acceptance status. Project rap up meeting.
or
LIM
All j
HOW W, AUMS160
Attachment B: A quarter section representing annotation placement.
F'
I"
L
3101 100
L 70
i 3109 110 i i 117 Aw/,� 3
i 3115 3114 1y n w3
A 31 18 ry
^ ^
i 3127 3122 121 3I 1b 15 117e ^
3130 13] 3124
3139 3136 3w� M d77j 3181 16 �. 3201 '. 3200 73 ^ o
y 320] 13208 173
2030 w s 3184 213201
3 3212 1741 ^ !
i% 3186 718 1321611A
320] °i a 320 32 �4P9' ^F F 76 3219
1i 3213
219
33
M r1 ^ m W m 190 ^ m F"�I.i .y'! ^ 330] Ofi 3pI 3300
312 33 307
190 ,pA 4: 3349 ,y IB 33 7qe 3319 3312
337
pp gg I OI •. 80'
R R N N ": 3424 19 931 mm 342q 3400 01 01 O6 0]
06 3413 4
! ^ :3 25 Ig ♦9 3d1 13 12 ^ m m .342
3454 �' m m 163 Q w ifi0
(� ymp� }� ywy jj }- 3524 1923 W m^190q 1625 m ,(��. 501 35M 3507
G F R N a LS 82 m ^ wpy 35-7
518
513 3512 3519 �M:: 524
600
519 3518 3525 530
�803 525 35243531 536
53 530 53 54
i
Attachment C: Methodolgy for creating featured linked annotations in ESRI
Arclnfo workstation
This can also be found on the workstation help, keyword "AI_ANNO_ITEM"
and should be referred to exclusively.
Using an item named AI_ANNO_ITEM
To automatically update your annotation text when you update the attribute value
of a feature, use AI_ANNO_ITEM to link the annotation directly to a database
field. Create an annotation attribute table (TAT), add an item named
AI_ANNO_ITEM to the TAT, and set up a relate between the INFO data file or a
table in an external DBMS and the TAT. When ARCEDIT displays annotation, it
will first check to see if AI_ANNO_ITEM exists. If it does, ARCEDIT will display
the value of AI_ANNO_ITEM instead of the default $TEXT values.
The following two examples show how to use AI_ANNO_ITEM to update
annotation text displayed with multiple item values.
1. To create an annotation attribute table (TAT).
Create an annotation subclass named anno.type, then use
CREATEATTRIBUTES to create a TAT.
Arcedit: ec soilcov
Arcedit: createfeature anno.type
Arcedit: createattributes
2. To add a relate item and an item named, AI_ANNO_ITEM to the TAT.
Add a relate item called soilcov-id and an item named, AI_ANNO_ITEM to the
TAT. You define AI_ANNO_ITEM so make sure you set the item width wide
enough to contain a relate string. Use ITEMS to list the new items added to the
TAT.
Arcedit: additem soilcov-id 4 5 b
Adding SOILCOV-ID to TATTYPE.. .
Arcedit: additem ai_anno_item 25 25 c
Adding AI_ANNO_ITEM to TATTYPE
Arcedit: items
Column ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED
1 TYPE# 4 5 B
5 TYPE -ID 4 5 B
9 SOILCOV-ID 4 5 B
13 AI_ANNO_ITEM 25 25 C -
3. To add annotation records to the TAT
Use ANNOFEATURE to specify the type of feature that will position the
annotation and the item that will be the source for text. In this example, poly is
the feature and the item attributel is the source for text. ANNOCAPTURE adds
annotation records to the TAT.
Arcedit: annofeature poly attributel
Arcedit: annocapture
6 annotation added
4. To set up a relate between the feature attribute table and the TAT.
Set up relate named, rell , between soilcov's PAT and anno.type's TAT.
Arcedit: relate add
Relation Name: rell
Table Identifier: soilcov.pat
Database Name: INFO
INFO Item: soilcov-id
Relate Column: soilcov-id
Relate Type: linear
Relate Access: ro
Relate Name: <cr>
5. To select the desired annotation records and calculate AI_ANNO_ITEM
to equal the value of the desired related item.
In this example, soilcov's PAT has two items, attributel and attribute2. Three
annotation records are selected and AI_ANNO_ITEM is calculated to equal
'rel1//attributel'. Then two annotation records are selected and AI_ANNO_ITEM
is calculated to equal a different related item, 'rel1//attribute2'.
Arcedit:
select many
3 element(s) now selected
Arcedit:
list
Record
TYPE#
TYPE -ID SOILCOV AI_ANNO_ITEM
9
0 3
3
15
0 5
5
18
0 6
4
Arcedit:
calc ai_anno_item
='rell//attributel'
Arcedit:
list
Record
TYPE#
TYPE -ID SOILCOV Al ANNO ITEM
9
0 3
3 rell//attributel
15
0 5
5 rel1//attributel
18
0 6
4 rel1//attribute1
Arcedit:
select many