[OR Ss4] Survey Point Labels - Inconsistent Offsets Depending Upon Feature Definition

We are trying to fine tune our Survey Settings to allow the processing of Survey using OpenRoads Ss4. Coming at this from InRoads Survey, we have had a mixture of good results and some not so good.

Today, I was trying to figure out why my Survey Point Names seem to be offset further from their points than I remember them being, when I realized that the offsets were not the same for all points. It was my understanding that the survey point labels were partially read from the open XIN and some settings were not user configurable. We have locked down the color, level, weights and text size from the XIN, but this does not explain the differences in offsets of labels that are supposed to be set in code and not user configurable.

In the image I have attached, there is a guy wire (GUY) point which shows the point name, code and elevation being placed at what appears to be three corners of a square that is smaller that the range box of the guy wire cell. The guy wire cell is supposed to use a JPT code to draw a line to a nearby utility pole. I noticed this GUY does not have a JPT code assigned to it. Looking at some that do use a JPT, it appears that the labels for elevation and point name move further way from the cell when there is a connecting code used.

  

I made a selection set out of the GUY cell and an EP cell and their labels you can see the point name and elevation labels are different distances from from their respective cells. It looks like the code labels have retained their offset from the cell, but the others are arranged as though the aforementioned square has been scaled up for the EP compared to the size used to space out the GUY labels.

Other GUY codes show the labels spaced consistent with the EP labels and if I add the JPT code to it, the point name label and elevation labels move farther away, matching other points.

I believe this is new behavior. The one thing we have recently added is to use the Smart Objects VBA codes to annotate the survey using attribute values. These are setup to use element templates, text styles and dimension styles. If I check the label properties, they do not use the text style of None, but are using a style even though their XIN settings do not.

This new spacing makes it easier to confuse which point name label and which elevation is associated with which point.  

Parents
  • SS4 is enough to drive a man crazy! We use the XML file and Power GeoPak. We suffer from similar inconsistencies in feature code application and symbology. Check annotation scale locks and apply a survey redraw. You might get some insight checking with the Florida DOT cadd site.

    Sometimes I need a shoulder to cry when tweaking SS4 survey workflows and settings.

    Cliff

Reply
  • SS4 is enough to drive a man crazy! We use the XML file and Power GeoPak. We suffer from similar inconsistencies in feature code application and symbology. Check annotation scale locks and apply a survey redraw. You might get some insight checking with the Florida DOT cadd site.

    Sometimes I need a shoulder to cry when tweaking SS4 survey workflows and settings.

    Cliff

Children
No Data