GeoServer

KML Feature Limit not respected

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.7.1
  • Fix Version/s: 1.7.2
  • Labels:
    None
  • Number of attachments :
    0

Description

I'm trying to show/change how aggressively regionation acts, and the "KML Feature Limit" value seems to not affect the output at all.

Activity

Hide
David Winslow added a comment -

I've been unable to reproduce this problem. Looking at the code, it seems that when the feature limit is set to 1, it is automatically overridden with a value of 64; I can see how this might confuse you.

If you can provide some steps to reproduce the issue, I'll look into this further.

Show
David Winslow added a comment - I've been unable to reproduce this problem. Looking at the code, it seems that when the feature limit is set to 1, it is automatically overridden with a value of 64; I can see how this might confuse you. If you can provide some steps to reproduce the issue, I'll look into this further.
Hide
David Winslow added a comment -

Presumably this complaint could also be an interpretation of the fact that the regionating index is cached between requests, even if the per-tile feature limit changes. I've added code that clears out the cache when the regionating settings change, so this should be fixed as well.

Show
David Winslow added a comment - Presumably this complaint could also be an interpretation of the fact that the regionating index is cached between requests, even if the per-tile feature limit changes. I've added code that clears out the cache when the regionating settings change, so this should be fixed as well.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: