Conversation
|
Hi Andrea, with this PR built and installed, the hint distance for mapmlusefeatures:true with the preview link of my test layer is initially: with mapmlusefeatures:false on the same request, it's about 8x larger. FWIW I don't think the feature simplification distance should be or is the same as the distance hint for the pregen module, because those features are already generalized and have topology preserved (maybe, but if not that's not our problem). |
|
Does not match what I see locally. Can you share your setup? Data and data directory? In the meantime please prioritize reviewing #384 |
I put the contents of this zip file into ${GEOSERVER_DATA_DIR}/data/canada. I add a pregen data source per this picture:
I'll review it starting today. |
|
@prushforth check out the new commit, it aligns the pixel simplification distance to the streaming renderer, that accounts exactly for a 8x difference. Mind, I would check rendering of complex linework to see if it still renders properly, the Java Graphics2D uses heavier antialiasing, it results in thicker lines, which in turns hides tiny misalignment, the leafleft client side rendering paints thinner lines, they might become visible. Some tuning of the value might be in order. |
|
Also a note, to build this you'll need fresh jars for GeoTools, API breaking changes are occurring in some modules as we prepare to ditch JAI and replace it with ImageN. |
|
Just saw this now. will check it out, thanks! |
|
The hints calculated and used match much better the equivalent from the raster experience now!! Thanks, great work! |
304a5dd to
c498e62
Compare

The simplification distance is no longer being passed down into the Query due to a refactor happened back in January. Re-enabling it.
@prushforth before I work on a test can you double check the pre-generalized it working for you now, or if it still needs some attention?
Checklist
mainbranch (backports managed later; ignore for branch specific issues).For core and extension modules:
[GEOS-XYZWV] Title of the Jira ticket.The PR will be merged when all the build checks are green (see automated QA checks), there is a code committer review, and the checklist has been fulfilled.