Regarding Copan Lite for Windows 09.07.
The Great Copan for Windows Questionnaire
We first released a free version of Copan for Windows two years ago, with little fanfare, and so far have over 3000 registered users world-wide, rather more than we expected.
Some of you have already given us feedback on problems encountered, suggestions for improvement, or even glowing
testimonials. Thank you.
Now we formally invite every one of you to fill in a short questionnaire on your experience with and thoughts on Copan.
It will take approximately 5 minutes to complete.
Your participation is completely voluntary and your responses will be strictly confidential.
However, it is very important for us to learn your opinions.
[Feb'11 update: The survey is now closed. Thanks to all who participated!]
Added but not Announced
A couple of things were added to the previous release (09.06) but were not mentioned in the last Copan News:
- Further improvements were made to the interpretation of Leica GSI files in the Field modules.
This is something of an ongoing process.
Please let us know how this is working for you.
(Anyone who's ever tried to interpret a variety of Leica GSI files will know how difficult it is.)
- The help page on Info Display File was expanded to include appropriate settings for the international A4 page size.
Announced but not Added
Something was promised in the last Copan News but, inadvertently, not added to the previous release (09.06):
- Area decimals has now been added to General Program Settings, really.
Traverse Closure Report Improved
- When computing an open traverse in Map Trav / Map Check, Copan no longer gives the (annoying) warning "End point not found" popup.
- The bearing of any traverse misclosure, in Field Data / Field Bearing / Map Trav / Map Check, is now restored to normal precision.
(The traverse misclosure bearing was rounded off in version 08.03.)
- The traverse leg count, already in the closure dialog, has now been added to the output listing.
Import Ascii Improved
- A small bug, added to version 08.08, that sometimes caused excessive field-widths when in fixed format, has been squashed.
- The point replacement policy (when point # already exists) now always begins as Ask before replacing, for safety.
Before, it would always begin as whatever was chosen during the previous session.
Underhill Web Site