Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Reference Frame in User's Guide #80

Closed
wapayze opened this issue Dec 15, 2020 · 3 comments · Fixed by #79
Closed

Default Reference Frame in User's Guide #80

wapayze opened this issue Dec 15, 2020 · 3 comments · Fixed by #79

Comments

@wapayze
Copy link

wapayze commented Dec 15, 2020

Hi,
This isn't a big issue. Section 3.3.1 of the User's Guide still says that the default reference frame on import is GDA94.
Cheers,
Bill.

@harry093
Copy link
Contributor

Good pick up @wapayze! Thanks for letting us know

@jhaasdyk-au
Copy link
Collaborator

Greetings Roger! A nice easy issue for my first posting to the DynAdjust issues logs.
(By the way, I'm really enjoying the User Guide... I find it concise yet informative, and easy to read.
Many thanks for all of the work you've put in here!)

The User Guide (release 1.2.6, Aug 2022) requires an exhaustive update to reflect:

  • Update of default reference frame from GDA94 to GDA2020

The following sections are incorrect (unchanged to reflect earlier updates to defaults):

  • pg 8, Section1.3.2 Program execution and command line options indicates:
    "For example [...] import will adopt the Geocentric Datum of Australia 1994 (GDA94) as the default value"
  • pg 175, Table A.4 Reference Frame Options "The default reference frame is GDA94"
  • pg 193, Last paragraph "...default reference frame ... GDA94"

The use of 'Default = GDA94' is not strictly incorrect in the following examples, but is now outdated.

  • pg 22, Figure 3.1
  • pg 32, Lower-most callout box
  • **pg 194, Table B.1 (if space permits...)
  • pg 218, C.2 Import log file (IMP) example callout

@jhaasdyk-au
Copy link
Collaborator

jhaasdyk-au commented Aug 29, 2022

On a related matter,

  • pg 193, Last paragraph indicates "DynAdjust will set ... default geoid model... to AUSGeoid09"
    Is this still true? It appears that geoid.exe (now?) requires explicit declaration of the geoid file.

In anycase, an exhaustive update of documentation to adopt and advise on AUSGeoid2020 is certainly in order.
If software changes are required, then that is a more significant issue.

If updating Section 5.2.1 Geoid models, consider adding also reference to AGQG and AVWS

[AUSGeoid AUSGeoid09 AUSGeoid2020 AGQG- terms for text searching]

rogerfraser added a commit to rogerfraser/DynAdjust that referenced this issue Sep 5, 2022
rogerfraser added a commit that referenced this issue Sep 5, 2022
[skip-ci] Update the User's Guide to address #80
rogerfraser added a commit to rogerfraser/DynAdjust that referenced this issue Dec 6, 2022
rogerfraser added a commit to rogerfraser/DynAdjust that referenced this issue Dec 6, 2022
rogerfraser added a commit to rogerfraser/DynAdjust that referenced this issue Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants