-
Notifications
You must be signed in to change notification settings - Fork 6
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
Tree shapefile dump fails because of a null geometry [Part of 1714] #1728
Comments
Using a production data dump, I ran trees.sql with an additional
Survey details |
https://treescount.nycgovparks.org/survey/detail/414/ showing the short median block edge with a single tree instead of 2 |
Incrementally stepping through the subqueries in trees.sql.
|
layoutBoxes.sql contains the following logic:
I added several When I update the statement to
The query produces geometry for both trees
|
Fixes point placement on short segments, as reported on azavea/nyc-trees#1728 Also fixes slighly wrong distance on offsetted points (#53)
It boils down to this issue: Filed upstream here: https://trac.osgeo.org/postgis/ticket/3138 I committed a workaround in the treekit code that also fixes another issue of slight misplacement for offsetted points: |
NOTE: the new code should also be faster (in addition to more robust) |
Even better, upgrade to treekit/treekit@efb8e37 |
Happened again on May 31st 2015, 01:30:10.566. |
Can you provide data to reproduce the problem ? I need the input road line and the trees data array. |
I think this last report was from production. #1738 fixes the issue, but is still in review and not yet deployed. |
Occurred in production on May 23 2015 10:30 AM EST.
The text was updated successfully, but these errors were encountered: