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

support bounding boxes that span the antimeridian #34

Merged
merged 3 commits into from
Feb 1, 2018
Merged

Conversation

cportele
Copy link
Member

resolves #31

Note that OpenAPI includes and links still go to the master branch,
i.e. will only be updated once the changes have been merged.

resolves #31

Note that OpenAPI includes and links still go to the master branch,
i.e. will only be updated once the changes have been merged.
@cportele
Copy link
Member Author

* Left box edge, coordinate axis 1
* Bottom box edge, coordinate axis 2
* Right box edge, coordinate axis 1
* Top box edge, coordinate axis 2
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I presume the coordinate axis order is CRS-dependent? So Axis 1 could either be an Easting or Northing?

In that case, maybe "Lower left corner, coordinate axis 1" & "Lower left corner, coordinate axis 2" is more accurate? (cf Upper right)

Or "SouthWest" & "NorthEast"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I was struggling how to best write it considering that

  • the axis order of the CRS applies and
  • WGS84 longitude/latitude is the only CRS that we discuss in the core.

It would be nice, if we can find a wording that is unambiguous, but not (too) confusing for developers that are not familiar with coordinate reference systems. I agree, "lower left corner"/"upper right corner" is better.

Copy link

@rcoup rcoup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@cportele
Copy link
Member Author

cportele commented Feb 1, 2018

Agreement on 2018-02-01: Merge immediately

@cportele cportele merged commit 516922e into master Feb 1, 2018
@cportele cportele deleted the issue-31 branch February 1, 2018 16:34
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 this pull request may close these issues.

Bounding Box Terminology for Geographic CRS
2 participants