Carlson Software Forum

[CS06]

I find the help section on level reduction a bit lacking and confusing.

The example file (Pg202.lev) appears to have a fatal flaw in line 8 with a
BS on an ER "end" ... but this mistake is ignored by the program during its
adjustment.

Since the help doesn't explain much I decided to play with the routine, even
recreating the data shown in the example. To my surprise, the program does
not appear to recognize the "station" field as meaning anything. Entering an
elevation for an earlier appearance of a station does not produce the same
value later in the file, whether as a starting point or a closing point.

Please correct me if I'm wrong, but why is the ER record on station C (line
28) using the pre-adjustment elevation of 106.25 instead of 106.275 as
determined on line 11? The same apparent error is repeated on lines 19 and
20 where pre-adjustment elevations are constrained to.

In types; Start, Turn, Sideshot, and End ... what is a Description Shot?
Appears to be associated with adding a note, but I'm guessing I'm missing
why it looks like a shot in that it allows each field to be used.

I can't find an explanation of what the 2 possible Code items mean/do. EL
vs. FE? Didn't seem to have an effect on the values produced.

It appears that storing the points to a CRD file replaces the value of any
points in the CRD file with matching names (ONLY if they already exist). Out
of curiousity I added some extra different values and found that it takes
the last listed elevation and uses that alone in replacing the elevation
value.

Is this format something that a particular digital level exports?

Thanks in advance for any input.

Rich

I used the level reduction routine for the first time today on a production
need. 5 individual runs from known points, each closing back on itself each
time.

I noticed that when I started a new run (within the same file as shown in
the example), I could not give it a starting elevation. The software would
actually error when I tried adjust, but would not let me enter an elevation.
Through trial and error I eventually figured out that I needed to save the
file and reopen it to be able to enter that value.

I think this is an error and when the user selects (SR) it should then allow
an entry in the adjusted elevation column, no different than when an (ER)
record is entered and it allows the entry of the closing elevation.

Rich

Would it be too much to ask to allow file attachment in this newsgroup? Even
if with a size restriction?

"Rich" <rmaherNOSPAM@kdmmeridian.com> wrote in message
news:e8qac3$rem$1@update.carlsonsw.com...

[CS06]

I find the help section on level reduction a bit lacking and confusing.

The example file (Pg202.lev) appears to have a fatal flaw in line 8 with a
BS on an ER "end" ... but this mistake is ignored by the program during
its
adjustment.

Since the help doesn't explain much I decided to play with the routine,
even
recreating the data shown in the example. To my surprise, the program does
not appear to recognize the "station" field as meaning anything. Entering
an
elevation for an earlier appearance of a station does not produce the same
value later in the file, whether as a starting point or a closing point.

Please correct me if I'm wrong, but why is the ER record on station C
(line
28) using the pre-adjustment elevation of 106.25 instead of 106.275 as
determined on line 11? The same apparent error is repeated on lines 19 and
20 where pre-adjustment elevations are constrained to.

In types; Start, Turn, Sideshot, and End ... what is a Description Shot?
Appears to be associated with adding a note, but I'm guessing I'm missing
why it looks like a shot in that it allows each field to be used.

I can't find an explanation of what the 2 possible Code items mean/do. EL
vs. FE? Didn't seem to have an effect on the values produced.

It appears that storing the points to a CRD file replaces the value of any
points in the CRD file with matching names (ONLY if they already exist).
Out
of curiousity I added some extra different values and found that it takes
the last listed elevation and uses that alone in replacing the elevation
value.

Is this format something that a particular digital level exports?

Thanks in advance for any input.

Rich

For the benefit of others not hearing the voices...

On Sun, 9 Jul 2006 00:14:17 -0700, "Rich"
<rmaherNOSPAM@kdmmeridian.com> wrote:

The example file (Pg202.lev) appears to have a fatal flaw in line 8 with a
BS on an ER "end" ... but this mistake is ignored by the program during its
adjustment.
^

Mistake

Since the help doesn't explain much I decided to play with the routine, even
recreating the data shown in the example. To my surprise, the program does
not appear to recognize the "station" field as meaning anything. Entering an
elevation for an earlier appearance of a station does not produce the same
value later in the file, whether as a starting point or a closing point.
^

Not considered, just a simple editor.

Please correct me if I'm wrong, but why is the ER record on station C (line
28) using the pre-adjustment elevation of 106.25 instead of 106.275 as
determined on line 11? The same apparent error is repeated on lines 19 and
20 where pre-adjustment elevations are constrained to.
^

Mistake

In types; Start, Turn, Sideshot, and End ... what is a Description Shot?
Appears to be associated with adding a note, but I'm guessing I'm missing
why it looks like a shot in that it allows each field to be used.
^

Still under development

I can't find an explanation of what the 2 possible Code items mean/do. EL
vs. FE? Didn't seem to have an effect on the values produced.
^

ELevation vs. Fixed Elevation (for future or current use in SurvNET)

It appears that storing the points to a CRD file replaces the value of any
points in the CRD file with matching names (ONLY if they already exist). Out
of curiousity I added some extra different values and found that it takes
the last listed elevation and uses that alone in replacing the elevation
value.
^

Not considered, just a simple editor.

Is this format something that a particular digital level exports?
^

No
(my note: I hope that SurvCE program running our digital levels will
output to a format readable by this editor!)

In the interest of sharing. Being a denizen of many newsgroups I know
how useful they can be as a tool for both the users of software and
the developers. Oh, and the silly ones can be a colossal waste of
time, but fun.

Take care,

Rich