Closed jakepruitt closed 8 years ago
@jakepruitt see: https://github.com/mapnik/mapnik/blob/master/test/unit/geometry/geometry_strategy_test.cpp#L97-L105
and
https://github.com/mapnik/mapnik/blob/master/include/mapnik/util/geometry_to_wkt.hpp#L43
and
https://github.com/mapnik/mapnik/blob/master/include/mapnik/util/geometry_to_geojson.hpp#L32
as I think they might be better routes then what it looks like you might be doing?
I just added functionality for updating the fixtures and running the benchmark with the ginormous polygon. If you want to overwrite all of the existing features, use
UPDATE=true make test
and if you want to run the ginormous polygon through clipping and simplification (warning, tends to take ~10 mins) use
BENCHMARK=true make test
Just synced with @jakepruitt on this. Pending that it builds on windows, it is ready to merge. Phase 1 is done:
ReverseSolution
leads to failures)This sets us up nicely for potential future phases and improvements:
strictly_simple=true
actually change the geometry result for any of the tests? If not (yet) how can we detect this and then fix it to ensure that we have coverage of when it does change results and how?
This pull request adds geometry test data to mapnik-vector-tile tests, with the goal of improving coverage and making mapnik-vector-tile robust against various invalid and bad geometries. The current strategy for these tests is:
input
folder.expected
folder of geometry-test-data.refs #153
cc/ @flippmoke, @springmeyer, @artemp