Yahoo Archive - 2013 

You can search all users group archives using the Google Search gadget
 

Click here for an overview of the Compass Users Group Archives:

Archives Overview.


Messsage #: 347
Date: Mon, 28 Jan 2013 05:21:35 -0700
From: "Larry Fish" 
Subject: LRUD handling.

Hi everybody,

Many people have requested this feature and I've finally had the time to
work on it. Compass now has the option of setting the LRUD associations on a
survey-by-survey basis. Here is description of the new features:

1. LRUD Associations. When Compass builds passage models it needs to
associate the LRUDs with either the From Station or the To Station. In the
past, Compass could only do this at the file level, which meant that every
shot in every survey was handled the same way. Compass now has the option of
a controlling LRUD Handling at the Survey Level. In other words, every
Survey can associate the LRUDs differently. The Editor now allows you to set
the option in the header of every survey.

2. LRUD Tools. To aid in the process of converting files to the new system,
Compass has new tools that allow you to set the LRUD Associations for large
blocks of selected surveys all it once. 
There are also new tools that allow you to shift the LRUDs forward or
backwards one shots for selected surveys. This allows you fix surveys where
the LRUDs were entered with the wrong station.

3. Overriding LRUD Settings. You can override the survey-level LRUD Flags by
changing the settings in the Project Manager. These "Override Settings" can
be saved either to the MAK file or as the Project Manager Defaults.
The version is the internet.

Larry Fish


Messsage #: 348
Date: Mon, 28 Jan 2013 18:47:41 -0500
From: Dwight Livingston 
Subject: Re: [compass-users] LRUD handling.
  
    Larry
      
      Thanks for adding the new LRUD features. We will use them.
      
      With that option a setting, I now have even more use for a way to
      save my survey settings. I press the "save settings" but they
      don't take. Am I doing something wrong, or does this need a fix?
      
      Thanks
      
      Dwight
      
      On 1/28/2013 7:21 AM, Larry Fish wrote:
    
       
          
            Hi everybody,
              
              Many people have requested this feature and I've finally
              had the time to
              work on it. Compass now has the option of setting the LRUD
              associations on a
              survey-by-survey basis. Here is description of the new
              features:
              
              1. LRUD Associations. When Compass builds passage models
              it needs to
              associate the LRUDs with either the From Station or the To
              Station. In the
              past, Compass could only do this at the file level, which
              meant that every
              shot in every survey was handled the same way. Compass now
              has the option of
              a controlling LRUD Handling at the Survey Level. In other
              words, every
              Survey can associate the LRUDs differently. The Editor now
              allows you to set
              the option in the header of every survey.
              
              2. LRUD Tools. To aid in the process of converting files
              to the new system,
              Compass has new tools that allow you to set the LRUD
              Associations for large
              blocks of selected surveys all it once. 
              There are also new tools that allow you to shift the LRUDs
              forward or
              backwards one shots for selected surveys. This allows you
              fix surveys where
              the LRUDs were entered with the wrong station.
              
              3. Overriding LRUD Settings. You can override the
              survey-level LRUD Flags by
              changing the settings in the Project Manager. These
              "Override Settings" can
              be saved either to the MAK file or as the Project Manager
              Defaults.
              The version is the internet.
              
              Larry Fish
  
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2890 / Virus Database: 2639/6050 - Release Date: 01/22/13


Messsage #: 349
Date: Tue, 29 Jan 2013 03:38:21 -0700
From: "Larry Fish" 
Subject: RE: [compass-users] LRUD handling.

Hi Dwight,

I assume you were talking about the settings in the Editor. If so, I think
I've fixed the problem and also fixed another nasty bug that I found while
working on this issue. There is a new version of Compass on the internet
with these changes.

Also, be aware that saving the default settings is a bit complicated. This
is because the setting-values get saved with each survey so they can be
different depending on which file you load into the editor and which survey
you select within the editor. To change these options, you use the "Options
- Survey Settings" item from the menu bar.  When you save the file, the
settings will be saved with it. These settings are not saved using "Options
- Save Default User Settings" item on the menu bar.

There is also the default setting for new surveys. These options are set
using the "Options - Default Settings (for new surveys)" item from the menu
bar. These setting can be saved using the "Options - Save Default User
Settings" item on the menu bar. These will be the settings that are used
when the Editor is first run, but they will revert to a different set of
settings when you load a survey file. Even if you load a survey file and
change the settings, when you start a new survey, these default settings
that you previously saved will apply.

Let me know if you have any questions.

Larry  

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Dwight Livingston
Sent: Monday, January 28, 2013 4:48 PM
Subject: Re: [compass-users] LRUD handling.

Larry

Thanks for adding the new LRUD features. We will use them.

With that option a setting, I now have even more use for a way to save my
survey settings. I press the "save settings" but they don't take. Am I doing
something wrong, or does this need a fix?

Thanks

Dwight

On 1/28/2013 7:21 AM, Larry Fish wrote:

Hi everybody,

Many people have requested this feature and I've finally had the time to
work on it. Compass now has the option of setting the LRUD associations on a
survey-by-survey basis. Here is description of the new features:

1. LRUD Associations. When Compass builds passage models it needs to
associate the LRUDs with either the From Station or the To Station. In the
past, Compass could only do this at the file level, which meant that every
shot in every survey was handled the same way. Compass now has the option of
a controlling LRUD Handling at the Survey Level. In other words, every
Survey can associate the LRUDs differently. The Editor now allows you to set
the option in the header of every survey.

2. LRUD Tools. To aid in the process of converting files to the new system,
Compass has new tools that allow you to set the LRUD Associations for large
blocks of selected surveys all it once. 
There are also new tools that allow you to shift the LRUDs forward or
backwards one shots for selected surveys. This allows you fix surveys where
the LRUDs were entered with the wrong station.

3. Overriding LRUD Settings. You can override the survey-level LRUD Flags by
changing the settings in the Project Manager. These "Override Settings" can
be saved either to the MAK file or as the Project Manager Defaults.
The version is the internet.

Larry Fish

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2890 / Virus Database: 2639/6050 - Release Date: 01/22/13

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 350
Date: Tue, 29 Jan 2013 18:01:57 +0100
From: "Paul De Bie" 
Subject: RE: [compass-users] LRUD handling.

Hi Larry,

is the LRUD setting saved in the DAT or in the MAK file? 

tx

Paul De Bie
http://www.scavalon.be
http://scavalon.blogspot.com

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Larry Fish
Sent: Tuesday, January 29, 2013 11:38 AM
Subject: RE: [compass-users] LRUD handling.

Hi Dwight,

I assume you were talking about the settings in the Editor. If so, I think I've fixed the problem
and also fixed another nasty bug that I found while working on this issue. There is a new version of
Compass on the internet with these changes.

Also, be aware that saving the default settings is a bit complicated. This is because the
setting-values get saved with each survey so they can be different depending on which file you load
into the editor and which survey you select within the editor. To change these options, you use the
"Options - Survey Settings" item from the menu bar.  When you save the file, the settings will be
saved with it. These settings are not saved using "Options - Save Default User Settings" item on
the menu bar.

There is also the default setting for new surveys. These options are set using the "Options -
Default Settings (for new surveys)" item from the menu bar. These setting can be saved using the
"Options - Save Default User Settings" item on the menu bar. These will be the settings that are
used when the Editor is first run, but they will revert to a different set of settings when you load
a survey file. Even if you load a survey file and change the settings, when you start a new survey,
these default settings that you previously saved will apply.

Let me know if you have any questions.

Larry  

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Dwight
Livingston
Sent: Monday, January 28, 2013 4:48 PM
Subject: Re: [compass-users] LRUD handling.

Larry

Thanks for adding the new LRUD features. We will use them.

With that option a setting, I now have even more use for a way to save my survey settings. I press
the "save settings" but they don't take. Am I doing something wrong, or does this need a fix?

Thanks

Dwight

On 1/28/2013 7:21 AM, Larry Fish wrote:

Hi everybody,

Many people have requested this feature and I've finally had the time to
work on it. Compass now has the option of setting the LRUD associations on a
survey-by-survey basis. Here is description of the new features:

1. LRUD Associations. When Compass builds passage models it needs to
associate the LRUDs with either the From Station or the To Station. In the
past, Compass could only do this at the file level, which meant that every
shot in every survey was handled the same way. Compass now has the option of
a controlling LRUD Handling at the Survey Level. In other words, every
Survey can associate the LRUDs differently. The Editor now allows you to set
the option in the header of every survey.

2. LRUD Tools. To aid in the process of converting files to the new system,
Compass has new tools that allow you to set the LRUD Associations for large
blocks of selected surveys all it once. 
There are also new tools that allow you to shift the LRUDs forward or
backwards one shots for selected surveys. This allows you fix surveys where
the LRUDs were entered with the wrong station.

3. Overriding LRUD Settings. You can override the survey-level LRUD Flags by
changing the settings in the Project Manager. These "Override Settings" can
be saved either to the MAK file or as the Project Manager Defaults.
The version is the internet.

Larry Fish

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2890 / Virus Database: 2639/6050 - Release Date: 01/22/13

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 351
Date: Tue, 29 Jan 2013 13:48:57 -0700
From: "Larry Fish" 
Subject: RE: [compass-users] LRUD handling.

Hi Paul,

The individual settings are saved in the DAT file. Each survey header has a
flag that sets the LRUD associations for that survey, so each survey can
have a different setting.

There are also global settings that can override the individual survey
settings. When the override settings are enabled, Compass ignores the flags
for each survey and forces all the surveys to follow one setting. The
override flags are found in the MAK file so they affect all surveys that are
controlled by the MAK file.

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Paul De Bie
Sent: Tuesday, January 29, 2013 10:02 AM
Subject: RE: [compass-users] LRUD handling.

Hi Larry,

is the LRUD setting saved in the DAT or in the MAK file? 

tx

Paul De Bie
http://www.scavalon.be
http://scavalon.blogspot.com

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Larry Fish
Sent: Tuesday, January 29, 2013 11:38 AM
Subject: RE: [compass-users] LRUD handling.

Hi Dwight,

I assume you were talking about the settings in the Editor. If so, I think
I've fixed the problem and also fixed another nasty bug that I found while
working on this issue. There is a new version of Compass on the internet
with these changes.

Also, be aware that saving the default settings is a bit complicated. This
is because the setting-values get saved with each survey so they can be
different depending on which file you load into the editor and which survey
you select within the editor. To change these options, you use the "Options
- Survey Settings" item from the menu bar.  When you save the file, the
settings will be saved with it. These settings are not saved using "Options
- Save Default User Settings" item on the menu bar.

There is also the default setting for new surveys. These options are set
using the "Options - Default Settings (for new surveys)" item from the menu
bar. These setting can be saved using the "Options - Save Default User
Settings" item on the menu bar. These will be the settings that are used
when the Editor is first run, but they will revert to a different set of
settings when you load a survey file. Even if you load a survey file and
change the settings, when you start a new survey, these default settings
that you previously saved will apply.

Let me know if you have any questions.

Larry  

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Dwight Livingston
Sent: Monday, January 28, 2013 4:48 PM
Subject: Re: [compass-users] LRUD handling.

Larry

Thanks for adding the new LRUD features. We will use them.

With that option a setting, I now have even more use for a way to save my
survey settings. I press the "save settings" but they don't take. Am I doing
something wrong, or does this need a fix?

Thanks

Dwight

On 1/28/2013 7:21 AM, Larry Fish wrote:

Hi everybody,

Many people have requested this feature and I've finally had the time to
work on it. Compass now has the option of setting the LRUD associations on a
survey-by-survey basis. Here is description of the new features:

1. LRUD Associations. When Compass builds passage models it needs to
associate the LRUDs with either the From Station or the To Station. In the
past, Compass could only do this at the file level, which meant that every
shot in every survey was handled the same way. Compass now has the option of
a controlling LRUD Handling at the Survey Level. In other words, every
Survey can associate the LRUDs differently. The Editor now allows you to set
the option in the header of every survey.

2. LRUD Tools. To aid in the process of converting files to the new system,
Compass has new tools that allow you to set the LRUD Associations for large
blocks of selected surveys all it once. 
There are also new tools that allow you to shift the LRUDs forward or
backwards one shots for selected surveys. This allows you fix surveys where
the LRUDs were entered with the wrong station.

3. Overriding LRUD Settings. You can override the survey-level LRUD Flags by
changing the settings in the Project Manager. These "Override Settings" can
be saved either to the MAK file or as the Project Manager Defaults.
The version is the internet.

Larry Fish

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2890 / Virus Database: 2639/6050 - Release Date: 01/22/13

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 352
Date: Tue, 29 Jan 2013 22:31:30 +0100
From: "Paul De Bie" 
Subject: RE: [compass-users] LRUD handling.

OK thanks Larry. I'll have to study the changes since I have written a conversion tool to convert
from/to Compass DAT files. 

I suppose "old" DAT files are treated as before? 

Paul De Bie
http://www.scavalon.be
http://scavalon.blogspot.com

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Larry Fish
Sent: Tuesday, January 29, 2013 9:49 PM
Subject: RE: [compass-users] LRUD handling.

Hi Paul,

The individual settings are saved in the DAT file. Each survey header has a flag that sets the LRUD
associations for that survey, so each survey can have a different setting.

There are also global settings that can override the individual survey settings. When the override
settings are enabled, Compass ignores the flags for each survey and forces all the surveys to follow
one setting. The override flags are found in the MAK file so they affect all surveys that are
controlled by the MAK file.

Larry

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Paul De Bie
Sent: Tuesday, January 29, 2013 10:02 AM
Subject: RE: [compass-users] LRUD handling.

Hi Larry,

is the LRUD setting saved in the DAT or in the MAK file? 

tx

Paul De Bie
http://www.scavalon.be
http://scavalon.blogspot.com

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Larry Fish
Sent: Tuesday, January 29, 2013 11:38 AM
Subject: RE: [compass-users] LRUD handling.

Hi Dwight,

I assume you were talking about the settings in the Editor. If so, I think I've fixed the problem
and also fixed another nasty bug that I found while working on this issue. There is a new version of
Compass on the internet with these changes.

Also, be aware that saving the default settings is a bit complicated. This is because the
setting-values get saved with each survey so they can be different depending on which file you load
into the editor and which survey you select within the editor. To change these options, you use the
"Options - Survey Settings" item from the menu bar.  When you save the file, the settings will be
saved with it. These settings are not saved using "Options - Save Default User Settings" item on
the menu bar.

There is also the default setting for new surveys. These options are set using the "Options -
Default Settings (for new surveys)" item from the menu bar. These setting can be saved using the
"Options - Save Default User Settings" item on the menu bar. These will be the settings that are
used when the Editor is first run, but they will revert to a different set of settings when you load
a survey file. Even if you load a survey file and change the settings, when you start a new survey,
these default settings that you previously saved will apply.

Let me know if you have any questions.

Larry  

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Dwight
Livingston
Sent: Monday, January 28, 2013 4:48 PM
Subject: Re: [compass-users] LRUD handling.

Larry

Thanks for adding the new LRUD features. We will use them.

With that option a setting, I now have even more use for a way to save my survey settings. I press
the "save settings" but they don't take. Am I doing something wrong, or does this need a fix?

Thanks

Dwight

On 1/28/2013 7:21 AM, Larry Fish wrote:

Hi everybody,

Many people have requested this feature and I've finally had the time to
work on it. Compass now has the option of setting the LRUD associations on a
survey-by-survey basis. Here is description of the new features:

1. LRUD Associations. When Compass builds passage models it needs to
associate the LRUDs with either the From Station or the To Station. In the
past, Compass could only do this at the file level, which meant that every
shot in every survey was handled the same way. Compass now has the option of
a controlling LRUD Handling at the Survey Level. In other words, every
Survey can associate the LRUDs differently. The Editor now allows you to set
the option in the header of every survey.

2. LRUD Tools. To aid in the process of converting files to the new system,
Compass has new tools that allow you to set the LRUD Associations for large
blocks of selected surveys all it once. 
There are also new tools that allow you to shift the LRUDs forward or
backwards one shots for selected surveys. This allows you fix surveys where
the LRUDs were entered with the wrong station.

3. Overriding LRUD Settings. You can override the survey-level LRUD Flags by
changing the settings in the Project Manager. These "Override Settings" can
be saved either to the MAK file or as the Project Manager Defaults.
The version is the internet.

Larry Fish

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2890 / Virus Database: 2639/6050 - Release Date: 01/22/13

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 353
Date: Tue, 29 Jan 2013 15:43:41 -0700
From: "Larry Fish" 
Subject: RE: [compass-users] LRUD handling.

Hi Paul,

Yes, the old dat files are treated like they were before. If the LRUD
association flag is missing, the program defaults to having the LRUDs
associated with the From station. That can be overridden at the Project
Manager Level or at the MAK file level. If you load a survey, the program
will add the LRUD flag when save the survey. It will be set to whatever
settings you are currently using. You can set the individual flags for large
blocks of surveys in the editor. If you modify a MAK file, the override flag
will be added to the file. 

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Paul De Bie
Sent: Tuesday, January 29, 2013 2:32 PM
Subject: RE: [compass-users] LRUD handling.

OK thanks Larry. I'll have to study the changes since I have written a
conversion tool to convert from/to Compass DAT files. 

I suppose "old" DAT files are treated as before? 

Paul De Bie
http://www.scavalon.be
http://scavalon.blogspot.com

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Larry Fish
Sent: Tuesday, January 29, 2013 9:49 PM
Subject: RE: [compass-users] LRUD handling.

Hi Paul,

The individual settings are saved in the DAT file. Each survey header has a
flag that sets the LRUD associations for that survey, so each survey can
have a different setting.

There are also global settings that can override the individual survey
settings. When the override settings are enabled, Compass ignores the flags
for each survey and forces all the surveys to follow one setting. The
override flags are found in the MAK file so they affect all surveys that are
controlled by the MAK file.

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Paul De Bie
Sent: Tuesday, January 29, 2013 10:02 AM
Subject: RE: [compass-users] LRUD handling.

Hi Larry,

is the LRUD setting saved in the DAT or in the MAK file? 

tx

Paul De Bie
http://www.scavalon.be
http://scavalon.blogspot.com

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Larry Fish
Sent: Tuesday, January 29, 2013 11:38 AM
Subject: RE: [compass-users] LRUD handling.

Hi Dwight,

I assume you were talking about the settings in the Editor. If so, I think
I've fixed the problem and also fixed another nasty bug that I found while
working on this issue. There is a new version of Compass on the internet
with these changes.

Also, be aware that saving the default settings is a bit complicated. This
is because the setting-values get saved with each survey so they can be
different depending on which file you load into the editor and which survey
you select within the editor. To change these options, you use the "Options
- Survey Settings" item from the menu bar.  When you save the file, the
settings will be saved with it. These settings are not saved using "Options
- Save Default User Settings" item on the menu bar.

There is also the default setting for new surveys. These options are set
using the "Options - Default Settings (for new surveys)" item from the menu
bar. These setting can be saved using the "Options - Save Default User
Settings" item on the menu bar. These will be the settings that are used
when the Editor is first run, but they will revert to a different set of
settings when you load a survey file. Even if you load a survey file and
change the settings, when you start a new survey, these default settings
that you previously saved will apply.

Let me know if you have any questions.

Larry  

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Dwight Livingston
Sent: Monday, January 28, 2013 4:48 PM
Subject: Re: [compass-users] LRUD handling.

Larry

Thanks for adding the new LRUD features. We will use them.

With that option a setting, I now have even more use for a way to save my
survey settings. I press the "save settings" but they don't take. Am I doing
something wrong, or does this need a fix?

Thanks

Dwight

On 1/28/2013 7:21 AM, Larry Fish wrote:

Hi everybody,

Many people have requested this feature and I've finally had the time to
work on it. Compass now has the option of setting the LRUD associations on a
survey-by-survey basis. Here is description of the new features:

1. LRUD Associations. When Compass builds passage models it needs to
associate the LRUDs with either the From Station or the To Station. In the
past, Compass could only do this at the file level, which meant that every
shot in every survey was handled the same way. Compass now has the option of
a controlling LRUD Handling at the Survey Level. In other words, every
Survey can associate the LRUDs differently. The Editor now allows you to set
the option in the header of every survey.

2. LRUD Tools. To aid in the process of converting files to the new system,
Compass has new tools that allow you to set the LRUD Associations for large
blocks of selected surveys all it once. 
There are also new tools that allow you to shift the LRUDs forward or
backwards one shots for selected surveys. This allows you fix surveys where
the LRUDs were entered with the wrong station.

3. Overriding LRUD Settings. You can override the survey-level LRUD Flags by
changing the settings in the Project Manager. These "Override Settings" can
be saved either to the MAK file or as the Project Manager Defaults.
The version is the internet.

Larry Fish

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2890 / Virus Database: 2639/6050 - Release Date: 01/22/13

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 354
Date: Sat, 30 Mar 2013 22:52:49 -0400
From: "David A. Riggs" 
Subject: Editor Adding Binary Junk to Flags Field

Hello Larry,

I just updated to the latest Compass version from a 2011 release,
which was used to create this project's .MAK and .DAT files. When I
started adding new survey data, as I enter each shot, the editor is
adding progressively more and more junk binary data into the Flags
field.

I saved the .DAT (after making a safe copy first!) and examined it in
a hex editor; the Flags field for each shot starts with three null
bytes, followed by one additional binary byte for each shot, so that
each shot's Flags has one more byte count than the previous shot. I
can't discern a pattern in the binary bytes themselves after the three
null bytes.

If I delete all the bogus flags values in the editor, they ALL
reappear, with the same values as before, as soon as I add a new shot.

Screenshot:

  http://www.flickr.com/photos/driggs/8604108781/

It just so happens that I have a real flag set on the second shot in
that example, but if I delete all Flags, including the 'L', all the
junk ones are still recreated when I add a new shot.

Has my .DAT become corrupted somehow? Does my data need converted for
the new release? Have I triggered some new bug?

Thanks!

Dave Riggs
Morgantown, WV

David A. Riggs 


Messsage #: 355
Date: Sun, 31 Mar 2013 09:30:14 -0600


Messsage #: 356
From: "Allison, Stan" 
Subject: Re: [compass-users] Editor Adding Binary Junk to Flags Field

Hi Larry and David,

I noticed the same issue this morning when entering the some data. I was
able to fix the problem by setting all of the flags to blank and then
saving the file when I was done with data entry. I'll send Larry a PM with
some sample data.

Jô

On Sat, Mar 30, 2013 at 8:52 PM, David A. Riggs wrote:

 **

 Hello Larry,

 I just updated to the latest Compass version from a 2011 release,
 which was used to create this project's .MAK and .DAT files. When I
 started adding new survey data, as I enter each shot, the editor is
 adding progressively more and more junk binary data into the Flags
 field.

 I saved the .DAT (after making a safe copy first!) and examined it in
 a hex editor; the Flags field for each shot starts with three null
 bytes, followed by one additional binary byte for each shot, so that
 each shot's Flags has one more byte count than the previous shot. I
 can't discern a pattern in the binary bytes themselves after the three
 null bytes.

 If I delete all the bogus flags values in the editor, they ALL
 reappear, with the same values as before, as soon as I add a new shot.

 Screenshot:

 http://www.flickr.com/photos/driggs/8604108781/

 It just so happens that I have a real flag set on the second shot in
 that example, but if I delete all Flags, including the 'L', all the
 junk ones are still recreated when I add a new shot.

 Has my .DAT become corrupted somehow? Does my data need converted for
 the new release? Have I triggered some new bug?

 Thanks!

 Dave Riggs
 Morgantown, WV

 --
 David A. Riggs 

Hi Larry and David,I noticed the same issue this morning when entering the some data. I was able to fix the problem by setting all of the flags to blank and then saving the file when I was done with data entry. I'll send Larry a PM with some sample data.
Stan
On Sat, Mar 30, 2013 at 8:52 PM, David A. Riggs <[email protected]> wrote:

ˇ
      
      Hello Larry,

I just updated to the latest Compass version from a 2011 release,
which was used to create this project's .MAK and .DAT files. When I
started adding new survey data, as I enter each shot, the editor is
adding progressively more and more junk binary data into the Flags
field.

I saved the .DAT (after making a safe copy first!) and examined it in
a hex editor; the Flags field for each shot starts with three null
bytes, followed by one additional binary byte for each shot, so that
each shot's Flags has one more byte count than the previous shot. I
can't discern a pattern in the binary bytes themselves after the three
null bytes.

If I delete all the bogus flags values in the editor, they ALL
reappear, with the same values as before, as soon as I add a new shot.

Screenshot:

http://www.flickr.com/photos/driggs/8604108781/

It just so happens that I have a real flag set on the second shot in
that example, but if I delete all Flags, including the 'L', all the
junk ones are still recreated when I add a new shot.

Has my .DAT become corrupted somehow? Does my data need converted for
the new release? Have I triggered some new bug?

Thanks!

Dave Riggs
Morgantown, WV

David A. Riggs <[email protected]>


Messsage #: 357
Date: Sun, 31 Mar 2013 12:24:00 -0400
From: "David A. Riggs" 
Subject: Re: [compass-users] Editor Adding Binary Junk to Flags Field

On Sun, Mar 31, 2013 at 11:30 AM, Allison, Stan  wrote:

 I noticed the same issue this morning when entering the some data. I was able to fix the problem by setting all of the flags to blank and then saving the file when I was done with data entry. I'll send Larry a PM with some sample data.

Hi Stan!

Thanks for confirming that I'm not crazy! I also sent Larry my .DAT
file off-list.

Setting the Flags to blank didn't work for me. I wound up opening the
.DAT file in a text editor (outside of Compass) and manually removing
all the junk characters between #| ... #. Then when I re-opened the
project and compiled it, all was well. I did confirm that even after
this fix, when I add a new shot in the survey editor, it re-creates
all that binary junk again!

- DR

David A. Riggs 


Messsage #: 358
Date: Sun, 31 Mar 2013 18:04:33 -0400 (EDT)
From: [email protected]
Subject: Re: [compass-users] Editor Adding Binary Junk to Flags Field

Hi Everyone,

I Just wanted to let you know that I won't be able to respond to this
problem for a while. Last week I fell while riding my bike; the front
wheel slipped off the concrete bike path and into a grove in the dirt
which locked the wheel and threw me hard on to concrete. The result was
that I fractured my pelvis. It is not a bad fracture and they expect it to
heal in about six weeks without any special treatment. However, for the
moment it is still quite painful and I have to walk with a walker. That
means I can't get up the stairs to my office where my work computer is
and, since I don't have any of my programming tools on the other
computers, I can't look at this problem. At the rate that I've been
healing, I'd guess that it would be another couple weeks before I can dig
into the problem.

From the descriptions, it will probably be easy to fix. I suspect that I
introduced a bug when I made some recent changes.

Thank for all the feedback; it is really helpful for finding and fixing
problems like this.

Larry

 On Sun, Mar 31, 2013 at 11:30 AM, Allison, Stan 
 wrote:

 I noticed the same issue this morning when entering the some data. I was
 able to fix the problem by setting all of the flags to blank and then
 saving the file when I was done with data entry. I'll send Larry a PM
 with some sample data.

 Hi Stan!

 Thanks for confirming that I'm not crazy! I also sent Larry my .DAT
 file off-list.

 Setting the Flags to blank didn't work for me. I wound up opening the
 .DAT file in a text editor (outside of Compass) and manually removing
 all the junk characters between #| ... #. Then when I re-opened the
 project and compiled it, all was well. I did confirm that even after
 this fix, when I add a new shot in the survey editor, it re-creates
 all that binary junk again!

 - DR

 --
 David A. Riggs 


Messsage #: 359
Date: Wed, 3 Apr 2013 14:51:45 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] Editor Adding Binary Junk to Flags Field

Hi Dave and Stan,

I finally managed to make it up the stairs and access my work computer. I've
solved the problem where the garbage data appeared in the Flags Column.
There is a new version on the internet. 

My sitting time limited, to so I didn't have a lot of time to thoroughly
test it, so please check it and make sure everything is working properly.

Thanks

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Saturday, March 30, 2013 8:53 PM
Subject: [compass-users] Editor Adding Binary Junk to Flags Field

Hello Larry,

I just updated to the latest Compass version from a 2011 release,
which was used to create this project's .MAK and .DAT files. When I
started adding new survey data, as I enter each shot, the editor is
adding progressively more and more junk binary data into the Flags
field.

I saved the .DAT (after making a safe copy first!) and examined it in
a hex editor; the Flags field for each shot starts with three null
bytes, followed by one additional binary byte for each shot, so that
each shot's Flags has one more byte count than the previous shot. I
can't discern a pattern in the binary bytes themselves after the three
null bytes.

If I delete all the bogus flags values in the editor, they ALL
reappear, with the same values as before, as soon as I add a new shot.

Screenshot:

http://www.flickr.com/photos/driggs/8604108781/

It just so happens that I have a real flag set on the second shot in
that example, but if I delete all Flags, including the 'L', all the
junk ones are still recreated when I add a new shot.

Has my .DAT become corrupted somehow? Does my data need converted for
the new release? Have I triggered some new bug?

Thanks!

Dave Riggs
Morgantown, WV

David A. Riggs 

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 360
Date: Wed, 03 Apr 2013 17:59:05 -0400
From: Tony Canike 
Subject: Re: [compass-users] Editor Adding Binary Junk to Flags Field

Thanks Larry!  Hope you heal up quick!

Larry Fish wrote:

 Hi Dave and Stan,

 I finally managed to make it up the stairs and access my work 
 computer. I've solved the problem where the garbage data appeared in 
 the Flags Column. There is a new version on the internet.

 My sitting time limited, to so I didn't have a lot of time to 
 thoroughly test it, so please check it and make sure everything is 
 working properly.

 Thanks

 Larry

 ------------------------------------------------------------------------

 *From:*[email protected] 
 [mailto:[email protected]] *On Behalf Of *David A. Riggs
 *Sent:* Saturday, March 30, 2013 8:53 PM
 *To:* [email protected]
 *Subject:* [compass-users] Editor Adding Binary Junk to Flags Field

 Hello Larry,

 I just updated to the latest Compass version from a 2011 release,
 which was used to create this project's .MAK and .DAT files. When I
 started adding new survey data, as I enter each shot, the editor is
 adding progressively more and more junk binary data into the Flags
 field.

 I saved the .DAT (after making a safe copy first!) and examined it in
 a hex editor; the Flags field for each shot starts with three null
 bytes, followed by one additional binary byte for each shot, so that
 each shot's Flags has one more byte count than the previous shot. I
 can't discern a pattern in the binary bytes themselves after the three
 null bytes.

 If I delete all the bogus flags values in the editor, they ALL
 reappear, with the same values as before, as soon as I add a new shot.

 Screenshot:

 http://www.flickr.com/photos/driggs/8604108781/

 It just so happens that I have a real flag set on the second shot in
 that example, but if I delete all Flags, including the 'L', all the
 junk ones are still recreated when I add a new shot.

 Has my .DAT become corrupted somehow? Does my data need converted for
 the new release? Have I triggered some new bug?

 Thanks!

 Dave Riggs
 Morgantown, WV

 --
 David A. Riggs  
  
    Thanks Larry!  Hope you heal up quick!
    
    Larry Fish wrote:
    
       
            
              Hi Dave and
                    Stan,
               
              I finally
                    managed to make it up the stairs
                    and access my work computer. I’ve solved the problem
                    where the garbage
                    data appeared in the Flags Column. There is a new
                    version on the internet. 
               
              My sitting
                    time limited, to so I didn’t
                    have a lot of time to thoroughly test it, so please
                    check it and make sure
                    everything is working properly.
               
              Thanks
               
              Larry
               
                    
                From: [email protected]
                      [mailto:[email protected]]
                      On Behalf Of David
                      A. Riggs
                      Sent:
                      Saturday, March 30, 2013
                      8:53 PM
                      To:
                      [email protected]
                      Subject:
                      [compass-users] Editor
                      Adding Binary Junk to Flags Field
              
               
                
                  
                    Hello
                          Larry,
                          
                          I just updated to the latest Compass version
                          from a 2011 release,
                          which was used to create this project's .MAK
                          and .DAT files. When I
                          started adding new survey data, as I enter
                          each shot, the editor is
                          adding progressively more and more junk binary
                          data into the Flags
                          field.
                          
                          I saved the .DAT (after making a safe copy
                          first!) and examined it in
                          a hex editor; the Flags field for each shot
                          starts with three null
                          bytes, followed by one additional binary byte
                          for each shot, so that
                          each shot's Flags has one more byte count than
                          the previous shot. I
                          can't discern a pattern in the binary bytes
                          themselves after the three
                          null bytes.
                          
                          If I delete all the bogus flags values in the
                          editor, they ALL
                          reappear, with the same values as before, as
                          soon as I add a new shot.
                          
                          Screenshot:
                          
                          http://www.flickr.com/photos/driggs/8604108781/
                          
                          It just so happens that I have a real flag set
                          on the second shot in
                          that example, but if I delete all Flags,
                          including the 'L', all the
                          junk ones are still recreated when I add a new
                          shot.
                          
                          Has my .DAT become corrupted somehow? Does my
                          data need converted for
                          the new release? Have I triggered some new
                          bug?
                          
                          Thanks!
                          
                          Dave Riggs
                          Morgantown, WV
                          
                          --
                          David A. Riggs <[email protected]>


Messsage #: 361
Date: Wed, 3 Apr 2013 20:29:25 -0700 (PDT)
From: Tom 
Subject: Re: [compass-users]

Larry,
hope you feel better and heal well. 
Tom

Larry,hope you feel better and heal well. Tom


Messsage #: 362
Date: Fri, 5 Apr 2013 12:03:59 -0400
From: "David A. Riggs" 
Subject: Re: [compass-users] Editor Adding Binary Junk to Flags Field

On Wed, Apr 3, 2013 at 4:51 PM, Larry Fish  wrote:

 I finally managed to make it up the stairs and access my work computer. I've solved the problem where the garbage data appeared in the Flags Column. There is a new version on the internet.

 My sitting time limited, to so I didn't have a lot of time to thoroughly test it, so please check it and make sure everything is working properly.

Hi Larry,

I did a quick test with the new version, and can confirm that it is no
longer adding junk flags when I add new shots to my fixed .DAT file. I
don't know what it would have done had I not already fixed my .DAT
file with a text editor, however.

Thanks so much, and I hope you heal up quickly!

- DR

David A. Riggs 


Messsage #: 363
Date: Fri, 5 Apr 2013 14:49:48 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] Editor Adding Binary Junk to Flags Field

David,

 I did a quick test with the new version, and can confirm
 that it is no longer adding junk flags when I add new shots
 to my fixed .DAT file. I don't know what it would have done
 had I not already fixed my .DAT file with a text editor,
 however.

I think it is probably fixed. I was able to track the problem down to a
specific variable. I had expected the variable to be empty, but sometimes it
would have garbage in it. I now explicitly clear the variable so it can't
have garbage in it.

The only question was "why did this suddenly show up now?" The code in that
section hasn't changed in years. I think I know the answer and I'm pretty
sure everything is completely fixed but there is always the possibility that
I've overlooked something.

Larry


Messsage #: 364
Date: Sun, 07 Apr 2013 20:38:36 -0000
From: "Tom" 
Subject: Re: To convert again... Auriga

has there been any progress on this? Is this the only way to convert?
Or is there another way already done? I looked at RosettaStal which would be a long way around to convert, I think?
Tom

 Hi Jean,
 
 I thought maybe Christian or Luc would see your post and have an answer.
 Since they haven't responded and since I don't have any direct experience
 with Auriga, you probably should contact them directly. There is contact
 information here:
 
   http://www.speleo.qc.ca/auriga/
 
 There is an Auriga users group on the web and the both Christian and Luc's
 email address are also available at the very bottom of the page.
 
 Larry Fish
 
   _____  
 
 From: [email protected] [mailto:[email protected]]
 On Behalf Of Jean Sept
 Sent: Tuesday, August 21, 2012 3:13 AM
 To: [email protected]
 Subject: [compass-users] To convert again... Auriga
 
 Hi,
 
 step by step, bug after bug, my VBA macro seems now to work at about 90 %
 ...
 Anyway, it is not possible to reach 100 % because some features are
 different and can not be converted.
 I don't know if I will go ahead to generate also the .MAK file to solve the
 question of the fixed point...
 
 But now, I want to make another step and convert the compass data to Auriga
 (to use it on a palm).
 For this, the only way is to go through the conduit developped by Christian
 Chenier. But I have two kind of results :
 the first one is to get a file with nothing inside
 the second is to get a huge number of orphelines
 
 Do somebody here have some experience about it ?
 
 Recent Activity: 
 
 *
  9TAzk3MzU5NzE0BGdycElkAzE3MTMxMDMzBGdycHNwSWQDMTcwNTkwNTczMARzZWMDdnRsBHNsaw
 N2bWJycwRzdGltZQMxMzQ1MTg1NDEx?o=6 New Members 1 
  
  U5NzE0BGdycElkAzE3MTMxMDMzBGdycHNwSWQDMTcwNTkwNTczMARzZWMDdnRsBHNsawN2Z2hwBH
 N0aW1lAzEzNDUxODU0MTE- Visit Your Group 
  
  TMxMDMzBGdycHNwSWQDMTcwNTkwNTczMARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTM0NTE4NTQxM
 Q-- Yahoo! Groups
 
 Switch to:
  20Format:%20Traditional Text-Only,
  est Daily Digest .
 
 Unsubscribe .   Terms of Use
 
 .


Messsage #: 365
Date: Sun, 7 Apr 2013 17:19:51 -0400
From: Luc Le Blanc 
Subject: Re: [compass-users] Re: To convert again... Auriga

Hi,

Since last December, Auriga imports/exports Compass files to/from the
memory card on the PDA. Conversion rules are explained in the
reference manual.

Auriga also runs on Android devices thanks to the StyleTap PalmOS
emulator (50$).

Comments, suggestions are welcome. Bug reports get promptly handled.

Luc Le Blanc
http://www.speleo.qc.ca/Auriga

2013/4/7 Tom :
 has there been any progress on this? Is this the only way to convert?
 Or is there another way already done? I looked at RosettaStal which would be a long way around to convert, I think?
 Tom

 --- In [email protected], "Larry Fish"  wrote:

 Hi Jean,

 I thought maybe Christian or Luc would see your post and have an answer.
 Since they haven't responded and since I don't have any direct experience
 with Auriga, you probably should contact them directly. There is contact
 information here:

   http://www.speleo.qc.ca/auriga/

 There is an Auriga users group on the web and the both Christian and Luc's
 email address are also available at the very bottom of the page.

 Larry Fish

   _____

 From: [email protected] [mailto:[email protected]]
 On Behalf Of Jean Sept
 Sent: Tuesday, August 21, 2012 3:13 AM
 To: [email protected]
 Subject: [compass-users] To convert again... Auriga

 Hi,

 step by step, bug after bug, my VBA macro seems now to work at about 90 %
 ...
 Anyway, it is not possible to reach 100 % because some features are
 different and can not be converted.
 I don't know if I will go ahead to generate also the .MAK file to solve the
 question of the fixed point...

 But now, I want to make another step and convert the compass data to Auriga
 (to use it on a palm).
 For this, the only way is to go through the conduit developped by Christian
 Chenier. But I have two kind of results :
 the first one is to get a file with nothing inside
 the second is to get a huge number of orphelines

 Do somebody here have some experience about it ?


Messsage #: 366
Date: Mon, 8 Apr 2013 08:22:05 -0700 (PDT)
From: Tom 
Subject: Re: [compass-users] Re: To convert again... Auriga

Thank-you.
I had looked in the manual and now realize I had an old version. The software version I have loaded is 2.07.ˇ 

From: Luc Le Blanc 
Subject: Re: [compass-users] Re: To convert again... Auriga
Date: Sunday, April 7, 2013, 2:19 PM

Hi,

Since last December, Auriga imports/exports Compass files to/from the
memory card on the PDA. Conversion rules are explained in the
reference manual.

Auriga also runs on Android devices thanks to the StyleTap PalmOS
emulator (50$).

Comments, suggestions are welcome. Bug reports get promptly handled.

Luc Le Blanc
http://www.speleo.qc.ca/Auriga

2013/4/7 Tom :
 has there been any progress on this? Is this the only way to convert?
 Or is there another way already done? I looked at RosettaStal which would be a long way around to convert, I think?
 Tom

 --- In [email protected], "Larry Fish"  wrote:

 Hi Jean,

 I thought maybe Christian or Luc would see your post and have an answer.
 Since they haven't responded and since I don't have any direct experience
 with Auriga, you probably should contact them directly. There is contact
 information here:

ˇ  http://www.speleo.qc.ca/auriga/

 There is an Auriga users group on the web and the both Christian and Luc's
 email address are also available at the very bottom of the page.

 Larry Fish

ˇˇˇ_____

 From: [email protected] [mailto:[email protected]]
 On Behalf Of Jean Sept
 Sent: Tuesday, August 21, 2012 3:13 AM
 To: [email protected]
 Subject: [compass-users] To convert again... Auriga

 Hi,

 step by step, bug after bug, my VBA macro seems now to work at about 90 %
 ...
 Anyway, it is not possible to reach 100 % because some features are
 different and can not be converted.
 I don't know if I will go ahead to generate also the .MAK file to solve the
 question of the fixed point...

 But now, I want to make another step and convert the compass data to Auriga
 (to use it on a palm).
 For this, the only way is to go through the conduit developped by Christian
 Chenier. But I have two kind of results :
 the first one is to get a file with nothing inside
 the second is to get a huge number of orphelines

 Do somebody here have some experience about it ?

Yahoo! Groups Links

Thank-you.I had looked in the manual and now realize I had an old version. The software version I have loaded is 2.07.  --- On Sun, 4/7/13, Luc Le Blanc <[email protected]> wrote:From: Luc Le Blanc <[email protected]>Subject: Re: [compass-users] Re: To convert again... AurigaTo: [email protected]: Sunday, April 7, 2013, 2:19 PMHi,Since last December, Auriga imports/exports Compass files to/from thememory card on the PDA. Conversion rules are explained in thereference manual.Auriga also runs on Android devices thanks to the StyleTap PalmOSemulator (50$).Comments, suggestions are welcome. Bug reports get promptly
 handled.-- Luc Le Blanchttp://www.speleo.qc.ca/Auriga2013/4/7 Tom <[email protected]>:> has there been any progress on this? Is this the only way to convert?> Or is there another way already done? I looked at RosettaStal which would be a long way around to convert, I think?> Tom>>> --- In [email protected], "Larry Fish" <[email protected]> wrote:>>>> Hi Jean,>>>>>>>> I thought maybe Christian or Luc would see your post and have an answer.>> Since they haven't responded and since I don't have any direct experience>> with Auriga, you probably
 should contact them directly. There is contact>> information here:>>>>>>>>  <http://www.speleo.qc.ca/auriga/> http://www.speleo.qc.ca/auriga/>>>>>>>> There is an Auriga users group on the web and the both Christian and Luc's>> email address are also available at the very bottom of the page.>>>>>>>> Larry Fish>>>>>>>>   _____>>>> From: [email protected] [mailto:[email protected]]>> On Behalf Of Jean Sept>> Sent: Tuesday, August 21, 2012 3:13 AM>> To: [email protected]>> Subject: [compass-users] To convert again... Auriga>>>>>>>>>>>> Hi,>>>> step by step, bug after bug, my VBA macro seems now to work at about 90 %>> ...>> Anyway, it is not possible to reach 100 % because some features are>> different and can not be converted.>> I don't know if I will go ahead to generate also the .MAK file to solve the>> question of the fixed point...>>>> But now, I want to make another step and convert the compass data to Auriga>> (to use it on a
 palm).>> For this, the only way is to go through the conduit developped by Christian>> Chenier. But I have two kind of results :>> the first one is to get a file with nothing inside>> the second is to get a huge number of orphelines>>>> Do somebody here have some experience about it ?-----------------ur group on the web, go to:    http://groups.yahoo.com/group/compass-users/<*> Your email settings:    Individual Email | Traditional<*> To change settings online go to:    http://groups.yahoo.com/group/compass-users/join    (Yahoo! ID required)<*> To change
 settings via email:    [email protected]     [email protected]<*> To unsubscribe from this group, send an email to:    [email protected]<*> Your use of Yahoo! Groups is subject to:    http://docs.yahoo.com/info/terms/


Messsage #: 367
Date: Mon, 8 Apr 2013 11:32:32 -0400
From: Luc Le Blanc 
Subject: Re: [compass-users] Re: To convert again... Auriga

2013/4/8 Tom 

 Thank-you.
 I had looked in the manual and now realize I had an old version.
 The software version I have loaded is 2.07.

Subscribe to the spam-free Auriga e-mail list and you'll be notified
of new versions.

I forgot to mention this import feature also applies to Toporobot and
VisualTopo, while the export feature also targets Survex, Therion and
Walls. Next version will add sketches to the Therion export.

Luc Le Blanc
http://www.speleo.qc.ca/Auriga


Messsage #: 368
Date: Mon, 08 Apr 2013 18:21:37 +0200
From: Martin Sluka 
Subject: Re: [compass-users] To convert again... Auriga

Thanx

Martin

Apr 8, 2013 v 5:32 PM, Luc Le Blanc :

 export feature also targets Survex, Therion and
 Walls. Next version will add sketches to the Therion export.

Martin Sluka - Studio Sluka

prodej HahnemĀhle DFA 
tisk fotografi° a reprodukc°

Na Rovnosti 2692/21
130 00 Praha 3
tel.: +420 603513640
mail: [email protected]
web: http://www.piezografie.cz

ThanxMartinApr 8, 2013 v 5:32 PM, Luc Le Blanc <[email protected]>:export feature also targets Survex, Therion andWalls. Next version will add sketches to the Therion export.
Martin Sluka - Studio Slukaprodej HahnemĀhle DFA tisk fotografi° a reprodukc°Na Rovnosti 2692/21130 00 Praha 3tel.: +420 603513640mail: [email protected]: http://www.piezografie.cz


Messsage #: 369
Date: Sun, 28 Apr 2013 20:42:46 -0000
From: "Tom" 
Subject: importing Winkarst files into Compass

Larry,
I have Winkart files I would like to import into Compass. I have tried using Winkarst to save as Compass files and save as SEF files, but they both import with errors. Compass stops listing errors after 25 lines so I can't go through one by one and correct them and frankly don't want to do it that way. And I don't want to hand enter everything obviously.
 
How can I accomplish this best? 
thanks,
Tom


Messsage #: 370
Date: Mon, 29 Apr 2013 04:23:45 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] importing Winkarst files into Compass

Hi Tom,

It is unclear from your description whether the problem is with the format
of the data or with the data itself. 

Format Errors: These errors would occur because WinKarst exports the surveys
so that data format doesn't exactly match the Compass format. This will
cause Compass to miss data items or misinterpret them.

Data Errors. With these kinds of errors, Compass can read the data correctly
but Compass cannot assemble the data into a connected set of passages. This
is usually caused by organizational problems having to do with the order the
surveys and shots.

From your description, it sounds like the problem is probably an
organizational issue, however I can't be sure without knowing more about the
error messages you received.

