You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
See #247 (Loose Invalidity handling for geometries)
TODO:
method(:contains?)
gives something understandable w. correct arity)#invalid_reason
which can bail out toUnknown validity
if a check is not yet implemented in the pure ruby versionRGeo::GeosError
for usage of unsafe methods that are not handled correctly by geos.The text was updated successfully, but these errors were encountered: