Please be kindly noted that Gallery will be under scheduled maintenance on Thursday, June 21st UTC 4am-6am.During the time system will not be available,thanks for your understanding and support.

×

Please be kindly noted that Gallery will be under scheduled maintenance on Thursday, June 21st UTC 4am-6am.During the time system will not be available,thanks for your understanding and support.

×

Another Bridge Proposal

Another Bridge Proposal

  • Recap-pointcloud-3500-3500

    ReCAP PointCloud.JPG

    378.0KB

    2017/07/13

  • Pintcloudmesh-3500-3500

    PintCloudMesh.JPG

    351.0KB

    2017/07/13

  • General-view-3500-3500

    General View.jpg

    4787.0KB

    2017/07/13

  • Civil3d-analysis-3500-3500

    Civil3D Analysis.JPG

    267.0KB

    2017/07/13

  • Bridge-175-ft-span-03-3500-3500

    Bridge 175 ft span 03.jpg

    2919.0KB

    2017/07/13

  • Bridge-80-ft-span-3500-3500

    Bridge 80 ft span.jpg

    6560.0KB

    2017/07/13

  • Bridge-80-ft-span-02-3500-3500

    Bridge 80 ft span 02.jpg

    5138.0KB

    2017/07/13

  • 23-ft-envelop-02-3500-3500

    23 ft Envelop 02.jpg

    16713.0KB

    2017/07/13

  • 23-ft-envelop-01-3500-3500

    23 ft Envelop 01.jpg

    8296.0KB

    2017/07/13

Description

A bridge proposal over a railroad, for preliminary approach, to justify the need to raise the structure profile.

Comments
X176

Great practical application of InfraWorks AND the use of drones. Thanks for sharing Oscar!

about 2 years ago
X120

Thank you!... You are now asking some serious questions:

- were your fotos GPS tagged by your camera or not?
YES
- If yes, your model should already be geo-located by Pix 4D wouldn't it?
Correct, for this particular flyover we used Pix4D mapper, but you can use any other application such as Drone Deploy, Skycatch, Site Scan, etc. All of which will give you GPS referenced images attached to a default coordinate system.
- If not, how did you georeference the model?
Depending on the scope of what you are trying to achieve, you need a camera with GPS in order to locate your images to a fixed known point. If you don’t have one, then you need to define Ground Control Points prior to flying, and then use those GCP’s to reference your images after they have gone the preliminary processing part within the software you are using for this purpose.
- In both cases, did you get a grip on the project geo-accuracy or did you use additional reference points, measured on-site?
For this case we use the default coordinates and make the proper transformation to our local coordinate system and units system, as this is a preliminary approach. For more precision/accuracy we define GCP’s on the ground, reference to known BM’s and CP’s, and then we correlate our collected data to all this reference points. Be very careful with your verticals though! And choose wisely the software to use, this is crucial for the efficiency of these workflows.

about 2 years ago
X120

Very cool - kudos!
Some additional questions;
- were your fotos GPS tagged by your camera or not?
- If yes, your model should already be geo-located by Pix 4D wouldn't it?
- If not, how did you georeference the model?
- In both cases, did you get a grip on the project geo-accurracy or did you use additional reference points, measured on-site?

about 2 years ago
X120

Yes Sir, I used a Phantom 4, manual flying as we had to comply with FAA regulations for this particular location, and then I processed the data in Pix 4D and after that we converted the .las file into a .rcp file for easy use into Autodesk products, in this case Infraworks. Some analysis for the profile was done in Civil 3D as well.

about 2 years ago
X120

Hi Oscar, did you use a drone to film the scene and then convert that into a 3D model?

about 2 years ago
X120
Oscar Castaneda
Winter Springs, Florida, United States of America

The license and other terms for contributing and using assets in the Autodesk Gallery are found in theAutodesk Terms of Use.

Statistics

  • 1.6 K
  • 5
  • 5
Industries

Categories

Products

Autodesk Online Gallery

© 2014 Autodesk, Inc. All rights reserved.

All use of this Service is subject to the terms and conditions of the applicable Autodesk terms of service accepted upon access of this Service.

This Service may incorporate or use background Autodesk technology components. For information about these components, click here: http://www.autodesk.com/cloud-platform-components

Trademarks

Autodesk, the Autodesk logo, and Fusion 360 are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates.

All other brand names, product names or trademarks belong to their respective holders.

Third-Party Software Credits and Attributions

Ruby gems is Copyright (c) Chad Fowler, Rich Kilmer, Jim Weirich and others. Portions copyright (c) Engine Yard and Andre Arko

bootstrap-select.js is Copyright (C) 2013 bootstrap-select

Backbone.js is Copyright (c) 2010-2013 Jeremy Ashkenas, DocumentCloud

Apple-Style Flip Counter is Copyright (c) 2010 Chris Nanney

imagesLoaded is Copyright © 2013 David DeSandro

jQuery is Copyright 2013 jQuery Foundation and other contributors http://jquery.com/

jQuery timepicker addon is Copyright (c) 2013 Trent Richardson

jQuery ColorBox is Copyright (c) 2013 Jack Moore

jQuery.gritter is Copyright (c) 2013 Jordan Boesch

Masonry is Copyright (c) 2013 David DeSandro

Underscore is Copyright (c) 2009-2013 Jeremy Ashkenas, DocumentCloud and Investigative

Reporters & Editors

underscore_string is Copyright (c) 2011 Esa-Matti Suuronen esa-matti@suuronen.org

Icanhaz.js is ICanHaz.js is Copyright (c) 2010 Henrik Joreteg (Mustache and Mustache.js are Copyright (c) 2009 Chris Wanstrath (Ruby) and Copyright (c) 2010 Jan Lehnardt (JavaScript) respectively)

Calendario is Copyright (c) Codrops 2014 by tympanus

All the above software components are licensed under the MIT license.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


Portions relating to lightbox are licensed under Creative Commons Attribution 2.5 License (http://creativecommons.org/licenses/by/2.5/). Lightbox was authored by Lokesh Dhakar (lokeshdhakar.com).