REQUEST FOR PROPOSALS
THE DEVELOPMENT OF A GEOGRAPHIC INFORMATION SYSTEM (GIS)
CITY OF FREMONT, NEBRASKA
The City of Fremont, Nebraska is seeking qualified consulting firms to submit proposals for a
Geographic Information System.
Sealed Proposals are due by 4:00 p.m. September 11, 2020. Late proposals will not be accepted.
Sealed proposals shall be hand carried or delivered by traceable means to:
City of Fremont
400 East Military Avenue
Fremont, NE 68025
All proposals should be clearly marked: Request for Proposal for Geographic Information System
(GIS). RFP # PL-003
The City of Fremont (City) is soliciting proposals from experienced, qualified GIS design and
consulting firms to support and provide geographic information system products and services.
This RFP is focused on Cadastral and Municipal GIS layer development and Web-GIS system
implementation. However, optional pricing for utility mapping and GIS development are also
requested. The final agreement will potentially support all City departments, including utility
and municipal functions for GIS needs based on available funding.
The selected firm will be the designated consultant to provide all planned, as well as "optional"
GIS related services during the duration of an agreement with the City of Fremont. It is the
intent of the City to contract with a proven and experienced GIS firm who specializes in
accurate, functional GIS data development and software tools for cities. The potential projects
identified in this RFP are broad in range of mapping abilities and the selection process will
have the goal of finding a sole firm with experience in all abilities, however, subcontractors and
teams will be considered. It is the priority of the City to contract with an experienced firm in
order to streamline communication and avoid excessive costs or errors in GIS projects and
The City Fremont, NE consists of approximately 25 square miles with approximately 11,460
parcels within the City Limits. The Fremont extra-territorial zoning jurisdiction extends 2 miles
beyond the City limits, stopping at the Platte River on the south. The number of parcels within
this area is not currently known, however, most of the area consists of farm land.
A – Project Scope
1 -CADASTRAL DATA CONVERSION
• Projection/Coordinate System -The delivered system will be in Esri format and geo-
referenced to real-world coordinates in the Nebraska State Plane coordinates. The
delivered database will form a contiguous, seamless, edge-matched base of the City’s
maps. The system will be built upon the Nebraska Low Distortion Projection (LDP) Zone 8-
Dodge County, NAD 2022 utilizing the parameters defined by the Nebraska State
• Cadastral Data Development - All final cadastral data deliverables shall meet all
requirements for migration to the ESRI Parcel Fabric, utilizing survey control and COGO
methodology. The respondent shall describe in detail the proposed method planned for
data conversion. All information contained on the existing maps shall be captured in the
new GIS database. Enhancements to the existing maps are encouraged and should be
thoroughly explained in the proposal.
Research to be fully utilized as part of the GIS mapping project as available includes:
• Available and most current digital aerial photography and County Assessment maps
• General Land Office (GLO) plats. (Quarter section, Section, Township & Range boundary
lines shall be mapped in the GIS according to GLO plat distances.)
• Registered Section Corner documents. (Section and quarter section corners shall be
adjusted to any available registered section corner location. The registered section
corner documents shall be hyperlinked to the corresponding layer in the GIS.)
• Recorded Subdivision Plats acquired from the State Surveyors Office (SSO), City Public
Works Department, or Dodge County eRegister of Deeds office. All original lots and
original blocks as identified on the recorded subdivision plats shall be mapped as closed
polygons and attributed with the corresponding lot or block number. All subdivision
boundaries shall be mapped as closed polygons and attributed with the corresponding
• Highway Right-of-Way plans acquired from Nebraska Department of Transportation
(NDOT). Highway rights-of-way shall be mapped by referencing the maps and highway
plans as needed.
The successful respondent must adhere to the following compilation requirements:
• Edge Matching - All mapped line features must be both visually and coordinate edge
matched with adjacent features.
• Common Boundaries - All graphic features that share a common boundary, regardless of
digital map layer, must have the exact same digital representation of that feature in all
common layers. The respondent shall describe the method used to accomplish this.
• Point Duplication - No duplication of points that occur within a data string is permitted.
• Connectivity - Where graphic elements visually meet, they must also digitally meet. All
confluence of line, area, tangent, and polygon data must be exact mathematically. No
“overshoots”, “undershoots”, offsets, or “pseudo nodes” are permitted. Lines that connect
polygons must intersect those polygons precisely; that is, every end point must be an
intersection point of the respective polygon.
• Line Quality - A high quality cartographic appearance shall be achieved. Transitions from
straight line to curvilinear line segments shall be mathematically tangent, smooth, and
without angular inflections at the point of tangency. No zero length line features shall be
included. Curvilinear graphic features should be smooth with a minimum number of
points. When appropriate, line-smoothing routines shall be used to minimize the angular
inflection in curvilinear elements. All straight lines (lines that should be straight) shall be
defined by the two terminus points only.
• Segmentation - The digital representation of linear elements must also reflect the visual
network structure of the data type. All data elements representing differing features shall
be distinguished in the database by layering or other effective method. An element should
not be broken or segmented unless that segmentation reflects a visual or attribute code
characteristic, or unless the break is forced by data base limitations.
• Point Criteria - All point features shall be digitized as a single X, Y coordinate pair at the
visual center of that graphic feature.
The structure of the cadastral data will not inhibit the execution of GIS functions across
boundaries or artificial discontinuities (file edges or other delimitation). The respondent
shall process the database as the last step prior to delivery of data to ensure that spatial
continuity is achieved. All polygons and lines shall be verified by the respondent prior to
delivery for proper closure and connectivity as appropriate.
All data will be delivered in Esri file geodatabase. Esri topology validation must be performed
prior to delivery, and the resultant error layers must be delivered to the City. A list of specific
topology rules that will be applied should be included in your response. At a minimum,
topology rules must be applied that enforce each of the topology business rules outlined
above. Known topology exceptions must be marked in the geodatabase prior to delivery. The
Esri local government information model will be used for all applicable data layers developed
for the City.
ANNOTATION AND DYNAMIC LABELING
Annotation and dynamic labels shall be used in concert to achieve an aesthetically pleasing
and cartographically complete hard copy map. Annotation should be used to represent lot
dimensions and miscellaneous text.
Annotation will be optimized initially for the production of hard copy maps at 1’=100’, 1”= 200’,
and 1”=400’. In general, the orientation and display of annotation shall follow accepted rules for
cartographic production to ensure high quality, readable, and aesthetic map products for
display and plotting. All annotation shall be consistent in terms of defined fonts, levels, angles,
and offsets. Annotations shall be placed as follows:
• To obscure the minimum amount of other map features
• To occur at least once on each map sheet for which the map feature appears
• To be uniform in orientation throughout the data base
• To be correct in regard to grammar and spelling
Dynamic labels should be used to represent at a minimum the following features:
• Original Lots
• Government Lots
• Original Blocks
• Map Blocks
• Roads and
• Section, Township
• Named Creeks,
Rivers, & Lakes
• City Limits
• County parcel ID
CADASTRAL GIS DATA MODEL
All cadastral data should be delivered in an Esri personal geodatabase. This geodatabase
must include one or more feature datasets that have pre-defined projections, coordinate
systems, and map extents as previously described. Individual feature classes will reside within
the feature datasets. All feature classes will be citywide in extent, and all topology validation
will be performed citywide.
All data should, at a minimum, meet the standards defined by the Nebraska Information
Technology Commission (NITC) standards and guidelines
The following outlines the type of feature class data layers to be created within the GIS
database, methodology to be used to create the data layers, and the type of research to be
referenced for each specific data layer.
Polygon Feature Classes
• Lot Boundaries – lot boundaries shall be mapped as closed polygons by referencing the
recorded subdivision plats and tax maps.
• Tract Boundaries
• Original Block Boundaries – complete closed polygons shall be created with original block
number as attribute data.
• Water (lakes, large rivers, minor waterways) – water boundaries shall be mapped directly
from available and most current aerial photography. The water feature name shall be
included as an attribute. Free data shall not be used to properly map hydrology data
• Subdivision boundaries – complete closed polygons shall be created with subdivision
name as attribute data. Recorded subdivision plat research and tax maps used as
• City Boundary – complete closed polygon with city name as attribute data.
• Township & Range Boundary – complete closed polygon with Township & Range
numbers as attribute data.
• Section Boundaries – complete closed polygons with section number as attribute data.
Section lines shall be adjusted based off GLO plat research, registered section corner
document research, tax maps, occupation lines, and recorded subdivision plat research.
• ¼ Section Boundaries – complete closed polygons with quarter section quadrant as
• Road and Railroad Right-of-Way Boundaries – This layer shall be a “closed” polygon
feature class throughout the entire City. Utilize existing maps, occupation lines, and State
and US Hwy. right-of-way research shall be acquired from NDOT as needed.
Point Feature Classes
• Address Points – Integrate existing NG911 address points into the GIS dataset.
Polyline Feature Classes
• Road Centerlines – Obtain road centerlines and address points from the E911 PSAP and
establish an update cycle.
• Railroad Centerlines- Obtain railroad centerlines from the E911 PSAP and establish an
• Water (streams) – re-draw streams from available and most recent aerial photography.
Existing City maps can also be used as reference. Name and type attributes shall be
CADASTRAL MAP MAINTENANCE WORKFLOW
The respondent is encouraged to present a workflow that is used to streamline the map
maintenance process. The workflow must have the capability of publishing the feature classes
specified above on an as-needed basis. Any underlying map maintenance data model must
reside entirely within a geodatabase, and must reside within the same geodatabase as the
published feature classes. All aspects of the map maintenance workflow must take place
entirely within the geodatabase.
Quality control is an essential part to ensuring the integrity of the database. Each respondent
shall describe in detail the various automated and manual quality control procedures
implemented throughout the conversion process to detect errors at each step and achieve the
accuracy requirements for the project.