Currently, all errors reported by MEOS are treated as "stopping" errors, and a MEOS Exception is always raised, regardless of the error level reported by MEOS. This level should be taken into account to report warnings as such. For example, when inputting a geography with incorrect values, the following error is reported by MEOS:
MeosTextInputError: MeosTextInputError (22): Coordinate values were coerced into range [-180 -90, 180 90] for GEOGRAPHY
This is just a warning, since MEOS corrects the error coercing the values, by it is still raised as an exception in PyMEOS.
Currently, all errors reported by MEOS are treated as "stopping" errors, and a MEOS Exception is always raised, regardless of the error level reported by MEOS. This level should be taken into account to report warnings as such. For example, when inputting a geography with incorrect values, the following error is reported by MEOS:
MeosTextInputError: MeosTextInputError (22): Coordinate values were coerced into range [-180 -90, 180 90] for GEOGRAPHYThis is just a warning, since MEOS corrects the error coercing the values, by it is still raised as an exception in PyMEOS.