-
Notifications
You must be signed in to change notification settings - Fork 58
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
Test: Invalid aggregation test with PROJ 5.1 #994
Comments
cc/ @jgoizueta , who is more or less aware of this issue and will probably take over this in the next RT shift. |
Fixes #994 With exact point 0,0 transformations, the point is between tiles and can appear in several
@Algunenano can you check your tests are OK with #998 ? |
The test I was complaining about is now fixed, but now there are other ones:
And finally:
The first 2 seem to be related to playing too close to (0,0) with transformations. And the last one can be fixed by just bringing the changes done to Windshaft in CartoDB/Windshaft@f447db1. |
For the aggregations I think the right thing to do is to avoid duplicates, so I reponed #889 |
I've got the
aggregated ids are unique for default aggregation
failing when running the tests under PROJ 5.1. Apparently it checks that there are no duplicated points between tiles, but there is a point appearing in both tested tiles:The feature that appears in both tiles is this one:
With the bug fixed in PROJ 5.1, the point (0,0) appears in all 4 tiles that contain that point. I don't know if this is a bug in the test or the implementation of the
default
aggregation.cc/ @CartoDB/rt-managers
The text was updated successfully, but these errors were encountered: