When I start a new project, a topo for example,?ÿI've been creating a job that just has control points.?ÿ Then I create another job to store the actual topo points and simply reference in the control job.?ÿ This works great but there's?ÿa minor nuisance I've come across that I can't seem to find an answer about.?ÿ If I'm working in the topo job and set a control point, I don't see an option to also save the point to the control job (or better yet save it to the control job only).?ÿ Does anyone know if this is even possible??ÿ I know I can copy the point?ÿover later but this is tedious and half the time I seem to forget.?ÿ Any info would be appreciated.
Export the new control point(s) as a txt file (I think you can restrict the export to specific point numbers), then import it into the control job file.
I've never tried the control file, but I'm sure that's the way to go.?ÿ
I dump my rw5 and a txt file onto a stick every night, so the next day, if I'm starting a new file, I just import the txt from the stick into the new job.?ÿ Most of the time I just continue in the same job file from the day before, though.
What's the advantage to having two separate files for control and topo??ÿ Control are low numbers and topo 1000+
I've never tried the control file, but I'm sure that's the way to go.?ÿ
I dump my rw5 and a txt file onto a stick every night, so the next day, if I'm starting a new file, I just import the txt from the stick into the new job.?ÿ Most of the time I just continue in the same job file from the day before, though.
What's the advantage to having two separate files for control and topo??ÿ Control are low numbers and topo 1000+
I used to just have everything in 1 job-- control points, topo points, AND construction staking points if we happened to do that much of a single project.?ÿ On bigger projects it gets to be a pretty big ball of confusion though so I looked for ways to simplify things.?ÿ Now when I start a new project the first thing I do is make a control job and import points to it if I'm using an existing network.?ÿ Then I make a topo job and reference in the control job.?ÿ The 2?ÿthings I like about the?ÿcontrol job is the points in the control job don't appear in your map view of the topo job?ÿso they don't clutter up?ÿthe screen (you can still set up on them and?ÿstake them out as if they were in your topo job), and you can re-use point numbers.?ÿ For example, if I have control points 100-105 in my control job I can set control points 100-103 in the topo job and set up or stake out to either set without problems.?ÿ If?ÿyou wanted to add a topo control point to the control job you'd have to renumber it of course, so I guess maybe the best way to think of it is the control job is a master list of control points with the ability to set secondary/working control in your topo or stake jobs.
Anyway, I make a stake job too now for new projects and reference the control job into that as well.?ÿ This has made things a million times less confusing but I'm sure most of the veterans know all this.?ÿ Like I say though, 1 thing I wish I could do was store a newly set control point to the control job but that doesn't seem to be an option.
I keep all of my points in the same job, I just keep all of my control below 100. And then start any topo or stakeout points at 200. Then you have from 200-9999 at least available.?ÿ
?ÿ
If you want to keep the separate jobs, the easiest thing to do is export the new control point to a text file. Then just import it into your control job. You can restrict your export to any number of points based on point number.
I keep all of my points in the same job, I just keep all of my control below 100. And then start any topo or stakeout points at 200. Then you have from 200-9999 at least available.?ÿ
?ÿ
If you want to keep the separate jobs, the easiest thing to do is export the new control point to a text file. Then just import it into your control job. You can restrict your export to any number of points based on point number.
Right, but it seems?ÿodd to me that there simply?ÿisn't a button right on the store screen that says "Store this point to your control job".
I keep all of my points in the same job, I just keep all of my control below 100. And then start any topo or stakeout points at 200. Then you have from 200-9999 at least available.?ÿ
?ÿ
If you want to keep the separate jobs, the easiest thing to do is export the new control point to a text file. Then just import it into your control job. You can restrict your export to any number of points based on point number.
Right, but it seems?ÿodd to me that there simply?ÿisn't a button right on the store screen that says "Store this point to your control job".
I suspect that there isn't a lot of demand for something like that. You are the first person that I have ever heard of using that option honestly.
I keep all of my points in the same job, I just keep all of my control below 100. And then start any topo or stakeout points at 200. Then you have from 200-9999 at least available.?ÿ
?ÿ
If you want to keep the separate jobs, the easiest thing to do is export the new control point to a text file. Then just import it into your control job. You can restrict your export to any number of points based on point number.
Right, but it seems?ÿodd to me that there simply?ÿisn't a button right on the store screen that says "Store this point to your control job".
I suspect that there isn't a lot of demand for something like that. You are the first person that I have ever heard of using that option honestly.
Right, but it seems?ÿodd to me that there simply?ÿisn't a button right on the store screen that says "Store this point to your control job".
I guess it preserves the integrity of your control file, that it's something you uploaded and contains the master unmolested coordinates, and those new points are just unproven, newly collected field points.