Exporting points, getting rid of the " marks added to the Description

Shawn Billings

Shawn Billings

Shawn Billings
5PLS
I'm creating lines directly in the field using shape tags. No need for special codes. I've been using Carlson Field to Finish for many years (just rounding the corner on a decade!). I'm like you Adam, it's incredible how much time F2F saves and not just that, it's accurate. Better to produce that in the field than to try and reproduce it in the office. A complex surface can be generated in minutes instead of hours (or days). I've done it both ways, I would not want to go back. Having said that about Carlson, I have to say that I much prefer generating line work directly in J-Field than I do keeping up with field codes. Trying to remember which line I was on in the field was a pain. I use a lot of curves in our topo and keeping up with PC and PT was a pain. I don't have to keep track of that now. I select line in the collect screen, make sure my code is right (because that will determine the export layer for dwg) and go to work, when I come to a curve, I toggle from line to curve and it keeps track like a Texas two-step 123, 23, 23, 23 until I'm done collecting curves.

The only thing I rely on for Carlson is symbols. We can produce symbols in J-Field, but I'm still clinging to symbol creation in F2F. I hope to make the full migration eventually.
 
Adam

Adam

Well-Known Member
5PLS
Shawn Billings said:
I'm creating lines directly in the field using shape tags. No need for special codes. I've been using Carlson Field to Finish for many years (just rounding the corner on a decade!). I'm like you Adam, it's incredible how much time F2F saves and not just that, it's accurate. Better to produce that in the field than to try and reproduce it in the office. A complex surface can be generated in minutes instead of hours (or days). I've done it both ways, I would not want to go back. Having said that about Carlson, I have to say that I much prefer generating line work directly in J-Field than I do keeping up with field codes. Trying to remember which line I was on in the field was a pain. I use a lot of curves in our topo and keeping up with PC and PT was a pain. I don't have to keep track of that now. I select line in the collect screen, make sure my code is right (because that will determine the export layer for dwg) and go to work, when I come to a curve, I toggle from line to curve and it keeps track like a Texas two-step 123, 23, 23, 23 until I'm done collecting curves.

The only thing I rely on for Carlson is symbols. We can produce symbols in J-Field, but I'm still clinging to symbol creation in F2F. I hope to make the full migration eventually.
Click to expand...

How do you handle multiple codes and the connection of those lines?
 
Adam

Adam

Well-Known Member
5PLS
Old ways for me I quess, but I am way quicker just typing in the info. The new keyboard really makes this fast too with the previous texts stored for quick recall. I use an N in the description for join nearest found in Carlson. What if it's two existing lines and you are going back to fill in the intersection shot. I use two codes so each line will get drawn on the correct layer. J field only allows one tag or code, so how do handle the layer of the second line?
 
Shawn Billings

Shawn Billings

Shawn Billings
5PLS
How do you handle multiple codes and the connection of those lines?

Start a new tag and use "By Find" to start at an existing point or pass through an existing point.

On top of facilitating multiple lines passing through a common point. I like this a lot more than Carlson's JPN (join point) code. Carlson makes you memorize the point name, Javad let's you pick it from the map.

A good example of this is power lines coming together at a single pole. My Carlson F2F description might be UP PRL1 PRL2 PRL3 GY1. The UP stands for utility pole and makes a symbol on the map. PRL is a line code in layer PWRLINE. GY is a line code in layer GUY_ANCHOR. With Javad, I shoot the pole. Then when I get to the guy anchor I start a line at the anchor and use by find to connect the line to the pole. Same with the power lines. Whether they be points under the line or another pole, I shoot the point and connect by find to the power pole.
 
Adam

Adam

Well-Known Member
5PLS
Shawn Billings said:
How do you handle multiple codes and the connection of those lines?

Start a new tag and use "By Find" to start at an existing point or pass through an existing point.

On top of facilitating multiple lines passing through a common point. I like this a lot more than Carlson's JPN (join point) code. Carlson makes you memorize the point name, Javad let's you pick it from the map.

There is a Near command in Carlson that I have truncated to N which will draw to the nearest point without having to look up the point number or pick it from the map. I have played around with Tags some, but haven't gotten it working for me yet.
Click to expand...
 
Robert P Stenerson

Robert P Stenerson

Active Member
Shawn Billings said:
I see that you are using the space separator already. There should be no reason to add a space to the beginning of the description. The separator provides the space.
Click to expand...

Hi Shawn, that's exactly what I was expecting, but when I don't put a space, the description is appended to the code (no space) in the export file which hoses me for the Carlson input to the .crd file. Again, I understand the J-Field tag use is great for AutoCAD guys importing linework and layers, etc, but we're not there and not going to be, <ref my previous "... the mountain is not coming to me">, my data has to play by Carlson protocols for our field to finish drawing.

It's raining here in Erie today, and I'm in the office, so maybe we can try a support session with different sessions and try it so that I can get what I need/want???
 
Mikhail Drakin

Mikhail Drakin

Developer
Ok, I see that we really need more options for quoting fields. The thing is, I want to keep compatibility with general spreadsheet software, which requires proper screening of quotes, separators and spaces. I will replace "Quote Fields with Quotes" checkbox with more general selection of 3 or probably 4 options (Quote Fields: never / with separators / with separators and quotes / strict). This should cover all possible needs. Among other issues, we also need strict quoting option if we want to create CSVs which can be imported back in J-Field without losing too much data.
 
You must log in or register to reply here.
Top