HomeMy WebLinkAboutRFP - 2207226 P 836Administrative Services
Purchasing Division
CITY OF FORT COLLINS
REQUEST FOR PROPOSAL
PROPOSAL NUMBER P-836
PLACEMENT OF FEATURE LINKED ADDRESS ANNOTATIONS
PROPOSAL DATE: 2:00 p.m. (our clock) MAY 7, 2002
215 North Mason Street - 2nd Floor - P.O. Box 580 - Fort Collins, CO 80522-0580 - (970) 221-6775 - FAX (970) 221-6707
updated, it will automatically update the annotation text displayed. For example, if you update
soilcov's item ATTRIBUTETs 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 AI_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
9
1 LANG# 4 5 B
5 LANG-ID 4 5 B
9 Al 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.
/*langrel.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 %lang% 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 Al_ANNO_ITEM to equal
the value of the related item.
Arcedit: select many
5 element(s) now selected
Arcedit: calc ai_anno_item ='tang//text'
7. To update the annotation text displayed by changing the database table name of the
related file.
10
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.
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.
11
O
n
N
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
Streets with north to south direction of travel.
Address reads from left to right at angle of 90° and
the address is centered within the polygon.
O
O
O
O
Streets with east to west direction of travel
Address reads from north to south at angle of 0° and the
address is centered within the polygon.
160
Figure 1. General rules for the placement of address annotations for East, West and North South
Streets.
12
2. General Rules for North and South 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 360arcels as shown.
South Facing Cul-de-sac 0 South 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
centered within the polygon and follows an angle within the polygon and follows an angle
consistent with how the parcels surround the cul- a consistent with how the parcels surround the
de -sac. cul-de-sac.
N
430
O�J aD M C �n
North 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.
11
1004
O O
O
m
O
180
W
O
0
O O�
O (D N
O O O
O
id
O
North Facing Cul-de-sac
Address reads from left to right at angles
between 90° and 1800. The address is
centered within the polygon and follows an
angle consistent with how the parcels
surround the cul-de-sac.
Figure 2. General rules for the placement of address annotations for North and South facing cul-de-sacs.
13
O
N
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 360 parcels as show.
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
centered within the polygon and follows an angle within the polygon and follows an angle
consistent with how the parcels surround the cul- 9 consistent with how the parcels surround the
de -sac. cul-de-sac.
(p O
N
6O O O p O O
�O� �u
%5
1�
q0�6 —
n
0 0 0 0
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.
s2r
11
� kl�
180
O
O
O
O
0
0 0
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.
Figure 3. General rules for the placement of address annotations for cul-de-sacs facing east and west.
14
REVIEW AND ASSESSMENT
Professional firms will be evaluated on the following criteria. These criteria will be the basis for
review of the written proposals and interview session.
The rating scale shall be from 1 to 5, with 1 being a poor rating, 3 being an average rating, and
5 being an outstanding rating.
WEIGHTING
QUALIFICATION
STANDARD
FACTOR
2.0
Scope of Proposal
Does the proposal show an understanding of the
project objective, methodology to be used and
results that are desired from the project?
2.0
Assigned Personnel
Do the persons who will be working on the project
have the necessary skills? Are sufficient people of
the requisite skills assigned to the project?
1.0
Availability
Can the work be completed in the necessary time?
Can the target start and completion dates be met?
Are other qualified personnel available to assist in
meeting the project schedule if required? Is the
project team available to attend meetings as
required by the Scope of Work?
1.0
Motivation
Is the firm interested and are they capable of doing
the work in the required time frame?
2.0
Cost and
Do the proposed cost and work hours compare
Work Hours
favorably with the project Manager's estimate? Are
the work hours presented reasonable for the effort
required in each project task or phase?
2.0
Firm Capability
Does the firm have the support capabilities the
assigned personnel require? Has the firm done
previous projects of this type and scope?
2/9/00
Reference evaluation (Top Ranked Firm)
The project Manager will check references using the following criteria. The evaluation rankings
will be labeled Satisfactory/Unsatisfactory.
QUALIFICATION
STANDARD
Overall Performance
Would you hire this Professional again? Did
they show the skills required by this project?
Timetable
Was the original Scope of Work completed
within the specified time? Were interim
deadlines met in a timely manner?
Completeness
Was the Professional responsive to client
needs; did the Professional anticipate
problems? Were problems solved quickly and
effectively?
Budget
Was the original Scope of Work completed
within the project budget?
Job Knowledge
a) If a study, did it meet the Scope of Work?
b) If Professional administered a construction
contract, was the project functional upon
completion and did it operate properly?
Were problems corrected quickly and
effectively?
2/9/00
PROFESSIONAL SERVICES AGREEMENT
THIS AGREEMENT made and entered into the day and year set forth below, by and
between THE CITY OF FORT COLLINS, COLORADO, a Municipal Corporation, hereinafter
referred to as the "City" and , [insert either a corporation, a partnership or an individual,
doing business
WITNESSETH:
hereinafter referred to as "Professional".
In consideration of the mutual covenants and obligations herein expressed, it is agreed
by and between the parties hereto as follows:
1. Scope of Services. The Professional agrees to provide services in accordance
with the scope of services attached hereto as Exhibit "A", consisting of ( ) page[s],
and incorporated herein by this reference.
2. The Work Schedule. [Optional] The services to be performed pursuant to this
Agreement shall be performed in accordance with the Work Schedule attached hereto as
Exhibit "B", consisting of ( ) page[s], and incorporated herein by this reference.
3. Time of Commencement and Completion of Services. The services to be
performed pursuant to this Agreement shall be initiated within ( ) days following
execution of this Agreement. Services shall be completed no later than . Time is of the
essence. Any extensions of the time limit set forth above must be agreed upon in writing by the
parties hereto.
4. Early Termination by City. Notwithstanding the time periods contained herein,
the City may terminate this Agreement at any time without cause by providing written notice of
termination to the Professional. Such notice shall be delivered at least fifteen (15) days prior to
the termination date contained in said notice unless otherwise agreed in writing by the parties.
All notices provided under this Agreement shall be effective when mailed, postage prepaid and
sent to the following addresses:
PSA 05101
Professional: City: With Copy to:
In the event of any such early termination by the City, the Professional shall be paid for services
rendered prior to the date of termination, subject only to the satisfactory performance of the
Professional's obligations under this Agreement. Such payment shall be the Professional's sole
right and remedy for such termination.
5. Design, Project Indemnity and Insurance Responsibility. The Professional shall
be responsible for the professional quality, technical accuracy, timely completion and the
coordination of all services rendered by the Professional, including but not limited to designs,
plans, reports, specifications, and drawings and shall, without additional compensation,
promptly remedy and correct any errors, omissions, or other deficiencies. The Professional
shall indemnify, save and hold harmless the City, its officers and employees in accordance with
Colorado law, from all damages whatsoever claimed by third parties against the City; and for the
City's costs and reasonable attorneys fees, arising directly or indirectly out of the Professional's
negligent performance of any of the services furnished under this Agreement. The Professional
shall maintain commercial general liability insurance in the amount of $500,000 combined single
limits, and errors and omissions insurance in the amount of
6. Compensation. [Use this paragraph or Option 1 below.] In consideration of the
services to be performed pursuant to this Agreement, the City agrees to pay Professional a
fixed fee in the amount of ($ ) plus reimbursable direct costs. All such fees and
costs shall not exceed ($ ). Monthly partial payments based upon the
Professional's billings and itemized statements are permissible. The amounts of all such partial
payments shall be based upon the Professional's City -verified progress in completing the
services to be performed pursuant hereto and upon the City's approval of the Professional's
PSA 05101
2
CITY OF FORT COLLINS
REQUEST FOR PROPOSAL
PROPOSAL NUMBER P-836
PLACEMENT OF FEATURE LINKED ADDRESS ANNOTATIONS
The City of Fort Collins and the Poudre Fire Authority are soliciting proposals to find a qualified
contractor to produce feature linked address annotations. The data needs to be in the
Environmental Systems Research Institute (ESRI) Arclnfo annotation subclass format.
Written proposals, five (5) will be received at the City of Fort Collins' Purchasing Division, 215
North Mason St., 2nd floor, Fort Collins, Colorado 80524. Proposals will be received before
2:00 p.m. (our clock), May 7, 2002. Proposal No. P-836. If delivered, they are to be sent to
215 North Mason Street, 2nd Floor, Fort Collins, Colorado 80524. If mailed, the address is P.O.
Box 580, Fort Collins, 80522-0580.
Questions concerning the scope of the project should be directed to Tim Morales, Project
Manager, (970) 416-2728.
Questions regarding proposals submittal or process should be directed to Keith I. Ashby, CPPO,
Buyer, (970) 416-2191.
Sales Prohibited/Conflict of Interest: No officer, employee, or member of City Council, shall have
a financial interest in the sale to the City of any real or personal property, equipment, material,
supplies or services where such officer or employee exercises directly or indirectly any decision -
making authority concerning such sale or any supervisory authority over the services to be
rendered. This rule also applies to subcontracts with the City. Soliciting or accepting any gift,
gratuity favor, entertainment, kickback or any items of monetary value from any person who has
or is seeking to do business with the City of Fort Collins is prohibited.
Collusive or sham proposals: Any proposal deemed to be collusive or a sham proposal will be
rejected and reported to authorities as such. Your authorized signature of this proposal assures
that such proposal is genuine and is not a collusive or sham proposal.
The City of Fort Collins reserves the right to reject any and all proposals and to waive any
irregularities or informalities.
Sincerely,
Jam s B. O'Neil CPPO, FNIGP
Dire for of Purchasing & Risk Management
actual reimbursable expenses. Final payment shall be made following acceptance of the work
by the City. Upon final payment, all designs, plans, reports, specifications, drawings, and other
services rendered by the Professional shall become the sole property of the City.
6. Compensation. [Option 1] In consideration of the services to be performed
pursuant to this Agreement, the City agrees to pay Professional on a time and reimbursable
direct cost basis according to the following schedule:
Hourly billing rates:
Reimbursable direct costs:
with maximum compensation (for both Professional's time and reimbursable direct costs) not to
exceed ($ ). Monthly partial payments based upon the Professional's billings and
itemized statements of reimbursable direct costs are permissible. The amounts of all such
partial payments shall be based upon the Professional's City -verified progress in completing the
services to be performed pursuant hereto and upon the City's approval of the Professional's
reimbursable direct costs. Final payment shall be made following acceptance of the work by the
City. Upon final payment, all designs, plans, reports, specifications, drawings and other
services rendered by the Professional shall become the sole property of the City.
7. City Representative. The City will designate, prior to commencement of work, its
project representative who shall make, within the scope of his or her authority, all necessary and
proper decisions with reference to the project. All requests for contract interpretations, change
orders, and other clarification or instruction shall be directed to the City Representative.
8. Project Drawings. [Optional] Upon conclusion of the project and before final
payment, the Professional shall provide the City with reproducible drawings of the project
containing accurate information on the project as constructed. Drawings shall be of archival
quality, prepared on stable mylar base material using a non -fading process to prove for long
storage and high quality reproduction.
PSA 05101
3
9. Monthly Report. Commencing thirty (30) days after the date of execution of this
Agreement and every thirty (30) days thereafter, Professional is required to provide the City
Representative with a written report of the status of the work with respect to the Scope of
Services, Work Schedule, and other material information. Failure to provide any required
monthly report may, at the option of the City, suspend the processing of any partial payment
request.
10. Independent Contractor. The services to be performed by Professional are those
of an independent contractor and not of an employee of the City of Fort Collins. The City shall
not be responsible for withholding any portion of Professional's compensation hereunder for the
payment of FICA, Workers' Compensation, other taxes or benefits or for any other purpose.
11. Personal Services. It is understood that the City enters into this Agreement
based on the special abilities of the Professional and that this Agreement shall be considered as
an agreement for personal services. Accordingly, the Professional shall neither assign any
responsibilities nor delegate any duties arising under this Agreement without the prior written
consent of the City.
12. Acceptance Not Waiver. The City's approval of drawings, designs, plans,
specifications, reports, and incidental work or materials furnished hereunder shall not in any way
relieve the Professional of responsibility for the quality or technical accuracy of the work. The
City's approval or acceptance of, or payment for, any of the services shall not be construed to
operate as a waiver of any rights or benefits provided to the City under this Agreement.
13. Default. Each and every term and condition hereof shall be deemed to be a
material element of this Agreement. In the event either party should fail or refuse to perform
according to the terms of this agreement, such party may be declared in default.
14. Remedies. In the event a party has been declared in default, such defaulting
party shall be allowed a period of ten (10) days within which to cure said default. In the event
the default remains uncorrected, the party declaring default may elect to (a) terminate the
PSA 05101
4
Agreement and seek damages; (b) treat the Agreement as continuing and require specific
performance; or (c) avail himself of any other remedy at law or equity. If the non -defaulting
party commences legal or equitable actions against the defaulting party, the defaulting party
shall be liable to the non -defaulting party for the non -defaulting party's reasonable attorney fees
and costs incurred because of the default.
15. Binding Effect. This writing, together with the exhibits hereto, constitutes the
entire agreement between the parties and shall be binding upon said parties, their officers,
employees, agents and assigns and shall inure to the benefit of the respective survivors, heirs,
personal representatives, successors and assigns of said parties.
16. Law/Severability. The laws of the State of Colorado shall govern the
construction, interpretation, execution and enforcement of this Agreement. In the event any
provision of this Agreement shall be held invalid or unenforceable by any court of competent
jurisdiction, such holding shall not invalidate or render unenforceable any other provision of this
Agreement.
PSA 05/01
5
17. Special Provisions. [Optional] Special provisions or conditions relating to the
services to be performed pursuant to this Agreement are set forth in Exhibit "_", consisting of
( ) page[s], attached hereto and incorporated herein by this reference.
THE CITY OF FORT COLLINS, COLORADO
By:
John F. Fischbach
City Manager
By:
James B. O'Neill II, CPPO, FNIGP
Director of Purchasing & Risk Management
DATE:
ATTEST:
City Clerk
APPROVED AS TO FORM:
Assistant City Attorney
[Insert Professional's name] or
[Insert Partnership Name] or
[Insert individual's name]
Doing business as _[insert name of business]
la
Title:
CORPORATE PRESIDENT OR VICE PRESIDENT
Date:
ATTEST:
Corporate Secretary
(Corporate Seal)
PSA 05/O1
0
No Text
woo, .4
7�" I?ilrll
bung
r 14
Ri
=uml
TI
IMMI
V1.
-4,0
j4 4
;ds "llmill
ME...
RN1,MA k\
;jIllf go
1'1� min
17'
A A
PAR' "4111
vp0U-A_ w 1
I
I
Section 1.0: Proposal Requirements
1. General Description
The City of Fort Collins and the Poudre Fire Authority are soliciting proposals to find a
qualified contractor to produce feature linked address annotations. The data needs to be in
the Environmental Systems Research Institute (ESRI) Arclnfo annotation subclass format.
2. Proposal Submittal
The City of Fort Collins shall not reimburse any firm for the costs incurred in the preparation
and presentation of their proposal. Proposals must contain the following information.
a. Company history and experience with type of work requested in the scope of
work.
b. The name of the company representative responsible for coordinating with the
City.
c. A written description of the proposed services as required below.
d. Pricing as requested
3. Attachments
Attachment A. Map attached to show area of data coverage.
Attachment B. Sample quarter section showing how annotations should be
placed.
Attachment C. ESRI Arclnfo Workstation help page describing method for
creating feature linked annotations.
Attachment D. Annotation placement specifications
Section 2.0: Background
1. General Information
The Poudre Fire Authority (PFA) and the City of Fort Collins GIS are working together to
create an application that will generate a map runbook to be used in emergency response
vehicles. PFA currently produces a very detailed map book known as a runbook for their
operational boundary. The runbooks are a very important reference for adequate emergency
response.
The current method of updating the runbooks is to take pieces from the city's GIS parcel
data layer then make edits to fit in their run books. The type of edits made to the parcel data
in the run books consist of changing addresses to match those of the structures on the
parcels. Another principal editing task is the placement of annotations for addresses. It was
identified early into the project that a key element to the runbook mapping application would
be that the data used by the application be linked directly to the city's active GIS data. This
would provide users with the most up to date maps. Address annotations are a principal part
of the runbook maps and it is our desire to make these annotations dynamic, so that
changes in the address data are reflected immediately in the maps.
Section 3.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. A sample data set will be supplied to the contractor for bid
purposes at their request.
2. Pilot Project
To determine further details, a pilot project will take place. Feature linked annotation
addresses will be created for 4 quarter sections for the City of Fort Collins address database
at several different scales by a qualified contractor. The differences in scales represent
subset areas within the quarter sections. The contractor is required to use ESRI's Arclnfo
Workstation or Maplex 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 software used. 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. 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,
which will be described in attachment D.
3. 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.
4. Timeline
a. Written proposals due in Purchasing Office
May 7, 2002
b. Proposal evaluations completed
May 21, 2002
c. Top respondents chosen for oral interviews
May 23, 2002
d. Purchase order issued
May 24, 2002
e. Pilot data delivered to contractor
May 28, 2002
f. Evaluation and QC of pilot data delivered to the
June 6, 2002
City of Fort Collins by contractor
g. City of Fort Collins delivers address data for
June 13, 2002
annotation production
h. Final product as outlined in the scope of work
shall be delivered no later than
July 8,2002
i. Quality control completed and the contractor is
July 29, 2002
notified to the status of acceptance.
Section 4.0: Quality Control
1. Annotation Placement
After delivery the City of Fort Collins will review 25 randomly chosen quarter sections for
completeness and accuracy of annotation placement. 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.
3
The parameters used for the quality control will be based on the guidelines in attachment D.
Because corner lots may have two addresses the placement for corner lots will not be
deemed as an error, however both addresses must be captured.
The contractor does not have to accurately place addresses within dense apartment,
condominium and business complexes, however the addresses still must be present.
2. 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.
N
I is
FA Ai
„I
■vd-71
T
121
Wrl
Attachment B: A quarter section representing annotation placement.
7
2 $ ^ 3101
n
3109 fllgil
21 it]
3115
3121 ty 131
3127 15 137
1601121$64
3131
S
153 3161 tfi i2i� 3201 3200n r K K r
3139 1]3
0
320] '3206
2030 ''m m 3186 21\7, 32121741 r $
pp ❑ 9 3218 114
3 r
3207 $$ N hf m a$ �. 3/a�w^�nf F n ]6 3215
3213,'2n f _
3300
F $ m 3 349 3312 33 ? 30] '
3312
33
n: i4 F Pv N w W &] t�, t90 'fA 3349 y O� �iy� �'3 2q 33t9 '
$ $
so
3412 ? m
340] 406 i� 3N9 MI(
' 4 q5 6 w9 3413 d18 m m -342
pR R _ 06
35'�9�Z.. 3454�� < < 163 m m 160
3512 922 M 501
_1�2 3518
$507 3500 506
3524 19� W 190 1625 y 501 ,3506 35113
3519 .5243512
5
62m m w0� 3513 - 3512 p 24 1600
_ ym� fin{ [y�y my yob g� p y� p 3519 3510 3525 530
M M bi bi m & dS nm 803 525 3524 3531 3536
53 530 53 ] 54
v
E'
N
Attachment C: Methodolgy for creating featured linked annotations in ESRIArclnfo
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 attribute1 is the
source for text. ANNOCAPTURE adds annotation records to the TAT.
Arcedit: annofeature poly attribute1
Arcedit: annocapture
6 annotation added
7
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, attribute) and attribute2. Three annotation records
are selected and AI_ANNO_ITEM is calculated to equal 'rell//attributel'. Then two annotation
records are selected and AI_ANNO_ITEM is calculated to equal a different related item,
'rel l //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 AI ANNO ITEM
9
0 3
3 rell//attributel
15
0 5
5 rell//attributel
18
0 6
4 rel1//attributel
Arcedit:
select many
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
='rell//attribute2'
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
8