If you want, you can send me copies of the data and I can fix it. I've got
lots of tools that make it easy for me to do. (You don't need to worry about
your data. I've never give out data or any information about the caves I
have unless I've been told specifically that I can do so.)

You can email the data to me. My regular email address should appear in the
header of this email. I won't post it in the body of this email because the
body of these emails appear on the internet and the email address will get
harvested by SPAMers. If you can't find the email address, use the on line
form to contact me and I will send you the email address you should use.
Here is a link to the online form:

http://www.fountainware.com/compass/CompassContact/CompassContact.php

If you decide to send me the data, I'd prefer the Compass or SEF data since
I don't have current versions of WinKarst installed on my computer. Also,
please give me as much information as you can about the cave, particularly
if it is large and complicated. If the problem with the data is
organizational, I may have to reorganize things to get it work.

Let me know if you have any more questions or thoughts.

Larry

________________________________________
From: [email protected] [mailto:[email protected]]
On Behalf Of Tom
Sent: Sunday, April 28, 2013 2:43 PM
Subject: [compass-users] importing Winkarst files into Compass

ˇ 
Larry,
I have Winkart files I would like to import into Compass. I have tried using
Winkarst to save as Compass files and save as SEF files, but they both
import with errors. Compass stops listing errors after 25 lines so I can't
go through one by one and correct them and frankly don't want to do it that
way. And I don't want to hand enter everything obviously.

How can I accomplish this best? 
thanks,
Tom


Messsage #: 371
Date: Mon, 29 Apr 2013 11:05:15 -0700 (PDT)
From: Tom 
Subject: RE: [compass-users] importing Winkarst files into Compass

Hi Larry, 
Thanks. 
From your reply I would say it is both format and data errors.
Compass couldn't handle aliases and also had errors with passage shots. Is there a way to produce a full error logfile?

I can/will send you both sef and compass exports from winkarst. I think in the end I want to do it myself, so if you figure it out and tell me what is going on...

I liked winkarst because I could use notepad ++ to edit raw files. I would like to do that in compass also, because I think it would be faster than using the compass GUI.

Thanks again.

On Mon, Apr 29, 2013 3:23 AM PDT Larry Fish wrote:

Hi Tom,

It is unclear from your description whether the problem is with the format
of the data or with the data itself. 

Format Errors: These errors would occur because WinKarst exports the surveys
so that data format doesnÉ?Tt exactly match the Compass format. This will
cause Compass to miss data items or misinterpret them.

Data Errors. With these kinds of errors, Compass can read the data correctly
but Compass cannot assemble the data into a connected set of passages. This
is usually caused by organizational problems having to do with the order the
surveys and shots.

From your description, it sounds like the problem is probably an
organizational issue, however I can't be sure without knowing more about the
error messages you received.

If you want, you can send me copies of the data and I can fix it. I've got
lots of tools that make it easy for me to do. (You don't need to worry about
your data. I've never give out data or any information about the caves I
have unless I've been told specifically that I can do so.)

You can email the data to me. My regular email address should appear in the
header of this email. I won't post it in the body of this email because the
body of these emails appear on the internet and the email address will get
harvested by SPAMers. If you can't find the email address, use the on line
form to contact me and I will send you the email address you should use.
Here is a link to the online form:

http://www.fountainware.com/compass/CompassContact/CompassContact.php

If you decide to send me the data, I'd prefer the Compass or SEF data since
I don't have current versions of WinKarst installed on my computer. Also,
please give me as much information as you can about the cave, particularly
if it is large and complicated. If the problem with the data is
organizational, I may have to reorganize things to get it work.

Let me know if you have any more questions or thoughts.

Larry

________________________________________
From: [email protected] [mailto:[email protected]]
On Behalf Of Tom
Sent: Sunday, April 28, 2013 2:43 PM
To: [email protected]
Subject: [compass-users] importing Winkarst files into Compass

Aˇ 
Larry,
I have Winkart files I would like to import into Compass. I have tried using
Winkarst to save as Compass files and save as SEF files, but they both
import with errors. Compass stops listing errors after 25 lines so I can't
go through one by one and correct them and frankly don't want to do it that
way. And I don't want to hand enter everything obviously.

How can I accomplish this best? 
thanks,
Tom

------------------------------------

Yahoo! Groups Links


Messsage #: 372
Date: Mon, 29 Apr 2013 11:05:17 -0700 (PDT)
From: Tom 
Subject: RE: [compass-users] importing Winkarst files into Compass

Hi Larry, 
Thanks. 
From your reply I would say it is both format and data errors.
Compass couldn't handle aliases and also had errors with passage shots. Is there a way to produce a full error logfile?

I can/will send you both sef and compass exports from winkarst. I think in the end I want to do it myself, so if you figure it out and tell me what is going on...

I liked winkarst because I could use notepad ++ to edit raw files. I would like to do that in compass also, because I think it would be faster than using the compass GUI.

Thanks again.

On Mon, Apr 29, 2013 3:23 AM PDT Larry Fish wrote:

Hi Tom,

It is unclear from your description whether the problem is with the format
of the data or with the data itself. 

Format Errors: These errors would occur because WinKarst exports the surveys
so that data format doesnÉ?Tt exactly match the Compass format. This will
cause Compass to miss data items or misinterpret them.

Data Errors. With these kinds of errors, Compass can read the data correctly
but Compass cannot assemble the data into a connected set of passages. This
is usually caused by organizational problems having to do with the order the
surveys and shots.

From your description, it sounds like the problem is probably an
organizational issue, however I can't be sure without knowing more about the
error messages you received.

If you want, you can send me copies of the data and I can fix it. I've got
lots of tools that make it easy for me to do. (You don't need to worry about
your data. I've never give out data or any information about the caves I
have unless I've been told specifically that I can do so.)

You can email the data to me. My regular email address should appear in the
header of this email. I won't post it in the body of this email because the
body of these emails appear on the internet and the email address will get
harvested by SPAMers. If you can't find the email address, use the on line
form to contact me and I will send you the email address you should use.
Here is a link to the online form:

http://www.fountainware.com/compass/CompassContact/CompassContact.php

If you decide to send me the data, I'd prefer the Compass or SEF data since
I don't have current versions of WinKarst installed on my computer. Also,
please give me as much information as you can about the cave, particularly
if it is large and complicated. If the problem with the data is
organizational, I may have to reorganize things to get it work.

Let me know if you have any more questions or thoughts.

Larry

________________________________________
From: [email protected] [mailto:[email protected]]
On Behalf Of Tom
Sent: Sunday, April 28, 2013 2:43 PM
To: [email protected]
Subject: [compass-users] importing Winkarst files into Compass

Aˇ 
Larry,
I have Winkart files I would like to import into Compass. I have tried using
Winkarst to save as Compass files and save as SEF files, but they both
import with errors. Compass stops listing errors after 25 lines so I can't
go through one by one and correct them and frankly don't want to do it that
way. And I don't want to hand enter everything obviously.

How can I accomplish this best? 
thanks,
Tom

------------------------------------

Yahoo! Groups Links


Messsage #: 373
Date: Mon, 29 Apr 2013 20:10:17 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] importing Winkarst files into Compass

Hi Tom,

I've added a feature to Compass that allows you to turn off the 25-item
limit on errors. There is now a checkbox at the top of the error list titled
"Truncate Error List." If you uncheck the box, it will show you all the
errors. The new version is posted here:

http://fountainware.com/compass/downloads/download.htm

Compass files can also be edited manually like Karst Files can. In fact, the
Karst file format is based on the Compass format. Back in the early 80's
Gary lived in Denver and at the time, Compass was an Apple-Only program.
Gary wanted to port it to the PC and so I gave him copies of the Compass
source code, so originally Karst and Compass had the same file format. Of
course the formats took different directions long ago.

Here is a description of the Compass file format:

http://www.fountainware.com/compass/HTML_Help/Compass_Editor/surveyfileforma
t.htm

The biggest problem with using Notepad to edit Compass files, is that
Compass uses Form-Feeds (Control-L) to separate surveys. Notepad will not
allow you to enter those characters directly from the keyboard, although you
can scoop one up using the clipboard and paste it into place.

A better choice would be XEdit, which is a notepad-like text editor that I
wrote many years ago. It allows you see and enter control characters such as
Form-Feeds/Ctrl-Ls. It has lots of Macro capabilities and it doesn't add any
additional formatting like other editors can do. Of course any additional
formatting, like inserting or removing Hard Returns, can corrupt a Compass
file. XEdit is free. You can get a copy here:

http://www.fountainware.com/Products/xedit/index.htm

Let me know if you have any questions.

Larry

________________________________________

From: [email protected] [mailto:[email protected]]
On Behalf Of Tom

Sent: Monday, April 29, 2013 12:05 PM

Subject: RE: [compass-users] importing Winkarst files into Compass

Hi Larry, 

Thanks. 

From your reply I would say it is both format and data errors.

Compass couldn't handle aliases and also had errors with passage shots. Is
there a way to produce a full error logfile?

I can/will send you both sef and compass exports from winkarst. I think in
the end I want to do it myself, so if you figure it out and tell me what is
going on...

I liked winkarst because I could use notepad ++ to edit raw files. I would
like to do that in compass also, because I think it would be faster than
using the compass GUI.

Thanks again.

On Mon, Apr 29, 2013 3:23 AM PDT Larry Fish wrote:

Hi Tom,

It is unclear from your description whether the problem is with the format

of the data or with the data itself. 

Format Errors: These errors would occur because WinKarst exports the
surveys

so that data format doesn't exactly match the Compass format. This will

cause Compass to miss data items or misinterpret them.

Data Errors. With these kinds of errors, Compass can read the data
correctly

but Compass cannot assemble the data into a connected set of passages. This

is usually caused by organizational problems having to do with the order
the

surveys and shots.

From your description, it sounds like the problem is probably an

organizational issue, however I can't be sure without knowing more about
the

error messages you received.

If you want, you can send me copies of the data and I can fix it. I've got

lots of tools that make it easy for me to do. (You don't need to worry
about

your data. I've never give out data or any information about the caves I

have unless I've been told specifically that I can do so.)

You can email the data to me. My regular email address should appear in the

header of this email. I won't post it in the body of this email because the

body of these emails appear on the internet and the email address will get

harvested by SPAMers. If you can't find the email address, use the on line

form to contact me and I will send you the email address you should use.

Here is a link to the online form:

http://www.fountainware.com/compass/CompassContact/CompassContact.php

If you decide to send me the data, I'd prefer the Compass or SEF data since

I don't have current versions of WinKarst installed on my computer. Also,

please give me as much information as you can about the cave, particularly

if it is large and complicated. If the problem with the data is

organizational, I may have to reorganize things to get it work.

Let me know if you have any more questions or thoughts.

Larry

________________________________________

From: [email protected] [mailto:[email protected]]

On Behalf Of Tom

Sent: Sunday, April 28, 2013 2:43 PM

To: [email protected]

Subject: [compass-users] importing Winkarst files into Compass

Larry,

I have Winkart files I would like to import into Compass. I have tried
using

Winkarst to save as Compass files and save as SEF files, but they both

import with errors. Compass stops listing errors after 25 lines so I can't

go through one by one and correct them and frankly don't want to do it that

way. And I don't want to hand enter everything obviously.

How can I accomplish this best? 

thanks,

Tom

------------------------------------

Yahoo! Groups Links

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 374
Date: Tue, 30 Apr 2013 08:32:36 -0700 (PDT)
From: Tom 
Subject: RE: [compass-users] importing Winkarst files into Compass

Thanks. I'll look at it tonight. I use notepad++, not windows notepad.

On Mon, Apr 29, 2013 7:10 PM PDT Larry Fish wrote:

Hi Tom,

I've added a feature to Compass that allows you to turn off the 25-item
limit on errors. There is now a checkbox at the top of the error list titled
"Truncate Error List." If you uncheck the box, it will show you all the
errors. The new version is posted here:

http://fountainware.com/compass/downloads/download.htm

Compass files can also be edited manually like Karst Files can. In fact, the
Karst file format is based on the Compass format. Back in the early 80's
Gary lived in Denver and at the time, Compass was an Apple-Only program.
Gary wanted to port it to the PC and so I gave him copies of the Compass
source code, so originally Karst and Compass had the same file format. Of
course the formats took different directions long ago.

Here is a description of the Compass file format:

http://www.fountainware.com/compass/HTML_Help/Compass_Editor/surveyfileforma
t.htm

The biggest problem with using Notepad to edit Compass files, is that
Compass uses Form-Feeds (Control-L) to separate surveys. Notepad will not
allow you to enter those characters directly from the keyboard, although you
can scoop one up using the clipboard and paste it into place.

A better choice would be XEdit, which is a notepad-like text editor that I
wrote many years ago. It allows you see and enter control characters such as
Form-Feeds/Ctrl-Ls. It has lots of Macro capabilities and it doesn't add any
additional formatting like other editors can do. Of course any additional
formatting, like inserting or removing Hard Returns, can corrupt a Compass
file. XEdit is free. You can get a copy here:

http://www.fountainware.com/Products/xedit/index.htm

Let me know if you have any questions.

Larry

________________________________________

From: [email protected] [mailto:[email protected]]
On Behalf Of Tom

Sent: Monday, April 29, 2013 12:05 PM

To: [email protected]

Subject: RE: [compass-users] importing Winkarst files into Compass

Hi Larry, 

Thanks. 

From your reply I would say it is both format and data errors.

Compass couldn't handle aliases and also had errors with passage shots. Is
there a way to produce a full error logfile?

I can/will send you both sef and compass exports from winkarst. I think in
the end I want to do it myself, so if you figure it out and tell me what is
going on...

I liked winkarst because I could use notepad ++ to edit raw files. I would
like to do that in compass also, because I think it would be faster than
using the compass GUI.

Thanks again.

------------------------------

On Mon, Apr 29, 2013 3:23 AM PDT Larry Fish wrote:

Hi Tom,

It is unclear from your description whether the problem is with the format

of the data or with the data itself. 

Format Errors: These errors would occur because WinKarst exports the
surveys

so that data format doesn't exactly match the Compass format. This will

cause Compass to miss data items or misinterpret them.

Data Errors. With these kinds of errors, Compass can read the data
correctly

but Compass cannot assemble the data into a connected set of passages. This

is usually caused by organizational problems having to do with the order
the

surveys and shots.

From your description, it sounds like the problem is probably an

organizational issue, however I can't be sure without knowing more about
the

error messages you received.

If you want, you can send me copies of the data and I can fix it. I've got

lots of tools that make it easy for me to do. (You don't need to worry
about

your data. I've never give out data or any information about the caves I

have unless I've been told specifically that I can do so.)

You can email the data to me. My regular email address should appear in the

header of this email. I won't post it in the body of this email because the

body of these emails appear on the internet and the email address will get

harvested by SPAMers. If you can't find the email address, use the on line

form to contact me and I will send you the email address you should use.

Here is a link to the online form:

http://www.fountainware.com/compass/CompassContact/CompassContact.php

If you decide to send me the data, I'd prefer the Compass or SEF data since

I don't have current versions of WinKarst installed on my computer. Also,

please give me as much information as you can about the cave, particularly

if it is large and complicated. If the problem with the data is

organizational, I may have to reorganize things to get it work.

Let me know if you have any more questions or thoughts.

Larry

________________________________________

From: [email protected] [mailto:[email protected]]

On Behalf Of Tom

Sent: Sunday, April 28, 2013 2:43 PM

To: [email protected]

Subject: [compass-users] importing Winkarst files into Compass

Larry,

I have Winkart files I would like to import into Compass. I have tried
using

Winkarst to save as Compass files and save as SEF files, but they both

import with errors. Compass stops listing errors after 25 lines so I can't

go through one by one and correct them and frankly don't want to do it that

way. And I don't want to hand enter everything obviously.

How can I accomplish this best? 

thanks,

Tom

------------------------------------

Yahoo! Groups Links


Messsage #: 375
Date: Thu, 23 May 2013 21:53:50 -0000
From: "Zeb" 
Subject: KML Export problems

I'm having trouble with the KML Export on one computer. When I try to save the file it says "Specified module could not be found." When I tried it on my laptop it works fine. Both are windows 7 with the latest version of compass. Has anyone had this problem in the past? Have a solution?

Thanks

Zeb  


Messsage #: 376
Date: Thu, 23 May 2013 19:53:10 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] KML Export problems

Hi Jeb,

The error message usually means that the program is trying to load a Windows
DLL and can't find it. That would tend to mean that a Windows DLL is missing
a DLL or a DLL has somehow become damaged. 

DLL's are Windows library files that contain important subroutines that can
be used by programs. Windows has a large set of these DLLs that are
distributed and installed whenever Windows is installed. If a DLL becomes
deleted or damaged, the programs that use it will have errors. 

Since this is happening in a part of the code that writes an "XML" file, I
would guess that the missing/damaged DLL would be one or both of:
"MSXML4R.dll" and "msxml4.dll" since those are Windows DLLs that handle XML
files.

This is just an educated guess. I would need more information to help verify
the guess. Here are a few questions that might help solve the problem:

1. Is there any additional error information, like the name of the module it
can't load or any numbers that might indicate where the error is occuring?

2. Where exactly does the error occur? As soon as you press the "Export KML"
button? After you've selected a filename and pressed the "Save" button? Does
it fail immediately or does the "Progress" bar on the bottom left side of
the windows move before the error appears?

3. Have you removed any Microsoft Programs, like Internet Explorer from the
computer? Have you made in major changes to this computer? Have you run any
cleanup tools on the computer?

4. Both the Viewer and CaveXO can export KML files. Which program are you
exporting from?

The more detailed information you can give me the better. 

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Zeb
Sent: Thursday, May 23, 2013 3:54 PM
Subject: [compass-users] KML Export problems

I'm having trouble with the KML Export on one computer. When I try to save
the file it says "Specified module could not be found." When I tried it on
my laptop it works fine. Both are windows 7 with the latest version of
compass. Has anyone had this problem in the past? Have a solution?

Thanks

Zeb 

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 377
Date: Thu, 30 May 2013 18:22:23 -0400
From: Tony Canike 
Subject: How to reorganizing a Compass .DAT file

I have inherited a Compass file for an almost 17 mile cave that was 
surveyed over a 50 year period. The single large Compass file needs some 
serious reorganization, and I am looking for your advice please on how 
to approach this. (This is way beyond the "manipulate surveys" feature 
in Compass I believe.)

The good news is that the data appears to be complete and accurate, and 
it generates a good line plot. The data has been in loving care for many 
years by good folks, most of whom were qualified cave surveyors and 
cartographers.

The bad news is that the data from hundreds and hundreds of survey trips 
has been combined into about 60 surveys in the Compass file. This makes 
visualizing the cave difficult, as it is nearly impossible to turn on 
and off layers and sections of the cave when viewing or plotting the 
data.  It is also difficult to maintain the data, and to extract 
statistics (how many survey trips, who surveyed in which year, etc.)

So I think I want to (a) separate the "combined" surveys into separate 
Compass surveys, one for each survey trip, and (b) separate the one big 
.DAT file into multiple .DAT files by cave section.

In the process, I think I also want to (c) fix the station name 
prefixes, as they have grown to 6 or more characters with lots of 
special characters in them.  A typical station name is something like 
BZ_%&K22, where K22 was what the survey team wrote in their book, and 
the BZ_%& is the prefix someone added to separate it from the 10 other 
"K" surveys in the cave. (Ugh.)

How would you approach this?   I am comfortable with editing Compass 
files in a text editor.  And I have the original survey notes, or at 
least almost all of them.

And how would you (d) double-check your work to ensure the integrity of 
the survey data?  One little typo could change a tie in or disconnect a 
shot, and corrupt the line plot.

Thanks,

Tony.


Messsage #: 378
Date: Fri, 31 May 2013 04:53:28 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] How to reorganizing a Compass .DAT file

Hi Tony,

Thanks for you email. Here are some thoughts:

 (a) separate the "combined" surveys into separate

 Compass surveys, one for each survey trip,

Based on this question, I've added a new feature to the Compass Editor. It
allows you to split any survey into two surveys. If you down load the latest
version, there will be a "Split" button on the survey Editor page. That
ought to make it easier to break your surveys into separate trips.

 (b) separate the one big .DAT file into multiple .DAT files

 by cave section.

The "Manipulate Surveys" option in the Project Manager will do this. You
load file you wan to break up into separate surveys into the right-hand list
and then choose the surveys you want to save to a particular file by
dragging them to the left-hand list and saving them. You repeat the process
for as many files as you want to create, putting different surveys into each
one.

 (c) fix the station name prefixes, as they have grown to 6

 or more characters with lots of special characters in them.

There is a tool in the Editor that allows you make changes to a large number
of surveys at once. You can find the option by selecting the "Surveys-Block
Modify Surveys" option from the menu bar. On the "Shot Items" page there is
an option to add or remove prefixes from station names. This could be used
to removed a prefix and then add a better one back. The tool only works on
the Surveys that you selected in the main list. This allows you to apply the
changes only to specific sets of surveys.

 (d) double-check your work to ensure the integrity of the

 survey data? One little typo could change a tie in or

 disconnect a shot, and corrupt the line plot.

I run into this problem all the time when I'm making changes to the
software. Here is what I recommend:

1. Back everything up at every stage of the process. Disk space is huge
these days and cave files are tiny compared to pictures and movies, so there
is no reason that you shouldn't make backups every few minutes. That way if
you make a mistake, you can go back to a previous version, even if it turns
out the mistake happened a couple weeks ago.

2. Recompile to data periodically to see if anything has changed. You can
compare the line plots visually to see if anything has changed. You can also
look at the compiler statistics to see if anything has changed. For example,
if the cave length, depth or any of the other statistics has suddenly
changed you know you've created a problem. 

You can use a file-compare program like WinDiff to compare old and new
versions of the PLT file. This can pickup subtle changes that you may not
notice in the plot or the statistics. This only works if you don't changes
the order of the shots or surveys in the file. If the order changes, the
plot file will be different, even the statistics and visual appearance are
exactly the same.

Let me know if you have any questions. Also let me know if there are any
other tools that would be helpful to you. I'm working on some new data
organization tools for the next version of Compass and suggestions would be
helpful.

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Tony Canike
Sent: Thursday, May 30, 2013 4:22 PM
Subject: [compass-users] How to reorganizing a Compass .DAT file

I have inherited a Compass file for an almost 17 mile cave that was 
surveyed over a 50 year period. The single large Compass file needs some 
serious reorganization, and I am looking for your advice please on how 
to approach this. (This is way beyond the "manipulate surveys" feature 
in Compass I believe.)

The good news is that the data appears to be complete and accurate, and 
it generates a good line plot. The data has been in loving care for many 
years by good folks, most of whom were qualified cave surveyors and 
cartographers.

The bad news is that the data from hundreds and hundreds of survey trips 
has been combined into about 60 surveys in the Compass file. This makes 
visualizing the cave difficult, as it is nearly impossible to turn on 
and off layers and sections of the cave when viewing or plotting the 
data. It is also difficult to maintain the data, and to extract 
statistics (how many survey trips, who surveyed in which year, etc.)

So I think I want to (a) separate the "combined" surveys into separate 
Compass surveys, one for each survey trip, and (b) separate the one big 
.DAT file into multiple .DAT files by cave section.

In the process, I think I also want to (c) fix the station name 
prefixes, as they have grown to 6 or more characters with lots of 
special characters in them. A typical station name is something like 
BZ_%&K22, where K22 was what the survey team wrote in their book, and 
the BZ_%& is the prefix someone added to separate it from the 10 other 
"K" surveys in the cave. (Ugh.)

How would you approach this? I am comfortable with editing Compass 
files in a text editor. And I have the original survey notes, or at 
least almost all of them.

And how would you (d) double-check your work to ensure the integrity of 
the survey data? One little typo could change a tie in or disconnect a 
shot, and corrupt the line plot.

Thanks,

Tony.

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 379
Date: Sat, 01 Jun 2013 08:35:42 -0400
From: Tony Canike 
Subject: Re: [compass-users] How to reorganizing a Compass .DAT file

Larry, thank for the ideas and the new split feature! That was fast work.

Sounds like it will help a lot, I'll try it out this weekend.

Appreciate the support,

Tony.

On 5/31/2013 6:53 AM, Larry Fish ([email protected]) wrote

 Hi Tony,

 Thanks for you email. Here are some thoughts:

  (a) separate the "combined" surveys into separate

  Compass surveys, one for each survey trip,

 Based on this question, I've added a new feature to the Compass 
 Editor. It allows you to split any survey into two surveys. If you 
 down load the latest version, there will be a "Split" button on the 
 survey Editor page. That ought to make it easier to break your surveys 
 into separate trips.

  (b) separate the one big .DAT file into multiple .DAT files

  by cave section.

 The "Manipulate Surveys" option in the Project Manager will do this. 
 You load file you wan to break up into separate surveys into the 
 right-hand list and then choose the surveys you want to save to a 
 particular file by dragging them to the left-hand list and saving 
 them. You repeat the process for as many files as you want to create, 
 putting different surveys into each one.

  (c) fix the station name prefixes, as they have grown to 6

  or more characters with lots of special characters in them.

 There is a tool in the Editor that allows you make changes to a large 
 number of surveys at once. You can find the option by selecting the 
 "Surveys-Block Modify Surveys" option from the menu bar. On the "Shot 
 Items" page there is an option to add or remove prefixes from station 
 names. This could be used to removed a prefix and then add a better 
 one back. The tool only works on the Surveys that you selected in the 
 main list. This allows you to apply the changes only to specific sets 
 of surveys.

  (d) double-check your work to ensure the integrity of the

  survey data? One little typo could change a tie in or

  disconnect a shot, and corrupt the line plot.

 I run into this problem all the time when I'm making changes to the 
 software. Here is what I recommend:

 1. Back everything up at every stage of the process. Disk space is 
 huge these days and cave files are tiny compared to pictures and 
 movies, so there is no reason that you shouldn't make backups every 
 few minutes. That way if you make a mistake, you can go back to a 
 previous version, even if it turns out the mistake happened a couple 
 weeks ago.

 2. Recompile to data periodically to see if anything has changed. You 
 can compare the line plots visually to see if anything has changed. 
 You can also look at the compiler statistics to see if anything has 
 changed. For example, if the cave length, depth or any of the other 
 statistics has suddenly changed you know you've created a problem.

 You can use a file-compare program like WinDiff to compare old and new 
 versions of the PLT file. This can pickup subtle changes that you may 
 not notice in the plot or the statistics. This only works if you don't 
 changes the order of the shots or surveys in the file. If the order 
 changes, the plot file will be different, even the statistics and 
 visual appearance are exactly the same.

 Let me know if you have any questions. Also let me know if there are 
 any other tools that would be helpful to you. I'm working on some new 
 data organization tools for the next version of Compass and 
 suggestions would be helpful.

 Larry

 ------------------------------------------------------------------------

 *From:*[email protected] 
 [mailto:[email protected]] *On Behalf Of *Tony Canike
 *Sent:* Thursday, May 30, 2013 4:22 PM
 *To:* [email protected]
 *Subject:* [compass-users] How to reorganizing a Compass .DAT file

 I have inherited a Compass file for an almost 17 mile cave that was
 surveyed over a 50 year period. The single large Compass file needs some
 serious reorganization, and I am looking for your advice please on how
 to approach this. (This is way beyond the "manipulate surveys" feature
 in Compass I believe.)

 The good news is that the data appears to be complete and accurate, and
 it generates a good line plot. The data has been in loving care for many
 years by good folks, most of whom were qualified cave surveyors and
 cartographers.

 The bad news is that the data from hundreds and hundreds of survey trips
 has been combined into about 60 surveys in the Compass file. This makes
 visualizing the cave difficult, as it is nearly impossible to turn on
 and off layers and sections of the cave when viewing or plotting the
 data. It is also difficult to maintain the data, and to extract
 statistics (how many survey trips, who surveyed in which year, etc.)

 So I think I want to (a) separate the "combined" surveys into separate
 Compass surveys, one for each survey trip, and (b) separate the one big
 .DAT file into multiple .DAT files by cave section.

 In the process, I think I also want to (c) fix the station name
 prefixes, as they have grown to 6 or more characters with lots of
 special characters in them. A typical station name is something like
 BZ_%&K22, where K22 was what the survey team wrote in their book, and
 the BZ_%& is the prefix someone added to separate it from the 10 other
 "K" surveys in the cave. (Ugh.)

 How would you approach this? I am comfortable with editing Compass
 files in a text editor. And I have the original survey notes, or at
 least almost all of them.

 And how would you (d) double-check your work to ensure the integrity of
 the survey data? One little typo could change a tie in or disconnect a
 shot, and corrupt the line plot.

 Thanks,

 Tony.
  
    Larry, thank for the ideas and the new split feature! That was fast
    work.
    
    Sounds like it will help a lot, I'll try it out this weekend.
    
    Appreciate the support,
    
    Tony.
    
    On 5/31/2013 6:53 AM, Larry Fish
      ([email protected]) wrote
    
       
            
              Hi Tony,
              Thanks for you
                    email. Here are some
                    thoughts:
              > (a)
                    separate the "combined"
                    surveys into separate
              > Compass
                    surveys, one for each survey
                    trip,
              Based on this
                    question, I've added a new
                    feature to the Compass Editor. It allows you to
                    split any survey into two
                    surveys. If you down load the latest version, there
                    will be a "Split" button on
                    the
                    survey Editor page. That ought to make it easier to
                    break your surveys into
                    separate trips.
              > (b)
                    separate the one big .DAT file
                    into multiple .DAT files
              > by cave
                    section.
              The
                    "Manipulate Surveys" option
                    in the Project Manager will do this. You load file
                    you wan to break up into
                    separate surveys into the right-hand list and then
                    choose the surveys you want
                    to save to a particular file by dragging them to the
                    left-hand list and saving
                    them. You repeat the process for as many files as
                    you want to create, putting
                    different surveys into each one.
              > (c) fix
                    the station name prefixes, as
                    they have grown to 6
              > or more
                    characters with lots of
                    special characters in them.
              There is a
                    tool in the Editor that allows
                    you make changes to a large number of surveys at
                    once. You can find the option
                    by selecting the "Surveys->Block Modify Surveys"
                    option from the
                    menu bar. On the "Shot Items" page there is an
                    option to add or
                    remove prefixes from station names. This could be
                    used to removed a prefix and
                    then add a better one back. The tool only works on
                    the Surveys that you selected
                    in the main list. This allows you to apply the
                    changes only to specific sets of
                    surveys.
              > (d)
                    double-check your work to ensure
                    the integrity of the
              > survey
                    data? One little typo could
                    change a tie in or
              >
                    disconnect a shot, and corrupt the
                    line plot.
              I run into
                    this problem all the time when
                    I'm making changes to the software. Here is what I
                    recommend:
              1. Back
                    everything up at every stage of
                    the process. Disk space is huge these days and cave
                    files are tiny compared to
                    pictures and movies, so there is no reason that you
                    shouldn't make backups
                    every few minutes. That way if you make a mistake,
                    you can go back to a
                    previous version, even if it turns out the mistake
                    happened a couple weeks ago.
              2. Recompile
                    to data periodically to see
                    if anything has changed. You can compare the line
                    plots visually to see if
                    anything has changed. You can also look at the
                    compiler statistics to see if
                    anything has changed. For example, if the cave
                    length, depth or any of the
                    other statistics has suddenly changed you know
                    you've created a problem. 
              You can use a
                    file-compare program like
                    WinDiff to compare old and new versions of the PLT
                    file. This can pickup subtle
                    changes that you may not notice in the plot or the
                    statistics. This only works
                    if you don't changes the order of the shots or
                    surveys in the file. If the
                    order changes, the plot file will be different, even
                    the statistics and visual
                    appearance are exactly the same.
              Let me know if
                    you have any questions.
                    Also let me know if there are any other tools that
                    would be helpful to you. I'm
                    working on some new data organization tools for the
                    next version of Compass and
                    suggestions would be helpful.
              Larry
               
               
               
                    
                From: [email protected]
                      [mailto:[email protected]]
                      On Behalf Of Tony
                      Canike
                      Sent:
                      Thursday, May 30, 2013 4:22
                      PM
                      To:
                      [email protected]
                      Subject:
                      [compass-users] How to
                      reorganizing a Compass .DAT file
              
               
                
                    
                          I have inherited a Compass file for an almost
                          17 mile cave that was 
                          surveyed over a 50 year period. The single
                          large Compass file needs some 
                          serious reorganization, and I am looking for
                          your advice please on how 
                          to approach this. (This is way beyond the
                          "manipulate surveys"
                          feature 
                          in Compass I believe.)
                          
                          The good news is that the data appears to be
                          complete and accurate, and 
                          it generates a good line plot. The data has
                          been in loving care for many 
                          years by good folks, most of whom were
                          qualified cave surveyors and 
                          cartographers.
                          
                          The bad news is that the data from hundreds
                          and hundreds of survey trips 
                          has been combined into about 60 surveys in the
                          Compass file. This makes 
                          visualizing the cave difficult, as it is
                          nearly impossible to turn on 
                          and off layers and sections of the cave when
                          viewing or plotting the 
                          data. It is also difficult to maintain the
                          data, and to extract 
                          statistics (how many survey trips, who
                          surveyed in which year, etc.)
                          
                          So I think I want to (a) separate the
                          "combined" surveys into
                          separate 
                          Compass surveys, one for each survey trip, and
                          (b) separate the one big 
                          .DAT file into multiple .DAT files by cave
                          section.
                          
                          In the process, I think I also want to (c) fix
                          the station name 
                          prefixes, as they have grown to 6 or more
                          characters with lots of 
                          special characters in them. A typical station
                          name is something like 
                          BZ_%&K22, where K22 was what the survey
                          team wrote in their book, and 
                          the BZ_%& is the prefix someone added to
                          separate it from the 10 other 
                          "K" surveys in the cave. (Ugh.)
                          
                          How would you approach this? I am comfortable
                          with editing Compass 
                          files in a text editor. And I have the
                          original survey notes, or at 
                          least almost all of them.
                          
                          And how would you (d) double-check your work
                          to ensure the integrity of 
                          the survey data? One little typo could change
                          a tie in or disconnect a 
                          shot, and corrupt the line plot.
                          
                          Thanks,
                          
                          Tony.


Messsage #: 380
Date: Sun, 02 Jun 2013 13:48:23 -0400
From: Tony Canike 
Subject: split survey feature - thanks

Thanks Larry, gave it a quick test just now and worked fine.  I compiled 
my cave before and after splitting, and the cave statistics were stable 
(except, of course, for the number of surveys.)

Thanks again,

Tony.


Messsage #: 381
Date: 04 Sep 2013 06:49:36 -0700
From: 
Subject: Map to Dat

Hey Larry, 

 

Been testing your Map to Dat tool. IÉ?Tve been
waiting for such a tool for years! In the past I have spent many an evening
converting manually old paper surveys to survey data.  

 

IÉ?Tve got a suggestion or 2:  

-         
it
would be nice if the survey stations (e.g. A1, A2) would be visible as labels
next to the points in the map 

-         
a
possibility to zoom in/out the map (especially when loading a big map, IÉ?Tm
missing the possibility to zoom it smaller) 

 

Then a bug maybe: doesnÉ?Tt work OK with TIFF
files. Sometimes it loads the image but in reversed color (black background).  

 

Then something that is really important for
reconstructing accurately a cave: elevation data.  

Now you provided the possibility to set the
starting and ending elevation of the cave. But finally, this results in the inclinations
being spread out proportionally over the whole cave. For vertical caves, or
caves that have pits, this is not OK. 
Imagine a 50 m deep cave. There is just a 50 m long horizontal crawlway
ending with a 50 m pit, basically 2 shots. The data that MaptoDat gives me are
not useable and will not lead to a realistic representation of the cave. 

 

A way to solve this, would be to give the user
the possibility to enter manually the elevation for each survey shot. 

 

Finally:
the tool is only for working on cave plans. Could it be used somehow for cave
profiles too? Of course, this would give exactly the same problem as above, but
this time for the azimuths.  

 

As you
might have guessed, IÉ?Tm working a lot with surveys of vertical cavesÉ?› 

 

Kind regards 

 

Paul De Bie


Messsage #: 382
Date: Thu, 5 Sep 2013 15:08:40 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] Map to Dat

Hi Paul,

Thanks for your email and suggestions. Some of your suggestions are already
in the version you have and I was able to add some other. 

 it would be nice if the survey stations (e.g. A1, A2)
 would be visible as labels next to the points in the map

There is a new version on the internet with this feature. 

 A possibility to zoom in/out the map (especially when loading
 a big map, I'm missing the possibility to zoom it smaller)

This is also in the new version.

 Then a bug maybe: doesn't work OK with TIFF files.
 Sometimes it loads the image but in reversed color
 (black background).

I wrote the TIFF routines myself and I have a couple hundred test TIFF files
all of which work fine. The problem is that there are hundreds of
combinations of options in the TIFF files and it is difficult to test them
all. If you could send me copy of one of the problem files, I can figure out
why it is displaying improperly.
ˇ
 A way to solve this, would be to give the user the possibility
 to enter manually the elevation for each survey shot.

You can already do this. All the values in the "Accumulated Data" list can
be edited. When you change the values of the Elevations, the Inclination and
Length changes appropriately. If you change the value Plan Length the Slope
Length and the Inclination changes.

 Finally: the tool is only for working on cave plans.
 Could it be used somehow for cave profiles too?
 Of course, this would give exactly the same problem as above,
 but this time for the azimuths. 
ˇ
I've thought about this a lot. I've even thought about having two displays
so you could load two images, one for the plan map and one for the profiles
map. That way, you could be measuring azimuths and lengths on one plan-image
and inclinations on the profile image I finally concluded that there are so
many complications that it would be more trouble than it is worth. Here are
some the issues I'm concerned about: 

To calculate inclinations from points on a profile, you need to know the
length of the shot. But to calculate the length of the shot, you have to
know three things: 1) the Azimuth of the shot, 2) the Rotation or Viewing
Angle of the Profile and 3) whether the profile is normal or "Unfolded."

