Grading/Site Plans

  • “Site development plans showing the uses of the parcel of land, existing and proposed structures, setbacks, yards and open space, maximum slope of property (if exceeds 12%), lot layout, the size and number of parking spaces, routes of vehicular access, the location of signs, the location of landscaping, trash enclosures, loading spaces, sight zones,…” (Title 30.16.240 Document Submittal Requirements)
  • 2012 International Building Code - Appendix J - Grading Plans

Procedure

  1. Proposal email
    1. $1500 Grading Plan
    2. $1500 Topographic Survey
      1. might need to have Boyd Nelson or John Jonaupour to set property corners or mark them
      2. Obtain LV Stateplane coordinates lot corners (Assessor Parcel, rent GPS from Monsen or from above surveyor)
  2. Get signed contract and deposit
    1. \\ge01\GISEProjects\ProjectName\Docs (save owner info and scanned signed contract here), give hard copy to Cindy to file
    2. 192.168.100.21
  3. Project Folder Structure
    1. X:\H10000 - City of Las Vegas project number or I:\16016-WCraigBaptistChurch-TRIPLED\GISE16016
      1. _Shortcuts
      2. Base Drawings
      3. Blocks
      4. Documents
      5. Engineering Drawings
      6. GIS
      7. Reports
      8. Sheet Set
      9. Submittals
      10. Survey Drawings
  4. Record Drawing Request (e.g. Ernesto Hernandez APN 139-19-811-043, 4007 Pleasant Rd)
    1. Clark County Building Department - Building Footprint/Grading Plan on file
      1. email dsrecords@clarkcountynv.gov
      2. Sandy Linehan, Records Technician, 702-455-3029
    2. City of Las Vegas
  5. Utility Plan (items not shown on grading plan)
      1. need parcel number, address, cross streets, project description, Clark County OpenWeb
    1. Clark County Water Reclamation District
      1. email sewerlocation@cleanwaterteam.com
      2. “Will you please email me a PDF of nearby sewer pipelines and as-built drawings near the parcel in the subject line”
    2. Southwest Gas
      1. email swgengplansubmittal@swgas.com
      2. provide parcel number, address, project name and description
      3. ftp account (https://files.swgas.com), Lauretta.Fagan@SWGas.com, 702-365-2099
    3. NV Energy
    4. Cox Cable
    5. Telephone
  6. Survey (Horizontal Control is different sheet)
    1. Request boundary survey by John Jahanpour (john@hjburke.com, 702-452-8753)
      1. set property corners
      2. provide basis of bearing - centerline of road and property line
    2. Legal Description
    3. Basis of Bearings
    4. monuments (section corners with LV stateplane coordinates)
      1. City of Las Vegas
        1. Mike Kinney 702-229-6938, mkinney@lasvegasnevada.gov, Projection is NAD83 NRCS Las Vegas Zone US Foot (AutoCAD Civil 3D). Mike said Civil 3D will reproject the aerial photos from standard stateplane coordinates to new City stateplane coordinates which have the ground to grid factor already fixed. Also, at the beginning of a project, send Mike an email and he will send the nearest Section Corner and Quarter Corner GPS coordinates.
  7. Geotechnical Soils Report
  8. GIS
    1. building footprints?
    2. aerial photos
    3. Assessor Parcel Boundary (min 100 ft around site)
    4. Vicinity Map - street centerline
  9. Field topographic survey
  10. Import Survey Shots
    1. use USB thumb drive to copy points from TSC2 to computer

Prerequisites

  1. Geotechnical/Soils Report
  2. Survey - boundary and topographic
  3. Architect/Residential Designer - provide building footprint
    1. Fire Sprinklers - need mechanical engineer to provide demand
      1. Lee Marx (lee@amfireman.com) Sprinkler Designer

Street Right of Way

City of Jerome Idaho

  • Jerome Idaho City Code - Title 16 Subdivision Regulations - 16.28.050 Streets
    • Residential Right of Way
      • Alley
      • Service road = 25 ft
      • Local street = 56 ft
      • Collector street = 64 ft
      • Arterial street = 80 ft
    • Commercial Right of Way
      • Alley
      • Service road = 25 ft
      • Local street = 60 ft
      • Collector street = 64 ft
      • Arterial street = 80 ft
    • Cul-de-sac Right of Way = 100 ft
      • Idaho Fire Code 2012 Edition, Appendix D - Fire Apparatus Access Roads - Section D103. Cul-de-sac 96 foot diameter

Outline

  • Surveying Objective - AutoCAD 2004 drawing that has the following
    • Contours as 3D polylines (not Civil 3D surface)
    • Survey points as AutoCAD blocks (not Civil 3D points)
    • GIS street centerline surrounding the project (not AutoCAD Map dataset)
    • GIS Assessor parcel (not AutoCAD Map dataset)
    • GIS Aerial photo (not Bing Maps)
    • Use Nevada East Zone Stateplane Coordinates, units feet
    • Architect - building footprint
  • Step 1 - ArcMap - add street centerline layer, select boundary, export to shapefile
  • Step 2 - ArcMap - add Assessor parcel geodatabase, select parcel, export to shapefile
  • Step 3 - Civil 3D - add subset of street centerline boundary shapefile
  • Step 4 - Civil 3D - add subset of Assessor parcel boundary shapefile
  • Step 5 - Civil 3D - add aerial photo
  • Step 6 - Civil 3D - Surveying - nearest benchmark point
  • Step 7 - Civil 3D - Surveying - import points
  • Step 8 - Civil 3D - Surveying - create existing surface and contours
  • Step 9 - Civil 3D - Proposed Surface Feature Lines
  • Step 10 - Revit - create building footprint
  • Step 11 - Revit - Site Plan
  • Step 12 - Revit - Publish Coordinates
  • Step 13 - Revit - Shared Coordinates.
  • Step 14 - Revit - export building footprint to Civil 3D
  • Step 15 - Civil 3D - assign finish floor elevation to building foot print
  • Step 16 - Civil 3D - grade site, create proposed surface
  • Step 17a - Civil 3D - finish drafting and plot
  • Step 17b - NavisWorks - export georeferenced building in Revit to NavisWorks (NWC). Note Revit does NOT create a geo-referenced FBX file. Then export to kml to display in Google Earth. InfraWorks cannot place the native Revit model using the geographic coordinates. Issues with Revit Plugin called Site Designer

Checklist

Notes

    • 1. Standard Note No. 1: The Owner, Site Developer, Contractor, and/or their authorized agents shall each day remove all sediment, mud, construction debris, or other potential pollutants that may have been discharged to, or accumulated in, the public rights of way of the ___(insert applicable jurisdiction) as a result of construction activities associated with this site development or construction project. Such materials shall be prevented from entering the storm sewer system.
    • 2. Standard Note No. 2: Additional construction site discharge best management practices may be required of the owner and his or her agents due to unforeseen erosion problems or if the submitted plan does not meet the performance standards specified in the (insert jurisdiction’s ordinance reference) and the Las Vegas Valley Construction Site BMP Guidance Manual.
    • 3. Standard Note No. 3: Temporary or permanent stabilization practices will be installed on disturbed areas as soon as practicable and no later than 14 days after the construction activity in that portion of the site has temporarily or permanently ceased. Some exceptions may apply; refer to the Nevada Stormwater General Permit for Construction Activity NVR100000, Section III.A.5.
    • 4. Standard Note No. 4: At a minimum, the Contractor or his agent shall inspect all disturbed areas, areas used for storage of materials and equipment that are exposed to precipitation, vehicle entrance and exit locations, and all BMPs weekly, and within 24 hours after any rain event of 0.5 inches or more. The Contractor or his agent shall update or modify the Stormwater Pollution Prevention Plan as necessary. Some exceptions to weekly inspections may apply, such as suspension of land disturbance activities. Refer to the Nevada Stormwater General Permit for Construction Activity NVR100000, Section III.A.12.
    • 5. Standard Note No. 5: Accumulated sediment in BMPs shall be removed within seven days after a stormwater runoff event or prior to the next anticipated storm event, whichever is earlier. Sediment must be removed when BMP design capacity has been reduced by 50 percent or more.
    • For more info, contact Brenden Scherr, 702-455-8990, bms@clarkcountynv.gov

Grading Plan Review Checklist - without Parcel Map

  • 2012 International Building Code (IBC) Amendments - Section J104.2 Grading plan requirements
  • Code Legend: Bldg Dept-2012 IBC
  • 01-00 Minimum Required Sheet Size: 24“x36”
  • 02-00 All sheets must be legible - must be reproducible in our electronic files
  • 03-00 Legend identifying CC approved Standard Symbols and Abbreviations
  • 04-00 North Arrow and Bar scale (on each sheet) 1“=60' Smallest
  • 05-24 Registered design professional/Engineer original seal (we seal), signature and date
  • 06-00 Date and expiration date of Engineer's stamp
  • 07-00 Engineer's name, address, phone number and fax
  • 08-00 Revision Box
  • 09-00 Project Name - address and location of property
  • 10-01 General vicinity of the proposed site and vicinity map
  • 11-02 Property line limits and accurate contours of existing ground and details of terrain and area drainage.
  • 12-03 Limiting dimensions, elevations or finish contours to be achieved by the grading…
  • 13-04 Location of any building or structures on the property where the work is to be performed and the location of any buildings or structures on land of adjacent owners that are within 100 feet of the property…
  • 14-05 Recommendations included in geotechnical and the engineering geology report…
  • 15-06 A statement that the site shall be graded in accordance with the approved geotechnical report…
  • 16-07 Locations of other existing topographic features whether natural or manmade such as streets, drainage structures, mapped faults, pavements, walls, etc. Existing condition of the streets (Paved/Gravel/Unimproved), Proposed driveway location(s) and elevations
  • 17-08 The cut to fill transition line (where no over-excavation is required)
  • 18-17 Details and cross sections at property lines with walls
  • 19-10 Details and cross sections of typical fill slopes and cut slopes
  • 20-18 Details and cross sections on slopes steeper than 5H:1V
  • 21-11 Elevation datum and benchmark as established by the NAVD88, Clark County benchmark
  • 22-12 Existing contours must extend at least 100 feet beyond the property lines
  • 23-13 Proposed finish contours or spot elevations at the property corners
  • 24-14 Elevation of curbs, crown elevation, or centerline of roads. Street names (Public or Private)
  • 25-15 Earthwork quantities in cubic yards
  • 26-16 Finish Floor Elevation
  • 27-19 Setback dimensions of cut and fill slopes from site boundaries
  • 28-00 Drainage Across Property Lines - concentrated drainage not allowed unless easement
  • 29-00 Location of fault lines and setbacks
  • 30-00 Base flood Elevation in Zone A, AE, AH, AO, reference FIRM or approved Drainage Study
    • visit RFCD FloodZone, enter the parcel number and get a report if parcel is located in flood zone
    • Clark County Regional Flood Control District - Flood View Report
  • 31-00 Limits of flood zones, reference FIRM Panel, Series and Date
    • Visit Clark County Regional Flood Control District - Flood View Advanced and determine the FEMA Panel number for the site, e.g. 2185
    • Visit RFCD Document Library ? Flood Insurance Rate Maps ? map2185.pdf and from the title block, find the Map Number 32003C2185F and Map Revised November 16, 2011 date.
    • Determine if parcel is located in Flood Zone as shown on Flood Insurance Rate Maps (FIRM)

GIS

Create Elevation Contours from LIght Detection And Ranging (Lidar)

  • Procedure

Obtain LiDAR data

  1. Source 1 - Obtain lidar data from craig.hale@snwa.com and judy.brandt@snwa.com at Southern Nevada Water Authority
    1. SNWA Metadata
    2. LiDAR dataset is in LAS 1.1 data format
    3. collected on 1 meter posting or 1.4 meter
    4. Bare Earth class are 2, 8, 25, and 26
    5. When creating contours use classess 8, 25 (roads and dark ground surface), and 26 (overpass). Note sure why the metadata doesn't include class 2 (bare earth)
    6. Data project in UTM Zone 11 North, WGS84 on the Ellipsoid
    7. Vertical projection is on the GRS80 ellipsoid.
  2. Source 2 - download the same data from USGS - National Map - Lidar Point Cloud
    1. USGS Metadata
    2. NAVD88 vertical datum (so are the elevations ellipsoid like SNWA or based on the Geoid model?)
    3. WGS_1984_UTM_Zone_11N
    4. USGS Lidar Metadata
  3. Background on LiDAR data
    1. when creating the clipping boundary, ESRI says it must be in the same projection as the dataset, so in this case Lidar data is in UTM, then clipping boundary also needs to be in UTM. The clip didn't work when I used Stateplane coordinates, so Surface Contour took 2 hours and created contours for all of Southern Nevada (also had wrong elevations). According to Margaret J. ESRI tech support, Surface Contour command doesn't honor the clip boundary when using Lidar dataset.
    2. How do you clip a Lidar dataset? According to Margaret J. ESRI tech support, need to first convert into a multipoint feature, then clip that.
    3. Classification Value = 2 Ground, see Working with LAS classification in ArcGIS
    4. ArcMap Lidar Properties - Filter

Convert LiDAR elevations from ellipsoid to Geoid heights

  1. NOAA Vertical Datum Transformation - vdatum.info@noaa.gov
    1. NOAA Vertical Datum Transformation Download VDatum (select vdatum_all_20141222.zip)
  2. edit E:\downloads\noaa.gov\vdatum\vdatum.bat
    1. edit the path on the last line to read
    2. “C:Program FilesJavajre1.8.0_65binjava.exe” -jar vdatum.jar
  3. LiDAR data is tiled by Assessor Book and Section number
    1. class_14008_prelim.las
    2. class_14009_prelim.las
    3. class_14016_prelim.las
    4. class_14017_prelim.las
  4. takes about 7 minutes for VDATUM to process one .las file
  5. contours are funky around the edges, so if project is close or straddles lidar boundary, then process both
  6. NOAA Vertical Datum

LAStools

  1. unzip file
  2. load LAStools in ArcToolbox (right click on ArcToolbox and select Add Toolbox…)
    1. E:downloads\rapidlasso.com\LAStools\ArcGIS_toolboxLAStools.tbx
  3. run las2las (filter)
  4. drop z values below 550 meters
    1. if this range is narrow, then will save time editing the contours, removing building elevations, trees, cars, etc which skew the topo. Recommend doing an iteration to find the highest and lowest elevations onsite and around it. Then use this value here in las2las.
    2. drop z values above 750 meters
    3. drop_classification 0, 1, 3, 4, 5, 6, 7, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24
    4. ArcToolbox las2las (filter)

Create LAS Dataset

  1. ArcToolbox > Data Management Tools > LAS Dataset > Create LAS Dataset
  2. Input Files - select the Results folder from the VDatum conversion
  3. Output LAS Dataset - (not stored in a file geodatabase)
  4. Coordinate System: WGS_1984_UTM_Zone_11N
    1. XY Coordinate System tab > Projected Coordinate Systems > UTM > WGS 1984 > Northern Hemisphere > WGS 1984 UTM Zone 11N
      1. Defaults to Custom Coordinate System: NAD83_UTM_zone_11N, units meters (I think this is wrong)
    2. Z Coordinate System > Vertical Coordinate Systems > North America > NAVD1988 (elevation in meters)
  5. check Compute Statistics
  6. check Store Relative Paths
  7. ArcToolbox Create LAS Dataset

Surface Contour in Feet

  1. Open ArcMap
  2. add LAS dataset (should already be done from previous create LAS dataset
  3. ArcToolbox > 3D Analyst Tools > Triangulated Surface > Surface Contour
    1. ArcToolbox Surface Contour with CLV Layer Names
  4. skip the following
  5. Table of Contents > right click on LAS dataset
  6. Filter tab > check classes 2, 8, 25, 26 (not included in every dataset)
  7. Symbology tab > remove outlyers (values less than 0 and greater than 1000)
    1. ArcMap LAS Layer Properties - Bogus Data

Project Contours to Stateplane Coordinates

  1. Need a file geodatabase to store the contours in
  2. ArcToolbox > Data Management Tools > Projections and Transformations > Project
    1. project from UTM to Stateplane coordinates
  3. Z Coordinate System tab > (NAVD88 feet)
    1. ArcToolbox Project Stateplane Coordinates

Smooth Contours

  1. ArcToolbox > Cartography Tools > Generalization > Smooth Line
  2. smoothing tolerance 50 feet
  3. Reference
  4. Create a file geodatabase to store surface contour data

LiDAR to Multipoint

  1. Need 3D Analyst Extension enabled (Customize > Extensions > check 3D Analyst)
  2. ArcToolbox > 3D Analyst Tools > Conversion > From File > LAS to Multipoint
    1. output feature class in a file geodatabase Lidar2010MultiPnt
    2. Average Point Spacing is 1 meter
    3. Input class codes 2, 8, 25, 26
    4. Input Return Values - check Any returns
    5. Coordinate System: leave blank, should be WGS_1984_UTM_Zone_11N
    6. Z Factor is 1
    7. takes about 1.5 hrs to run
    8. ArcToolbox LAS to Multipoint
    9. ArcToolbox LAS to Multipoint
  1. ArcCatalog > right click > New > LAS Dataset > SNWALidar2010.lasd
    1. NOTE: only works with raw LiDAR data. Doesn't work with ArcCatalog LAS Dataset (.lasd)
    2. LAS Dataset Properties > LAS Files tab > Folder > class_las
    3. XY Coordinate System tab > Projected Coordinate Systems > UTM > WGS 1984 > Northern Hemisphere > WGS 1984 UTM Zone 11N
    4. Z Coordinate System > Vertical Coordinate Systems > I don't know what to add here, I don't see GRS80, no mention in Metadata how to use GEOID03, best guess is Vertical Coordinate Systems > World > WGS1984
  2. Create file geodatabase, SNWAlidar2010fdb

Create IDW Surface

  1. ArcToolbox > 3D Analyst Tools > Raster Interpolation > IDW to convert Multipoint dataset into surface raster
    1. elevation Shape.Z
    2. cell size 3.28 ft
    3. ArcToolbox IDW

Generate Contours

  1. ArcToolbox > 3D Analyst Tools > Raster Surface > Contour
    1. Problem, appears elevation values are still in meters, not converted to feet (even when I set the Z coordinate in the project tab, it doesn't change the value)
    2. Input raster: IDW surface
    3. Output polyline features: file geodatabase
    4. Contour interval = 1
    5. Z Factor = 3.2808 (1 meter = 3.2808 feet)
  2. Compare values with GISMO 2003 5 foot contours values (E:gisdata\crgeo\shapefil\con5f03_l.shp)

Smooth Contours

  1. ArcToolbox > Cartography Tools > Generalization > Smooth Line
    1. smoothing tolerance 50 feet
  2. Reference
  3. Create a file geodatabase to store surface contour data

Export Contours to Shapefile

  1. con1f14017
  2. ArcToolbox > 3D Analyst Tools > Triangulated Surface > Surface Contour
    1. Use this to convert directly from LAS LiDAR to Contours. Problem is the dataset is too big, so don't recommend this step.
    2. turn off geoprocessing in the background, Geoprocessing > Geoprocessing Options > uncheck Enable Background Processing
    3. (skip - doesn't work with Lidar datasets) change the Environment > Processing Extent to a polygon boundary (e.g. G5 Medical offsite basin boundary/project limit)
    4. use Contour interval of 1 which is unitless (contours increase by 1), no need to enter units, such as 2 ft = 0.6096 meters

Export 1ft Contours

  • CLV layers
    • C-TOPO-MINR-N is Civil Topographic Contours Minor New
    • C-TOPO-MAJR-N is Civil Topographic Contours Major New
    • C-TOPO-MINR-E is Civil Topographic Contours Minor Existing
    • C-TOPO-MAJR-E is Civil Topographic Contours Major Existing

Export Aerial Image from ArcMap

  • Using GISMO aerial photos
  • Having problems with ArcMap 10.3 image export (right click on the image in the table of contents and select Data ? Export Data. Workaround:
    • 1. use Windows ? Image Analysis. Select the tif image then at the bottom of the window, click the Clip button. This saves the image in an AppData folder but in some unknown format.
    • 2. then click the Save button at the bottom right corner of the Image Analysis window (alternative in the table of contents, right click on the clipped image and export).
    • 3. Export Raster Data
      • Data Frame (Current)
      • Spatial Reference - Data Frame (Current)
      • Format: TIFF
      • Compression Type: NONE
    • 4. click No on output raster
      • ArcMap Export Raster
    • 5. Civil 3D
      • set spatial reference
      • current layer: VA-GIS, VA-IMG, IMAGE
      • MAPIINSERT (right click on image to change relative path)

Research Existing Improvement Plans - Offsites and Drainage Study

  • Clark County Building Department - Document Image Search Tool
    • Drainage Study (DS) 05-17297
    • Offsites 05-35708
  • Clark County OpenWeb to research Building Department images
    • OpenWeb Link to Building Department Records

Surveying

  • find nearest benchmark, e.g. No. 46, Station 4C02 21W6, NE corner of Lake Mead and Betty, near PC of Lake Mead, elevation 544.594 meters (1786.72 ft), see Township 20 Range 62 section 21
    • Chris Albers recommends GPS on 4 benchmarks around the site, minimum occupation of 20 minutes

Research Records

    That portion of the Southeast Quarter (SE 1/4) of the Northwest Quarter (NW 1/4) 
    of Section 21, Township 20 South, Range 62 East, M.D.M., described 
    as follows:
    
    COMMENCING at the Southwest corner of the Northwest Quarter (NW 1/4)
    of said Section 21;
    Thence North 89°45'48" East, along the South line thereof, a distance
    of 1675.04 feet to a point;
    Thence North 0°28'40" West, and parallel to the West line of the 
    Northwest Quarter (NW 1/4) of said Section 21, a distance of 914.00
    feet to the TRUE POINT OF BEGINNING;
    Thence North 0°28'40" West, a distance of 79 feet to a point;
    Thence North 89°45'48" East, a distance of 325 feet to a point;
    Thence South 0°28'40" East, a distance of 79 feet to a point;
    Thence South 89°45'48" West, a distance of 325 feet to the TRUE 
    POINT OF BEGINNING.
  

Field Survey

  • Equipment to bring
  1. Clothing
    1. hat
    2. long sleeve shirt with front pocket for cell phone
    3. work boots
    4. safety vest
  2. Equipment
    1. Field book
    2. Pencil
    3. Automatic Level
    4. Level/Philly Rod
  3. Equipment Bag
    1. Hammer
    2. Orange Paint
    3. Cordless Drill
    4. Nails and washers
  4. Water and Food

Adjusting GPS and Benchmarks

  • Problem - I have two different elevations, one from GPS using the Geoid and the other County published Benchmark. Using TBC, how do I adjust all the GPS data so it uses the benchmark elevations?

Trimble Business Center

AutoCAD Civil 3D

  • Remember, Civil3D can only import a points file saved in ANSI/ASCII text file, so either Excel or TBC exports the points file in another format UTF. I had to use UltraEdit to open the file, then Save As ANSI/ASCII then Civil 3D would import the points file.
  • Remember, AutoCAD doesn't understand Civil 3D points, so need to convert to blocks

Step 3 Civil 3D - add subset of street centerline boundary shapefile

    • OPTIONS > Profiles tab > CLV2014.C3D > Set Current
    • NEW
    • should have layers like VS-CL and V-ANNO-LBL
  • assign coordinate system
    • Application Menu > Drawing Utilities > Drawing Settings
    • Units and Zone tab > USA, Nevada category
      • NAD83 NCRS, Las Vegas Zone, US Foot
        • Selected coordinate system code: NV83.NCRS-LVF
      • NV83-EF coordinate system (old GIS data)
      • AutoCAD Civil 3D Drawing Settings
  • MAPIMPORT shapefiles
    • Field Heading - Drawing Layer = VS-CL
    • Field Heading - Data = Create object data, then Select Fields, uncheck everything but STRNAME field
    • AutoCAD Civil 3D Map Import
  • Zoom Extent (Z E or ZE)
  • verify street centerlines should be assigned to VS-CL layer
  • Modelspace Annotation Scale, change from 1”=1' to 1“=100'
  • make V-ANNO-LBL layer current
  • Annotate Tab > Text Style CLV-Bold.10
  • MTEXT the street name, need to have a better solution to add annotation
    • Clark County GIS - OpenWeb Application - Streets Surrounding Site
    • Civil 3D Label Street Names Surrounding the Site
  • Optionally Add Aerial Photos
    • add Bing Maps (just a rough overlay, better if we done GPS survey)
    • use MAPIINSERT to import GIS Aerial Photos
    • Layer
      • VA-GIS
      • VA-IMG
      • IMAGE

Step 4 Civil 3D Import Parcel

  • GIS Assessor Parcel Layer
    • V-PROP-PRCL-GIS
    • VI-PROP-PRCL
    • PARCEL
  • MAPIMPORT
    • Drawing Layer = V-PROP-BNDY-GIS
    • Data = APN (uncheck everything else)
  • check on Import polygons as closed polylines
  • MTEXT parcel number and owner name
  • Save As step04ImportParcel.dwg and close
  • optionally - save as AutoCAD 2004 and give to Clair/Josh

Step 5 Civil 3D Create Existing Surface

Step 6 Civil 3D Create Proposed Surface

  1. Determine the existing elevation of the street centerline at the center of the building footprint. Say this elevation is 1900 ft. Then the Finish Floor (FF) Elevation will be 18 inches above that, so FF = 1901.50 ft.
  2. Create a feature line of the building footprint and assign the FF elevation
  3. Determine lot drainage
    1. RFCD Typical Lot Drainage
    2. A, B, C Lot Drainage
    1. Lot Drainage

Cleanup DWG

  • PURGE - remove unused blocks
  • UCS - delete any named coordinate systems

Step 8 Revit - create building footprint

  • Create building footprint in Revit, doesn't matter where its located
  • Create driveway
  • Save (01BasicBldg.rvt) and close.
  • New Project based on Residential template, save as Step09LinkCAD.rvt
  • Project Browser > Site Plan (double click to activate)
  • Insert > Link CAD then select the site plan drawing from Civil 3D
    • Revit Link CAD
  • ZA Zoom All
  • VG Visibility Graphic > Site > check on Survey Point (will turn on Project Base Point later)
  • move Survey Point to corner of lot with pin/clip (paperclip icon) state off (red diagonal line through the paperclip)
  • Manage > Project Location panel > Coordinates > Acquire Coordinates (then select DWG parcel boundary)
  • VG Visibility Graphic ? Site ? check on Project Base Point
  • move Project Base Point to a corner of the lot (unsure if clip state should be on or off)
  • Save As SitePlan.rvt
  • select site boundary
  • Properties > Shared Site > DefaultLocation
  • Record current position as DefaultLocation > Change > Duplicate > Name = SiteCoords
  • Revit Select Site

Step 10 Revit - Publish Coordinates

  • Insert > Link Revit - to link in building footprint (.rvt) into the civil engineering site (.rvt)
  • position building using Move and Rotate
  • with building footprint still selected, Properties ? Shared Site ? Publish the current shared coordinate system…
  • Change to SiteCoords > Reconcile
  • Save
  • Revit Coordinates/Origin Point
    • Relative/Project Internal Coordinates - center/middle of the screen from the intersection of the 4 elevation symbols, can export to DWG using this coordinate, but why?
    • Project (circle with X icon)- can NOT export to DWG using this coordinate
    • Survey/Shared Coordinates (triangle with dot icon) - can export to DWG using this coordinate (this is what we want)
    • Not Shared, Publish or Acquire (use this, acquire from Civil 3D)

Step 11 Revit - Shared Coordinates

  • Link Revit - insert the building footprint onto the site plan. Move and rotate the building to fit on the site. Then Publish coordinates from Site to Building Footprint. VG turn on Project location and move on to the site. Save the file.
    • Revit Shared Coordinate

Step 12 Revit - export building footprint to Civil 3D

  • Open Building Footprint
  • Application Menu > Export > CAD Formats > DWG
  • Select Export Setup click the … button
  • Units & Coordinates tab > Foot
  • Units & Coordinates tab > Coordinate system basis = Shared
  • Revit Export to DWG using the Survey/Shared Coordinate

Step 13b Navisworks

Electronic Submittal

Clark County Building Department - Fire Prevention

  • 4701 W Russell Rd, Las Vegas NV 89118, 702-455-7100, permits@clarkcountynv.gov
    • Fulton R. Cochran, Assistant Fire Chief, fulton.cochran@clarkcountynv.gov, 702-455-7062 (final say on fire plans review)
    • Kevin O. Hoyt, Fire Plans Checker, kevin.hoyt@clarkcountynv.gov, 702-455-7101, Cell 702-281-3755
    • Edward J. Kaminski, PE, Fire Protection Engineer, ekaminski@clarkcountynv.gov, 702-455-7130 (575 E Flamingo Rd)
    • Craig A. Meyers, Plans Checker, cmeyers@clarkcountynv.gov, 702-455-7128 (575 E Flamingo Rd)
  • Fire Department Plan Submittal is for Contractors, Civil Engineering plans which require mylar signatures must be submitted hard copies.
  • Track Plan Review Status Online
    • Plan Review Status (left side of screen in brown box)
    • Enter application number
    • Plan tracking status ? FD PLAN TRACKING
      • IN FEE VERIFICATION - means reviewed
      • READY FOR PICK-UP - means approved/corrections sent
      • VIEW APPLICATION FEES to see if any money is owed
    • Clark County Permits Inspections Electronic Reviews - Fire Prevention Electronic Plan Review
    • Clark County Permits Inspections Electronic Reviews - ProjectDox Invitation
    • Review Coordinator's Email: ddspdplansexam@co.clark.nv.us
    • Submittal Coordinator's Email: dspdsubmittal@co.clark.nv.us
    • Tech Support's Email: TechSystemsSupport@co.clark.nv.us
    • Clark County Permits Inspections Electronic Reviews - ProjectDox Invitation Page 2

GFive Medical

  • PAC# 15-41871
  • HTE# 15-65114 Civil Improvement Plans (Fire Dept) <strike>15-64776</strike>
  • Address: 3071 N Nellis Blvd
  • Parcel: 140-17-501-011
  • Land ID: 000079839
  • Name: null
  • General Location:
    • Application Type (Cheatsheet)
      • FDSR - Automatic Fire Sprinkler Systems - New System Construction (<I>FD AUTO FIRE SPRINKLER SYS CONSTRUCTION</I>)
      • FSPC - Fire Lane/Access Plan (<I>FD FIRE LANE ACCESS, GENERAL PLAN</I>)
    • Total Estimated Value: $291,000
    • Total Square Footage: 8555 ft2
    • Tenant Unit Number: null
    • Tenant Name: GFIVE
    • Notes: Enter detailed Description of Work: Warehouse-new
    • checkbox: I will be submitting plans electronically
  • Electronic Stamps and Signature - must be inserted as JPEG image,

City of North Las Vegas

City of Las Vegas - Public Works

  • Flood Control
    • Oh Sung 702-229-1815
    • Peter Jackson 702-229-5266, pjackson@lasvegasnevada.gov
    • Albert Sung, ysung@lasvegasnevada.gov

Las Vegas Valley Water District (LVVWD)

    • Click Yes if you want HGL
      • Nass at 702-259-8173 does the HGL requests
      • Lowest topo elevation and Highest topo elevation (not elevation/height of the building fixtures)
    • Click No on My Application if you just want to submit a water plan .dwf
  • Open Monday-Thursday (702-258-3165)
    • Engineering Services Division
      • Michael A. Dishari, PE, Senior Civil Engineer, Michael.Dishari@lvvwd.com Engineer 702-258-3171
      • Phillip Orme, Engineering Plans Examiner II, phillip.orme@lvvwd.com, 702-258-3893
      • Raquelle Felsing (raquelle.felsing@lvvwd.com), 702-258-3165, raquelle.felsing@lvvwd.com is the lady who answers the phone and can give some information
      • Aalison Moore 702-822-8402, aalison.moore@lvvwd.com can upload plans to the Digital Plan System (DPS)
    • Jonathan Pickus, Senior Manager, Information Technologies, jon.pickus@lvvwd.com, 702-259-8224
    • J. Russ Coffey, Principal GIS Analyst, Engineering Technology Support Division, russ.coffey@lvvwd.com, 702-691-5292. Can only provide GIS data to Engineering Services Division, so I guess they can then give it to me.
  • Need to obtain the water plan for 10 E Charleston, APN 162-03-110-074, E-Tech Construction & Development, Inc, 1115 S Casino Center Blvd, Suite #3, Las Vegas NV 89104.
    • 5/8” water line, being required to add RPPA for domestic water use
    • existing DC 6“ fire line, being required to upgrade to RPDA
    • mainline in the alley is 8” PVC
    • HGL request - lowest elevation 2032 and highest elevation 2033 (is this the topo elevation or the proposed fixtures?

Water Reclamation District

Post Construction Certification

References

Navigation

Civil Engineering Engineering - Computer Engineering - Electrical Mechanical Engineering

Print/export
QR Code
QR Code engineer-civil:gradingplan (generated for current page)