I want SurvPC to process linework in the data collector ONLY on points that are coded with a special code telling it to do so and then stop when telling it to do so: ie., EP B, EP, EP, EP, EB E.?ÿ When I set up code EP to carry line work, and I configure the points to be stored with line details, ALL points on EP will be automatically joined.
Can I get just the points between start and stop special codes to control whether a line is drawn in the data collector?
Add numbers to each code for each line you want.....So the first EP line would be EP1 B....EP1 E
The next line would be EP2 B......EP2 E
?ÿ
That way the F2F will only connect the codes with the correct number.
I suggest making a dummy project and then just manually draw the points in map mode with the different codes to make sure it is doing what you want.
OK - could work.?ÿ
What I really want to be able to do is use any code as a stand-alone point or in a line by using begin and end designators (plus curves in between).?ÿ This means all codes are designated as lines...which means Carlson/F2F will automatically join them up as far as I can tell.?ÿ I suppose I could put a begin designator at the end of each stand alone shot to keep it from joining to its previous, like coded shot, but I don't want to have to do this.
It sounds like Carlson/F2F wants a code to either be a line or stand-alone point.?ÿ Right?
We??re not on SurvPC yet but achieved what you want in another way.
Code PTR Point Tree
Code TR Line of Trees
?ÿ
for Connifeer Trees we just add a C, and F for Fruit.
we then add some notes for Trunk size, species and number of apples hanging there.
?ÿ
I have no help in SurvPC.
But, for the desktop F2F, yes if I just want an EOP shot to be NOT part of a line, I call it XEOP.
Also, I only have to begin (B) lines, I never have to (E) end them.
I get what you are asking now...What I suggested above will work for the lines. That said, the points aren't as clear. What we found unintentionally is that the desktop F2F is different than the survpc software on the data collector in that codes are either for points or linework on survpc. So you could make a code for just points, but it won't also do linework. Vice versa codes for linework won't do just points and draws all kinds of weird things. I think putting the X in front would work in that is a familiar code, but the X doesn't let the linework start. It would be nice if survpc had a code to not draw linework.
?ÿ
Maybe one of the Carlson staff will be on and check out this thread.
For isolated shots, EP or BLD, on their own, not part of a line, I usually enter it as the start of a line (EP+7 or EP ST).?ÿ With no second shot, it won't connect the point to anything else.?ÿ And it won't get connected to the next start of a line either.
@jph?ÿ
We're new to SurvPC.?ÿ We are coming from Trimble (TSC, Access).?ÿ We have figured out this difference and how to work around it by starting a line that will effectively only have one shot.?ÿ
Has SurvPC / Surve CE always been this way?
We??re not on SurvPC yet but achieved what you want in another way.
Code PTR Point Tree
Code TR Line of Trees
That's the ticket right there. We have two different codes for items that could be lines or symbols, like vaults. VLT will start a line, VLTP will insert a symbol. Still doesn't stop crews from screwing it up, but the functionality is there.
I hate putting begin and end codes on linestrings, I always just bump the suffix number to start a new string. It's super easy nowadays with the "find the next unused line string number" key.
