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

Box intersection that cannot be represented? #90

Open
clarisma opened this issue Mar 17, 2023 · 0 comments
Open

Box intersection that cannot be represented? #90

clarisma opened this issue Mar 17, 2023 · 0 comments
Labels
clarify Spec is unclear about behavior

Comments

@clarisma
Copy link
Owner

Since Box can represent a bounding box that straddles the Antimeridian, there may be a situation where such a Box is intersected with a regular bbox. Conceptually, such an intersection might result in two bboxes (the eastern and western parts). What happens at this point, since the resulting Box cannot represent more than one single bounding box?

  • an empty Box is returned; or
  • an exception is thrown (which one? A custom type?)

Related to #40 and #86

@clarisma clarisma added the clarify Spec is unclear about behavior label Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarify Spec is unclear about behavior
Projects
None yet
Development

No branches or pull requests

1 participant