LiDAR Team

Demetrio Gonzales

Anh Nguyen

Mike Rosell

Loaded the provided file (scan of SSB under construction from last term)
Performed Target Base Registration (Sphere’s diameter 72.5mm) – large residual error
Obtained the Georeferencing registered file from Christian – smaller error of 0.02
Segmentation – trial run by focused on selected section of the building à exported as .las file
Attempted to run the .las file using Recap – unsuccessful
Directly imported the file into Revit to construct the 3D model – not as clear
Familiarized with the Visualization and Reality Model software LumenRT – watched tutorial video on YouTube

The goal of the LiDAR team is to gather the raw field spatial data, so that it can be transformed and organized into useful data for the BIM team and, ultimately, the end user. We have been tasked with the initial field scan, point cloud registration, georeferencing, and upload of all gathered information to the [PROGRAM HERE] modeling program for final presentation.

The very first step needed in the process was to practice registration and georeferenced on the Trimble Real Work program. The team utilized scans that were taken, of the student center, before completion of the product. It was a very useful learning experience as it allowed the group to practice without fear of making a mistake with the final scan data; As well as determine what parts of the process could have errors and mistakes.

Field work was the next necessary step in our project. In order to get a complete scan of the new student center without over engineering the problem, we were careful of our scanner and target placement. Areas with large lines of sight were the best position for our scanner, as well areas with higher elevation. This allowed the group to scan the maximum amount of area possible. We positioned [TYPE OF TARGET] targets around the area, these targets would be useful for our registration processes later. Our field work was performed in conjunction with the drone group on the same day, so we were able to coordinate our data and workloads better than if we had gone on separate occasions. All safety precautions for onsite field work were followed and we were able to finish the job while keeping everyone safe.

The registration of our final data scan differed in ways from our original practice material. A few new trials were encountered as the practice data was registered using a manual point registration and a few target registrations. This final data registration was all target based. Despite some mild setbacks it was agreed upon that, overall, the target-based registration was far more efficient and reliable than manual point registration. To register the targets all we needed was the target type and the dimensions of the target. Using this data, the program was able to pick out which targets were the same between different scans and match them together automatically. Even with a confidence in the system our group took the time to manually review each scan to see if there was any drift detected between the two-point clouds. These checks were easiest to do by looking at each target and seeing if there were any ‘ghost’ targets, which is when it appears there are two overlapping targets rather than one single one; This lets the team know if the scans have drifted apart from each other between registrations. After correcting a few mistakes, the group had an accurate point cloud model of the student center.

Georeferencing the registered scans was made much easier with the targets we had set up. Utilizing the height of the targets as well as the height of the points we had placed them on, the group was able to pinpoint the exact elevation of the point cloud. Similarly, using the coordinates of all the targets the point clout was able to rotate nicely to fit the real-world coordinates.

Our registered and georeferenced point cloud was then exported from Trimble Real Work to [PROGRAM] for modeling and detailing. This final product would be used for presentations and submittal to the end user.

UAV Photogrammetry/ Field Work Team

Sergio Najera

Jorge Mercado

Christian Emerett

UAV

At the beginning of any UAV project, the first step is to make certain that you have the clearance to fly in the area that the site is located. By viewing a VFR map (http://vfrmap.com/) provided by the Federal Aviation Administration (FAA) it is possible to determine what airspace locations fall under. Cal Poly Pomona falls under a Class D airspace which restricts flights from surface to 2,700 feet above ground level (AGL). The control tower in charge of this airspace is Brackett Airport which has given clearance to the university for research projects including UAV’s. Therefore we contacted Michael DeSalvio (M.Bt, RBP, RSO Manager, Environmental Health and Safety Strategic Enterprise Risk Management) who is in charge of granting permission from the UAV flight on campus. The request was given to him on the 5th of November for the dates 11/30/18, 12/08/18, and 12/17/18 to fly and collect the data required to create the 3D model.

Next a plan must be formed in order to be prepared on how to collect the photos to create the 3D model accurately. Using google earth we established a proposed set of aerial targets that we can use for both controlling our model as well as checking its accuracy. But this was only proposed a walk-through of the site in its current conditions was performed on October 9th , 2018 where true locations of the aerial targets were determined to best control the model as well as provide control to be used for our scanning portion of the project.

Once the control had been established, we continued to press forward with creating a flight plan based on the area of the site and the heights of the buildings surrounding the area using the program Drone Deploy. Due to limitations of flight to 400 feet AGL and the height of the CLA building, adjustments had to be made to the flight plan in order to not get too close to this building and not exceed our height limitation. The first flight will be at 200 ft AGL with the camera at Nadir (90 degrees) and will consists of 271 images for a total time of 15.03 mins. The second flight which will capture the sides of the building to best model it overall will be a hatched flight path at 100 ft AGL at an oblique angle of 65 degrees consisting of 211 images and a total time of 12.24 mins.

Field Work

First step of field work began with the reconnaissance of the site and planning on where to have control for both the UAV as well as the terrestrial scanner. We then planned a day to have everyone become more familiar with the equipment we will be using which include the Trimble TSC3 Handhelds, Trimble R10 GNSS Base/Rover Receivers, as well as a 2-meter rod and bi-pod. With the plan on placement for the aerial targets in place, we are now able to break into teams and distribute the control plot to the team leaders. We will be utilizing 4 receivers as rovers, and 2 as stationary bases, all collecting data through fast static (post-processing kinematics) for a minimum of 20 minutes at each control point. This will allow us to collect enough data for accuracy as well as any editing that must be made in the post-processing procedure where we will also tie in CORS.

Website Team

Lee Thao

Eric Hermoso

The website team began by reviewing website templates from previous Senior Projects. The tabs included: Home, About Us, Preliminary Engineering, Field Survey, Design Alternatives, Staging and Cost, and Report. The team decided to use Wix.com since the website editor was free and the tools were straight forward.

Eric created an account on Wix.com and quickly set up the template. He added all tabs and text boxes where it was appropriate. Then he researched other website templates and considered integrating a interactive visual. He is currently working on programming a script to allow for these applications.

Lee updated the Cal Poly logo and gathered images of the new Student Building to be added into the Homepage gallery. Then she summarized and updated the scope and project description. She also organized the “About Us” page and collaborated with Christian to produce an overview of the preliminary engineering. Lee later reached out to the group for personal statements.

Right now, the interactive point cloud interface is still being decided whether which web graphics library (WebGL) platform should be used Potree or Sketchfab. Sketchfab enables viewers to move freely around or inside the 3D scene. The issue with Sketchfab is that there is a limit of 500MB of space that can be used for free. If planed to use more than 500MB then a payment plan must be required. Sketchfab does not provide tools for users to analyze a 3d model when they want to gather information from a specific object. Potree is a free open source WebGl based point cloud renderer for large point clouds. It allows users to interact and analyze information and at the same time download the files. These two WebGL are still being tested out to see which one provides better quality information.

Potree has a hard time rendering points because the amount of points. It is still not known why it gives distorted points. Proper modifications were made for the point cloud file; two software were used to change the point density in order to make the points clear and visible. RECAP and Trimble Real Works allowed to make these modifications and then it was uploaded to Potree. The results looked promising but there is still some modification that need to be done.

BIM Team

Nathan Barnett

Ray Yzaguirre

Nick Furr

As the BIM group, we were tasked with creating a 3D model of a portion of the new student services building at Cal Poly Pomona. The model must incorporate a wide variety of features of the building, including main structural features and utility lines. The model will then be cross-compared with data of the building from our 3D backpack scan and UAV survey of the building.

To begin the semester, we had to choose our modeling computer program. Autodesk Revit was selected as our program, due to its popularity of use as a modeling software in industry and its convenience of access on campus. Our next step was to familiarize ourselves with the construction plans and choose an area of the building that would be best to model. As a group, we chose the Northwest corner of the Western “Maple Bar” portion of the two buildings. The portion of the building is two stories and contains a wide variety of rooms, including a multipurpose room, copy and work room, mechanical room, plumbing room, storage room, and a kitchen. The wide variety of room types ensures a building sample which encompasses most main features of the building; including HVAC, electrical, plumbing, and structural components. The portion of the building also contains a curved exterior building face and staircase, a challenge for us as a group and a unique visual addition to the BIM model. After the building portion was selected, we further compiled all plans relevant to our portion of the building. We have about 40 plan pages compiled relevant to our portion of the project. However, at this point we were left with some questions about the plans and building, mostly with regard to missing dimensions in the plans. A solution for this was when our class took a field trip to the services building construction site for preliminary evaluation. Here we addressed any general questions correlating with the completion of the model we had with the project manager at the site. We also took a few dimensions of the building with a tape measure, and took pictures to have as a reference for creating our BIM model. Most other work has been done on the Revit computer program. As a group, no members have used Revit prior to the project. Some time in the quarter was put forth in training for Revit. So far, a large portion of both floors of the chosen section of the building has been modeled. Attached are a few screenshots for reference of our progress. For the future, we plan to complete our Revit model with more detail, as well as complete a LumenRT model for visual purposes. Work has begun with completing our LumenRT model, however more is to be done as we do not currently have access to the computer power or necessary LumenRT add-ons due to campus restrictions. We have begun to address this with campus IT.