stac-extensions / stac-extensions/view

Azimuth description and diagram do not match

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
6
Forks
3
PR merge metrics
No merged PRs in 30d

Description

(This is kind of the same point as #14, but that issue requests a change to the definition - I'm simply noting that the diagram doesn't match the written definition)

view:azimuth is defined as:

Viewing azimuth angle. The angle measured from the sub-satellite point (point on the ground below the platform) between the scene center and true north. Measured clockwise from north in degrees (0-360).

which I interpret as "Azimuth is the angle between the lines S-North and S-P", where S = Sub Satellite Point and P = Target (or Scene Centre) Point.

However, the diagram in the readme indicates a different definition such that "Azimuth is the angle between the lines P-North and P-S":
Image

In short, if a satellite is due south of the target and we ignore spherical geometry awkwardness, which of these values is view:azimuth meant to be?

  • 0 degrees, the satellite is looking north (text description)
  • 180 degrees, the satellite is located south of the target (diagram)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the view:azimuth definition and the diagram in the README, then compare both with the issue's due-south example. Confirm the intended azimuth convention with the extension's view-angle context, and update the written definition and diagram so they agree and the example has an unambiguous answer.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.