Notifications
Clear all

All data, except text and hatching, shall be 3D with true x, y, and z coordinates

16 Posts
9 Users
0 Reactions
28 Views
(@totalsurv)
Posts: 797
Registered
Topic starter
 

"All data, except text and hatching, shall be 3D with true x, y, and z coordinates"

This was included as part of a topographic survey specification. I normally wouldn't have all objects in 3D like this. Is this something anybody does?

 
Posted : 17/10/2018 1:42 pm
(@leegreen)
Posts: 2195
Customer
 

Yes, I have been doing this Microstation for 25 years.

 
Posted : 17/10/2018 2:03 pm
(@thebionicman)
Posts: 4437
Customer
 

In Civil3D you can access the more powerful functions if you draft in 3D. It can be a pain for a boundary surveyor but pays big dividends for engineers teamed with modern construction firms.

 
Posted : 17/10/2018 2:55 pm
(@peter-ehlert)
Posts: 2951
 

we used 3D line work on most everything (boundary included) more than 20 years ago.
Originally I think it was because of a Navy contract requirement, we ended up adopting it company wide after we became acclimated.

 
Posted : 17/10/2018 3:42 pm
(@totalsurv)
Posts: 797
Registered
Topic starter
 
Posted by: leegreen

Yes, I have been doing this Microstation for 25 years.

Can I ask how you deal with reflector-less shots which may have been shot for example midway up a power pole. Do you adjust them on to the level of the surface model?

Also do you then measure all walls?ÿand building lines with the prism pole at the base of the wall rather than any reflector-less shots?

?ÿ

 
Posted : 17/10/2018 11:27 pm
(@totalsurv)
Posts: 797
Registered
Topic starter
 
Posted by: Peter Ehlert

we used 3D line work on most everything (boundary included) more than 20 years ago.
Originally I think it was because of a Navy contract requirement, we ended up adopting it company wide after we became acclimated.

It's not just line work they are looking for it is everything.

 
Posted : 17/10/2018 11:29 pm
(@chris-mills)
Posts: 718
Registered
 

It all depends on the client and what they understand by 3D.

Take it exactly as it is stated and the survey is a full scan point cloud. Most clients seem to mean that there aren't any 2D points, so shots such as the reflectorless half way up a pole need to be adjusted to the bottom (with a top as well, perhaps). We have, on occasion, created all the walls and columns as 3D facets within a building - as requested - only to find the client comes back and says it is too difficult to handle, can we do something simpler.

 
Posted : 17/10/2018 11:38 pm
(@leegreen)
Posts: 2195
Customer
 
Posted by: Totalsurv
Posted by: leegreen

Yes, I have been doing this Microstation for 25 years.

Can I ask how you deal with reflector-less shots which may have been shot for example midway up a power pole. Do you adjust them on to the level of the surface model?

Also do you then measure all walls?ÿand building lines with the prism pole at the base of the wall rather than any reflector-less shots?

?ÿ

With reflectorless shots on a pole, you would have locate it at ground level or adjust the rod height. DOT's often want all topo features in 3d., and at the correct location. They need this data for an accurate cost estimate of removals and design. With data collectors today, this really is not as hard as you think. Just always be aware of your rod height. If there is a point that does not have an accurate elevation, InRoads has a code DNC (Do not Contour) that is added after the code.?ÿ We create separate?ÿDGN files for text and boundary that are 2d reference files.

?ÿ

Is your deliverable?ÿin DGN or DWG??ÿ It appears this may be more challenging?ÿfor DWG users.

 
Posted : 18/10/2018 1:19 am
(@totalsurv)
Posts: 797
Registered
Topic starter
 

Is your deliverable?ÿin DGN or DWG??ÿ It appears this may be more challenging?ÿfor DWG users.

It would be DWG deliverable. What about building lines do you just move everything to floor level?

 
Posted : 18/10/2018 2:42 am
(@leegreen)
Posts: 2195
Customer
 

No, you will shoot only a first-floor elevation at the door entrance. The building footprint will have the elevation of the ground around the perimeter.

 
Posted : 18/10/2018 3:19 am
(@chris-mills)
Posts: 718
Registered
 

We normally put an plan offset onto the ground floor threshold level, to throw it inside the building - that way there isn't any doubt that it is intended to be the floor and not the external ground.

We also tend to give a ridge and eaves level to the roof, when appropriate.

 
Posted : 18/10/2018 4:00 am
(@mvanhank222)
Posts: 374
Registered
 
Posted by: leegreen

No, you will shoot only a first-floor elevation at the door entrance. The building footprint will have the elevation of the ground around the perimeter.

I agree I create a code for the building to shoot reflectorless and a code to shoot the adjacent ground elevations.?ÿ

 
Posted : 18/10/2018 5:04 am
(@rasmussenls)
Posts: 33
Registered
 

This thread is all great information. Thanks!! Most often, good communication with the client helps understand why they are asking for this information and the goal being to provide them with the information that will make their job run efficiently. I might humbly ask why they need "all data...3D" for my own understanding... (are they using the data to create a TIN? are they asking for a TIN? as leegreen mentioned with the DOT...) Anyway, my 2cents 😀

 
Posted : 18/10/2018 5:42 am
(@totalsurv)
Posts: 797
Registered
Topic starter
 
Posted by: RasmussenLS

I might humbly ask why they need "all data...3D"

To make my life more difficult I imagine.

 
Posted : 18/10/2018 11:20 am
(@wa-id-surveyor)
Posts: 909
Registered
 

This is pretty much how all our topo work is completed for the past few years.?ÿ All in DWG format.?ÿ Its great for the end users, or so i hear.?ÿ Its not hard at the survey level but does get complicated if you're not accustomed to data in this state.?ÿ The replace Z value with current elevation toggle is the key when making inquiries on the data.?ÿ?ÿ

 
Posted : 18/10/2018 11:39 am
Page 1 / 2