Number-2 is the hard part. Most maps don't give much information about
profiles. Typically the best you get is a line drawn on the plan map showing
how the profile is oriented. Then there are several different ways of
expressing the rotation. For example, if the cave is rotated 45 degrees, the
"viewing angle" or direction you are looking to toward is 315 degrees. At
the same time, the direction the cave is facing is 135 degrees. I've seen
all three used to express the rotation of a cave.

Working with a plan and profile image at the same time adds even more
complications. It is possible for the plan and profile images to have
different scales and different rotations.

All this is a lot of information to get right and a small mistake in any one
of those parameters will make the survey completely inaccurate. I will think
about the problem some more, but I don't have much time right now to work on
this issue.

Let me know if you have any questions.

Larry


Messsage #: 383
Date: Thu, 5 Sep 2013 15:53:59 -0600
From: "Larry Fish" 
Subject: A couple annoucements

Hi Everybody,

I have a couple announcements:

1. MapToDat. There is a new utility program called MapToDat. It allows you
to reconstruct Compass DAT files from a scammed image of a paper map. The
process works by clicking on survey stations in the map image. This is a lot
easier than the usual process which involves taking measurement with a ruler
and protractor and using trigonometry to calculate Azimuth, Inclination and
Tape.  There is a more detailed description on the Compass web page.

2. SVG Exporter. I've just fixed a number of problems in the SVG Exporter.
Most of the problems have to do with Adobe Illustrator making unexpected
changes to the data. For example, it randomly converts numbers in Stations
names to hex format, so that the Station "A1" becomes "A_x31." It also
converts shot values to an unusual format if the shot is short or vertical
and the offset is due East, West, North or South. These two problems can
cause large distortions when the SVG Exporter merges, morphs or round-trips
the cave.

The new version of the SVG Exporter is on the Compass web site.

3. Another thing to be careful of with the SVG Exporter is survey order. If
you are adding new surveys to the survey file that forms the basis of your
SVG Map, don't add the new surveys to the beginning of the file. Add them to
the end.

Compass normally assumes that the first station in the cave is the Entrance.
The entrance then becomes the starting location of the cave, having a
coordinate of East=0, North=0, Vertical=0. All other stations are referenced
relative to that station. If you add a new survey to the beginning of the
file, you automatically change the Entrance station and that shifts the
coordinates of all other stations in the cave.

The SVG Exporter positions the cave on paper according to the location of
the center of the cave. The coordinates of the center of the cave will shift
if you change the entrance to the cave. (The actual center doesn't move,
only the coordinates change.) When the SVG Exporter processes the data, the
position of the cave will be wrong unless you readjust the cave position.

There are some instances where the entrance of the cave will actually be
changed. For example, you might have discovered a new entrance. If that is
the case, then you need to run your digital map through the SVG Exporter and
reposition the cave. Here are the steps to do this:

A. Once your base Plot-File and Target SVG file have been loaded into the
SVG Exporter, press the "Match Target" button. This will use all the
settings that are embedded in SVG map. If you've changed the Entrance
station, the Map Display may show that the cave is no longer positioned
appropriately.

B. Go to the Pos/Scale page and reposition the cave where you want it. 

3. Press the Merge/Morph/Save button. This will save the new positioning
information so you can use the new cave with the new entrance.

Larry Fish


Messsage #: 384
Date: Fri, 6 Sep 2013 09:30:59 +0200
From: "Paul De Bie" 
Subject: RE: [compass-users] A couple annoucements

Hi Larry,

as usual tx again for your work, it is so much appreciated by many!
Have you seen my message on the user group yesterday regarding map to dat? 

About SVG exporter: I have been taking my first steps with this and Inkscape - mastering all this
this will be my project for next winter. Looks as if I have got a steep learning curve ahead...but
your tutorial is great... where do you find the time to do all this!!

You say "Compass normally assumes that the first station in the cave is the Entrance".
Could this be changed somehow? Can't you give us the possibility to indicate what the entrance
station is? 
It is something that has caused me a lot of headaches. Very often, we survey caves from bottom to
entrance. In the kind of exploration that we do, it is mostly the standard practise. You explore a
new vertical cave, you bottom it and then survey it on the way out. Even horizontal passage is often
surveyed in a similar way. 
For such caves, the entrance (for Compass) is located at the bottom...

It is important for stuff such as elevation of the stations: it will be wrong, because Compass
assumes the first station being at zero. Now mostly I use MAK projects and set a fixed station on
the real entrance, so this problem can be addressed easily. But for stuff such as "Display distance
from entrance" (a fantastic feature by the way!) it can't be solved that way and as you say
yourself, the survey order is very important to get this right...

cheers

Paul De Bie
http://www.scavalon.be
http://scavalon.blogspot.com

 -----Original Message-----
 From: [email protected] [mailto:[email protected]] On Behalf Of Larry Fish
 Sent: Thursday, September 05, 2013 11:54 PM
 To: [email protected]
 Subject: [compass-users] A couple annoucements
 
 Hi Everybody,
 
 I have a couple announcements:
 
 1. MapToDat. There is a new utility program called MapToDat. It allows you
 to reconstruct Compass DAT files from a scammed image of a paper map. The
 process works by clicking on survey stations in the map image. This is a lot
 easier than the usual process which involves taking measurement with a ruler
 and protractor and using trigonometry to calculate Azimuth, Inclination and
 Tape.  There is a more detailed description on the Compass web page.
 
 2. SVG Exporter. I've just fixed a number of problems in the SVG Exporter.
 Most of the problems have to do with Adobe Illustrator making unexpected
 changes to the data. For example, it randomly converts numbers in Stations
 names to hex format, so that the Station "A1" becomes "A_x31." It also
 converts shot values to an unusual format if the shot is short or vertical
 and the offset is due East, West, North or South. These two problems can
 cause large distortions when the SVG Exporter merges, morphs or round-trips
 the cave.
 
 The new version of the SVG Exporter is on the Compass web site.
 
 3. Another thing to be careful of with the SVG Exporter is survey order. If
 you are adding new surveys to the survey file that forms the basis of your
 SVG Map, don't add the new surveys to the beginning of the file. Add them to
 the end.
 
 Compass normally assumes that the first station in the cave is the Entrance.
 The entrance then becomes the starting location of the cave, having a
 coordinate of East=0, North=0, Vertical=0. All other stations are referenced
 relative to that station. If you add a new survey to the beginning of the
 file, you automatically change the Entrance station and that shifts the
 coordinates of all other stations in the cave.
 
 The SVG Exporter positions the cave on paper according to the location of
 the center of the cave. The coordinates of the center of the cave will shift
 if you change the entrance to the cave. (The actual center doesn't move,
 only the coordinates change.) When the SVG Exporter processes the data, the
 position of the cave will be wrong unless you readjust the cave position.
 
 There are some instances where the entrance of the cave will actually be
 changed. For example, you might have discovered a new entrance. If that is
 the case, then you need to run your digital map through the SVG Exporter and
 reposition the cave. Here are the steps to do this:
 
 A. Once your base Plot-File and Target SVG file have been loaded into the
 SVG Exporter, press the "Match Target" button. This will use all the
 settings that are embedded in SVG map. If you've changed the Entrance
 station, the Map Display may show that the cave is no longer positioned
 appropriately.
 
 B. Go to the Pos/Scale page and reposition the cave where you want it.
 
 3. Press the Merge/Morph/Save button. This will save the new positioning
 information so you can use the new cave with the new entrance.
 
 Larry Fish
 
 ------------------------------------
 
 Yahoo! Groups Links


Messsage #: 385
Date: Fri, 6 Sep 2013 11:14:08 +0200
From: "Paul De Bie" 
Subject: RE: [compass-users] Map to Dat

Hi Larry,

I had tried to change elevation in the "Live Data" table but not in the accumulated data! Stupid me.

TIFF: choose any file you like here:
https://www.dropbox.com/sh/sywn6kz4pof7kbi/oOPcUlzXX8

OK, tx for the explanation about the profile. I agree it ain't simple at all. In fact, you will
always need both plan and profile to reconstruct a cave. 

One more suggestion: add the possibility to handle nodes. Caves are (mostly) never linear. 

regards

Paul De Bie
http://www.scavalon.be
http://scavalon.blogspot.com

 -----Original Message-----
 From: [email protected] [mailto:[email protected]] On Behalf Of Larry Fish
 Sent: Thursday, September 05, 2013 11:09 PM
 To: [email protected]
 Subject: RE: [compass-users] Map to Dat
 
 Hi Paul,
 
 Thanks for your email and suggestions. Some of your suggestions are already
 in the version you have and I was able to add some other.
 
  it would be nice if the survey stations (e.g. A1, A2)
  would be visible as labels next to the points in the map
 
 There is a new version on the internet with this feature.
 
  A possibility to zoom in/out the map (especially when loading
  a big map, I'm missing the possibility to zoom it smaller)
 
 This is also in the new version.
 
  Then a bug maybe: doesn't work OK with TIFF files.
  Sometimes it loads the image but in reversed color
  (black background).
 
 I wrote the TIFF routines myself and I have a couple hundred test TIFF files
 all of which work fine. The problem is that there are hundreds of
 combinations of options in the TIFF files and it is difficult to test them
 all. If you could send me copy of one of the problem files, I can figure out
 why it is displaying improperly.
 
  A way to solve this, would be to give the user the possibility
  to enter manually the elevation for each survey shot.
 
 You can already do this. All the values in the "Accumulated Data" list can
 be edited. When you change the values of the Elevations, the Inclination and
 Length changes appropriately. If you change the value Plan Length the Slope
 Length and the Inclination changes.
 
  Finally: the tool is only for working on cave plans.
  Could it be used somehow for cave profiles too?
  Of course, this would give exactly the same problem as above,
  but this time for the azimuths.
 
 I've thought about this a lot. I've even thought about having two displays
 so you could load two images, one for the plan map and one for the profiles
 map. That way, you could be measuring azimuths and lengths on one plan-image
 and inclinations on the profile image I finally concluded that there are so
 many complications that it would be more trouble than it is worth. Here are
 some the issues I'm concerned about:
 
 To calculate inclinations from points on a profile, you need to know the
 length of the shot. But to calculate the length of the shot, you have to
 know three things: 1) the Azimuth of the shot, 2) the Rotation or Viewing
 Angle of the Profile and 3) whether the profile is normal or "Unfolded."
 
 Number-2 is the hard part. Most maps don't give much information about
 profiles. Typically the best you get is a line drawn on the plan map showing
 how the profile is oriented. Then there are several different ways of
 expressing the rotation. For example, if the cave is rotated 45 degrees, the
 "viewing angle" or direction you are looking to toward is 315 degrees. At
 the same time, the direction the cave is facing is 135 degrees. I've seen
 all three used to express the rotation of a cave.
 
 Working with a plan and profile image at the same time adds even more
 complications. It is possible for the plan and profile images to have
 different scales and different rotations.
 
 All this is a lot of information to get right and a small mistake in any one
 of those parameters will make the survey completely inaccurate. I will think
 about the problem some more, but I don't have much time right now to work on
 this issue.
 
 Let me know if you have any questions.
 
 Larry
 
 ------------------------------------
 
 Yahoo! Groups Links


Messsage #: 386
Date: Fri, 06 Sep 2013 08:50:57 -0400
From: Christian Chenier 
Subject: RE: [compass-users] Map to Dat

Hi Larry,
Your comments about the difficulty with profiles 
are correct when considering projected profiles. 
For extended profile (perhaps what you call 
"unfolded"), the length of the shot is always 
measurable. In fact, this is the only view in 
which you will know the exact length of a shot 
just by looking at the line. (eg. in plan view, 
the drawn length is always going to be shorter 
than reality, except for completely horizontal 
shots; same idea in projected profiles). The 
slope is also easily measurable in extended 
profiles. The only thing missing from that view 
is the azimuth (of course!). Thus, if you combine 
an extended profile with a plan view, you can 
recover all required information, without having 
to specify altitudes for intermediate stations.

Of course, this method requires the existence of 
an extended profile... something that I've found 
not very common in the US... perhaps because so 
many US caves are mazy and an extended profile 
won't represent these caves well. For alpine 
caves, they are quite useful... thus the many 
extended profiles used in Europe, Mexico, etc...

Chris

At 05:08 PM 05/09/2013, Larry Fish wrote:

Hi Paul,

Thanks for your email and suggestions. Some of your suggestions are already
in the version you have and I was able to add some other.

  it would be nice if the survey stations (e.g. A1, A2)
  would be visible as labels next to the points in the map

There is a new version on the internet with this feature.

  A possibility to zoom in/out the map (especially when loading
  a big map, I'm missing the possibility to zoom it smaller)

This is also in the new version.

  Then a bug maybe: doesn't work OK with TIFF files.
  Sometimes it loads the image but in reversed color
  (black background).

I wrote the TIFF routines myself and I have a couple hundred test TIFF files
all of which work fine. The problem is that there are hundreds of
combinations of options in the TIFF files and it is difficult to test them
all. If you could send me copy of one of the problem files, I can figure out
why it is displaying improperly.

  A way to solve this, would be to give the user the possibility
  to enter manually the elevation for each survey shot.

You can already do this. All the values in the "Accumulated Data" list can
be edited. When you change the values of the Elevations, the Inclination and
Length changes appropriately. If you change the value Plan Length the Slope
Length and the Inclination changes.

  Finally: the tool is only for working on cave plans.
  Could it be used somehow for cave profiles too?
  Of course, this would give exactly the same problem as above,
  but this time for the azimuths.

I've thought about this a lot. I've even thought about having two displays
so you could load two images, one for the plan map and one for the profiles
map. That way, you could be measuring azimuths and lengths on one plan-image
and inclinations on the profile image I finally concluded that there are so
many complications that it would be more trouble than it is worth. Here are
some the issues I'm concerned about:

To calculate inclinations from points on a profile, you need to know the
length of the shot. But to calculate the length of the shot, you have to
know three things: 1) the Azimuth of the shot, 2) the Rotation or Viewing
Angle of the Profile and 3) whether the profile is normal or "Unfolded."

