Using the Merge by Break Value option for a Service Area solve drops locations and gives different results than Not Overlapping option.
Last Published: August 25, 2014No Product Found
Bug ID Number
NIM031378
Submitted
January 15, 2008
Last Modified
June 5, 2024
Applies to
No Product Found
Version found
9.2
Version Fixed
9.3
Status
Fixed
The bug has been fixed. See the Version Fixed and Additional Information, if applicable, for more information.
Workaround
For the points that are not included in the original Merge by Break Value polygon generation:1. Select by Location. Select all the points that are within the generated polygons.2. Switch Selections3. Export the selected features.4. Create a new service area the same as the first with the exported points.5. Merge the output polygons with the original polygons to get the result that was supposed to be generated the first time through.To Correct the different results:1. Run the Solver with Not Overlapping Selected.2. Merge polygons generated. Dissolve the merge. Based on the assumption that the Not Overlapping selection is the correctly generated set of polygons. If the merge is the correct solve, use "For the points that are not included in the original Merge by Break Value polygon generation" then merge and dissolve.=========Added by Jay Sandhu:Switch to Detailed polygons (not generalized) for the merged case and re-solve. All points will be covered by polygons. Also change the Trim distance from 100 to something meaninggul, say 30 and re-solve. The polygons will be much better looking and more simillar to the ones generated by the non-overlapping option. But do note that there will always be a difference between the polygons generated by the two methods as the underlying data in the merge case is all the lines together and for non-overlapping it is one set of lines at a time.