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

New Class - NominalResolution #235

Open
5 tasks
stansmith907 opened this issue Sep 20, 2019 · 0 comments · May be fixed by #324
Open
5 tasks

New Class - NominalResolution #235

stansmith907 opened this issue Sep 20, 2019 · 0 comments · May be fixed by #324
Labels
new feature Add new functionality not currently available

Comments

@stansmith907
Copy link
Contributor

stansmith907 commented Sep 20, 2019

Class Definition: nominalResolution
"distance between consistent parts of (center, left side, right side) adjacent pixels"

Rules:

  • optional

Element Definitions:

  • scanningResolution: { measure } "distance between consistent parts of (center, left side, right side) adjacent pixels in the scan plane"
  • groundResolution: { measure } "consistent parts of (center, left side, right side) adjacent pixels in the object space"

Rules:

  • only one may be selected. Although this type of restriction is generally a writer consideration, in this case having both values is not logical.
  • both elements are "distance" measures. So type is fixed as "distance". It may be OK to drop type from mdEditor, but it will remain part of { measure } and thus output by mdJson writer.
  • scanningResolution: required if not groundResolution
  • groundResolution: required if not scanningResolution

mdJson:

{
   "nominalResolution": {
      "scanningResolution": { 
         "type": "distance",
         "value": 999.9,
         "unitOfMeasure": "units"
      },
      "groundResolution": {
         "type": "distance",
         "value": 999.9,
         "unitOfMeasure": "units"
      }
   }
}
@hmaier-fws hmaier-fws added the new feature Add new functionality not currently available label Apr 22, 2024
@jwaspin jwaspin linked a pull request Apr 30, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature Add new functionality not currently available
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants