Search

SSRS (BIDS) Map Distribution Range invalid by Paul Dioguardo

Active

1
0
Sign in
to vote
Type: Bug
ID: 774163
Opened: 12/12/2012 2:01:56 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I have a map report created in VS BIDS 2008 R2 and published to SSRS 2008 R2. The map displays the counties (polygons) in Pennsylvania along with data resulting from a query. The map distribution is setup for equal distribution across 5 ranges. The ranges appear with overlapping values. There does not appear to be a way of forcing the ranges to not overlap. i.e, ranges appearing as 0-100, 100-200, 300-400 etc, should appear as 0-100, 101-200, 201-300, 301-400, etc. Having a range end value of one range match the start range value of the subsequent range is actually invalid. Even the examples in the MS SSRS on-line help documentation display the incorrectly overlapping ranges, but I can't find a way to force the ranges to not overlap while remaining dependent on a query result (and not a static custom-defined range)

The organization I work for is responsible for publishing correct data which is reviewed and used by researchers and governmental agencies. Publishing a map with overlapping distribution ranges is not acceptable.
Details (expand)

Product Language

English

Version

SQL Server 2008 R2 SP1

Category

Developer Tools (SSDT, BIDS, etc.)

Operating System

Windows Server 2008 (all editions)

Operating System Language

US English

Steps to Reproduce

1) Create a map report in BIDS with a spatial layer involving polygons or points, with enough spatial features and associated attribute data to be divided into different range classes or series via the data distribution settings (for example Equal Distribution, 5 ranges). Add a legend.
2) Preview the map and legend

Actual Results

The map and legend display. The ranges displayed have values that overlap between the end value for one range and the start value of the subsequent range.

Perhaps something like:
590 - 620
620 - 650
650 - 680

or
105.5 - 110.5
110.5 - 115.5

Expected Results

The end value of one range should be separated from the start value of a subsequent range by one unit of measurement (whatever units the data consists of, i.e. 10, 1, 0.1 or 0.01, etc)
For example:
591 - 620
621 - 650
651 - 680
or
105.5 - 110.5
110.6 - 115.5

Platform

 

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Sign in to post a workaround.