-
January 9, 2024 at 10:28 am
Seems an odd response from Trimble. They could satisfy both your need and the other clients need by making the warning of duplicate points a setting that can be turned on or off. Certainly not difficult programming to implement.
-
January 9, 2024 at 10:44 am
It does have a duplicate point warning if the points are in a job already. However if you are linked to a job say a csv file then it doesn’t warn you. I like linking more than importing because importing brings in unnecessary points back at the office and is no fun to deal with. Linking allows only what you use to come in makes for a cleaner experience managing a project that’s large and ongoing better."
-
==============================================================
-
Trying to reply to both of you at the same time. There is a setting for the warning, but it doesn't affect points stored in staking. It will always warn me if I'm just in measure, but not for staked and stored points.
-
In this case they weren't linked, but just imported csv's. Linking definitely has its advantages, but at the time it had caused some other kind of new issues for us, I can't remember what it specifically was as it was well over a year ago now. Nowadays if I'm not getting a new upload, but still want to use everything in the previous job, I will export a csv of the the previous one and start a new job with the current date and import the csv I created. This makes it so the office doesn't have to process data from several visits.
"They probably use a suffix to use notepad find and replace before going into cad. Much easier and a space is not an issue. Now if you bring the data back into tbc you can remember them.
That's a definite maybe, but not sure. I just know at one time I called some control points I set CP1213 (just for an example, a PK I set in between a lot 12 and 13), and I was asked to go with for example 1213CP instead, so all my permanent control has CP as a suffix. It doesn't appear that they ever change the numbers on my staked and stored points though, because a few new uploads later and they're coming in with the new CSV. It creates a bit of bloat, but I never know when I might be short on options and need to set up on, or check to a nail I set for footings a while back that they never got around to forming yet.
Also another way to auto handle this is to add a constant. So your comped point 248 gets 1000 added so now it’s 1248. So no alpha characters.
We do that in other cases, but it uses up numbers that could potentially be accidentally used again (same reason you suggested the prefix). Usually it's when a house needs to be recalced for whatever reason, my PM might do it in the office and then send me a new CSV with the original calc numbers but with a 1 in front of it, exactly like your example above.
I personally like alph it allows the crews to identify what they are staking. So in the code of comped point I might have 5’ O/S TBC the comped point name is TBC100. Or like one job we had a lot of info to mark on a stake and the crew chief wanted it so the helper could start marking the stake up as he narrowed in. So every point computed had the offset distance from centerline like 143.21_100. Then once he accepted he could read cut fill station and a bunch of other stuff easily to his helper. Now I had to do that after the fact for him as it was all done by someone else originally. But it took me just 15 minutes for 60 points. Normally I would have given him a layout road and a list of stations and offsets he needed vs points. You can have the code automatically switch to point name and a few other ways in access.
Around here we don't typically have to do a lot of stationing or offsets. Typically wood stakes are either set for a 4' O/S from building corner, just for the excavator to dig the basement. A single cut stake with cut from the top of the stake to the grade of the proposed underside of footing. Then we return to put nails in the ground for footings and depending on builder, we often have to come back and put nails on the footings for the walls. Suffix S for staking, P for pinning, N for nails on footings. Then a new set of numbers for the as built/final survey.
<b style="background-color: var(--bb-content-background-color); font-family: inherit; font-size: inherit; color: var(--bb-body-text-color);">Lots of ways to skin that cat. It’s really about finding the best way for field and office is all. I try and not get to worked up on my end honestly I prefer to work with the crews to make it easier on them and make sense to them.
Yeah I agree 100%. We aren't told exactly how to do anything, unless the way we do it ends up causing a problem or a lot of extra work. Since we're still in the first few years of switching over to Trimble there are a lot of teething pains. A lot of the things I do, aren't the way I did it in the beginning, but I was constantly trying to improve my efficiency while also making life easier for myself and the office.
<b style="background-color: var(--bb-content-background-color); font-family: inherit; font-size: inherit; color: var(--bb-body-text-color);"> They like alph in beginning especially when staking a variety of different things so they have a first Quick Look at what it is and stake like items. Just points and a mixture of curb n gutter and inlets or water lines etc I can add whatever to the front end of computed and then they can just have a as staked point number range and the point name goes into the the code field. No work or typing on there part. Which this time of year is nice. With thick gloves. lol. But I do all my comps in TBC not civil 3d cad so I have lots of options easily available and I can start out generic then rename all quickly how the want."
Our calcs and drafting are all done in Microsurvey so far, but I hear that eventually they're switching to some different program that the big company we merged with uses. Something I hadn't heard of before, but it was also second hand info. Seems like around here everyone hates TBC but I have zero experience with that and I have almost no drafting experience so all my calcs are done in Access, which actually works great for anything I have to do. That's one area of Access I can't say I have struggled with at all.
Reply to: rover83
Yeah, link to stake files instead of import for a much easier workflow. Also….stake points are not handled in the same way as measured points in TBC, they are grouped separately and have different characteristics.
I set all the default point names every project so that it automatically starts/finds the newest point number for that function. All stake points are STK0001 and up, all stake codes are the design name. Topo points are 10000-series, cogo points are COG0001, etc. etc.
If I stake something twice, both stakeout shots are getting stored separately, with different STK names so I can review and QC in the office, and output any needed stakeout reports. Once I start staking I don’t change the point name, because it doesn’t matter…if I need to add anything else I’ll turn on Descriptions and put more info there.
Usually I'm given a new CSV of the entire job, if there are new calcs in it, but occasionally I am given a CSV of just the specific new points I need. In this case would it make sense to link that CSV? Assuming I created a new job with the full job CSV imported.
I have been a way from every day surveying and when I returned I was handed civil 3d microsurgery TBC . Out of all of them for comps and was/qc and managing projects TBC was the easiest and quickest I was able to become productive with. Now I have a cad tech that hates TBC but mostly because he doesn’t want to think. He wants to open TBC up and it be ready to go like civil 3d.
He does most of his comps in civil 3d. For there crews. So he is use to that. Which for some things I don’t think makes a big difference it’s what you get use to. Me I like everything going through TBC that’s going to or coming from the field. It is just easy for me to use tbc as a management tool as well. I put notes comments in it. So if boss asked me something about a project. I open it up and have everything from raw data to whatever right at my fingertips. I have a layer just for notes and such. So I can leader them to exact point issues or whatever. Say existing curb didn’t match design. I have a note that states that and what I adjusted to etc. even what field book page at times. I don’t have to navigate the million folders on a server to find a what or who did what.
You can link to as many different csv files as you want and job files. Now you don’t want to link to job files of a different datum. Or that have point numbers that have the same name but different coordinates.
So I had one project that was started before I arrived. They used the same point number over and over again but changed the elevation for different lifts. It was a cluster.
Now lets give a scenario. You have a job where you set a new control point on lots 13 and 14. It’s in job file A. You have a csv file that has everything but that one point you have a new job file B created and have linked to the csv file. You get around and some concrete truck parks and breaks down so you are well heck I will set up on that point at lot 13 and 14. But it’s not in your csv file. Just on your map screen layers link to that job DONT have to import. Do a station set up and then so you don’t mess with duplicate point numbers in that file and the csv file and your current file unlink after your station set up from job file A. Your point is in it because you used it but not all of those other points. The linked file only shows visibly what’s your linked to. It’s not in your job until you use it. I hardly ever import a bunch of points to a job file. I almost always link. Now I do keep my crews a csv file with all control updated in the project folder separate from any csv file to stake from. That way once all is done and they are off to a new project they can delete everything except the control file and latest csv file. No need once I have confirmed all raw data has been backed up for them to have a million files. Like tomorrow I am going to a new project new client but we did some work on that site with another client. They still have the control file csv in that project folder We will copy that control file to the new project file folder and link to it the csv file and set whatever additional control and do our mapping. Now I will see how well everything checks qa/qc maybe even an adjustment I doubt it it’s in between good control but if it all checks I will add that to the csv control file and place updated in both project folders . To be honest this is a scenario that a weighted average of the points actually make sense. I basically will be coming off of good control to set enough to see into and out of a building so ware house type building. So no traversing really needed. I hope lol. But if so I will do whatever is necessary to get it correct. It’s to map some rough stuff inside the warehouse. Which will take longer to get to the site then actually do.
I might have different csv stake out files for a project site so say we do all the rough staking subgrade. For a client. That’s one csv file then later they want drainage and curb and gutter I get that in a different csv file then buildings another. It’s all in the project folder. So if they are setting building corners on one end and contractor said hey can you before you leave set subgrade where the stock pile was we are ready now for that area. They simply link to that csv and stake unlink when don so they don’t have a million points to look at on the screen. Or maybe the cre sees a stake with hub and cut on it. They can link to that csv file stake it and see if that cut matches or is it disturbed. As @rover83 stated since adding stk or in your case a suffix no duplicate point numbers arise.
You as a party chief are in as much as the office a manager on a site. You have to manage the job just as much if not more than the office. Now I do my best to listen and make it easy for my crew chiefs to know they can say this would help this stinks. I had a crew chief on a project that was linear staking. The point numbers were all random not even in sequential order but even worse it was like 100 -120 then 1000 - 1020 even 5000 numbers. It was a straight line pretty much. So me knowing he likes to use the map and how sometimes he misses a point because scale on map or refresh rate I simply had him send me the csv file and I remembered them in a logical order. The cad person that did it has not been in the field so he just didn’t know. But It goes that way sometimes. I do try and remember what it’s like and go to the field enough to be able to help understand what they need even if it’s for a hour on a project just to see if I can help improve their needs. I mean honestly sitting in the office I have no elements to deal with. Now there are times I have to say deal with it I am swamped. But usually it’s a few minute task .
<b style="background-color: transparent; font-family: inherit; font-size: inherit; color: var(--bb-body-text-color);">So I had one project that was started before I arrived. They used the same point number over and over again but changed the elevation for different lifts. It was a cluster.
Now lets give a scenario. You have a job where you set a new control point on lots 13 and 14. It’s in job file A. You have a csv file that has everything but that one point you have a new job file B created and have linked to the csv file. You get around and some concrete truck parks and breaks down so you are well heck I will set up on that point at lot 13 and 14. But it’s not in your csv file. Just on your map screen layers link to that job DONT have to import. Do a station set up and then so you don’t mess with duplicate point numbers in that file and the csv file and your current file unlink after your station set up from job file A. Your point is in it because you used it but not all of those other points. The linked file only shows visibly what’s your linked to. It’s not in your job until you use it.
When you say "it's not in the job until you use it" it reminds me when I was first trying linked jobs, because my PM liked doing it that way when he was in the field, but he was telling me that they would always have to inverse the linked points first, before they (could be staked?). I'm not even sure if that is what he said, or if he was remembering correctly. He only had experience on the TSC3 also, with a much older version of Access obviously.
I hardly ever import a bunch of points to a job file. I almost always link. Now I do keep my crews a csv file with all control updated in the project folder separate from any csv file to stake from. That way once all is done and they are off to a new project they can delete everything except the control file and latest csv file. No need once I have confirmed all raw data has been backed up for them to have a million files.
I was following until "delete everything except control and latest csv". I'm not sure what I would be deleting.
<b class="">Like tomorrow I am going to a new project new client but we did some work on that site with another client. They still have the control file csv in that project folder We will copy that control file to the new project file folder and link to it the csv file and set whatever additional control and do our mapping. Now I will see how well everything checks qa/qc maybe even an adjustment I doubt it it’s in between good control but if it all checks I will add that to the csv control file and place updated in both project folders . To be honest this is a scenario that a weighted average of the points actually make sense.
Can you elaborate on the weighted averaging? I only remember seeing this with gnss measurements, which I used when trying to get shots in heavy canopy, but I think you're referring to something different.
I basically will be coming off of good control to set enough to see into and out of a building so ware house type building. So no traversing really needed. I hope lol. But if so I will do whatever is necessary to get it correct. It’s to map some rough stuff inside the warehouse. Which will take longer to get to the site then actually do.
I might have different csv stake out files for a project site so say we do all the rough staking subgrade. For a client. That’s one csv file then later they want drainage and curb and gutter I get that in a different csv file then buildings another. It’s all in the project folder. So if they are setting building corners on one end and contractor said hey can you before you leave set subgrade where the stock pile was we are ready now for that area. They simply link to that csv and stake unlink when don so they don’t have a million points to look at on the screen. Or maybe the cre sees a stake with hub and cut on it. They can link to that csv file stake it and see if that cut matches or is it disturbed. As @rover83 stated since adding stk or in your case a suffix no duplicate point numbers arise.
We don't tend to have a lot of jobs that sound like this. Curb and gutter isn't something that we're asked to stake out very often, hubs aren't a thing here either. It's usually either a subdivision, with maybe 50-100 houses in a phase, each house house maybe an average of 10-12 corners to layout (though townhouses can be over 50 corners), maybe 6 offsets for the excavation of each house. So that and giving a single cut stake for each house is the typical layout. The houses often get calced in stages, they might send my PM the plans for multiple houses at a time and he calcs them and schedules us whenever they ask for the layout. Some clients keep changing the houses, so new plot plan and stakeout sheet and new CSV for whatever houses changed.
The CSV will have all that layout, plus every lot corner and bend (calc and set bar), all control and benchmarks and anything else that has already been done (like previous layout, temporary spikes etc).
You as a party chief are in as much as the office a manager on a site. You have to manage the job just as much if not more than the office. Now I do my best to listen and make it easy for my crew chiefs to know they can say this would help this stinks.
Our workload has slowed down a lot over the winter, though the office guys still seem to be pretty slammed. If I was still working solo right now I could probably find the time to manage CSV's and separate them into nice organized files that I could link as needed. I'm currently working with another PC as neither of us have a helper. Since it's slow, they're just trying to make it easier on the both of us. The upside is that both of us have picked up little tricks from each other. The other PC isn't old, but he's been a PC a lot longer than I and I considered him pretty set in his ways, likes to stick to his routine, but I got him hooked on the IMU and a few other life hacks that I mentioned I liked doing. I also picked up some things he does that just made sense.
I had a crew chief on a project that was linear staking. The point numbers were all random not even in sequential order but even worse it was like 100 -120 then 1000 – 1020 even 5000 numbers. It was a straight line pretty much. So me knowing he likes to use the map and how sometimes he misses a point because scale on map or refresh rate I simply had him send me the csv file and I remembered them in a logical order. The cad person that did it has not been in the field so he just didn’t know. But It goes that way sometimes. I do try and remember what it’s like and go to the field enough to be able to help understand what they need even if it’s for a hour on a project just to see if I can help improve their needs. I mean honestly sitting in the office I have no elements to deal with. Now there are times I have to say deal with it I am swamped. But usually it’s a few minute task .
My old PM was bad about number ordering, but nowadays it wouldn't bother me until I'm doing the notes and inversing points, then it would be mildly aggravating. For layout I usually start with the furthest point from the gun and work my way back to it, that way if it goes off the BS a little, there's a better chance the points still check. I know others like to start at the lowest number and work up, but I just walk to the point I want to do and pick it off the screen. I never used point lists, because as soon as I created one, an excavator or other workers would be in my way, or asking about a tight corner they were worried about etc, and I would be back to some random order of layout anyway.
Like you said, more than one way to skin a cat. I'll probably be fine tuning my routines for another 20 years. Thanks again for all the help.
I meant delete the old jobs sorry. Just keep the csv files in the project folders is all.
I don’t know why if being linked to a csv file he would have to inverse to be able to stake them maybe a glitch or something but even back to survey controller days I don’t remember anything like that survey controller was the software name before turning into Trimble Access when the TSC3 came out. So it could have been a bug in one of the releases and that was his work around Or maybe they were inversing to check distance or diagonals maybe as a work flow to check office calcs But most definitely not necessary for staking a point in a linked file .
Ok I have done this but more for concept not production for your everyday applications. I assume your PM is getting plans either digital cad drawing or paper and he is taking the house plans and placing them on the lots so maybe buyer chooses lot 1 and wants house model X but you go layout the X house on said lot maybe they change and want house model B so now you go back and re stake or maybe it’s the garage flips etc
Anyway have you tried just staking to a dxf or dwg vs all the points files in theory you could have every house model plan in your project folder he gives you the PM the lot corners and the stake for grade which I assume is for finish floor or something similar you then could turn on whatever model house goes on that lot it’s not referenced in right place yet so maybe the dxf name is the house model I assume you would know the regulations for setbacks side lines and you could just comp a couple points based on that and translate rotate the dxf in stake and offset as needed or he could send the dxf file that’s already placed in correct location and you stake it that way vs all the points . If I have the design then I can stake 4 corners for digging foundation have same dxf when I return to set nails seems that could work into a decent work flow you could experiment and test this on a lot he has pre comped just do it that way then layers turn on the dxf use your snap commands in access and stake however he comped . Of course I would have loved to had this capability back in the 90’s when I did subdivision work instead of trial and error on the hood of a truck wiggle in a house on a lot lol. Of course the lady always sais can you rotate it this way or that way slide it here and there until it ends up back in the same place . I have been there and done that . Oh sometimes I just wanted to run away You should pm me sometime I think we could talk on phone and maybe I would be more useful as I can’t always relate in writing what’s in my old head glad to help anyway I can . @rover83 is probably much more knowledgeable with this than I am he has been involved way more than me . I try and remember how I did it years ago and then figure out how the data collector software can make it more productive and not lose the quality . I still will borrow a crews gear bring it to the farm and just try things or use my emulator . I can do it long hand and in the data collector now I am finding the data collector can do it multiple ways then I figure out how to manage that work flow etc
Okay, not sure what specific issue he had with linking. So basically everything should work normally just that you can add and remove the csv's that are linked as needed, even if you used the points for a setup or check?
The cut stake we give us for underside of footing. First step is always to dig the hole. Almost all houses around here have an 8 or 9' basement, very few without.
I understand what you're saying with the DXF idea. I don't stake dxf's often, sometimes they don't match up with the actual points so I never assume that they do. I just use them as a guide to find my way around the job. Also I think staking a DXF is assuming that you're always staking offsets? I know in other parts of the world that's the way it's always done. Here they have us stake actual building corners. The offsets are only for excavation, leaving enough room for the footings and big o that goes around it.
The same idea could likely be used for house models calced in a CSV... however we have to have an approved plot plan sent to us by the builder and then my PM calcs it and checks it and I check the setbacks against the plot plan before I do the layout. So I'm the double checker. If I was to do it myself then there is only a single checker and sometimes the concrete guys are forming up before I leave the hole, so being checked at the office later isn't a great solution either.
That and we have a policy against rotating and translating in access. A large surveying firm nearby that my PM came from had this policy before we even switched to Trimble. I used to do it all the time in Fieldgenius and it was never a problem but in Trimble we can do it only if we create a second job, a duplicate set of points with a different name (with a number prefix like your example yesterday) but it's not very efficient, so we do a local job with just the calcs, set up where the client wants the house and backsight line..tie in enough of the corners from the original job to relate them and make sure it fits minimum setbacks.
Damn, I really hate to say this but it really sounds like your office is trying their best to make it tougher to do your job.
You can link and de-link to your heart's content, as long as you remember that there are search rules when duplicate points exist:
When points of the same name exist in a single CSV file, the software uses the first point.
When points of the same name exist in multiple CSV files, the software uses the point in the first CSV file. The first CSV file is the first one in the file selection list. To change the order of the CSV files, tap the tabs at the top of the file selection screen. If you change the order of the CSV files, this may change the order in which files are selected.
When you accept a CSV file selection, and you then go back and select more CSV files, all subsequent files are appended to the initial selection, using the rules. This assumes that the original selection is not altered.
Trimble recommends that you do not use multiple CSV files that contain points of the same name.
I've never had a DXF mismatch with a point, if the point and the DXF were in the same location in the drawing file. This could perhaps be the CAD software being used and/or a feet units problem.
You can indeed stake to vertices of a DXF, not just offsets. I used to get the plot plan, then translate/rotate into my master boundary basemap, check that the foundation/building is within the setbacks (and that they did not screw with the lot dimensions...and that I have the right lot number!), then spit out that properly oriented building polyline to a DXF and go stake it.
Access does translate/rotate just fine (it better, considering it's such a simple routine). It also lets you translate/rotate DXFs and other map files too. I get that they don't want things getting too whacked out, or have a bad translate/rotate, but it sounds like you have enough checks built into your workflow that it shouldn't be a problem.
Sorry, we got rained out and I had digested and replied to half your message, then the rain stopped enough to finish the last cut stake. I see now you mention snap commands, so that's how you're staking corners with the DXF....I have never used those.
I've been there with the rotating multiple times.....back when I was using field genius a builder had me move it a few times so he didn't have to cut down some trees...then he said ah shit! The garage entrance is on the side of this house.....so we had to move it back. I think it was 7 rotations total. It was pretty easy with fieldgenius other than the tiny damn buttons.
I still have fieldgenius and have used it on a mansion last summer, where the guy was trying to squeeze it between the trees as the method we use in Trimble would have taken forever by trial and error.
I guess this year we're apparently losing our fieldgenius office licenses so I can't use that anymore. Rotate and translating in access seems to work very similar to fieldgenius so we'll probably have to be able to use that again, even if it means a set of duplicate points, or the office figuring out what the issue is.
Mike,
As well as snapping to the ends of DXF lines, you can snap the intersections
Its really handy if your building has gridlines, but the office have not given you the points
While you can geo-locate a DXF in the field, its better done in the office - It is a good check that the dxf numbers matches the control file you got given
I will rotate and/or translate in the field if I have to, but I really hate doing so. It is really hard to check your calcs, and the liabilities are huge
Damn, I really hate to say this but it really sounds like your office is trying their best to make it tougher to do your job.
To be fair, they are not trying to do it. We're all struggling through this. I'm only talking about the problems, the things that make my job harder, not the good things. It really is a good company to work for, we do have a lot of great people and I've never had a job that wasn't extremely stressful at times. It's just that our city was in a huge residential housing boom and I was under a lot of pressure (from myself) to keep up.
You can link and de-link to your heart’s content, as long as you remember that there are search rules when duplicate points exist:
When points of the same name exist in a single CSV file, the software uses the first point.
When points of the same name exist in multiple CSV files, the software uses the point in the first CSV file. The first CSV file is the first one in the file selection list. To change the order of the CSV files, tap the tabs at the top of the file selection screen. If you change the order of the CSV files, this may change the order in which files are selected.
When you accept a CSV file selection, and you then go back and select more CSV files, all subsequent files are appended to the initial selection, using the rules. This assumes that the original selection is not altered.
Trimble recommends that you do not use multiple CSV files that contain points of the same name.
I wouldn't want to link multiple CSV's if I didn't know for sure that the points weren't duplicated. I would want to do like Olemanriver and have everything organized into different types, but with the way our current workflow goes, it would be a lot of extra hours to get to that point.
I’ve never had a DXF mismatch with a point, if the point and the DXF were in the same location in the drawing file. This could perhaps be the CAD software being used and/or a feet units problem.
This was not a software glitch, it was just a few specific subdivisions we've worked in. I think it might have had to do with the CAD file coming from the client and not being shifted to fit or something. I'm not sure the reason, I just know that even when checking offsets I project point to line and change the line to the 2 point method because I know that calcs for the corners should be right. I only use the DXF if I need to check offsets to a curve which is not most of the time.
You can indeed stake to vertices of a DXF, not just offsets. I used to get the plot plan, then translate/rotate into my master boundary basemap, check that the foundation/building is within the setbacks (and that they did not screw with the lot dimensions…and that I have the right lot number!), then spit out that properly oriented building polyline to a DXF and go stake it.
I understand the idea behind this, but until I was to actually try it I don't yet understand the advantages. I actually forgot to mention that the biggest DXF issue we had is that we have had a lot of trouble with them just not working at all in Access. There was a lot of experimentation in the office, one job with a ton of complicated gridlines, we really needed it and we got 6 different DXF's and finally got one to work. I think there was a couple causes, but one was probably Fieldgenius and Trimble access compatibility. I had the same issue way back with Magnet Field actually, but the DXF will always work in Fieldgenius. It's just bound to crash when you zoom into points too frequently.
Access does translate/rotate just fine (it better, considering it’s such a simple routine). It also lets you translate/rotate DXFs and other map files too. I get that they don’t want things getting too whacked out, or have a bad translate/rotate, but it sounds like you have enough checks built into your workflow that it shouldn’t be a problem.
The issue wasn't on the field side, it was something to do with processing on the office side once again. I think maybe some extensive TBC training would be very helpful.
I will try out snapping tomorrow just so that I know how to do it if needed. I have had a warning/prompt about geo-locating in the past, when adding a DXF through the layer manager. It is rare, and I wish I had investigated the cause further at the time, but things like this usually happen when I'm under a time crunch. I believe it has happened even when the DXF seemed to work perfectly fine, but like I said we rarely ever stake from it, we just use it as a visual aid, so we're not just looking at a sea of points. It's like having the plan and sketches all in front of you at the same time, instead of carrying a bunch of paper around and trying not to let the wind blow it away. LOL. <div>
Yes liabilities are huge. When we would rotate and translate for layout, it would just be the point range of the house only. Then I would check all the tightest corners to the boundary and make sure it met the minimums with some wiggle room for error.
BTW, as you can see I'm also learning how to use this site better through trial and error.
Mike,
As well as snapping to the ends of DXF lines, you can snap the intersections
Its really handy if your building has gridlines, but the office have not given you the points
While you can geo-locate a DXF in the field, its better done in the office – It is a good check that the dxf numbers matches the control file you got given
I will rotate and/or translate in the field if I have to, but I really hate doing so. It is really hard to check your calcs, and the liabilities are huge
</div>
Man I have come to love the description field. It is absolutely right there for a crew chief to add a little extra information that I might need to see. In staking or Topo or boundary. Just a neat little addition. They crews now have become use to it and like it more than yanking the field book out for a quick note or hey this water valve is missing lid or man hole lid is busted in half etc.
If you play around with the snaps. Also think of it this way corner to corner you can Cj that distance. You can create a point at whatever distance along that line a few ways. Coho or stake to the line go distance then you can coho points say for an added bay window from that line and points. I mean you can lay out the bedroom or kitchen if you would like. It’s all math and you seem to have a handle on that so you are going to be fine. Never be afraid to fail. Just have a back up plan until you get it down aka your pm pre comped points etc. Once you use it a while if you have not already you can add favorites program hot keys all sorts of stuff that make not having to navigate all the menus for your favorite tools. And functions. I am sure every brand has. This sorta thing. I don’t get to do that fun stuff as I am usually if in the field using someone else’s equipment and don’t want to mess there little world up. I actually got my crew chief back and so he helped me today or I helped him. He is a great young buck and works hard . I was purposely moving his hammer around today so he kept coming behind me and putting it back to where he keeps it. I finally told him look. This is your truck and your equipment. If I am not doing something right let me know. So tell me to put things back where I got them. He was like your the boss I said not today you are. He will be a great addition to the profession he is going to be an all star. I just wish I was his age again lol.
I use make notes that way or take pictures and add to the point in question, quite regularly. Very valuable tool.
I use hot keys all the time. Only thing lately is I'm switching between my DC and the other PC DC and he has a different set of hot keys. I set them up for the stuff I use constantly in a way that made sense for me. Our inverse key was the only one that was on the same hot key, so the rest I have to remember which DC in using. Lol.
What’s the reason for traversing with rounds, RTK, and static? Are you over killing your observations? More observations, if they are done correctly, are good but are you spending too much time for your required confidence for the type of project?
I combine total station, RTK, and static too but only,y to complete measurement tie-ins but never rounds.
No sir. I can’t gps every where so I will do conventional in those areas. It depends on job. How and what I do. I am setting control now on several different sites that will be used long term for many different things etc. so I try and get as much and as good control established for the sites in the beginning so we are not chasing our tails when a different project pops up. We have a 5” and a 3” gun. So 4 rounds kinda takes care of everything unless requirements change. Gets me to the sweet spot. Is all. And crews just are consistent
What’s the reason for traversing with rounds, RTK, and static? Are you over killing your observations?
Control work. Always always always measure in both faces for control work, and as soon as traverses get more than a half dozen or so points, RTK and/or static to both connect the traverse to the real world, and to tighten things up.
I combine total station, RTK, and static too but only,y to complete measurement tie-ins but never rounds.
Wait, are you saying that you never turn rounds to anything? When's the last time you checked your instrument collimation?