Number-2 is the hard part. Most maps don't give much information about
profiles. Typically the best you get is a line drawn on the plan map showing
how the profile is oriented. Then there are several different ways of
expressing the rotation. For example, if the cave is rotated 45 degrees, the
"viewing angle" or direction you are looking to toward is 315 degrees. At
the same time, the direction the cave is facing is 135 degrees. I've seen
all three used to express the rotation of a cave.

Working with a plan and profile image at the same time adds even more
complications. It is possible for the plan and profile images to have
different scales and different rotations.

All this is a lot of information to get right and a small mistake in any one
of those parameters will make the survey completely inaccurate. I will think
about the problem some more, but I don't have much time right now to work on
this issue.

Let me know if you have any questions.

Larry

Christian Chānier
Gatineau (Quābec), Canada
(819) 772-8824 

Hi Larry,
Your comments about the difficulty with profiles are correct when
considering projected profiles. For extended profile (perhaps what you
call "unfolded"), the length of the shot is always measurable.
In fact, this is the only view in which you will know the exact length of
a shot just by looking at the line. (eg. in plan view, the drawn length
is always going to be shorter than reality, except for completely
horizontal shots; same idea in projected profiles). The slope is also
easily measurable in extended profiles. The only thing missing from that
view is the azimuth (of course!). Thus, if you combine an extended
profile with a plan view, you can recover all required information,
without having to specify altitudes for intermediate stations.
Of course, this method requires the existence of an extended profile...
something that I've found not very common in the US... perhaps because so
many US caves are mazy and an extended profile won't represent these
caves well. For alpine caves, they are quite useful... thus the many
extended profiles used in Europe, Mexico, etc...

Chris

At 05:08 PM 05/09/2013, Larry Fish wrote:
  
Hi Paul,
Thanks for your email and suggestions. Some of your suggestions are
already
in the version you have and I was able to add some other. 
> it would be nice if the survey stations (e.g. A1, A2)
> would be visible as labels next to the points in the map
There is a new version on the internet with this feature. 
> A possibility to zoom in/out the map (especially when loading
> a big map, I'm missing the possibility to zoom it smaller)
This is also in the new version.
> Then a bug maybe: doesn't work OK with TIFF files.
> Sometimes it loads the image but in reversed color
> (black background).
I wrote the TIFF routines myself and I have a couple hundred test TIFF
files
all of which work fine. The problem is that there are hundreds of
combinations of options in the TIFF files and it is difficult to test
them
all. If you could send me copy of one of the problem files, I can figure
out
why it is displaying improperly.
 
> A way to solve this, would be to give the user the possibility
> to enter manually the elevation for each survey shot.
You can already do this. All the values in the "Accumulated
Data" list can
be edited. When you change the values of the Elevations, the Inclination
and
Length changes appropriately. If you change the value Plan Length the
Slope
Length and the Inclination changes.
> Finally: the tool is only for working on cave plans.
> Could it be used somehow for cave profiles too?
> Of course, this would give exactly the same problem as above,
> but this time for the azimuths. 
 
I've thought about this a lot. I've even thought about having two
displays
so you could load two images, one for the plan map and one for the
profiles
map. That way, you could be measuring azimuths and lengths on one
plan-image
and inclinations on the profile image I finally concluded that there are
so
many complications that it would be more trouble than it is worth. Here
are
some the issues I'm concerned about: 
To calculate inclinations from points on a profile, you need to know
the
length of the shot. But to calculate the length of the shot, you have
to
know three things: 1) the Azimuth of the shot, 2) the Rotation or
Viewing
Angle of the Profile and 3) whether the profile is normal or
"Unfolded."
Number-2 is the hard part. Most maps don't give much information
about
profiles. Typically the best you get is a line drawn on the plan map
showing
how the profile is oriented. Then there are several different ways
of
expressing the rotation. For example, if the cave is rotated 45 degrees,
the
"viewing angle" or direction you are looking to toward is 315
degrees. At
the same time, the direction the cave is facing is 135 degrees. I've
seen
all three used to express the rotation of a cave.
Working with a plan and profile image at the same time adds even
more
complications. It is possible for the plan and profile images to
have
different scales and different rotations.
All this is a lot of information to get right and a small mistake in any
one
of those parameters will make the survey completely inaccurate. I will
think
about the problem some more, but I don't have much time right now to work
on
this issue.
Let me know if you have any questions.
Larry

Christian Chānier
Gatineau (Quābec), Canada
(819) 772-8824


Messsage #: 387
Date: Sat, 5 Oct 2013 04:47:49 -0600
From: "Larry Fish" 
Subject: New version of Map to Dat

Hi Paul,

I wanted to let you know about several improvements to the MapToDat program
that I think you will like. When I was working with your TIFF images, I
realized what a lot of work it would be to reconstruct caves that have deep
pits. As a result, I've added an option to use Profiles as well as Plan maps
to reconstruct the survey.

The MapToDat now has two image displays, one for the Plan map and one for
the Profile. To reconstruct a survey, you load your Plan map into one
display and the Profile map into the other. (If both the Plan and Profile
are on the same Image, you just load the image twice, once into the Plan
Image and Once into the Profile.)

The program calculates the inclinations from the Station Elevations on the
profile map. It ignores all horizontal distances on the Profile Map. That
allows the program to calculate inclinations without knowing anything about
the profile orientation. Horizontal distances and Azimuth are taken from the
Plan map. There are also options to work with Plan-Only and Profile-Only
maps.

There are also a lot of other improvements.

1. TIFF FILES. The program now reads many more kinds of TIFF files. This
includes all of the TIFF files that were posted on your "dropbox" site.

2. IMPROVED ZOOM. There are several improvements to the zoom feature.

a. The program now uses a better resizing algorithm so the zoomed image is
much clear and the details are easier to see, even when you are zoomed way
out and the image is small.

b. The Station-Marks and Survey-Lines shrink or expland as you zoom in and
zoom out. They are not scaled and stay the same size whether the image is
zoomed or not. This makes the Station Marks and Survey Lines easy to see and
manipulate, no matter how the image is zoomed.

c. The "Mag Slider" uses a logarithmic scale that makes zooming in and out
smoother and more precise. 

d. The image stays centered on the same spot if you zoom in and out. (If you
zoom out to far, the program loses the zoom center and won't zoom back in on
the same spot.)

3. DRAG SCROLLING. The image will automatically scroll if you drag a Station
Marker past the edge of the screen.

4. MARK EDITING. In the past, you've had the option of repositioning a point
by dragging it to a new position. You now have the option of dragging all
the points at once to a new position. You can also drag all the downstream
points together or all the upstream points together.

The new version is up on the Internet. Let me know what you think.

Larry


Messsage #: 388
Date: Sat, 05 Oct 2013 20:30:42 +0200
From: Martin Sluka 
Subject: Re: [compass-users] New version of Map to Dat

I'm sorry, but all this data is possible achieved quite simple by help of Photoshop or Illustrator and Excel.

Martin Sluka

Oct 5, 2013 v 12:47 PM, Larry Fish :

 The program calculates the inclinations from the Station Elevations on the
 profile map. It ignores all horizontal distances on the Profile Map. That
 allows the program to calculate inclinations without knowing anything about
 the profile orientation. Horizontal distances and Azimuth are taken from the
 Plan map. There are also options to work with Plan-Only and Profile-Only
 maps.

Martin Sluka - Studio Sluka

prodej HahnemĀhle DFA 
tisk fotografi° a reprodukc°

Na Rovnosti 2692/21
130 00 Praha 3
tel.: +420 603513640
mail: [email protected]
web: http://www.piezografie.cz

I'm sorry, but all this data is possible achieved quite simple by help of Photoshop or Illustrator and Excel.Martin SlukaOct 5, 2013 v 12:47 PM, Larry Fish <[email protected]>:The program calculates the inclinations from the Station Elevations on theprofile map. It ignores all horizontal distances on the Profile Map. Thatallows the program to calculate inclinations without knowing anything aboutthe profile orientation. Horizontal distances and Azimuth are taken from thePlan map. There are also options to work with Plan-Only and Profile-Onlymaps.
Martin Sluka - Studio Slukaprodej HahnemĀhle DFA tisk fotografi° a reprodukc°Na Rovnosti 2692/21130 00 Praha 3tel.: +420 603513640mail: [email protected]: http://www.piezografie.cz


Messsage #: 389
Date: Sat, 5 Oct 2013 22:55:12 +0200
From: "Paul De Bie" 
Subject: RE: [compass-users] New version of Map to Dat

Come on, Martin. That is exactly the way I did it in the past. I've spent whole evenings
reconstructing old survey drawings with Photoshop and Excel. What a waste of time!

It is in no way comparable to this tool. Give it a try!  

Paul De Bie
  http://www.scavalon.be
  http://scavalon.blogspot.com

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Martin Sluka
Sent: Saturday, October 05, 2013 8:31 PM
Subject: Re: [compass-users] New version of Map to Dat

I'm sorry, but all this data is possible achieved quite simple by help of Photoshop or Illustrator
and Excel.

Martin Sluka

Oct 5, 2013 v 12:47 PM, Larry Fish :

The program calculates the inclinations from the Station Elevations on the
profile map. It ignores all horizontal distances on the Profile Map. That
allows the program to calculate inclinations without knowing anything about
the profile orientation. Horizontal distances and Azimuth are taken from the
Plan map. There are also options to work with Plan-Only and Profile-Only
maps.

Martin Sluka - Studio Sluka

prodej HahnemĀhle DFA 

tisk fotografi° a reprodukc°

Na Rovnosti 2692/21

130 00 Praha 3

tel.: +420 603513640

mail: [email protected]

web: http://www.piezografie.cz

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}


Messsage #: 390
Date: Sun, 06 Oct 2013 01:07:59 +0200
From: Martin Sluka 
Subject: Re: [compass-users] New version of Map to Dat

Oct 5, 2013 v 10:55 PM, Paul De Bie :

 It is in no way comparable to this tool. Give it a try!

I just use the Info window and Ruler tool. It is all. 

And Ruler tool and automatic Rotate if North on scan is not vertical.

Martin

Oct 5, 2013 v 10:55 PM, Paul De Bie <[email protected]>:It is in no way comparable to this tool. Give it a try!I just use the Info window and Ruler tool. It is all. And Ruler tool and automatic Rotate if North on scan is not vertical.
Martin


Messsage #: 391
Date: Mon, 7 Oct 2013 17:07:47 +0200
From: "Paul De Bie" 
Subject: RE: [compass-users] New version of Map to Dat

I know how Photoshop works, and I also used the ruler tool (even the Ruler and automatic rotate,
which is a "hidden" feature that many people are unaware of). 

But again, reconstructing survey data with these tools is a very tedious undertaking, and it
requires a lot of "note taking". Map to Dat does this all for you. You just click and end up with a
survey data file.

Paul De Bie
  http://www.scavalon.be
  http://scavalon.blogspot.com

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Martin Sluka
Sent: Sunday, October 06, 2013 1:08 AM
Subject: Re: [compass-users] New version of Map to Dat

Oct 5, 2013 v 10:55 PM, Paul De Bie :

It is in no way comparable to this tool. Give it a try!

I just use the Info window and Ruler tool. It is all. 

And Ruler tool and automatic Rotate if North on scan is not vertical.

Martin

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}


Messsage #: 392
Date: Tue, 08 Oct 2013 21:50:47 +0200
From: Martin Sluka 
Subject: Re: [compass-users] New version of Map to Dat

Screenshots, not note taking ;)

m.

Oct 7, 2013 v 5:07 PM, Paul De Bie :

 a lot of "note taking". 

Screenshots, not note taking ;)m.Oct 7, 2013 v 5:07 PM, Paul De Bie <[email protected]>:a lot of "note taking". 


Messsage #: 393
Date: 09 Oct 2013 04:16:52 -0700
From: 
Subject: RE: Re: [compass-users] New version of Map to Dat

I thought we were discussing cave surveying here, not childs play. 
 Let's remain serious, man. 

 Paul

---In [email protected],  wrote:

 Screenshots, not note taking ;) 

 m.
 
 Oct 7, 2013 v 5:07 PM, Paul De Bie :
 a lot of É?onote takingÉ??. 

er›I


Messsage #: 394
Date: Thu, 10 Oct 2013 07:19:10 +0200
From: Martin Sluka 
Subject: Re: [compass-users] New version of Map to Dat

I'm serious. 

The main problem with Photoshop is the information window is not scriptable. As you wrote to read and write data is very time consumable and one may misread the number very easy. But to make screenshot with surveying leg and info window is a question of one keystroke and drag with mouse. Screenshots are automatically saved into a folder. Highlighted screenshot is quick viewed  by pressing of space key, numbers are wrote to table. And one has data with control and archive. 

I'm on Mac but on Windows you may use a third party soft for screenshots. 

M. 

OdeslA≠no z iPhonu

9. 10. 2013 v 13:16, [email protected]:
 
 I thought we were discussing cave surveying here, not childs play. 
 
 Let's remain serious, man. 
 
 Paul
 
 ---In [email protected],  wrote:
 
 Screenshots, not note taking ;)
 
 m.
 
 Oct 7, 2013 v 5:07 PM, Paul De Bie :
 
 a lot of É?onote takingÉ??. 

I'm serious. The main problem with Photoshop is the information window is not scriptable. As you wrote to read and write data is very time consumable and one may misread the number very easy. But to make screenshot with surveying leg and info window is a question of one keystroke and drag with mouse. Screenshots are automatically saved into a folder. Highlighted screenshot is quick viewed  by pressing of space key, numbers are wrote to table. And one has data with control and archive. I'm on Mac but on Windows you may use a third party soft for screenshots. M. OdeslA≠no z iPhonu9. 10. 2013 v 13:16, [email protected]:


Messsage #: 395
Date: Sun, 20 Oct 2013 16:48:10 -0500
From: "Aram, Richard B" 
Subject: RE: [compass-users] New Version of Compass

Hi Larry,

I'm trying this again.  I don't find anything on the options list for Load All Settings or Save All Settings.  Has that moved?  Is it still available?

Thanks!

F'!
Rich Aram

From: [email protected] [mailto:[email protected]] On Behalf Of Larry Fish
Sent: Monday, June 11, 2012 3:13 AM
Subject: [EXTERNAL][compass-users] New Version of Compass

Hi Everyone,
I've just finished adding a new feature to Compass that many people have
requested. It allows you to save all the parameters from Complex Plotting
options.
Here is description of the feature from the help file:
"Loading/Saving All Settings. You have the option of saving all the Complex
Settings so you can restore the display to its current state without going
through the task of manually setting each individual option. To save the
settings, go to the Options Page and press the "Save All Settings" button.
Files are saved with the extension "ccml," but you can choose any name for
the file and you can save as many different setting files as you want by
choosing different names for the files.
The program currently saves 41 different parameters including the settings
for each individual survey and section, the spacing and colors of all the
Color Bars and every other important setting. The file format is XML, which
means you can edit the file with a normal text editor or parse it with
various XML parsing tools.
The settings can be restored by pressing the "Load All Settings" Button on
the Options page. This will restore all settings, but it will not enable the
display of Complex Options. This you must enable manually using the Enable
Complex Plotting control described at the top of the page.
Normally, the set of complex settings can only apply to one cave or one plot
file. For example, you wouldn't want to use the Complex settings for
Carlsbad Cavern on Mammoth Cave because many of the parameters would be
totally different. For example, the depth-bar settings would be entirely
different because the caves have such different depths. For this reason, the
program warns you if the Complex files came from a different cave than the
currently being displayed.
If you use this option with the option to save "Views" of the cave, you can
setup unique images of the cave that combine all the complex features of the
cave with specific views from certain angles and positions."
The new version is on the internet. Let me know if you notice any problems
or have any questions
Larry

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}


Messsage #: 396
Date: Sun, 20 Oct 2013 16:00:54 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] New Version of Compass

Hi Rich,

Just to be clear, those options apply specifically to Complex Options in the
Viewer. From the Viewer, select the "Preferences- Set Complex" option from
the Menu bar. In upper right side of the "Options Page," you will find two
buttons: "Load All Settings" and "Save All Settings."

If you don't see those two buttons, make sure you have the latest version of
Compass. Also make sure that when you install Compass that you don't have
any of the Compass programs running. If one or more of them is running, then
Windows won't let the installer replace the program file.

Let me know if you have any more questions.

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Aram, Richard B
Sent: Sunday, October 20, 2013 3:48 PM
Subject: RE: [compass-users] New Version of Compass

Hi Larry,

I'm trying this again.  I don't find anything on the options list for Load
All Settings or Save All Settings.  Has that moved?  Is it still available?

Thanks!

F'!a


Messsage #: 397
Date: Sun, 20 Oct 2013 17:30:02 -0500
From: "Aram, Richard B" 
Subject: RE: RE: [compass-users] New Version of Compass

Hi Larry,

Yes to all, I find it now.  Thanks!  This will be a big help to me.

There's still no way to reset the line weight of individual surveys, right?

F'!

From: [email protected] [mailto:[email protected]] On Behalf Of Larry Fish
Sent: Sunday, October 20, 2013 5:01 PM
Subject: [EXTERNAL]RE: [compass-users] New Version of Compass

Hi Rich,
Just to be clear, those options apply specifically to Complex Options in the Viewer. From the Viewer, select the "Preferences- Set Complex" option from the Menu bar. In upper right side of the "Options Page," you will find two buttons: "Load All Settings" and "Save All Settings."
If you don't see those two buttons, make sure you have the latest version of Compass. Also make sure that when you install Compass that you don't have any of the Compass programs running. If one or more of them is running, then Windows won't let the installer replace the program file.
Let me know if you have any more questions.
Larry

________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Aram, Richard B
Sent: Sunday, October 20, 2013 3:48 PM
Subject: RE: [compass-users] New Version of Compass

Hi Larry,

I'm trying this again.  I don't find anything on the options list for Load All Settings or Save All Settings.  Has that moved?  Is it still available?

Thanks!

F'!
Rich Aram

From: [email protected] [mailto:[email protected]] On Behalf Of Larry Fish
Sent: Monday, June 11, 2012 3:13 AM
Subject: [EXTERNAL][compass-users] New Version of Compass

Hi Everyone,
I've just finished adding a new feature to Compass that many people have
requested. It allows you to save all the parameters from Complex Plotting
options.
Here is description of the feature from the help file:
"Loading/Saving All Settings. You have the option of saving all the Complex
Settings so you can restore the display to its current state without going
through the task of manually setting each individual option. To save the
settings, go to the Options Page and press the "Save All Settings" button.
Files are saved with the extension "ccml," but you can choose any name for
the file and you can save as many different setting files as you want by
choosing different names for the files.
The program currently saves 41 different parameters including the settings
for each individual survey and section, the spacing and colors of all the
Color Bars and every other important setting. The file format is XML, which
means you can edit the file with a normal text editor or parse it with
various XML parsing tools.
The settings can be restored by pressing the "Load All Settings" Button on
the Options page. This will restore all settings, but it will not enable the
display of Complex Options. This you must enable manually using the Enable
Complex Plotting control described at the top of the page.
Normally, the set of complex settings can only apply to one cave or one plot
file. For example, you wouldn't want to use the Complex settings for
Carlsbad Cavern on Mammoth Cave because many of the parameters would be
totally different. For example, the depth-bar settings would be entirely
different because the caves have such different depths. For this reason, the
program warns you if the Complex files came from a different cave than the
currently being displayed.
If you use this option with the option to save "Views" of the cave, you can
setup unique images of the cave that combine all the complex features of the
cave with specific views from certain angles and positions."
The new version is on the internet. Let me know if you notice any problems
or have any questions
Larry

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}


Messsage #: 398


Messsage #: 399
  by mtaq1.grp.bf1.yahoo.com with SMTP; 20 Oct 2013 23:19:59 -0000
Authentication-Results:  pacmmta51 smtp.user_lski; auth=pass (PLAIN)
Date: Sun, 20 Oct 2013 17:19:58 -0600
From: dave belski 
Subject: Re: [compass-users] New Version of Compass

Larry,

I am using an older version of Compass and I am having trouble changing 
an azimuth reading error .  After inputing the correction, compass will 
not let me save the file with the corrections.  Help

Dave Belski


Messsage #: 400
Date: Sun, 20 Oct 2013 17:31:26 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] New Version of Compass

Hi Dave,

There are lots of different things that could cause this kind of problem,
depending on exactly what you mean. Can you give me a little more
information? 

1. When you say "won't let me save the file" what exactly do you mean? Do
you get an error message? Do you save and yet the data is not changed?

2. What do you mean by older? 6 months, 1 year, 25 years?

The more details you can give me, the easier it is for me to figure it out.

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of dave belski
Sent: Sunday, October 20, 2013 5:20 PM
Subject: Re: [compass-users] New Version of Compass

Larry,

I am using an older version of Compass and I am having trouble changing 
an azimuth reading error . After inputing the correction, compass will 
not let me save the file with the corrections. Help

Dave Belski

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 401


Messsage #: 402
  by mtaq5.grp.bf1.yahoo.com with SMTP; 21 Oct 2013 17:03:57 -0000
Authentication-Results:  pacmmta52 smtp.user_lski; auth=pass (PLAIN)
Date: Mon, 21 Oct 2013 11:03:56 -0600
From: dave belski 
Subject: Re: [compass-users] New Version of Compass

On 10/20/2013 5:31 PM, Larry Fish wrote:

 Hi Dave,

 There are lots of different things that could cause this kind of 
 problem, depending on exactly what you mean. Can you give me a little 
 more information?

 1. When you say "won't let me save the file" what exactly do you mean? 
 Do you get an error message? Do you save and yet the data is not changed?

 2. What do you mean by older? 6 months, 1 year, 25 years?

 The more details you can give me, the easier it is for me to figure it 
 out.

 Larry

 ------------------------------------------------------------------------
 *Larry,**
 *
*
**Here goes.**
**
**I have a cave, XX with many survey files.  When I try to correct a 
point on survey 3, and try to save it to the survey, I get a message 
"Can't rename file"   It is constant no matter what method I try to save 
it.  On one occasion, when I quit the program and booted it up again, 
the correction was there.  But this was not always the case.**
**
**My version of Compass:**
**
**Original copy, May 30, 2002**
**An update by disc June 25, 2004**
**Another partial update from the net  1/27/12**
**
**I upgraded to a new computer and I suspect something was lost in the 
process.**
**
**My solution to the problem is this.  Would you please cut me a 
installation disc of the newest and finest version of Compass with all 
the bells and whistles that I can install over what I have and be 
working with the new and improved version..**
**
**Let me know what the cost would be and I will send you a check.  I 
could try to get it from the internet but I'm sure I would screw it up 
somewhere along the way.  I am a good user, not a good hacker type.**
**
**The program as it is now installed works well.  But I have the feeling 
I am missing something.  I have copied all the instructions and keep 
them in a large notebook.    This has solved many problems.  But I am 
sure it is vastly out of date.**
**
**Thanks**
**
**Dave Belski **
**408 Southern Sky**
**Carlsbad, NM 88220**
**575 885 6168 home**
**575 361 6168 cell**
**
*
 *****
 *
 **
 ******** 
  
    On 10/20/2013 5:31 PM, Larry Fish
      wrote:
    
       
            
              Hi Dave,
              There are lots
                    of different things that
                    could cause this kind of problem, depending on
                    exactly what you mean. Can you
                    give me a little more information? 
              1. When you
                    say “won’t let me
                    save the file” what exactly do you mean? Do you get
                    an error message? Do
                    you save and yet the data is not changed?
              2. What do you
                    mean by older? 6 months, 1
                    year, 25 years?
              The more
                    details you can give me, the
                    easier it is for me to figure it out.
              Larry
               
        
        Larry,
    
      Here goes.
      
      I have a cave, XX with many survey files.  When I try to
        correct a point on survey 3, and try to save it to the survey, I
        get a message "Can't rename file"   It is constant no matter
        what method I try to save it.  On one occasion, when I quit the
        program and booted it up again, the correction was there.  But
        this was not always the case.
      
      My version of Compass:
      
      Original copy, May 30, 2002
      An update by disc June 25, 2004
      Another partial update from the net  1/27/12
      
      I upgraded to a new computer and I suspect something was
        lost in the process.
      
      My solution to the problem is this.  Would you please cut
        me a installation disc of the newest and finest version of
        Compass with all the bells and whistles that I can install over
        what I have and be working with the new and improved version..
      
      Let me know what the cost would be and I will send you a
        check.  I could try to get it from the internet but I'm sure I
        would screw it up somewhere along the way.  I am a good user,
        not a good hacker type.
      
      The program as it is now installed works well.  But I have
        the feeling I am missing something.  I have copied all the
        instructions and keep them in a large notebook.    This has
        solved many problems.  But I am sure it is vastly out of date.
      
      Thanks
      
      Dave Belski 
      408 Southern Sky
      Carlsbad, NM 88220
      575 885 6168 home
      575 361 6168 cell


