Constructing an invalid polygon (eg. with crossing loops or intersections) should throw an error. A descriptive error message should be provided. We could also consider providing a non-throwing API which provides a `is_valid()` method to check at runtime. In that case, results of a geo_within query on an invalid polygon will be undefined.