#3847 closed enhancement (fixed)
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 (1)
Change History (8)
by , 13 years ago
Attachment: | hatch-tiled.png added |
---|
comment:1 by , 13 years ago
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.
comment:2 by , 12 years ago
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"
comment:3 by , 12 years ago
Cc: | added |
---|
comment:4 by , 12 years ago
Milestone: | FUTURE → 6.2 release |
---|---|
Resolution: | → fixed |
Status: | new → closed |
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.
comment:6 by , 12 years ago
comment:7 by , 12 years ago
This is great news! I have tested with trunk, and I found an issue with hatches (angles between 90 and 180). See ticket #4095.
misaligned hatches example