Birch Creek Debris Mitigation Surveying - Exhibit D Topo Standards.pdf
PDF 251 KB Posted
- Solicitation number
- PWG126-FLOOD-6360
- Issued by
- San Bernardino County, California
About this file
This is a technical standards document issued by San Bernardino County (SBCO) establishing surveying and topographic data collection requirements for the Birch Creek Debris Mitigation Surveying project. The document specifies comprehensive surveying methodologies including centerline control establishment via RTK measurements from known base stations with minimum 121-minute static observation periods processed through CORS sites, and cross-sectional surveys collected via total station at 50-foot intervals. Topographic data collection requirements include establishment of centerline surveys for roadways and cross streets, cross-sections every 50 feet, survey coverage extending to existing right-of-way, fence lines, or specified distances from edge of pavement, and detailed pickup of utility infrastructure including vaults, boxes, signal light poles, crosswalk buttons, utility poles, valves, and manholes. Additional requirements include surveying all man-made features such as fences, gates, utilities, flow lines, curbs, pavements, sidewalks, pipes with specifications, traffic signs, driveways, and handicap ramps, as well as natural features including trees, bushes, and planters.
Deliverables must be provided in AutoCAD hybrid grid-ground format with specific notation standards including project identification, charge codes, survey dates, grid bearings in California Coordinate System Zone 5 NAD83(2011) Epoch 2010.0, scale factors, and benchmark references. The document establishes standardized surveyor descriptor conventions requiring base descriptors listed first with specific formatting rules, use of dashes for multi-component descriptors, and prohibition of spaces within descriptor names to ensure proper Civil3D software importation. The standards mandate four-corner documentation of utility vaults, pull boxes, signal light poles, and crosswalk buttons, with center-point measurements required for fire hydrants, utility poles, signal lights, street lights, and trees. All topo work must exclude RTK measurements and utilize total station collection methods exclusively.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SBCO Topo Standards
Control:
-Centerline control and topo traverse points may be established via RTK measurements from a known base; A “known base” is a position that is established by static observation for a minimum of 121 minutes, processed via OPUS or manually to a minimum of 3 CORS sites.
-A minimum of two (2) 3-minute RTK measurements on each position, a minimum of 90 minutes apart for each measurement.
-If RTK measurements are collected via real-time network, processing manually to a minimum of 3 CORS sites is required. All topo to be collected via total station, not RTK.
Topo:
Topo items to be collected, unless specifically told not to:
1. Establish centerline survey of roadway and cross streets by locating survey control monuments.
a. For ramp only jobs, centerline only needs to be established in directions that are needed to establish the delta of the quadrant the ramp occupies.
2. Cross section every 50-feet.
3. Topo the entire roadway up to either (to be specified by requestor):
a. Existing right-of-way, left and right of centerline
b. Fence line, left and right of centerline
c. 5-feet left or right of EP/Curb/Dike
4. At street intersections, survey up to limits listed above in #3, 50-feet beyond BCR/ECR
5. Pickup FOUR (4) corners of utility vaults/boxes, pull boxes, concrete pads under boxes, FOUR (4) corners of signal light poles/crosswalk push button poles, and diameter of utility poles (measured to center) and valves, manholes (top-center of lid elevation only, unless specifically asked for invert elev. too), bollards, etc.
6. Pickup all man-made features, fences, gates, utilities (vaults, fire hydrants, FOUR (4) corners of water meters, hose bibs, septic clean outs, utility poles, dead man, etc) flow lines, top of curb, gutter lips, ac dike, edge of pavement, concrete gutter lip/flow line and spandrel, catch basins or drainage structure (top of concrete and invert elevations), sidewalks, pipes (with pipe sizes, types, and invert elevations), traffic signs, striping’s, markings, grade breaks, driveways, handicap ramps (minimum of ¼ deltas and top/bottom of ramp x), etc.
7. Pickup all trees (measured to center of tree), bushes, planters, etc.
8. Data to be delivered in AutoCAD hybrid grid-ground format (see standard survey CAD file notes below)
9. ROW linework for roadways to be shown, and ROW linework for Flood Control to be shown where applicable.
Standard Survey CAD File Notes:
PROJECT NAME/TITLE
PROJECT CHARGE CODE (HXXXXX, F0XXXX, or TXXXXX) Project Job Number
DATE OF SURVEY: XX/XX/XXXX
DISTANCES AND COORDINATES ARE GROUND.
CF = 0.XXXXXXXX
1/CF = 1.XXXXXXXXXX
*NOTE - THIS DRAWING CONTAINS GRID BEARINGS
GRID COORDINATES*, BUT GROUND DISTANCES.
BASIS OF BEARINGS:
CCS83 ZONE 5, NAD83(2011), EPOCH 2010.0
BENCHMARK:
Benchmark description, including reference for description and elevation
NGVD-29 ELEV (NAVD-88) = XXXX.XX’
TO CONVERT TO GRID:
* SCALE PROJECT @ Pt #X (0.XXXXXXXX)
SBCo. Surveyor Descriptor Notes:
• The descriptor that is listed (the base descriptor) needs to be the first thing added EVERY TIME, no exceptions.
o Ex: FENCE-METAL-6’, not METAL-FENCE-6’
• When a descriptor has an asterisk (*) at the end, that descriptor can have anything you want after the main portion of the descriptor.
o Ex: CONC* - CONC1, CONC2, CONC3, etc o Ex: PP* - PP NO NUMBER, PP 123456E
• When a descriptor doesn’t have an asterisk (*), only what is shown on the descriptor list is valid; nothing can be added to this descriptor or it won’t import into Civil3D properly.
o EX: GP – nothing can be added after GP o Most descriptor’s without (*) are meant for single objects, not lines.
• Empty spaces within a descriptor confuse Civil3D. Any time you need to add information to a descriptor or combine descriptors, use a minus sign/dash (-). There are very, very few exceptions to this, so when in doubt, add the (-). A space IS required when starting (\) or ending (/) a line.
o Ex: PP NO NUMBER or PP 123456E, no (-) required o Ex: Tree 1”-6”, no (-) between ‘Tree’ & ‘1’ required o Ex: CLF-6’, (-) is required.
o Ex: SRF-WOOD-6’, (-) is required o CSPA-24”X36”, (-) is required.
o If you don’t add a (-) and instead use a space, Civil3D interprets that as a separate descriptor, so however many spaces you have in the descriptor, that’s how many descriptors Civil3D interprets.
• Topo the four (4) corners of all utility VAULT’s, PLBOX’s, BOX’s, SIGLGT’s, XWALK-BTN o Use VAULT, PLBOX, BOX for the line and use VAULT-*, PBOX-*, BX-* for the center ‘describing’ measurement o Use GB for base of SIGLGT and XWALK-BTN
• Measure to the center of all fire hydrants, guy poles, power poles, signal lights, street lights, trees, crosswalk buttons
File details come from the government source that posted it. Updated .