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

Always allow loose geometry creation, raise on operation that need more strict geometries #256

Closed
4 tasks done
BuonOmo opened this issue May 4, 2021 · 1 comment
Closed
4 tasks done

Comments

@BuonOmo
Copy link
Member

BuonOmo commented May 4, 2021

See #247 (Loose Invalidity handling for geometries)

TODO:

  • List OGC methods that need validity
  • do the metaprogramming part (RGeo 3.0 Roadmap #247 (comment)) and make sure it gives understandable methods (e.g. using method(:contains?) gives something understandable w. correct arity)
  • implement the pure ruby #invalid_reason which can bail out to Unknown validity if a check is not yet implemented in the pure ruby version
  • handle RGeo::GeosError for usage of unsafe methods that are not handled correctly by geos.
@BuonOmo BuonOmo mentioned this issue Sep 15, 2021
12 tasks
@BuonOmo BuonOmo changed the title Loose Invalidity handling for geometries Always allow loose geometry creation, raise on operation that need more strict geometries Sep 15, 2021
@BuonOmo
Copy link
Member Author

BuonOmo commented Sep 14, 2022

Closed by #275

@BuonOmo BuonOmo closed this as completed Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant