David Smiley

This only happens when parsing polygons. As a work-around, you could extend this method of the parser to do what you want. The parser is deliberately extensible.

> What do you think about adding a configuration boolean to parseIfSupported() and parse()? This would then be supplied to parseShapeByType() I think the proposed boolean, e.g. parsePolyAsRect, isn't so...

I sympathize the default behavior is not correct and ought to be changed (and thanks for reporting it). But the main consumer/user of this API (Apache Lucene-spatial-extras / Solr) prefers...

It’s ok to change a default. I just think it should be configurable.

Sorry, I have no estimate. The source has a comment as to how to approach it. Pull requests welcome :-)

> If a route is within distance of a point (I have a bunch of routes) Yes. Each route is a LineString, and you could test intersection against a circle...

> Could you show me an example that test intersection of LineString against a circle? Ouch; I was wrong! Anything can be intersected against a rectangle or point, but relations...

Oops; I was wrong; that was embarrassing. I was looking at the Spatial4j-native BufferedLineString shape but forgot that the JtsGeometry wrapper is in play here which does relate with a...

Thanks for reporting this issue. I saw that too and forgot to file an issue to make this truncation configurable. Unfortunately, right now, it is what it is -- there...

I agree @SeanTasker . Again, a Pull Request would be gladly accepted :-) BTW while working on https://issues.apache.org/jira/browse/SOLR-11731?focusedCommentId=16402457&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16402457 I empirically found that 7 decimals would produce sufficient precision for an...