Messsage #: 403
Date: Mon, 21 Oct 2013 12:14:35 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] New Version of Compass

Hi Dave,

There are multiple things that can cause the problem you are describing. The
most likely cause is the file is marked as "Read Only" but there are other
issues that can cause the problem. Below you will find a document I wrote
describing all the possible causes and fixes. If these solutions don't help
you, let me know and we'll figure out a solution.

Larry

PROBLEMS SAVING DATA OR HAVING DATA DISAPPEAR

There are several situations that can cause you to have problems saving
survey data from the Editor or other COMPASS programs. Most of these
problems are not actually caused by COMPASS, but are the result of the way
Windows works. However, they are easy to fix.

NOTE ON FILE EXTENSIONS.

File extensions are the last three letters of a filename that are used to
indicate the type of data that is stored in the file. COMPASS files have
file extensions like DAT, MAK, CLP, BAK etc. As an example, here is an
example of data file: "GROAN.DAT"

Under Windows, you have the options of hiding or displaying these
extensions. To fix these "data saving" problems, it is important to see the
extensions of each file. For this reason, you should make sure that Windows
displays all file extensions. To do this, go into Windows Explorer or My
Computer and select the "View" and then "Folder Options" from the menu bar.
At the top of the page, select the "View" tab and then make sure the "Hide
file extensions for known files types" option is not checked.

Here is a detailed descriptions of the problems:

1. READ ONLY FILES. It is possible to set any Windows file so that it can
only be read and cannot be renamed, deleted or modified. This type of file
is called a "Read Only" file. Normally, you have to deliberately set a file
to be Read Only, however, lately I am seeing a lot of files that get set to
Read Only because they have been copied from a CD-ROM. Apparently, when you
make a copy of a file to CD-ROM, Windows automatically sets it to be read
only.

If one of your survey data files has been set so that it is "Read Only,"
COMPASS may have trouble modifying or saving the file. Also, if any of the
backup files (*.BAK) or the temporary files "C$$$$$$$.$$$" are set to be
"Read Only," COMPASS may not be able to save your changes.

If see a copy of the temporary file "C$$$$$$$.$$$" sitting in the folder
with your other cave files, it is a sure sign that COMPASS is having trouble
saving data because it cannot delete, rename or add new data to some a file.
COMPASS only creates one of these "C$$$$$$$.$$$" files for a short period of
time when it is saving data. The only time COMPASS will leave this file is
when it could not create, delete, save or add data to an existing file.

You can solve this problem by removing the "Read Only" attribute from all
your cave data files. To do this, go to "Windows Explorer" or "My Computer"
and switch to the folder that contains your survey files. Highlight one of
the survey files and press the right mouse button. A menu will then be
displayed. Select the "Properties" option. At the bottom of the Properties
Page will be a list of Attributes. Be sure that the "Read Only" attribute is
not checked.

Be sure to do this process on all Survey files (DAT), Backup files (BAK),
and Temporary files (C$$$$$$$.$$$.) You can also just delete all the
Temporary and Backup files, but be careful not to delete any of your data
files.

2. FILE DATES. COMPASS uses the date of each file to make decisions about
when to process files. If the file date on a file is wrong, COMPASS may make
the wrong decision. This can give the appearance of newly added surveys not
appearing in the plot. For example, if you have a "Closed Data" (CLP) file
whose date is set a year in the future, COMPASS will be confused. COMPASS
normally closes the survey data when the Survey Data file is newer than the
Closed Data file. However, if the file date is set to one year in the
future, the Data File will always be older than Closed Data file, and so
COMPASS will never close it. As a result, the same old data will keep
appearing in the plots even though you have added new surveys to the file.

The solution to this problem is to force the Project Manager to close the
data. You can do this by setting the "Close All" option in Project Manager
and then pressing the "Process and View" button. You can also fix the
problem by deleting all your CLP files. Be careful not to delete any of your
Survey Data files (DAT) or Project Files (MAK).

3. MULTIPLE VERSIONS OF THE DATA. It is not unusual to have several copies
of the same survey data accessible on the computer. Some times it is in
different folders or hard drives. Sometimes it is on another computer or
server on a network. This can cause a problem where you are editing one set
of data but processing and displaying a different set of data. This will
cause any changes you make to not appear in the final plot.

You can solve this problem by making sure the program is always working on
the same data. You can also solve the problem by eliminating extra copies of
the same data. You should also avoid having more than one copy of COMPASS on
your computer. This is because different versions of COMPASS can default to
different folders, thereby causing confusion about which data is being
processed.

4. CORRUPTED FILES. Corrupted data in a survey file can cause COMPASS to
have problems reading the data. This can make it appear that some or all of
the data is missing from the file. The most common cause of data corruption
is editing COMPASS data with a word processor. Also, COMPASS data can be
corrupted when it is transmitted over the internet if it is not zipped or
put in an attachment.

Fixing corrupted data can be difficult. The only reliable way to do it is to
use the shareware plain-text editor that is available on the Fountain web
site. Even then, you must carefully study the file format and look for
sections in the file that no longer follow the format. The best place to
look for corruption is just before the place where the problem appears.

5. STATIONS DON'T APPEAR IN THE STATISTICS. The most likely reason for this
problem is that you are using "links" between surveys or caves. Normally,
COMPASS combines all the surveys and files in the project and treats them as
though they were a single cave. However, if you have duplicate stations in
different caves, these duplicates will interfere with each other creating
problems. For this reason, you have to use the "Linking" feature of COMPASS
to combine different files.

When you are using linking, the compiler and loop closer discard all the
stations a survey files, except those that form the key "links" between
files. This way, if there are duplicate stations names between different
files, they don't interfere with each other. However, this means that the
compiler and loop closer will not have those stations in memory when they
finish processing, so they won't show up in the list of stations.

You may be able to solve the problem by substituting unique station names
for the ones that interfere. That way, you could remove the links and then
the program would combine all the data and would not need to discard any
stations.

Back in the days of the DOS version of COMPASS, links were also used to
limit the size of the survey data because of the limited amount of data
available to DOS. With the Windows version, memory is not a problem. For
this reason, if you are working with data that is old, you may be able to
remove the links without worrying about station labels interfering with each
other.

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of dave belski
Sent: Monday, October 21, 2013 11:04 AM
Subject: Re: [compass-users] New Version of Compass

On 10/20/2013 5:31 PM, Larry Fish wrote:

Hi Dave,

There are lots of different things that could cause this kind of problem,
depending on exactly what you mean. Can you give me a little more
information? 

1. When you say "won't let me save the file" what exactly do you mean? Do
you get an error message? Do you save and yet the data is not changed?

2. What do you mean by older? 6 months, 1 year, 25 years?

The more details you can give me, the easier it is for me to figure it out.

Larry

  _____  

Larry,

Here goes.

I have a cave, XX with many survey files.  When I try to correct a point on
survey 3, and try to save it to the survey, I get a message "Can't rename
file"   It is constant no matter what method I try to save it.  On one
occasion, when I quit the program and booted it up again, the correction was
there.  But this was not always the case.

My version of Compass:

Original copy, May 30, 2002
An update by disc June 25, 2004
Another partial update from the net  1/27/12

I upgraded to a new computer and I suspect something was lost in the
process.

My solution to the problem is this.  Would you please cut me a installation
disc of the newest and finest version of Compass with all the bells and
whistles that I can install over what I have and be working with the new and
improved version..

Let me know what the cost would be and I will send you a check.  I could try
to get it from the internet but I'm sure I would screw it up somewhere along
the way.  I am a good user, not a good hacker type.

The program as it is now installed works well.  But I have the feeling I am
missing something.  I have copied all the instructions and keep them in a
large notebook.    This has solved many problems.  But I am sure it is
vastly out of date.

Thanks

Dave Belski 
408 Southern Sky
Carlsbad, NM 88220
575 885 6168 home
575 361 6168 cell

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 404
Date: Mon, 21 Oct 2013 12:35:33 -0600
From: "Larry Fish" 
Subject: RE: [compass-users] New Version of Compass

Dave,

It really would be a good idea to upgrade your installation. I've literally
made hundreds of changes during in the last 11 years. For example:

Since 2002 = 224 changes

Since 2004 = 200 changes

Since 2012 = 48 changes

Many of the changes have been bug fixes that could impact the problem you
are currently having.

The cost of the upgrade CD is $28 plus $5 shipping/handling for a total of
$33. There is an order form with my address and all relevant information
here:

http://www.fountainware.com/compass/Purchase/regform.htm

You can also order via credit card here:

http://www.fountainware.com/compass/Purchase/credit.htm

It is the forth item down under "CD-ROM Update - For registered users."

Let me know if you have any questions.

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of dave belski
Sent: Monday, October 21, 2013 11:04 AM
Subject: Re: [compass-users] New Version of Compass

On 10/20/2013 5:31 PM, Larry Fish wrote:

Hi Dave,

There are lots of different things that could cause this kind of problem,
depending on exactly what you mean. Can you give me a little more
information? 

1. When you say "won't let me save the file" what exactly do you mean? Do
you get an error message? Do you save and yet the data is not changed?

2. What do you mean by older? 6 months, 1 year, 25 years?

The more details you can give me, the easier it is for me to figure it out.

Larry

  _____  

Larry,

Here goes.

I have a cave, XX with many survey files.  When I try to correct a point on
survey 3, and try to save it to the survey, I get a message "Can't rename
file"   It is constant no matter what method I try to save it.  On one
occasion, when I quit the program and booted it up again, the correction was
there.  But this was not always the case.

My version of Compass:

Original copy, May 30, 2002
An update by disc June 25, 2004
Another partial update from the net  1/27/12

I upgraded to a new computer and I suspect something was lost in the
process.

My solution to the problem is this.  Would you please cut me a installation
disc of the newest and finest version of Compass with all the bells and
whistles that I can install over what I have and be working with the new and
improved version..

Let me know what the cost would be and I will send you a check.  I could try
to get it from the internet but I'm sure I would screw it up somewhere along
the way.  I am a good user, not a good hacker type.

The program as it is now installed works well.  But I have the feeling I am
missing something.  I have copied all the instructions and keep them in a
large notebook.    This has solved many problems.  But I am sure it is
vastly out of date.

Thanks

Dave Belski 
408 Southern Sky
Carlsbad, NM 88220
575 885 6168 home
575 361 6168 cell

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 405
Date: Mon, 21 Oct 2013 12:50:32 -0600
From: "Larry Fish" 
Subject: Line Weights

Hi Rich,
 There's still no way to reset the line weight of
 individual surveys, right?
That's correct. It will take quite a bit of coding to add that feature and
I'm fairly business with work right now. It is on my "to-do" list, although
that list literally has hundreds of items on it.
Larry


Messsage #: 406
Date: Thu, 07 Nov 2013 20:07:34 +0100
From: Roger Schuster 
Subject: Broken Sketch Editor installer?

Hello Larry,

yesterday I downloaded Sketch Editor from your Web site and installed it 
to c:\Program Files (x86)\compass\. The installer places 
SketchEditor.chm to this directory and a link  on my desktop pointing to 
"C:\Program Files (x86)\compass\SketchEditor.exe". But SketchEditor.exe 
is neither in this directory nor somewhere else on my computer. I also 
downloaded and installed the package a second time but with the same 
result. The other Compass packages install fine. I run Windows 7 German.

Regards,

Roger


Messsage #: 407
Date: Fri, 8 Nov 2013 03:13:15 -0700
From: "Larry" 
Subject: RE: [compass-users] Broken Sketch Editor installer?

Hi Roger,

I suspect the problem has to do with the installation directory and/or
64-bit Windows.

The Default Directory for installing the Sketch editor is "c:\cave\wcomp32."
I've deliberately avoided installing Compass programs to the "C:\Program
Files" directory because the newer versions of Windows place restrictions on
what you can do in those directories. For compatibility with previous
versions of Windows, I needed to maintain the ability to write data to the
configuration files in the installation directory.

I'm using Windows 7, 32-bits on my Desktop computer and just allowing the
installer to use its default settings works fine. It places the program in
"c:\cave\wcomp32" and puts an Icon on the desktop. Clicking on the Icon runs
the program. I've also installed it on my Win8 tablet and it runs without a
problem.

I also have a copy of Windows 7, 64-bits in a virtual machine so I can test
programs under it. The Sketch Editor installs without a problem under
Win7-64-bits. It places an Icon on the Desktop; clicking on the icon runs
the program as expected. 

You said that you installed the Sketch Editor to: "C:\Program Files (x86)\."
This is a special directory for 32-bit programs on a 64-bit operating
system. I believe Windows limits which programs can write data to that
directory.

I'm using a non-standard installer so my guess is that Window is blocking
the installation of the exe-file to that directory. (I'm not sure why it is
allowing the help file to be installed, and I'm not sure why it didn't block
the installation of the other Compass programs.) Here are some suggestions:

1. Install the program to the "c:\cave\wcomp32."

2. If you really need to have the program installed to "C:\Program Files
(x86)\," right click on the installation program and select the "Run as
Administrator" option. That may allow the file to be installed.

3. If that doesn't work, you can try turning off "User Account Control"
(UAC) temporarily. Here are some instructions for doing this:

http://windows.microsoft.com/en-us/windows7/turn-user-account-control-on-or-
off

I would do some more test myself, but my Virtual Machine copy of
Win7-64-bits, suddenly decided to install 135 updates and it will probably
be busy for a couple hours.
 
Let me know if these suggestions help or if you have any more questions.

Larry

From: [email protected] [mailto:[email protected]]
On Behalf Of Roger Schuster
Sent: Thursday, November 07, 2013 12:08 PM
Subject: [compass-users] Broken Sketch Editor installer?

Hello Larry,

yesterday I downloaded Sketch Editor from your Web site and installed it 
to c:\Program Files (x86)\compass\. The installer places 
SketchEditor.chm to this directory and a link  on my desktop pointing to 
"C:\Program Files (x86)\compass\SketchEditor.exe". But SketchEditor.exe 
is neither in this directory nor somewhere else on my computer. I also 
downloaded and installed the package a second time but with the same 
result. The other Compass packages install fine. I run Windows 7 German.

Regards,

Roger

Yahoo Groups Links


Messsage #: 408
Date: Fri, 08 Nov 2013 21:47:15 +0100
From: Roger Schuster 
Subject: Re: [compass-users] Broken Sketch Editor installer?

Hi Larry,

thank you for your support. After several attempts I found out it's some 
kind of interference between Sketch Editor and my virus scanner.

I disabled my virus scanner (Avast) and the installation of Sketch 
Editor went fine! But after enabling the virus scanner again after 
installation it warns me about a virus "Win32:Evo-gen" in 
SketchEditor.exe. False alert or truth? The online scanner at 
virustotal.com also brings one alert.

Regards,

Roger


Messsage #: 409
Date: Fri, 8 Nov 2013 20:34:20 -0700
From: "Larry" 
Subject: RE: [compass-users] Broken Sketch Editor installer?

Hi Roger,

None of the Compass programs should have any viruses or malware in them.
They generated with Delphi and almost everything that goes in them has been
written by me.

Virus scanners work by looking for patterns. Sometimes the patterns in the
code or data of a legitimate program will accidentally match a virus. I
searched the web and found dozens of reports of false positives for the
"Win32:Evo-gen" from people using Avast. All of them are in the last few
weeks. The last link below has some bad things to say about the company:

http://community.freepascal.org/bboards/message?message_id^5640
 &forum_id$082

http://forum.avast.com/index.php?topic8967.0

http://forums.cnet.com/7723-21578_102-601884/warning-about-avast/

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Roger Schuster
Sent: Friday, November 08, 2013 1:47 PM
Subject: Re: [compass-users] Broken Sketch Editor installer?

Hi Larry,

thank you for your support. After several attempts I found out it's some 
kind of interference between Sketch Editor and my virus scanner.

I disabled my virus scanner (Avast) and the installation of Sketch 
Editor went fine! But after enabling the virus scanner again after 
installation it warns me about a virus "Win32:Evo-gen" in 
SketchEditor.exe. False alert or truth? The online scanner at 
virustotal.com also brings one alert.

Regards,

Roger

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 410
Date: Sun, 10 Nov 2013 12:43:42 +0100
From: Roger Schuster 
Subject: Re: [compass-users] Broken Sketch Editor installer?

Hello Larry,

don't worry I trust you and know you don't spread malware. I was sure 
the virus alert was just a false positive. Anyway I dumped Avast (it 
started to annoy me with its many popup messages and by slowing down my 
computer) and all Compass packages are now installing and running fine. 
Case closed! ;)

Best regards,

Roger


Messsage #: 411
Date: 05 Dec 2013 02:03:59 -0800
From: 
Subject: duplicate statistics

 hello Larry
 thank you for instigating the duplicate shot statistic - excellent!
 I have now found many dups that I had not found previously when checking using the GIS program 
 thanks again
 Bob
-de›I

hello Larrythank you for instigating the duplicate shot statistic - excellent!I have now found many dups that I had not found previously when checking using the GIS program thanks againBob


Messsage #: 412
Date: Tue, 17 Dec 2013 10:42:29 -0500
From: "David A. Riggs" 
Subject: Single Instrument Correction

I recently performed a cave survey where the team used two compasses
and two inclinometers, one set exclusively for forward sights, one set
exclusively for backsights. This is, in fact, how we typically survey,
versus using a single set of instruments used for both front and
backsights.

In this case, the two inclinometers disagree, and I need to apply a
-2.0Ý correction to the forward clino. (I recorded the measured values
as given in cave, as we were only able to determine which instrument
was "off" once we were back on the surface.)

It appears that Compass allows instrument correction at the Survey
level, but I don't see the ability to specify that the correction be
applied to only forward or backsights; it appears that Compass will
apply this correction factor to both readings, even if backsights are
enabled for the Survey. Is this understanding correct?

Is there a way to specify instrument correction for only forward or
only backsight instrument?

If not, is my best bet for applying a correction to a single
instrument Repair Shots - Inclin - Repair Forward Inclination -
Formula, with multiplier 1.0 and offset -2.0? This option would not
preserve the recorded value, only the corrected value, right?

Thanks!

David A. Riggs
Germany Valley, WV

David A. Riggs 


Messsage #: 413
Date: Tue, 17 Dec 2013 13:38:15 -0500
From: Tony Canike 
Subject: Re: [compass-users] Single Instrument Correction

Great question, I was just thinking about that last week. 

 On Dec 17, 2013, at 10:42 AM, "David A. Riggs"  wrote:
 
 applied to only forward or backsights; it appears that Compass will
 apply this correction factor to both readings, even if backsights are
 enabled for the Survey. Is this understanding correct?


Messsage #: 414
Date: Tue, 17 Dec 2013 16:57:26 -0700
From: "Larry" 
Subject: RE: [compass-users] Single Instrument Correction

Hi David,

Thanks for your email.

You've pointed out an important shortcoming in Compass. As a result, I've
added a new feature that allows you to add secondary Compass/Inclinometer
correction factors that are added to the Compass and Inclination values for
back sights. The new version is on the internet here:
 
http://www.fountainware.com/compass/downloads/download.htm

I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.

Thanks again. This kind of feedback is very useful to me.

Larry Fish

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Tuesday, December 17, 2013 8:42 AM
Subject: [compass-users] Single Instrument Correction

I recently performed a cave survey where the team used two compasses
and two inclinometers, one set exclusively for forward sights, one set
exclusively for backsights. This is, in fact, how we typically survey,
versus using a single set of instruments used for both front and
backsights.

In this case, the two inclinometers disagree, and I need to apply a
-2.0Ý correction to the forward clino. (I recorded the measured values
as given in cave, as we were only able to determine which instrument
was "off" once we were back on the surface.)

It appears that Compass allows instrument correction at the Survey
level, but I don't see the ability to specify that the correction be
applied to only forward or backsights; it appears that Compass will
apply this correction factor to both readings, even if backsights are
enabled for the Survey. Is this understanding correct?

Is there a way to specify instrument correction for only forward or
only backsight instrument?

If not, is my best bet for applying a correction to a single
instrument Repair Shots - Inclin - Repair Forward Inclination -
Formula, with multiplier 1.0 and offset -2.0? This option would not
preserve the recorded value, only the corrected value, right?

Thanks!

David A. Riggs
Germany Valley, WV

David A. Riggs 

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 415
Date: Tue, 17 Dec 2013 22:15:01 -0500
From: "David A. Riggs" 
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:

 You've pointed out an important shortcoming in Compass. As a result, I've added a new feature that allows you to add secondary Compass/Inclinometer correction factors that are added to the Compass and Inclination values for back sights. The new version is on the internet here:

 http://www.fountainware.com/compass/downloads/download.htm

Hi Larry,

I write software myself, and I can't give you enough praise for adding
a significant feature like this within 12 hours of a request... on a
weekday! Thank you!

I'm curious about backwards compatibility with this feature. Our
Compass files are edited by several users, and compiled/viewed by many
more users. If I add a "secondary instrument corrector factor" to one
of our .DAT files, will users with yesterday's version of Compass be
able to view/edit it? Will their compiled lineplot be different than
mine?

If there are version issues related to data consistency, then I can
only test the feature now, but will probably have to refrain from
using it immediately until our other project members have time to
upgrade Compass.

Again, thanks so much for such a speedy implementation!

Dave Riggs
Germany Valley, WV

David A. Riggs 


Messsage #: 416
Date: Tue, 17 Dec 2013 23:40:05 -0500
From: "David A. Riggs" 
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:

 I've tested the feature on several large cave files, but since it is new code, there is a chance that I have missed something. Be on the lookout for any problems Let me know if you see anything so I can correct them quickly.

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley, WV

David A. Riggs 


Messsage #: 417
Date: Wed, 18 Dec 2013 04:58:32 -0700
From: "Larry" 
Subject: RE: [compass-users] Single Instrument Correction

Hi David,

 I write software myself, and I can't give you enough praise for adding
 a significant feature like this within 12 hours of a request... on a
 weekday! Thank you!

Thank you. Any praise is greatly appreciated.

 I'm curious about backwards compatibility with this feature.
 Our Compass files are edited by several users, and
 compiled/viewed by many more users. If I add a "secondary
 instrument corrector factor" to one of our .DAT files, will
 users with yesterday's version of Compass be able to
 view/edit it?

They will be able to read and process the files. However, older versions of
the software will not know how to save the data. If they edit a survey in
which the new correction factors have been saved, the new factors will be
lost.

Since any registered Compass user can download a new version at any time,
you should be able to upgrade everyone without any hassles.

 Will their compiled lineplot be different than
 mine?

Yes. If you have added back sight instrument corrections, then the shot
angles will be different.

Larry


Messsage #: 418
Date: Wed, 18 Dec 2013 14:12:57 -0700
From: "Larry" 
Subject: RE: [compass-users] Single Instrument Correction

Hi David,
I didn't even think about using the correction factors in the Validation
process. That shows how easy it is to overlook things.
I've fixed the problem and there is a new version of Compass on the web
site.
Larry 

From: [email protected] [mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Tuesday, December 17, 2013 9:40 PM
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:

 I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley, WV

David A. Riggs 

Yahoo Groups Links


Messsage #: 419
Date: Fri, 27 Dec 2013 10:39:02 -0700
From: Derek Bristol 
Subject: Re: [compass-users] Single Instrument Correction

I don't know if anyone else has been having problems, but since the update I'm getting a "" is not a valid floating point" error when trying to edit cave files or individual surveys with the Cave Editor. I can process data with the Project Manager, but there seems to be an issue with the Editor.

 On Dec 18, 2013, at 2:12 PM, "Larry"  wrote:
 
 Hi David,
 I didn't even think about using the correction factors in the Validation
 process. That shows how easy it is to overlook things.
 I've fixed the problem and there is a new version of Compass on the web
 site.
 Larry 
 
 -----Original Message-----
 From: [email protected] [mailto:[email protected]]
 On Behalf Of David A. Riggs
 Sent: Tuesday, December 17, 2013 9:40 PM
 To: [email protected]
 Subject: Re: [compass-users] Single Instrument Correction
 
 On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:
 
  I've tested the feature on several large cave files, but since it is new
 code, there is a chance that I have missed something. Be on the lookout for
 any problems Let me know if you see anything so I can correct them quickly.
 
 Hi Larry,
 
 I did a quick test with the editor by setting "Inclinometer
 Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
 file did correctly contain the new CORRECTIONS2 header.
 
 However, in the editor, neither the Shot Validation nor the Validate
 Backsights seem to honor the correction value. In other words, both
 only report an error if the two entered values differ by more than the
 Backsight Error Limit value; I would expect that both instruments
 would have their correction applied before comparison.
 
 Is there some way to "apply" the correction that I'm missing? Having
 never used the instrument correction feature before, I suppose I could
 simply be using it wrong!
 
 Minor note: I also notice that in the Edit Heading panel, when
 entering a value into the final field, "Inclinometer Correction-2",
 pressing the enter key gives a "Grid index out of range" error popup.
 
 Thanks again!
 
 Dave Riggs
 Germany Valley, WV
 
 -- 
 David A. Riggs 
 
 ------------------------------------
 
 Yahoo Groups Links

I don't know if anyone else has been having problems, but since the update I'm getting a "" is not a valid floating point" error when trying to edit cave files or individual surveys with the Cave Editor. I can process data with the Project Manager, but there seems to be an issue with the Editor.On Dec 18, 2013, at 2:12 PM, "Larry" <[email protected]> wrote:

 
      
      Hi David,
I didn't even think about using the correction factors in the Validation
process. That shows how easy it is to overlook things.
I've fixed the problem and there is a new version of Compass on the web
site.
Larry 

From: [email protected] [mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Tuesday, December 17, 2013 9:40 PM
ups.com
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry <[email protected]> wrote:
>
> I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.
>

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley, WV

David A. Riggs <[email protected]>

Yahoo Groups Links


Messsage #: 420
Date: Fri, 27 Dec 2013 13:31:44 -0700
From: "Larry" 
Subject: RE: [compass-users] Single Instrument Correction

Hi Derek,

I haven't had any other reports of problems with the new version of the
Editor. Testing the current version of the Editor, I don't receive any error
messages. I've sometimes had problems when the computer is set to the
European standard for decimal point or "thousands" separator, so I changed
the settings and still didn't have a problem. Without more information, my
best guess is that there is a corruption problem with the data you are
using.

Can you give me more information about exactly what you are doing to get the
error? For example, do you get the error the minute you open a file in the
Editor? Or do you get it when you select a survey? Does it only occur when
you enter data in one of the fields? If it occurs when you enter data in a
field, can you tell me which field? Is it in the Header or in the survey
shots?

One option would be to send me a copy of the data you are working on. That
way I can duplicate exactly what you are doing. At the same time, if the
data is corrupted in some way, I can fix it. If you choose to send me data,
don't send it to the whole group. Use this email address:

[email protected]

I keep all survey data private and confidential unless I have specific
instructions from the owner of the data to release it to someone.

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Derek Bristol
Sent: Friday, December 27, 2013 10:39 AM
Subject: Re: [compass-users] Single Instrument Correction

I don't know if anyone else has been having problems, but since the update
I'm getting a "" is not a valid floating point" error when trying to edit
cave files or individual surveys with the Cave Editor. I can process data
with the Project Manager, but there seems to be an issue with the Editor.

On Dec 18, 2013, at 2:12 PM, "Larry"  wrote:

Hi David,
I didn't even think about using the correction factors in the Validation
process. That shows how easy it is to overlook things.
I've fixed the problem and there is a new version of Compass on the web
site.
Larry 

From: [email protected] [mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Tuesday, December 17, 2013 9:40 PM
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:

 I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley, WV

David A. Riggs 

Yahoo Groups Links

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 421
Date: Fri, 27 Dec 2013 14:14:57 -0700
From: Derek Bristol 
Subject: Re: [compass-users] Single Instrument Correction

The issue is with the CaveEd32 application, not with a specific survey file. I've installed version 5.13.12.18.75 on two PCs (one running Windows 7 and the other running Windows 8.1) and get the same error when trying to open the Editor. It happens when opening the Editor directly, or opening through the Project Manager. I don't need to be opening a survey file to get the error. Again, the error is "" is not a valid floating point value". I can click OK and open the editor, but I get the message again when trying to open a survey file, and it won't let me actually open a survey (any survey) for viewing or editing of data. I also get the error when trying to access various functions within the Editor such as "Options - Survey Settings" or trying to create a new file.

The last version I had installed was from May, 2013 and didn't have this problem. I tried redownloading and reinstalling but there is no change.

Derek

 On Dec 27, 2013, at 1:31 PM, "Larry"  wrote:
 
 Hi Derek,
 
 I havenÉ?Tt had any other reports of problems with the new version of the Editor. Testing the current version of the Editor, I donÉ?Tt receive any error messages. IÉ?Tve sometimes had problems when the computer is set to the European standard for decimal point or É?othousandsÉ?? separator, so I changed the settings and still didnÉ?Tt have a problem. Without more information, my best guess is that there is a corruption problem with the data you are using.
 
 Can you give me more information about exactly what you are doing to get the error? For example, do you get the error the minute you open a file in the Editor? Or do you get it when you select a survey? Does it only occur when you enter data in one of the fields? If it occurs when you enter data in a field, can you tell me which field? Is it in the Header or in the survey shots?
 
 One option would be to send me a copy of the data you are working on. That way I can duplicate exactly what you are doing. At the same time, if the data is corrupted in some way, I can fix it. If you choose to send me data, donÉ?Tt send it to the whole group. Use this email address:
 
 [email protected]
 
 I keep all survey data private and confidential unless I have specific instructions from the owner of the data to release it to someone.
 
 Larry
 
 From: [email protected] [mailto:[email protected]] On Behalf Of Derek Bristol
 Sent: Friday, December 27, 2013 10:39 AM
 To: [email protected]
 Cc: 
 Subject: Re: [compass-users] Single Instrument Correction
 
 I don't know if anyone else has been having problems, but since the update I'm getting a "" is not a valid floating point" error when trying to edit cave files or individual surveys with the Cave Editor. I can process data with the Project Manager, but there seems to be an issue with the Editor.
 
 On Dec 18, 2013, at 2:12 PM, "Larry"  wrote:
 
 Hi David,
 I didn't even think about using the correction factors in the Validation
 process. That shows how easy it is to overlook things.
 I've fixed the problem and there is a new version of Compass on the web
 site.
 Larry 
 
 -----Original Message-----
 From: [email protected] [mailto:[email protected]]
 On Behalf Of David A. Riggs
 Sent: Tuesday, December 17, 2013 9:40 PM
 To: [email protected]
 Subject: Re: [compass-users] Single Instrument Correction
 
 On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:
 
  I've tested the feature on several large cave files, but since it is new
 code, there is a chance that I have missed something. Be on the lookout for
 any problems Let me know if you see anything so I can correct them quickly.
 
 Hi Larry,
 
 I did a quick test with the editor by setting "Inclinometer
 Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
 file did correctly contain the new CORRECTIONS2 header.
 
 However, in the editor, neither the Shot Validation nor the Validate
 Backsights seem to honor the correction value. In other words, both
 only report an error if the two entered values differ by more than the
 Backsight Error Limit value; I would expect that both instruments
 would have their correction applied before comparison.
 
 Is there some way to "apply" the correction that I'm missing? Having
 never used the instrument correction feature before, I suppose I could
 simply be using it wrong!
 
 Minor note: I also notice that in the Edit Heading panel, when
 entering a value into the final field, "Inclinometer Correction-2",
 pressing the enter key gives a "Grid index out of range" error popup.
 
 Thanks again!
 
 Dave Riggs
 Germany Valley, WV
 
 -- 
 David A. Riggs 
 
 ------------------------------------
 
 Yahoo Groups Links

The issue is with the CaveEd32 application, not with a specific survey file. I've installed version 5.13.12.18.75 on two PCs (one running Windows 7 and the other running Windows 8.1) and get the same error when trying to open the Editor. It happens when opening the Editor directly, or opening through the Project Manager. I don't need to be opening a survey file to get the error. Again, the error is "" is not a valid floating point value". I can click OK and open the editor, but I get the message again when trying to open a survey file, and it won't let me actually open a survey (any survey) for viewing or editing of data. I also get the error when trying to access various functions within the Editor such as "Options -> Survey Settings" or trying to create a new file.The last version I had installed was from May, 2013 and didn't have this problem. I tried redownloading and reinstalling but there is no change.DerekOn Dec 27, 2013, at 1:31 PM, "Larry" <[email protected]> wrote:

 

Hi Derek,

 

I havenÉ?Tt had any other reports of
problems with the new version of the Editor. Testing the current version of the
Editor, I donÉ?Tt receive any error messages. IÉ?Tve sometimes had
problems when the computer is set to the European standard for decimal point or
É?othousandsÉ?? separator, so I changed the settings and still didnÉ?Tt
have a problem. Without more information, my best guess is that there is a
corruption problem with the data you are using.

 

Can you give me more information about
exactly what you are doing to get the error? For example, do you get the error
the minute you open a file in the Editor? Or do you get it when you select a
survey? Does it only occur when you enter data in one of the fields? If it
occurs when you enter data in a field, can you tell me which field? Is it in
the Header or in the survey shots?

 

One option would be to send me a copy of
the data you are working on. That way I can duplicate exactly what you are
doing. At the same time, if the data is corrupted in some way, I can fix it. If
you choose to send me data, donÉ?Tt send it to the whole group. Use this
email address:

 

[email protected]

 

I keep all survey data private and
confidential unless I have specific instructions from the owner of the data to
release it to someone.

 

Larry

 

From: [email protected] [mailto:[email protected]] On Behalf Of Derek Bristol
Sent: Friday, December 27, 2013
10:39 AM
To: [email protected]
Cc: <[email protected]>
Subject: Re: [compass-users]
Single Instrument Correction

 

  

I don't know if anyone else has been having problems, but since the
update I'm getting a "" is not a valid floating point" error
when trying to edit cave files or individual surveys with the Cave Editor. I
can process data with the Project Manager, but there seems to be an issue with
the Editor.

On Dec 18, 2013, at 2:12 PM, "Larry" <[email protected]> wrote:

  

Hi David,
I didn't even think about using the correction factors in the Validation
process. That shows how easy it is to overlook things.
I've fixed the problem and there is a new version of Compass on the web
site.
Larry 

From: [email protected]
[mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Tuesday, December 17, 2013 9:40 PM
ups.com
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry <[email protected]> wrote:
>
> I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.
>

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley, WV

David A. Riggs <[email protected]>

Yahoo Groups Links


Messsage #: 422
Date: Fri, 27 Dec 2013 17:05:22 -0500
From: Tony Canike 
Subject: Re: [compass-users] Single Instrument Correction

Derek, does your error look like the below screenshot?    I only get it 
when I  Surveys-Find Shot/Station in File.

Been getting this error for years, one .DAT file I inherited has crazy 
station names, and I only get the error with that data file.

I just now downloaded the latest version of Compass, installed it, and 
still get the same error, but as I said, only when searching this one 
data file.

On 12/27/2013 4:14 PM, Derek Bristol ([email protected]) wrote
 The issue is with the CaveEd32 application, not with a specific survey 
 file. I've installed version 5.13.12.18.75 on two PCs (one running 
 Windows 7 and the other running Windows 8.1) and get the same error 
 when trying to open the Editor. It happens when opening the Editor 
 directly, or opening through the Project Manager. I don't need to be 
 opening a survey file to get the error. Again, the error is "" is not 
 a valid floating point value". I can click OK and open the editor, but 
 I get the message again when trying to open a survey file, and it 
 won't let me actually open a survey (any survey) for viewing or 
 editing of data. I also get the error when trying to access various 
 functions within the Editor such as "Options - Survey Settings" or 
 trying to create a new file.

 The last version I had installed was from May, 2013 and didn't have 
 this problem. I tried redownloading and reinstalling but there is no 
 change.

 Derek

 On Dec 27, 2013, at 1:31 PM, "Larry"   wrote:

 Hi Derek,

 I havenÉ?Tt had any other reports of problems with the new version of 
 the Editor. Testing the current version of the Editor, I donÉ?Tt 
 receive any error messages. IÉ?Tve sometimes had problems when the 
 computer is set to the European standard for decimal point or 
 É?othousandsÉ?? separator, so I changed the settings and still didnÉ?Tt 
 have a problem. Without more information, my best guess is that there 
 is a corruption problem with the data you are using.

 Can you give me more information about exactly what you are doing to 
 get the error? For example, do you get the error the minute you open 
 a file in the Editor? Or do you get it when you select a survey? Does 
 it only occur when you enter data in one of the fields? If it occurs 
 when you enter data in a field, can you tell me which field? Is it in 
 the Header or in the survey shots?

 One option would be to send me a copy of the data you are working on. 
 That way I can duplicate exactly what you are doing. At the same 
 time, if the data is corrupted in some way, I can fix it. If you 
 choose to send me data, donÉ?Tt send it to the whole group. Use this 
 email address:

 [email protected] 

 I keep all survey data private and confidential unless I have 
 specific instructions from the owner of the data to release it to 
 someone.

 Larry

 ------------------------------------------------------------------------

 *From:*[email protected] 
  
 [mailto:[email protected] 
 ] *On Behalf Of *Derek Bristol
 *Sent:* Friday, December 27, 2013 10:39 AM
 *To:* [email protected] 
 
 *Cc:*  
 *Subject:* Re: [compass-users] Single Instrument Correction

 I don't know if anyone else has been having problems, but since the 
 update I'm getting a "" is not a valid floating point" error when 
 trying to edit cave files or individual surveys with the Cave Editor. 
 I can process data with the Project Manager, but there seems to be an 
 issue with the Editor.

 On Dec 18, 2013, at 2:12 PM, "Larry"   wrote:

 Hi David,
 I didn't even think about using the correction factors in the Validation
 process. That shows how easy it is to overlook things.
 I've fixed the problem and there is a new version of Compass on the web
 site.
 Larry

 -----Original Message-----
 From: [email protected] 
  
 [mailto:[email protected]]
 On Behalf Of David A. Riggs
 Sent: Tuesday, December 17, 2013 9:40 PM
 To: [email protected] 
 Subject: Re: [compass-users] Single Instrument Correction

 On Tue, Dec 17, 2013 at 6:57 PM, Larry   wrote:
 
  I've tested the feature on several large cave files, but since it 
 is new
 code, there is a chance that I have missed something. Be on the 
 lookout for
 any problems Let me know if you see anything so I can correct them 
 quickly.

 Hi Larry,

 I did a quick test with the editor by setting "Inclinometer
 Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
 file did correctly contain the new CORRECTIONS2 header.

 However, in the editor, neither the Shot Validation nor the Validate
 Backsights seem to honor the correction value. In other words, both
 only report an error if the two entered values differ by more than the
 Backsight Error Limit value; I would expect that both instruments
 would have their correction applied before comparison.

 Is there some way to "apply" the correction that I'm missing? Having
 never used the instrument correction feature before, I suppose I could
 simply be using it wrong!

 Minor note: I also notice that in the Edit Heading panel, when
 entering a value into the final field, "Inclinometer Correction-2",
 pressing the enter key gives a "Grid index out of range" error popup.

 Thanks again!

 Dave Riggs
 Germany Valley, WV

 -- 
 David A. Riggs  

 ------------------------------------

 Yahoo Groups Links
  
    Derek, does your error look like the below screenshot?Aˇ Aˇ I only get
    it when IAˇ Surveys->Find Shot/Station in File.Aˇ 
    
    Been getting this error for years, one .DAT file I inherited has
    crazy station names, and I only get the error with that data file.
    
    I just now downloaded the latest version of Compass, installed it,
    and still get the same error, but as I said, only when searching
    this one data file.
    
    On 12/27/2013 4:14 PM, Derek Bristol
      ([email protected]) wrote
    
      Aˇ
          
            The issue is with the CaveEd32 application, not with a
              specific survey file. I've installed version 5.13.12.18.75
              on two PCs (one running Windows 7 and the other running
              Windows 8.1) and get the same error when trying to open
              the Editor. It happens when opening the Editor directly,
              or opening through the Project Manager. I don't need to be
              opening a survey file to get the error. Again, the error
              is "" is not a valid floating point value". I can click OK
              and open the editor, but I get the message again when
              trying to open a survey file, and it won't let me actually
              open a survey (any survey) for viewing or editing of data.
              I also get the error when trying to access various
              functions within the Editor such as "Options -> Survey
              Settings" or trying to create a new file.
            
            The last version I had installed was from May, 2013 and
              didn't have this problem. I tried redownloading and
              reinstalling but there is no change.
            
            Derek
            
              On Dec 27, 2013, at 1:31 PM, "Larry" <[email protected]>
              wrote:
              
                Aˇ
                  
                    Hi
                          Derek,
                    Aˇ
                    I
                          havenÉ?Tt had any other reports of
                          problems with the new version of the Editor.
                          Testing the current version of the
                          Editor, I donÉ?Tt receive any error messages.
                          IÉ?Tve sometimes had
                          problems when the computer is set to the
                          European standard for decimal point or
                          É?othousandsÉ?? separator, so I changed the
                          settings and still didnÉ?Tt
                          have a problem. Without more information, my
                          best guess is that there is a
                          corruption problem with the data you are
                          using.
                    Aˇ
                    Can you
                          give me more information about
                          exactly what you are doing to get the error?
                          For example, do you get the error
                          the minute you open a file in the Editor? Or
                          do you get it when you select a
                          survey? Does it only occur when you enter data
                          in one of the fields? If it
                          occurs when you enter data in a field, can you
                          tell me which field? Is it in
                          the Header or in the survey shots?
                    Aˇ
                    One
                          option would be to send me a copy of
                          the data you are working on. That way I can
                          duplicate exactly what you are
                          doing. At the same time, if the data is
                          corrupted in some way, I can fix it. If
                          you choose to send me data, donÉ?Tt send it to
                          the whole group. Use this
                          email address:
                    Aˇ
                    [email protected]
                    Aˇ
                    I keep
                          all survey data private and
                          confidential unless I have specific
                          instructions from the owner of the data to
                          release it to someone.
                    Aˇ
                    Larry
                    Aˇ
                          
                      From:
                            [email protected]
                            [mailto:[email protected]]
                            On Behalf
                                Of Derek Bristol
                            Sent:
                            Friday, December 27, 2013
                            10:39 AM
                            To:
                            [email protected]
                            Cc:
                            <[email protected]>
                            Subject:
                            Re: [compass-users]
                            Single Instrument Correction
                    
                    Aˇ
                    Aˇ 
                          
                            I don't know if anyone else
                                  has been having problems, but since
                                  the
                                  update I'm getting a "" is not a valid
                                  floating point" error
                                  when trying to edit cave files or
                                  individual surveys with the Cave
                                  Editor. I
                                  can process data with the Project
                                  Manager, but there seems to be an
                                  issue with
                                  the Editor.
                            
                                  On Dec 18, 2013, at 2:12 PM, "Larry"
                                  <[email protected]>
                                  wrote:
                            
                              Aˇ 
                              
                                Hi
                                      David,
                                      I didn't even think about using
                                      the correction factors in the
                                      Validation
                                      process. That shows how easy it is
                                      to overlook things.
                                      I've fixed the problem and there
                                      is a new version of Compass on the
                                      web
                                      site.
                                      Larry 
                                      
                                      -----Original Message-----
                                      From: [email protected]
                                      [mailto:[email protected]]
                                      On Behalf Of David A. Riggs
                                      Sent: Tuesday, December 17, 2013
                                      9:40 PM
                                      To: [email protected]
                                      Subject: Re: [compass-users]
                                      Single Instrument Correction
                                      
                                      On Tue, Dec 17, 2013 at 6:57 PM,
                                      Larry <[email protected]>
                                      wrote:
                                      >
                                      > I've tested the feature on
                                      several large cave files, but
                                      since it is new
                                      code, there is a chance that I
                                      have missed something. Be on the
                                      lookout for
                                      any problems Let me know if you
                                      see anything so I can correct them
                                      quickly.
                                      >
                                      
                                      Hi Larry,
                                      
                                      I did a quick test with the editor
                                      by setting "Inclinometer
                                      Correction-2" to a large value,
                                      -10.0. I confirmed that the saved
                                      .DAT
                                      file did correctly contain the new
                                      CORRECTIONS2 header.
                                      
                                      However, in the editor, neither
                                      the Shot Validation nor the
                                      Validate
                                      Backsights seem to honor the
                                      correction value. In other words,
                                      both
                                      only report an error if the two
                                      entered values differ by more than
                                      the
                                      Backsight Error Limit value; I
                                      would expect that both instruments
                                      would have their correction
                                      applied before comparison.
                                      
                                      Is there some way to "apply" the
                                      correction that I'm missing?
                                      Having
                                      never used the instrument
                                      correction feature before, I
                                      suppose I could
                                      simply be using it wrong!
                                      
                                      Minor note: I also notice that in
                                      the Edit Heading panel, when
                                      entering a value into the final
                                      field, "Inclinometer
                                      Correction-2",
                                      pressing the enter key gives a
                                      "Grid index out of range" error
                                      popup.
                                      
                                      Thanks again!
                                      
                                      Dave Riggs
                                      Germany Valley, WV
                                      
                                      -- 
                                      David A. Riggs <[email protected]>


Messsage #: 423
Date: Fri, 27 Dec 2013 18:09:57 -0700
From: "Larry" 
Subject: RE: [compass-users] Single Instrument Correction

Hi Derek,

I think I've found the problem. At least it shows the same symptom you
described. I've fixed it and put the new version on the internet.

The problem only appears if you use certain default settings. It didn't show
up on my computer because I wasn't using those settings.

Let me know if this solves the problem for you.

Larry  

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Derek Bristol
Sent: Friday, December 27, 2013 2:15 PM
Subject: Re: [compass-users] Single Instrument Correction

The issue is with the CaveEd32 application, not with a specific survey file.
I've installed version 5.13.12.18.75 on two PCs (one running Windows 7 and
the other running Windows 8.1) and get the same error when trying to open
the Editor. It happens when opening the Editor directly, or opening through
the Project Manager. I don't need to be opening a survey file to get the
error. Again, the error is "" is not a valid floating point value". I can
click OK and open the editor, but I get the message again when trying to
open a survey file, and it won't let me actually open a survey (any survey)
for viewing or editing of data. I also get the error when trying to access
various functions within the Editor such as "Options - Survey Settings" or
trying to create a new file.

The last version I had installed was from May, 2013 and didn't have this
problem. I tried redownloading and reinstalling but there is no change.

Derek

On Dec 27, 2013, at 1:31 PM, "Larry"  wrote:

Hi Derek,

I haven't had any other reports of problems with the new version of the
Editor. Testing the current version of the Editor, I don't receive any error
messages. I've sometimes had problems when the computer is set to the
European standard for decimal point or "thousands" separator, so I changed
the settings and still didn't have a problem. Without more information, my
best guess is that there is a corruption problem with the data you are
using.

Can you give me more information about exactly what you are doing to get the
error? For example, do you get the error the minute you open a file in the
Editor? Or do you get it when you select a survey? Does it only occur when
you enter data in one of the fields? If it occurs when you enter data in a
field, can you tell me which field? Is it in the Header or in the survey
shots?

One option would be to send me a copy of the data you are working on. That
way I can duplicate exactly what you are doing. At the same time, if the
data is corrupted in some way, I can fix it. If you choose to send me data,
don't send it to the whole group. Use this email address:

[email protected]

I keep all survey data private and confidential unless I have specific
instructions from the owner of the data to release it to someone.

Larry

  _____  

From:   [email protected]
[mailto:[email protected]] On Behalf Of Derek Bristol
Sent: Friday, December 27, 2013 10:39 AM
Subject: Re: [compass-users] Single Instrument Correction

I don't know if anyone else has been having problems, but since the update
I'm getting a "" is not a valid floating point" error when trying to edit
cave files or individual surveys with the Cave Editor. I can process data
with the Project Manager, but there seems to be an issue with the Editor.

On Dec 18, 2013, at 2:12 PM, "Larry"  wrote:

Hi David,
I didn't even think about using the correction factors in the Validation
process. That shows how easy it is to overlook things.
I've fixed the problem and there is a new version of Compass on the web
site.
Larry 

From: [email protected] [mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Tuesday, December 17, 2013 9:40 PM
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:

 I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley, WV

David A. Riggs 

Yahoo Groups Links

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }


Messsage #: 424
Date: Fri, 27 Dec 2013 18:17:56 -0700
From: "Larry" 
Subject: RE: [compass-users] Single Instrument Correction [1 Attachment]

Hi Tony,

The error you are getting is probably caused by corruption in the survey
file. If you would like, I can go through your data and clean up any
problems you have.

If you want me to do that, send the data directly to my personal email:

[email protected]

If you send me the data, let me know exactly what you have to do get the
error.

Larry

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Tony Canike
Sent: Friday, December 27, 2013 3:05 PM
Subject: Re: [compass-users] Single Instrument Correction [1 Attachment]

Derek, does your error look like the below screenshot?    I only get it when
I  Surveys-Find Shot/Station in File.  

Been getting this error for years, one .DAT file I inherited has crazy
station names, and I only get the error with that data file.

I just now downloaded the latest version of Compass, installed it, and still
get the same error, but as I said, only when searching this one data file.

On 12/27/2013 4:14 PM, Derek Bristol ([email protected]) wrote

The issue is with the CaveEd32 application, not with a specific survey file.
I've installed version 5.13.12.18.75 on two PCs (one running Windows 7 and
the other running Windows 8.1) and get the same error when trying to open
the Editor. It happens when opening the Editor directly, or opening through
the Project Manager. I don't need to be opening a survey file to get the
error. Again, the error is "" is not a valid floating point value". I can
click OK and open the editor, but I get the message again when trying to
open a survey file, and it won't let me actually open a survey (any survey)
for viewing or editing of data. I also get the error when trying to access
various functions within the Editor such as "Options - Survey Settings" or
trying to create a new file.

The last version I had installed was from May, 2013 and didn't have this
problem. I tried redownloading and reinstalling but there is no change.

Derek

On Dec 27, 2013, at 1:31 PM, "Larry"  wrote:

Hi Derek,

I haven't had any other reports of problems with the new version of the
Editor. Testing the current version of the Editor, I don't receive any error
messages. I've sometimes had problems when the computer is set to the
European standard for decimal point or "thousands" separator, so I changed
the settings and still didn't have a problem. Without more information, my
best guess is that there is a corruption problem with the data you are
using.

Can you give me more information about exactly what you are doing to get the
error? For example, do you get the error the minute you open a file in the
Editor? Or do you get it when you select a survey? Does it only occur when
you enter data in one of the fields? If it occurs when you enter data in a
field, can you tell me which field? Is it in the Header or in the survey
shots?

One option would be to send me a copy of the data you are working on. That
way I can duplicate exactly what you are doing. At the same time, if the
data is corrupted in some way, I can fix it. If you choose to send me data,
don't send it to the whole group. Use this email address:

[email protected]

I keep all survey data private and confidential unless I have specific
instructions from the owner of the data to release it to someone.

Larry

  _____  

From:   [email protected]
[mailto:[email protected]] On Behalf Of Derek Bristol
Sent: Friday, December 27, 2013 10:39 AM
Subject: Re: [compass-users] Single Instrument Correction

I don't know if anyone else has been having problems, but since the update
I'm getting a "" is not a valid floating point" error when trying to edit
cave files or individual surveys with the Cave Editor. I can process data
with the Project Manager, but there seems to be an issue with the Editor.

On Dec 18, 2013, at 2:12 PM, "Larry"  wrote:

Hi David,
I didn't even think about using the correction factors in the Validation
process. That shows how easy it is to overlook things.
I've fixed the problem and there is a new version of Compass on the web
site.
Larry 

From: [email protected] [mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Tuesday, December 17, 2013 9:40 PM
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:

 I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley, WV

David A. Riggs 

Yahoo Groups Links

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}

st1\:*{behavior:url(#default#ieooui) }

[email protected]
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry <[email protected]>
wrote:
>
> I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.
>

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley,
 WV

David A. Riggs <[email protected]>

Yahoo Groups Links

 

Messsage #: 425
Date: Mon, 30 Dec 2013 10:03:27 -0700
From: Derek Bristol 
Subject: Re: [compass-users] Single Instrument Correction

Problem solved. Thanks!

 On Dec 27, 2013, at 6:09 PM, "Larry"  wrote:
 
 Hi Derek,
 
 I think IÉ?Tve found the problem. At least it shows the same symptom you described. IÉ?Tve fixed it and put the new version on the internet.
 
 The problem only appears if you use certain default settings. It didnÉ?Tt show up on my computer because I wasnÉ?Tt using those settings.
 
 Let me know if this solves the problem for you.
 
 Larry  
 
 From: [email protected] [mailto:[email protected]] On Behalf Of Derek Bristol
 Sent: Friday, December 27, 2013 2:15 PM
 To: [email protected]
 Cc: 
 Subject: Re: [compass-users] Single Instrument Correction
 
 The issue is with the CaveEd32 application, not with a specific survey file. I've installed version 5.13.12.18.75 on two PCs (one running Windows 7 and the other running Windows 8.1) and get the same error when trying to open the Editor. It happens when opening the Editor directly, or opening through the Project Manager. I don't need to be opening a survey file to get the error. Again, the error is "" is not a valid floating point value". I can click OK and open the editor, but I get the message again when trying to open a survey file, and it won't let me actually open a survey (any survey) for viewing or editing of data. I also get the error when trying to access various functions within the Editor such as "Options - Survey Settings" or trying to create a new file.
 
 The last version I had installed was from May, 2013 and didn't have this problem. I tried redownloading and reinstalling but there is no change.
 
 Derek
 
 On Dec 27, 2013, at 1:31 PM, "Larry"  wrote:
 
 Hi Derek,
 
 I havenÉ?Tt had any other reports of problems with the new version of the Editor. Testing the current version of the Editor, I donÉ?Tt receive any error messages. IÉ?Tve sometimes had problems when the computer is set to the European standard for decimal point or É?othousandsÉ?? separator, so I changed the settings and still didnÉ?Tt have a problem. Without more information, my best guess is that there is a corruption problem with the data you are using.
 
 Can you give me more information about exactly what you are doing to get the error? For example, do you get the error the minute you open a file in the Editor? Or do you get it when you select a survey? Does it only occur when you enter data in one of the fields? If it occurs when you enter data in a field, can you tell me which field? Is it in the Header or in the survey shots?
 
 One option would be to send me a copy of the data you are working on. That way I can duplicate exactly what you are doing. At the same time, if the data is corrupted in some way, I can fix it. If you choose to send me data, donÉ?Tt send it to the whole group. Use this email address:
 
 [email protected]
 
 I keep all survey data private and confidential unless I have specific instructions from the owner of the data to release it to someone.
 
 Larry
 
 From: [email protected] [mailto:[email protected]] On Behalf Of Derek Bristol
 Sent: Friday, December 27, 2013 10:39 AM
 To: [email protected]
 Cc: 
 Subject: Re: [compass-users] Single Instrument Correction
 
 I don't know if anyone else has been having problems, but since the update I'm getting a "" is not a valid floating point" error when trying to edit cave files or individual surveys with the Cave Editor. I can process data with the Project Manager, but there seems to be an issue with the Editor.
 
 On Dec 18, 2013, at 2:12 PM, "Larry"  wrote:
 
 Hi David,
 I didn't even think about using the correction factors in the Validation
 process. That shows how easy it is to overlook things.
 I've fixed the problem and there is a new version of Compass on the web
 site.
 Larry 
 
 -----Original Message-----
 From: [email protected] [mailto:[email protected]]
 On Behalf Of David A. Riggs
 Sent: Tuesday, December 17, 2013 9:40 PM
 To: [email protected]
 Subject: Re: [compass-users] Single Instrument Correction
 
 On Tue, Dec 17, 2013 at 6:57 PM, Larry  wrote:
 
  I've tested the feature on several large cave files, but since it is new
 code, there is a chance that I have missed something. Be on the lookout for
 any problems Let me know if you see anything so I can correct them quickly.
 
 Hi Larry,
 
 I did a quick test with the editor by setting "Inclinometer
 Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
 file did correctly contain the new CORRECTIONS2 header.
 
 However, in the editor, neither the Shot Validation nor the Validate
 Backsights seem to honor the correction value. In other words, both
 only report an error if the two entered values differ by more than the
 Backsight Error Limit value; I would expect that both instruments
 would have their correction applied before comparison.
 
 Is there some way to "apply" the correction that I'm missing? Having
 never used the instrument correction feature before, I suppose I could
 simply be using it wrong!
 
 Minor note: I also notice that in the Edit Heading panel, when
 entering a value into the final field, "Inclinometer Correction-2",
 pressing the enter key gives a "Grid index out of range" error popup.
 
 Thanks again!
 
 Dave Riggs
 Germany Valley, WV
 
 -- 
 David A. Riggs 
 
 ------------------------------------
 
 Yahoo Groups Links

Problem solved. Thanks!On Dec 27, 2013, at 6:09 PM, "Larry" <[email protected]> wrote:

 

Hi Derek,

I think IÉ?Tve found the problem. At
least it shows the same symptom you described. IÉ?Tve fixed it and put the
new version on the internet.

The problem only appears if you use
certain default settings. It didnÉ?Tt show up on my computer because I wasnÉ?Tt
using those settings.

Let me know if this solves the problem for
you.

Larry  

 

From: [email protected] [mailto:[email protected]] On Behalf Of Derek Bristol
Sent: Friday, December 27, 2013
2:15 PM
To: [email protected]
Cc: <[email protected]>
Subject: Re: [compass-users]
Single Instrument Correction

 

  

The issue is with the CaveEd32 application, not with a specific survey
file. I've installed version 5.13.12.18.75 on two PCs (one running Windows 7
and the other running Windows 8.1) and get the same error when trying to open
the Editor. It happens when opening the Editor directly, or opening through the
Project Manager. I don't need to be opening a survey file to get the error.
Again, the error is "" is not a valid floating point value". I
can click OK and open the editor, but I get the message again when trying to
open a survey file, and it won't let me actually open a survey (any survey) for
viewing or editing of data. I also get the error when trying to access various
functions within the Editor such as "Options -> Survey Settings"
or trying to create a new file.

 

The last version I had installed was from May, 2013 and didn't have
this problem. I tried redownloading and reinstalling but there is no change.

 

Derek

On Dec 27, 2013, at 1:31 PM, "Larry" <[email protected]> wrote:

  

Hi Derek,

 

I havenÉ?Tt had any other reports of problems with the new
version of the Editor. Testing the current version of the Editor, I donÉ?Tt
receive any error messages. IÉ?Tve sometimes had problems when the computer
is set to the European standard for decimal point or É?othousandsÉ??
separator, so I changed the settings and still didnÉ?Tt have a problem.
Without more information, my best guess is that there is a corruption problem with
the data you are using.

 

Can you give me more information about exactly what you are doing
to get the error? For example, do you get the error the minute you open a file
in the Editor? Or do you get it when you select a survey? Does it only occur
when you enter data in one of the fields? If it occurs when you enter data in a
field, can you tell me which field? Is it in the Header or in the survey shots?

 

One option would be to send me a copy of the data you are working
on. That way I can duplicate exactly what you are doing. At the same time, if
the data is corrupted in some way, I can fix it. If you choose to send me data,
donÉ?Tt send it to the whole group. Use this email address:

 

[email protected]
 

I keep all survey data private and confidential unless I have
specific instructions from the owner of the data to release it to someone.

 

Larry

 

From: [email protected]
[mailto:[email protected]]
On Behalf Of Derek Bristol
Sent: Friday, December 27, 2013
10:39 AM
To: [email protected]
Cc: <[email protected]>
Subject: Re: [compass-users]
Single Instrument Correction

 

  

I don't know if
anyone else has been having problems, but since the update I'm getting a
"" is not a valid floating point" error when trying to edit cave
files or individual surveys with the Cave Editor. I can process data with the
Project Manager, but there seems to be an issue with the Editor.

On Dec 18, 2013, at 2:12 PM, "Larry" <[email protected]> wrote:

  

Hi David,
I didn't even think about using the correction factors in the Validation
process. That shows how easy it is to overlook things.
I've fixed the problem and there is a new version of Compass on the web
site.
Larry 

From: [email protected]
[mailto:[email protected]]
On Behalf Of David A. Riggs
Sent: Tuesday, December 17, 2013 9:40 PM
ups.com
Subject: Re: [compass-users] Single Instrument Correction

On Tue, Dec 17, 2013 at 6:57 PM, Larry <[email protected]> wrote:
>
> I've tested the feature on several large cave files, but since it is new
code, there is a chance that I have missed something. Be on the lookout for
any problems Let me know if you see anything so I can correct them quickly.
>

Hi Larry,

I did a quick test with the editor by setting "Inclinometer
Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
file did correctly contain the new CORRECTIONS2 header.

However, in the editor, neither the Shot Validation nor the Validate
Backsights seem to honor the correction value. In other words, both
only report an error if the two entered values differ by more than the
Backsight Error Limit value; I would expect that both instruments
would have their correction applied before comparison.

Is there some way to "apply" the correction that I'm missing? Having
never used the instrument correction feature before, I suppose I could
simply be using it wrong!

Minor note: I also notice that in the Edit Heading panel, when
entering a value into the final field, "Inclinometer Correction-2",
pressing the enter key gives a "Grid index out of range" error popup.

Thanks again!

Dave Riggs
Germany Valley,
 WV

David A. Riggs <[email protected]>

Yahoo Groups Links


Messsage #: 426
Date: Tue, 31 Dec 2013 12:06:32 -0500
From: Tony Canike 
Subject: Re: [compass-users] Single Instrument Correction

Just a public thanks to Larry for all his great help solving the issue 
with my data file.  Happy New Year everyone!

On 12/27/2013 8:17 PM, Larry ([email protected]) wrote

 Hi Tony,

 The error you are getting is probably caused by corruption in the 
 survey file. If you would like, I can go through your data and clean 
 up any problems you have.

 If you want me to do that, send the data directly to my personal email:

 [email protected] 

 If you send me the data, let me know exactly what you have to do get 
 the error.

 Larry

 ------------------------------------------------------------------------

 *From:*[email protected] 
 [mailto:[email protected]] *On Behalf Of *Tony Canike
 *Sent:* Friday, December 27, 2013 3:05 PM
 *To:* [email protected]
 *Subject:* Re: [compass-users] Single Instrument Correction [1 Attachment]

 Derek, does your error look like the below screenshot?    I only get 
 it when I Surveys-Find Shot/Station in File.

 Been getting this error for years, one .DAT file I inherited has crazy 
 station names, and I only get the error with that data file.

 I just now downloaded the latest version of Compass, installed it, and 
 still get the same error, but as I said, only when searching this one 
 data file.

 On 12/27/2013 4:14 PM, Derek Bristol ([email protected] 
 ) wrote

 The issue is with the CaveEd32 application, not with a specific 
 survey file. I've installed version 5.13.12.18.75 on two PCs (one 
 running Windows 7 and the other running Windows 8.1) and get the same 
 error when trying to open the Editor. It happens when opening the 
 Editor directly, or opening through the Project Manager. I don't need 
 to be opening a survey file to get the error. Again, the error is "" 
 is not a valid floating point value". I can click OK and open the 
 editor, but I get the message again when trying to open a survey 
 file, and it won't let me actually open a survey (any survey) for 
 viewing or editing of data. I also get the error when trying to 
 access various functions within the Editor such as "Options - Survey 
 Settings" or trying to create a new file.

 The last version I had installed was from May, 2013 and didn't have 
 this problem. I tried redownloading and reinstalling but there is no 
 change.

 Derek

 On Dec 27, 2013, at 1:31 PM, "Larry"   wrote:

 Hi Derek,

 I haven't had any other reports of problems with the new version of 
 the Editor. Testing the current version of the Editor, I don't 
 receive any error messages. I've sometimes had problems when the 
 computer is set to the European standard for decimal point or 
 "thousands" separator, so I changed the settings and still didn't 
 have a problem. Without more information, my best guess is that 
 there is a corruption problem with the data you are using.

 Can you give me more information about exactly what you are doing to 
 get the error? For example, do you get the error the minute you open 
 a file in the Editor? Or do you get it when you select a survey? 
 Does it only occur when you enter data in one of the fields? If it 
 occurs when you enter data in a field, can you tell me which field? 
 Is it in the Header or in the survey shots?

 One option would be to send me a copy of the data you are working 
 on. That way I can duplicate exactly what you are doing. At the same 
 time, if the data is corrupted in some way, I can fix it. If you 
 choose to send me data, don't send it to the whole group. Use this 
 email address:

 [email protected] 

 I keep all survey data private and confidential unless I have 
 specific instructions from the owner of the data to release it to 
 someone.

 Larry

 ------------------------------------------------------------------------

 *From:*[email protected] 
  
 [mailto:[email protected] 
 ] *On Behalf Of *Derek Bristol
 *Sent:* Friday, December 27, 2013 10:39 AM
 *To:* [email protected] 
 
 *Cc:*  
 *Subject:* Re: [compass-users] Single Instrument Correction

 I don't know if anyone else has been having problems, but since the 
 update I'm getting a "" is not a valid floating point" error when 
 trying to edit cave files or individual surveys with the Cave 
 Editor. I can process data with the Project Manager, but there seems 
 to be an issue with the Editor.

 On Dec 18, 2013, at 2:12 PM, "Larry"   wrote:

 Hi David,
 I didn't even think about using the correction factors in the 
 Validation
 process. That shows how easy it is to overlook things.
 I've fixed the problem and there is a new version of Compass on the web
 site.
 Larry

 -----Original Message-----
 From: [email protected] 
  
 [mailto:[email protected]]
 On Behalf Of David A. Riggs
 Sent: Tuesday, December 17, 2013 9:40 PM
 To: [email protected] 
 
 Subject: Re: [compass-users] Single Instrument Correction

 On Tue, Dec 17, 2013 at 6:57 PM, Larry   wrote:
 
  I've tested the feature on several large cave files, but since it 
 is new
 code, there is a chance that I have missed something. Be on the 
 lookout for
 any problems Let me know if you see anything so I can correct them 
 quickly.

 Hi Larry,

 I did a quick test with the editor by setting "Inclinometer
 Correction-2" to a large value, -10.0. I confirmed that the saved .DAT
 file did correctly contain the new CORRECTIONS2 header.

 However, in the editor, neither the Shot Validation nor the Validate
 Backsights seem to honor the correction value. In other words, both
 only report an error if the two entered values differ by more than the
 Backsight Error Limit value; I would expect that both instruments
 would have their correction applied before comparison.

 Is there some way to "apply" the correction that I'm missing? Having
 never used the instrument correction feature before, I suppose I could
 simply be using it wrong!

 Minor note: I also notice that in the Edit Heading panel, when
 entering a value into the final field, "Inclinometer Correction-2",
 pressing the enter key gives a "Grid index out of range" error popup.

 Thanks again!

 Dave Riggs
 Germany Valley, WV

 -- 
 David A. Riggs  

 ------------------------------------

 Yahoo Groups Links
  
    Just a public thanks to Larry for all his great help solving the
    issue with my data file.  Happy New Year everyone!
    
    On 12/27/2013 8:17 PM, Larry
      ([email protected]) wrote
    
       
            
              Hi Tony,
              The error you
                    are getting is probably
                    caused by corruption in the survey file. If you
                    would like, I can go through
                    your data and clean up any problems you have.
              If you want me
                    to do that, send the data
                    directly to my personal email:
              [email protected]
              If you send me
                    the data, let me know
                    exactly what you have to do get the error.
              Larry
               
                    
                From:
                      [email protected]
                      [mailto:[email protected]]
                      On Behalf Of Tony
                      Canike
                      Sent:
                      Friday, December 27, 2013
                      3:05 PM
                      To:
                      [email protected]
                      Subject:
                      Re: [compass-users]
                      Single Instrument Correction [1 Attachment]
              
               
              Derek,
                    does your error
                    look like the below screenshot?    I only get it
                    when I 
                    Surveys->Find Shot/Station in File.  
                    
                    Been getting this error for years, one .DAT file I
                    inherited has crazy station
                    names, and I only get the error with that data file.
                    
                    I just now downloaded the latest version of Compass,
                    installed it, and still
                    get the same error, but as I said, only when
                    searching this one data file.
              
                On
                      12/27/2013 4:14 PM, Derek Bristol ([email protected])
                      wrote
              
                 
                  
                    The issue is with
                          the CaveEd32 application, not with a
                          specific survey file. I've installed version
                          5.13.12.18.75 on two PCs (one
                          running Windows 7 and the other running
                          Windows 8.1) and get the same error
                          when trying to open the Editor. It happens
                          when opening the Editor directly, or
                          opening through the Project Manager. I don't
                          need to be opening a survey file
                          to get the error. Again, the error is "" is
                          not a valid floating
                          point value". I can click OK and open the
                          editor, but I get the message
                          again when trying to open a survey file, and
                          it won't let me actually open a
                          survey (any survey) for viewing or editing of
                          data. I also get the error when
                          trying to access various functions within the
                          Editor such as "Options
                          -> Survey Settings" or trying to create a
                          new file.
                  
                     
                  
                    The last version I
                          had installed was from May, 2013
                          and didn't have this problem. I tried
                          redownloading and reinstalling but there
                          is no change.
                  
                     
                  
                    Derek
                    
                          On Dec 27, 2013, at 1:31 PM, "Larry" <[email protected]>
                          wrote:
                    
                        
                        
                          Hi
                                Derek,
                           
                          I
                                haven’t had any other reports of
                                problems with the new version of
                                the Editor. Testing the current version
                                of the Editor, I don’t receive any
                                error messages. I’ve sometimes had
                                problems when the computer is set to the
                                European standard for decimal point or
                                “thousands” separator, so I changed the
                                settings and still didn’t have a
                                problem. Without more information, my
                                best
                                guess is that there is a corruption
                                problem with the data you are using.
                           
                          Can
                                you give me more information about
                                exactly what you are doing
                                to get the error? For example, do you
                                get the error the minute you open a file
                                in the Editor? Or do you get it when you
                                select a survey? Does it only occur
                                when you enter data in one of the
                                fields? If it occurs when you enter data
                                in a
                                field, can you tell me which field? Is
                                it in the Header or in the survey shots?
                           
                          One
                                option would be to send me a copy of the
                                data you are working
                                on. That way I can duplicate exactly
                                what you are doing. At the same time, if
                                the data is corrupted in some way, I can
                                fix it. If you choose to send me data,
                                don’t send it to the whole group. Use
                                this email address:
                           
                          [email protected]
                           
                          I
                                keep all survey data private and
                                confidential unless I have
                                specific instructions from the owner of
                                the data to release it to someone.
                           
                          Larry
                           
                                
                            From:
                                  [email protected]
                                  [mailto:[email protected]]
                                  On
                                      Behalf Of Derek
                                  Bristol
                                  Sent:
                                  Friday, December 27, 2013
                                  10:39 AM
                                  To:
                                  [email protected]
                                  Cc:
                                  <[email protected]>
                                  Subject:
                                  Re: [compass-users]
                                  Single Instrument Correction
                          
                           
                            
                                
                                  I
                                        don't know if anyone else has
                                        been having problems, but since
                                        the update I'm
                                        getting a "" is not a valid
                                        floating point" error when
                                        trying to
                                        edit cave files or individual
                                        surveys with the Cave Editor. I
                                        can process data
                                        with the Project Manager, but
                                        there seems to be an issue with
                                        the Editor.
                                  
                                        On Dec 18, 2013, at 2:12 PM,
                                        "Larry" <[email protected]>
                                        wrote:
                                  
                                     
                                    
                                      Hi
                                            David,
                                            I didn't even think about
                                            using the correction factors
                                            in the Validation
                                            process. That shows how easy
                                            it is to overlook things.
                                            I've fixed the problem and
                                            there is a new version of
                                            Compass on the web
                                            site.
                                            Larry 
                                            
                                            -----Original Message-----
                                            From: [email protected]
                                            [mailto:[email protected]]
                                            On Behalf Of David A. Riggs
                                            Sent: Tuesday, December 17,
                                            2013 9:40 PM
                                            To: [email protected]
                                            Subject: Re: [compass-users]
                                            Single Instrument Correction
                                            
                                            On Tue, Dec 17, 2013 at 6:57
                                            PM, Larry <[email protected]>
                                            wrote:
                                            >
                                            > I've tested the feature
                                            on several large cave files,
                                            but since it is new
                                            code, there is a chance that
                                            I have missed something. Be
                                            on the lookout for
                                            any problems Let me know if
                                            you see anything so I can
                                            correct them quickly.
                                            >
                                            
                                            Hi Larry,
                                            
                                            I did a quick test with the
                                            editor by setting
                                            "Inclinometer
                                            Correction-2" to a large
                                            value, -10.0. I confirmed
                                            that the saved .DAT
                                            file did correctly contain
                                            the new CORRECTIONS2 header.
                                            
                                            However, in the editor,
                                            neither the Shot Validation
                                            nor the Validate
                                            Backsights seem to honor the
                                            correction value. In other
                                            words, both
                                            only report an error if the
                                            two entered values differ by
                                            more than the
                                            Backsight Error Limit value;
                                            I would expect that both
                                            instruments
                                            would have their correction
                                            applied before comparison.
                                            
                                            Is there some way to "apply"
                                            the correction that I'm
                                            missing? Having
                                            never used the instrument
                                            correction feature before, I
                                            suppose I could
                                            simply be using it wrong!
                                            
                                            Minor note: I also notice
                                            that in the Edit Heading
                                            panel, when
                                            entering a value into the
                                            final field, "Inclinometer
                                            Correction-2",
                                            pressing the enter key gives
                                            a "Grid index out of range"
                                            error popup.
                                            
                                            Thanks again!
                                            
                                            Dave Riggs
                                            Germany
                                                    Valley,
                                                WV
                                            
                                            -- 
                                            David A. Riggs <[email protected]>