J-field Rotate and Translate is archaic

If I've got the parameters in front of me, it should take LESS than 30 seconds to key them in.
Old______ (can select by inverse between pnts)
New______brg or az
Pivot @________62
Points to rotate_______ S1 to S99, & S150 to S200
Or... Point groupings by name. That means point groupings remain intact, via group names. Groups can be edited.
Check box, always skip survey points.
Group select, same as above.
PT___ = pt____

Also, add an align program, that combines both of the above. With check box, to allow scale to change or not.

The watch word here is simplicity.

I like to use rotate translate, to perform trial and error looks at things, in the field.
For the most part, it needs only to modify
DESIGN points.

As it is, I avoid it. Especially rotate.

Thank you.
I use it all the time. I like it. I use the filter if i nees to separate point groups. I wish you could filter more than a range. I use 1..100 for pnts 1 thru 100 but you can't add commas if you wanna add another point.

For example 1-100,105,500,200-205
Once a point group is made, we should be able to store that group. And name it.
This way, we could have the design points in the field, in groups. And, a check box system, for what we Groups we want to rotate, or translate. Even "all design points", could be an option.
If a given group is S1 to S99, and not all points have values, or are used, but later we add in the un-used points, they should be included in the group.

Matt Johnson

Well-Known Member
Nate most of what you describe already exist and is simple to do. Currently there is not a scale option but it is planned for the future.

I uploaded a quick demonstration of Move and Rotate in J-Field. There are 2 survey points (1 and 2) and 200 design points (D1 through D200) in this project. First points D1 - D99 and D150 - D200 are moved from D1 to 1. Then this same group of points is rotated around 1 from D2 to 2.


Matt Johnson

Well-Known Member
"Point Groups" do not natively exist in J-Field but there are several ways to create groups that can easily be selected with the current filters:
  1. Put each group of points into its own page. Then you can easily select all the points in that page.
  2. Name the points in a group in some format that can easily be selected with the current name filter. For example D1.1 to D1.200, D2.1 to D2.50, etc. You can then use the filter to filter to D1 or D2 point groups.
  3. Assign all points in a group with a common description and then filter the points by description.

Shawn Billings

Shawn Billings
The rotate command can still use major improvements.

Your video demonstration of selecting various point ranges is very helpful.

For the task you performed, an align feature, similar to AutoCAD would have made the operation much faster. I end up using localization to do this because I'm more comfortable with it.
I would agree, the point group, would be a great feature. Its invaluable in Carlson, especially when working with large groups of points. One example of how they could be used is, You could have each deed in its own point group, once you locate some of the deed evidence for a specific deed or deeds you could then rotate and translate the point group associated with that deed using its point group, etc.


Well-Known Member
I very rarely calculate points then import them for boundary work. I plot the deed then import the linework to a page, name it, and then use the page to filter the points. I will put the deed on one page and my survey on the other page. If I have deeds that line up well they go on the first deed page, if they don't line up well with the subject deed I will put them on another page. It works just like groups. I also agree with Shawn that localization is a great way to do this plus you get to see residuals. I have used localization many times just to compare my results with the record.

We also have filter by code category under additional filters.

Select Category_20190111-08.31.53.png

Shawn Billings

Shawn Billings
I think we have plenty of ways already to segregate points.

The rotate command needs to be reworked. There should be an initial bearing entry, defined by points or direct entry. There should be a target bearing, also defined by points or direct entry. The difference between the two should be displayed as the angle of rotation, which can also be entered directly without entering the two bearings. This is how every modern rotate command I've seen from the last 15 years or more has worked. It covers every aspect of rotation a surveyor might encounter. Our present method is too restrictive and is not intuitive.
What Shawn said, but groupings, would be wonderful.
I.e., go to field, with 10 different deeds/old surveys. Name each deed/survey group. Grab each deed group, rotate, translate, (align), and use for searches. The faster/simpler, the better. It's mainly to search, but can be used to for all kinds of things, such as dividing property, etc.

Shawn Billings

Shawn Billings
If you import deeds as polylines, with each of those polylines in a separate layer (i.e. named after the deed), then the code in J-Field for the points will be the layer name. Use the filter by code and you will only have the points that were from that layer.

Matt Johnson

Well-Known Member
If you import deeds as polylines, with each of those polylines in a separate layer (i.e. named after the deed), then the code in J-Field for the points will be the layer name. Use the filter by code and you will only have the points that were from that layer.
There is really no need to even have to do this. If you import dwg files with polylines, the polyline and point nodes will be created with the following naming format:

Polyline Name: LAYERNAME_N
Polyline Node Names: LAYERNAME_N_N2
where LAYERNAME is the layer of the polyline in the dwg file, N is an integer assigned for each polyline and N2 is an integer for each node of that polyline.​
You can then just use the name filter with the search string LAYERNAME_N to filter to all the point nodes of the desired polyline.
If you are familiar Carlson SurvCE, the commands within the Map View are extremely useful. We import polylines for deed lines and proposed buildings, etc.
WE can then draw, modify, offset, and transform much like using CAD in the office. The simple solution here is sometimes to export points from the LS, import into SurvCE on the data collector. Do our rotations, offsets whatever to place the building footprint, then transfer points back to the LS for stakeout.

Shawn Billings

Shawn Billings
CAD tools in J-Field have been needing improvement for some time also. Carlson does have a very nice set of CAD features, pretty much everything you'd want to do with CAD in the field is available. Hopefully the list of improvements we've requested will get put on the front burner again soon.
Typically, I have the various deeds/plats reconciled into one figure and points. There are times where stuff doesn’t fit well everywhere and you have to realign multiple times and probably the polyline and page techniques do this better. For years I used the standard move/rotate the figure with TDS or Survce.

As mentioned, the align routine in Survce/cad, is slick and simple to teach. It often involves just two map and two field points. It allows for scaling, which I rarely use. The majority of times a 2x2 point fit makes this work on relatively small/tight figures. What would also be useful to me would also be a simple “turn the deed/plat angle/distance white box - off two existing corners, without having to jumble or re-jumble the whole file or group of points or entities - where things are kind of messy and don’t fit well all around.