Ticket #3847 (closed enhancement: fixed)

Opened 2 years ago

Last modified 18 months ago

polygon hatches do not join at polygon boundaries

Reported by: tbonfort Owned by: tbonfort
Priority: normal Milestone: 6.2 release
Component: Renderer API Version: svn-trunk (development)
Severity: normal Keywords:
Cc: havatv, sholl

Description

  • support for hatches that are continuous from one polygon to the other
  • support fot hatches that are continuous from one image request to the next

Attachments

hatch-tiled.png Download (27.2 KB) - added by kyngchaos 21 months ago.
misaligned hatches example

Change History

Changed 21 months ago by kyngchaos

misaligned hatches example

Changed 21 months ago by kyngchaos

I just ran into this problem also, only with WMS tiled requests (image attached). It looks like the hatches align across polygons for me (MS 6.0.1).

I'm guessing that hatches are aligned to the image request extents, so polygon hatches would align.

To make them align across image requests, I think it would need to align to projection coordinates, like 0, 0.

Changed 19 months ago by havatv

This functionality was suggested in RFC45 (see also #3846):

"give hatches and vector fills a stable geographical coordinate origin (0,0) to better support tiling and continuous rendering of neighbouring polygons"

Changed 19 months ago by sholl

  • cc sholl added

Changed 18 months ago by tbonfort

  • status changed from new to closed
  • resolution set to fixed
  • milestone changed from FUTURE to 6.2 release

committed in r12807.

imageObj now contains a refpoint pointObj object which contains the image coordinates of the (0,0) geographical point. This reference point it used to align the hatches across tiled requests.

Changed 18 months ago by tbonfort

autotest results updated in r12808

Changed 18 months ago by rouault

r12810 /trunk/mapserver/mapprimitive.c: Fix compilation with MSVC (#3847)

Changed 18 months ago by havatv

This is great news! I have tested with trunk, and I found an issue with hatches (angles between 90 and 180). See ticket #4095.

Note: See TracTickets for help on using tickets.