HomeMy WebLinkAboutApprove recommendation of award for 2007 Bozeman A_424
THE CITY OF BOZEMAN
20 E. OLIVE ~ P.O. BOX 1230
BOZEMAN, MONTANA 59771-1230
GIS DEPARTMENT
PHONE: (406) 582-2250 ~ FAX: (406) 582-2263
E-MAIL: jhenderson@bozeman.net
City of Bozeman, Montana
Request for Proposals
For Digital Orthoimagery and Contour Data
Notice is hereby given that proposals are invited and will be received for Digital Orthoimagery and Contour Data of
the City of Bozeman, Gallatin County, Montana.
This request for proposals is to provide:
• LiDAR data Collection and processing to bare earth
• Digital Ortho Imagery (1”=600’ scale, 6’ pixel, true color, ortho-rectified digital imagery)
• 1’ Contours, ASPRS Class 1
• Hydro Enforced Breaklines
• DTM & DEM
• FGDC compliant metadata for the imagery and GIS data
• Provide City of Bozeman with an automated tool to effectively view and QA/QC LAS data
Proposal documents and related data files are available on www.bozeman.net/gis/gis_ftp.aspx and may be
examined or obtained for no charge at the City of Bozeman GIS Department, Attention: Jon Henderson, P.O. Box
1230 Bozeman, Montana 59771, (406) 582-2250 or fax (406) 582-2263. Proposals must be delivered to the GIS
Department on or before 5:00 p.m. APRIL 11th, 2007.
The City reserves the right to accept or reject any or all proposals: to add or delete items and/or quantities; to waive
any irregularities and/or informalities in any proposal; to postpone the acceptance of the proposal and the award of
contract for a period not to exceed ten (10) working days from the date of the proposal opening and to further
advertise the RFP; and to make the award that is in the best interests of the City of Bozeman. The City of Bozeman
may reject any proposal that is not within the City’s budget resources for this project, or not in compliance with all
prescribed proposal procedures and requirements and may reject for good cause any and all proposals upon a finding
of the City that is in the public’s interest to do so.
This project is subject to the availability of funds.
For additional information, contact Jon Henderson, GIS Manager (406) 582-2250, or fax (406) 582-2263.
DATED THIS Sunday, April 1st, 2007 City of Bozeman, Montana
By:
Jon Henderson
GIS Manager,
Publish Date: Sunday, April 1st, 2007
25
2
Introduction
The City regularly uses aerial and topographic information to support regulatory, land management,
planning and engineering projects. This document defines the technical, cost and time scope for
developing a portion of the City’s GIS database. All final data will be stored in the City’s ArcSDE
database and will be made available to internal and external customers through various client
applications and downloadable data files.
This project is to update all aerial imagery for the entire 66 square mile planning boundary. This project
will also provide topographic contours for the entire area.
The desired flight dates are between April 24th and May 15th 2007. The desired project completion date
is 90 days from photo acquisition.
I. Proposal Submission Requirements
1) General Requirements:
All information required of the bidder/consultant must be completed in full, in ink, or typewritten. If
any information required on the proposal form/proposal is to be modified, it shall be crossed out in
ink. The amended information must be entered above or below and initialed in ink by the
bidder/consultant.
The proposal must be signed by a person authorized to commit the consultant to provide the goods
or service. Submission of a signed proposal will be interpreted to mean that consultant has hereby
agreed to all terms and conditions set forth in all of the sheets which make up this Request for
Proposals.
2) The proposal must be submitted no later than 5:00 p.m., April 11th, 2007. Proposals received after
5:00 p.m. will be returned unopened.
3) One (1) copy of the proposal shall be sealed and submitted to:
Jon Henderson
GIS Manager
P.O. Box 1230
Bozeman, MT 59771
4) Proposals must be plainly marked in the lower left-hand corner of the envelope as follows:
“Digital Orthoimagery Project 2007”
5) The City’s staff contact for this RFP is:
Jon Henderson
GIS Manager
Phone #: (406) 582-2250 FAX #: (406) 582-2263
E-mail address: jhenderson@bozeman.net
6) Proposal Format:
a) Section I - Statement of Understanding
An overall introduction, including a statement of the consultant’s understanding of each item
proposed in the Scope of Work, and a general description of the consultant’s approach.
b) Section II - Proposed Technology and Equipment
Detailed explanation of type of technology and equipment proposed to be utilized to obtain
the products necessary to comply with each item in the Scope of Work.
26
3
c) Section III - Personnel Qualifications
Names, relevant experience, professional registrations of consultant’s personnel with
background information on previous experience, qualifications, and skills relevant to each
item proposed upon in the Scope of Work section.
d) Section IV – References
A list of at least three clients for whom the consultant has provided similar services. This list
shall include the agency/company name, address, phone number and name of contact person
and, description of the similar project.
e) Section V – Subcontractors
A list and description of names, office locations, tasks, qualifications, and responsibilities of
any subcontractors that may be utilized for this project.
f) Section VI - Change in Scope
A proposed procedure to accommodate changes in scope of the contract, and addition or
deletion of task activities. The consultant will include a current fee schedule and a cost of
services proposal for any work that is to be provided or that the City may request after the
contract is awarded.
g) Section VII - Consultant’s Expectations of City Staff
Clearly define any expectations for information or support to be provided by City staff during
the project.
h) Section VIII - Delivery Schedule
A proposed schedule for delivering the products and services as described in the RFP.
i) Section IX - Price Proposal
The price proposal shall clearly state the costs to the City of Bozeman for the project.
The contract for services shall be between the City of Bozeman and the consultant.
The price information shall include staff-hours of effort planned for each task by the
categories (i.e., level of experience) of personnel who will perform the services, materials,
travel costs, equipment usage charges (rate and total cost), and any other direct charges.
7) Delivery to be FOB:
Physical address: 20 East Olive Street, Bozeman, Montana 59715
Mail stop address: P.O. Box 1230, Bozeman, Montana 59771.
8) All prospective consultants may submit written questions about, or request written clarifications of
the RFP, including written protests of the RFP’s terms and conditions or technical specifications no
later than 4/9/07. All questions must be in writing (includes email) and addressed to the City’s staff
contact. No other staff member will answer questions about this Request for Proposals.
II. Selection Criteria and Process
The proposals will be judged on the completeness and quality of content. Only those consultants who
supply complete information as required by the material contained herein will be considered for
evaluation. The City of Bozeman is seeking to contract with a firm that has the appropriate
qualifications using appropriate technology and methodology to ensure delivery of high quality
products and who has demonstrated extensive experience with, and an understanding of, similar
27
4
projects. The criteria for evaluating proposals are as follows, with the weight each item carries shown
in parentheses:
Criteria Weight
1. A demonstrated understanding of each item proposed 20%
2. The level of quality provided by the technology and methodology proposed 30%
3. The necessary qualifications, experience, organization, technical and
managerial staff, and equipment and facilities to carry out the work
20%
4. Prior experience on related or similar projects, and the
accessibility/availability of the individuals working on this project
10%
5. Ability to complete the work within a proposed time schedule 5%
6. Cost of acquiring the RFP deliverables 15%
The City may invite three or more prospective consultants to respond to the selection committee in
person or writing during the proposal evaluation. Failure to provide additional information, if requested,
may disqualify proposal from further consideration.
The evaluation of proposals and the determination of conformity and acceptability shall be the sole
responsibility of the City and will be based on information furnished or identified in the proposal as well
as on other information available to the City.
The City of Bozeman reserves the right to reject the proposal of any person/firm who previously failed
to perform properly to the satisfaction of the City of Bozeman, or complete on time agreements of
similar nature, or to reject the proposal of any person/firm who is not in a position to perform such an
agreement satisfactorily as determined by the City of Bozeman.
The City of Bozeman reserves the right to determine the best qualified consultant and negotiate a final
scope of service and cost, negotiate a contract with another consultant if an agreement cannot be reached
with the first selected consultant, or reject all proposals. The successful consultant will be required to
enter into a professional services contract with the City of Bozeman, which will incorporate the
consultant's scope of service and work schedule as part of the agreement.
The City assumes no liability or responsibility for costs incurred by firms in responding to this request
for proposals or request for interviews, additional data, or other information with respect to the selection
process, prior to the issuance of an agreement, contract or purchase order.
III. Time Line
These dates may be revised if any step takes longer than anticipated. The City reserves the right to
postpone the award.
RFP issued 4/01/07
Written questions submitted 4/09/07
Proposals due 4/11/07
Notice to award 4/23/07
IV. Acceptance of Proposals
The City reserves the right to accept or reject any and all proposals; to add or delete items and/or
quantities; to amend the RFP; to waive any minor irregularities, informalities, or failure to conform to the
RFP; to extend the deadline for submitting proposals; to postpone award for up to 30 days; to award one
or more contracts, by item or task, or groups of items or tasks, if so provided in the RFP and if multiple
awards are determined by the City to be in the public interest; and to reject, for good cause and without
liability therefore, any and all proposals and upon finding that doing so is in the public interest, to cancel
the procurement at any time prior to contract execution.
V. Withdrawal of Proposals
28
5
Proposals submitted may be withdrawn by written request if received before the hour set for the opening.
After that time, proposals may not be withdrawn for a period of fifteen (15) days and at no time after
award.
No responsibility shall attach to a City employee for the premature opening of a proposal not properly
addressed and identified in accordance with these documents.
When discrepancies occur between words and figures, the words shall govern.
VI. Scope of Work
The project scope, specifications and requirements that are outlined in this RFP are subject to
modification and final contract negotiations.
Image included on Page 13 or this RFP shows the area to be flown:
All data will be delivered in UTM, NAD83, meters, Zone 12, NAVD88.
Prior to receiving notice to proceed and after negotiations, before any data collection the contractor must
submit a project plan. The project plan will include the following:
1) A map showing the study area boundaries and flight path at a reasonable scale (approx. 1:150,000)
2) Documentation specifying altitude, air speed, scan angle, scan rate, LiDAR pulse rates, and other
flight and equipment information deemed appropriate.
3) A chart of areas of high Position Dilution of Precision (PDOP), or a list showing the time of the
beginning and end of high PDOP.
4) The proposed ground control plan containing Airborne GPS support. If necessary, the contractor
shall obtain all rights of entry, be responsible for all GPS control information and show all National
Spatial Reference System (NSRS) monuments that will be used for the GPS base stations for airborne
GPS control during the LiDAR acquisition.
1) Digital Imagery Specifications:
Digital Camera Defined
For the purposes of the Request for Proposal, a digital camera is defined as a stable mechanism that
collects the ground imagery without the use of film in a direct digital format. The City of Bozeman
recognizes that currently the USGS does not provide a calibration report on digital camera
technology; therefore, the vendors must satisfy Bozeman that the proposed camera system has been
calibrated, modeling all known errors, and exhibits a high degree of internal geometric accuracy,
stability and repeatability.
Imagery used for the development of the DTM and Orthoimagery shall be acquired only on clear days,
leaf-off conditions, with no snow and minimal puddling of rain water or other weather-related effects
obscuring the ground surface. At a minimum, National Map Accuracy Standards for the production of
the DTM and Orthoimagery must be adhered to. All control work shall be completed by the
consultant. The camera and magazines shall meet or exceed the most recent USGS specifications for
aerial camera systems. Aerotriangulation/bundle adjustment shall be performed by the current state-
of-the-art analysis software to maximize accuracy of the data. The consultant shall provide a copy of
the AT report.
The proposal shall include a proposed schedule of events necessary to complete the work. The
schedule shall include a process and schedule for the submittal of draft products for City review prior
to final submittals.
Failure to comply with any of these provisions may result in the rejection of the proposal.
a) Photographic Conditions
29
6
• Tree Cover. Photography shall be undertaken while the leaves are off the deciduous
trees; however, leaves on will be acceptable to the extent that the contractor can still compile
accurate contours.
• Clouds. Clouds or cloud shadows must not appear on the imagery. High, thin overcast
is permitted above the flying altitude if it does not cause ground mottling or a discernable
reduction in light levels and/or ground object shadows.
• Well-Defined Images. Collect imagery to obtain well-defined images. Do not attempt
imagery acquisition where the ground is obscured by haze, smoke, smog, dust, or falling
snow, sleet, rain, or other obscuring phenomena. Do not collect imagery when ground is
covered by water (flood), snow, or ice.
• Visibility. The minimum visibility at the time of exposure must be 10 miles or greater.
• Sun Angle. The majority of the project area will be collected when the sun angle is not
less than 40°. In mountainous areas with steep terrain and/or areas with tall trees or areas
with significant urban development with buildings 3 stories or taller (such as downtown
Bozeman), increase the minimum sun-to-horizon angle to acquire the photography during the
times of minimal shadow.
• Tilt will not exceed four degrees for any photographic frame and will average not more
than two degrees for any ten consecutive frames. Relative tilt exceeding six degrees between
any two successive frames may be cause for rejecting that portion of the flight lines.
• Crab angle as measured from the average line of flight will not exceed five degrees. The
course-heading differential between any two successive exposures will not exceed five
degrees.
• Forward overlap will be at least 55 percent between consecutive exposures. The average
sidelap will be at least 20 percent.
b) Image Quality/Radiometry
• There shall be no areas of an orthophoto where the process was incomplete due to image
gaps or lack of data.
• All digital orthophotos shall be radiometrically adjusted as necessary so that adjacent
digital orthophotos can be displayed simultaneously without an obvious visual edge seam
between them. Localized adjustment of the brightness values shall be performed to minimize
tonal differences between the join areas. For this adjustment, the orthophoto judged by visual
inspection to have the better contrast shall be used as the reference orthophoto. Localized
brightness values of the adjacent orthophoto shall be adjusted to that of the reference
orthophoto. When possible and feasible, the area adjusted should be bounded by a tonal break
ground feature such as a road, field line, shadow line, etc. The radiometric adjustment should
not compromise the accuracy, clarity, or resolution of the orthophoto.
• Prior to undertaking full digital orthophoto production, the Contractor shall furnish the
City with sample digital images to evaluate and accept as examples of overall image quality.
The City will select one image, which will become the standard to which all subsequent
digital orthophotos will be compared for acceptance/rejection relative to image quality.
2) LiDAR Specifications:
LiDAR Defined:
For the purposes of the Request for Proposal, Light Detection and Ranging (LiDAR) is defined as
airborne an airborne laser system, flown aboard rotary or fixed wing aircraft, that is used to acquire
x, y, and z coordinates of terrain and terrain features that are both man-made and naturally occurring.
LiDAR systems consist of an airborne Global Positioning System (GPS) with attendant GPS base
stations, Inertial Measurement Unit (IMU) and light emitting scanning laser.
The system measures ranges from the scanning laser to terrain surfaces within a scan width
beneath the aircraft. The time it takes for the emitted light (LIDAR return) to reach the
earth’s surface and reflect back to the onboard LIDAR detector is measured to determine the
range to ground. Scan widths will vary, depending on mission purpose, weather conditions,
desired point density and spacing, and other factors.
The other two components of LIDAR systems are the airborne GPS, which ascertains the in-
flight three-dimensional position of the sensor, and the IMU, which delivers precise
information about the attitude of the sensor.
30
7
3) Bare Earth Surface
LiDAR point cloud shall be filtered to a bare earth surface to create Digital Terrain Models (DTM)
capable of supporting the creation of 1’ contours.
VII. Control
All necessary horizontal and vertical control necessary to provide a DTM meeting the standards specified
herein shall be completed by the contractor.
VIII. Project Schedule
In their responses to this proposal, Respondents shall propose a detailed schedule of performance for
completion of all components of the production process. General project milestones should be presented;
final project milestones will be established prior to project initiation.
IX. Deliverables
The respondent shall submit a delivery schedule.
The Consultant shall deliver to the City for acceptance the following items:
• True Color Digital Ortho Imagery; 1”=600’ scale, 6” pixel, true color, orthorectified digital
imagery in GeoTIFF and entire project as mosaic in MrSID format
• 1’ Contours in ESRI geodatabase format
• High Density hydro enforced Breaklines in ESRI geodatabase format
• DTM in ESRI grid format, ESRI geodatabase format
• DEM in ESRI grid format created using bare earth points
• FGDC compliant metadata for the imagery and GIS data in XML format
All products delivered and developed under this proposal shall become the sole property of the City of
Bozeman with no restrictions on use or dissemination.
a) Digital Imagery
6-inch or 0.1524 meter pixel Ground Sample Distance (GSD) digital orthorectified color
digital imagery shall be obtained for the entire project area. Imagery shall be collected with a
minimum 30% side lap and 60% over lap to ensure coverage sufficient to produce stereo
images. Imagery shall be orthorectified to the NAD83/92 datum in survey feet or 0.1524
meters.
The City of Bozeman wishes to utilize a true aerial digital camera to reduce the amount of
time and expense required for processing, developing and scanning of film that is normally
associated with traditional aerial cameras. Digitally collected imagery ensures the highest
quality imagery from the time of image acquisition because there are no external sources for
contamination or degradation of image quality.
The City requires that digital image and LiDAR data be acquired simultaneously captured
during one flight to insure consistency between image and LiDAR datasets.
b) LiDAR Specifications
All LiDAR data must meet or exceed the Federal Emergency Management Agency's Guidelines and
Specifications for Flood Hazard Mapping Partners, Appendix A: Guidance for Aerial Mapping and
Surveying, April 2003.
The projection will be UTM, NAD83, meters, Zone 12 with North American Datum 1983/1990 HARN
adjustment. Vertical Datum will be North American Vertical Datum of 1988 (NAVD 88).
The flight season will be from 4/15/07 through 5/15/07 In the event that weather conditions are not
acceptable to meet this window the Consultant must receive written approval from the City before
flying.
The City requires the use of an Leica ALS 50 or equivalent LiDAR sensor with 83 kHz or
31
8
greater for this project
Media
Data will be delivered using portable USB hard drives (250 GB minimum). Upon final acceptance of
the data the Consultant will provide one set of data on DVD media. Tiles shall be contiguous and non-
overlapping and will be suitable for creating seamless topographic data mosaics that includes no "no
data" areas. The City and the Consultant will jointly determine the appropriate tiling scheme for mass
point and breakline data based on the estimated total number of mass point and breakline features that
are collected.
Topographic Data Formats
The following sections define the data formats required for the mass point and breakline features.
Mass Points
Mass point data shall be delivered in LAS files compatible with the LAS Specification 1.1 format and
must meet the requirements identified within this specification including header blocks, variable length
records and point data. City required items, not specifically noted as required in the LAS 1.1
Specification, are defined in the following sections.
The mass point data shall not contain any data voids and overlap between flight lines shall be removed.
The classification code for these files will follow the LAS 1.1 format and will include the following:
• Class 1 = Unclassified
• Class 2 = Ground
• Class 9 = Water
Class 1 will be utilized for all other features that do not fit into the Classes 2 or 9 including vegetation,
buildings, noise, etc.
Public header information must be contained as specified within the LAS 1.1 file specification.
Projection information for the point data must be specified in the Variable Length Records using the
GeoTIFF specification as the model per the LAS 1.1 file specification.
The Point Data Record Format shall follow the Point Data Record Format 1 as defined in the LAS 1.1
Specification. In addition to the required items, the Intensity shall be populated.
Compilation
The following compilation deliverables are required. • Digital Terrain Model
• Digital Elevation Model
• Digital elevation contours
• Digital spot elevations
• Digital orthophotography
• One copy of the Aero triangulation Report
• One copy of the Compilation Report
c) Breakline Specifications
Breaklines shall be delineated to insure the digital terrain model (DTM) is hydrologically correct. The
following guidelines will be used when developing breaklines:
Breaklines will be delivered in ArcGIS personal geodatabase format. Separate feature classes must be
delivered for each breakline feature type defined below.
Feature classes must be contained within a feature dataset with proper horizontal and vertical spatial
references defined. Feature classes must be Z-enabled where defined as three-dimensional breakline
features below. Those features captured as two-dimensional breaklines must have a floating point
ELEVATION attribute.
32
9
Breaklines will be captures for all features needed for the development of 1-ft contours that meet
ASPRS accuracy requirements.
• Road Features
Road features, not including bridges and overpasses, shall be captured as edge of pavement breaklines
as required to create a hydrologically correct digital terrain model. These features will be captured as
three-dimensional breaklines.
Breaklines will be captured for all hydrologically significant features as appropriate to support the
development of the generation of 1-foot contours meeting National Map Accuracy Standards.
Breakline features will be classified and separated as follows:
• Closed Water Body Features
Land water boundaries of constant elevation water bodies (lakes, reservoirs, etc.) will be delivered as
closed polygons with a constant elevation that reflects the water elevation at the time the data were
captured. Water body features will be captured for features one-fourth acre in size or greater. Water
bodies can be captured as two-or three-dimensional breaklines and LiDAR measurements that are
inside of water bodies will be classified as water in the LAS deliverable.
• Linear Hydrographic Features
Linear hydrographic features (streams, shorelines, canals, ditches, swales, embankments, etc.) will be
delivered as breaklines with varying elevations. All stream/river features that are 100 meters or greater
in length will be captured. Features that are 2 feet or less in width shall be captured as single breakline
features. Features that are greater than 2 feet in width shall be captured as double line features. All
features will be captured as three-dimensional breaklines. Linear features will cut through all bridges
and culverts that are identifiable on the imagery.
• Road Features
Road features, not including bridges and overpasses, shall be captured as edge of pavement breaklines
as required to create a hydrologically correct digital terrain model. These features will be captured as
three-dimensional breaklines.
• Soft Features
In areas where the LiDAR mass points are not sufficient to create a hydrologically correct DTM, soft
features such as ridges, valleys, top of banks, etc. shall be captured as soft breaklines of varying
elevations. These features will be captured as three-dimensional breaklines.
• Obscured Vegetated Areas
These are defined as vegetated areas that are considered obscured to the extent that adequate vertical
data cannot be clearly determined in order to accurately define the DTM. These features shall be
captured as two-dimensional closed polygon features. These features are for reference information
indicating areas where the vertical data may not meet the data accuracy requirements due to heavy
vegetation.
• Overpasses and Bridges
Overpass and bridge features will be captured as three-dimensional breaklines.
Posting
33
10
The LiDAR cloud will be collected at a density of 1 meter or sufficient to support the development of
one-foot contours. As defined here, obscured areas are those containing structures, vegetation or other
surface features that are of sufficient density to make it not possible to obtain bare earth postings.
Vertical Accuracy
The vertical accuracy for LiDAR data over well-defined surfaces shall meet the Federal Geographic
Data Committee’s (FGDC) published National Standard for Spatial Data Accuracy (NSSDA). Vertical
accuracies at the 95 percent confidence level for flat terrain are required, assuming all systematic errors
have been eliminated to the greatest extent possible and the errors are normally distributed. Accuracy
shall be tested to meet a 9.25-cm fundamental vertical accuracy at 95 percent confidence level using
RMSE (z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA).
Horizontal Accuracy
Horizontal accuracy is difficult to assess, however, the expected horizontal accuracy for the LiDAR
data over well-defined surfaces shall be determined. The City’s minimum expected horizontal
accuracy shall be tested to meet or exceed a 2 foot horizontal accuracy at 95 percent confidence level
using RMSE(r) x 1.7308 as defined by the National Standards for Spatial Data Accuracy (NSSDA).
Water Bodies
Shorelines of water bodies shall be captured as breaklines as define above and LiDAR measurements
that are inside of water bodies will be classified as water in the LAS deliverable.
Artifacts
The Consultant will deliver a complete LiDAR cloud where the bare earth classification (Class 2) is
free of artifacts not representing the earth's surface (cell towers, building, trees, vehicles, etc.). These
artifacts shall be classified as Class 1 – The bare-earth surface will be clean of artifacts of 95% or
greater.
d) Digital Terrain Model (DTM)
The DTM will be of such precision and quality to support projects such as slope analysis; develop
perspective plots; perform hydrographic and hydrologic analyses; generate cross-sections; regenerate
contours; as the control network in the development of Orthoimagery of the mapped areas; and other
products requiring continuous contours of mapped areas. The selection and spacing of DTM points
shall be defined by the contractor to be appropriate for the generation of 1-foot contours to conform to
ASPRS Accuracy Standards. Elevation data points shall be delivered as either a regular or irregular
DTM in an ESRI geodatabase compatible format. The City also requires a Digital Elevation Model
(DEM) in an ESRI geodatabase format. A TIN is not being requested under this solicitation.
Contours
The Consultant will develop one-foot contours created from the DTM dataset that are certified to meet
or exceed National Map Accuracy Standards for one-foot contours. These contours will be used for
cartographic visualization purposes. Contours must be delivered in ArcGIS geodatabase with an
elevation field and index contour identifier. Contours should be continuous and aesthetically pleasing
to the layperson.
Metadata
Metadata compliant with the Federal Geographic Data Committee's (FGDC) Content Standard for
Spatial Metadata in and ArcCatalog compatible XML format will be delivered. Metadata should be in
accordance with recommendation of the National Digital Elevation Program Guidelines for Digital
Elevation Data, Version 1. The following minimum guidelines must be adhered to in the metadata:
There should be one set of metadata per feature class and one set for the entire set of LiDAR mass
points for each project.
Metadata must be delivered in a format compatible with ArcGIS 9.x.
34
11
The metadata recommendations defined in Guidelines for Digital Elevation Data, Version 1.0 can
serve as a model for the metadata. The Consultant should expand upon these metadata as appropriate
based on their professional expertise.
Copies of all survey reports must be delivered in PDF format. The City will utilize these as
attachments to the FGDC metadata.
Survey Control
Ground control must be adequate to support the accuracy specifications identified below. The
Consultant must submit a report that documents all ground control and aircraft global positioning
system and aerial triangulation utilized in the project. All horizontal and vertical control surveys shall
be based upon first or second order survey control stations that are part of the National Geodetic
Survey's National Spatial Reference System. All horizontal control must be part of the North American
Datum 83 High Accuracy Reference Network. Vertical control must be in the North American Vertical
Datum of 1988.
Vertical Accuracy Report
The Consultant will prepare a vertical accuracy report that is based upon the comparison of a minimum
of twenty ground measurements per each ground cover classification listed below and image
measurements distributed through each project area collected for each of the following land cover
categories:
• Urban high density
• Urban residential area
• Bare ground/short grass/cropland
• Brush
• Forest
Accuracy inspections shall be made in flat or gradually sloping areas to minimize potential errors
related to horizontal map accuracies. Test points will be distributed throughout the project area to the
greatest degree possible. Accuracy testing and reports will be done in accordance the specifications of
the National Standards for Spatial Data Accuracy (NSSDA).
X. Quality Control and Acceptance Procedures
Quality Control
The City retains the sole right to determine contract adherence to quality control requirements. Judgment
that the Contractor is in breach of the quality control requirements may require suspension of any phase
of the contract until such time as the City can determine that such problem(s) have been remedied.
Respondents shall indicate in their proposal a description of the internal quality control processes they
will utilize throughout the various phases of the project to assure that the contract deliverables will be
acceptable. The Respondent may provide forms, flow charts, or other materials to document the quality
control process.
Acceptance Checks
An attempt will be made to complete checks of all deliverable products within 30 days of delivery.
Check plots and ArcGIS data will be subjected to a series of inspections that may include the following:
• Mounting, manipulation, and display of digital files on the City’s GIS system
• Comparison of data and file content with digital orthophotos
• Checks to verify the informational content of the data for completeness, correctness, and
database integrity
• Field checks to ensure compliance with ASPRS accuracy standards
• Other checks against specifications as may be appropriate
35
12
The City will be conducting checks of the hard copy and digital data provided.
Acceptance Procedures
After initial checking, work increments will be categorized by the City as follows:
• ACCEPTED: Products that meet specifications and contain no errors, or so few errors as to be
acceptable, will be formally indicated as accepted. The City may assume responsibility for
minor corrections, after which the Contractor will be notified, so that the problems will not recur
on subsequent products.
• RECEIVED-EDITED: The product has a number of errors that do not permit acceptance. For
the product to be accepted, the Contractor must correct all errors noted by the City. The City
will verify through a recorded edit that the Contractor has made all corrections called in for the
first edit.
• REJECTED: The number and character of errors detected by the City are such that the product
is formally returned to the Contractor without a complete edit. The City will formally notify the
Contractor of the rejected status of the product. The Contractor must edit and correct the
mapping for resubmittal to the City. If the City determines that there is an excessive number of
rejected products, the City may require the Contractor to suspend production until the problems
are resolved.
Completion of any required corrective actions shall not affect the Contractor’s production schedule.
Payment for work will not be authorized until the City has accepted the products. The acceptance
procedure will apply to all deliverable products to be received.
36
13
37