Bug List from RHUG

Document created by Kyle.gonterwitz_KSDOT on Dec 12, 2018Last modified by Kyle.gonterwitz_KSDOT on Jan 8, 2019
Version 4Show Document
  • View in full screen mode
IDActivity or FunctionIssueWorkaroundModule10.3.110.4.110.510.5.110.6.1Plan Submit byPriority
Bug-000101699Export Network ServiceThe Export Network tool does not get the latest geodatabase version state when executed as a service.Change the recycle frequency of the GP Service to minimize the impact of the issue in the current environment.Server

found

patch 4

existsexistsfixedNYSDOTHigh
BUG-000110742RealignRealigning a route to create a gap calibrates the To Measure on event incorrectlyDesktop@fixedNCDOTMedium
BUG-000106791ArcMap SymbologyCreating a layer from the Create Layer From Selected Features option does not honor the selection and displays all the features.DesktopfixedresolvedNCDOThigh

BUG-000108601

TFS-53113

Export Network ServiceTool fails to run if there is a complex route concurrency (one loop, one lollipop, plus a typical route shape that is partially concurrent with the loop and lollipop routes) across different time slices .  Previous thought bug was due to Production Mapping being installed in ArcGIS Desktop 10.5, but that is not the caseRemove route concurrency by reassigning to bogus route id or retiringServerfound patch 1fixedNCDOThigh

BUG-000106993

 

TFS #54450

Network Edit - Reverse RouteReverse Route causes calibration point measures to change beyond 6 decimal places.  Manually edit calibration point and recalibrate downstreamDesktopfoundfixNCDOThigh
NCDOT case 01889567Relocate Events ServiceRelocate events service stretches events beyond end of route.  The issue relates to a defect that is fixed in 10.5.1. However, cartographic realignments done in Roads and Highways pre-10.5.1 with the condition that there is more than one calibration point downstream of the edit will exhibit the symptom in this support incident.  Edits on 10.5.1 of Roads and Highways will not have this symptom.  Hotfix estimated August 4, 2017 that will mask the symptom of pre-10.5.1 cartographic realignment edits from external systems, such as AgileAsset’s system(s)Serverfoundhotfix*NCDOT

BUG-000101392

 

TFS51810

Route Edit -  extend, realignExtending a route to create a concurrency then realigning the other route to remove the concurrency on the same date results in incorrect event behaviors for the non-concurrent events on the realigned routeUse reassign instead of extend if possibleDesktopfound patch 4existsexistsfixNCDOThigh

TFS51854

Route Edit - Reverse, ReassignReverse and Reassign to Create Gap Causes Measures Downstream From Gap to be Incorrect.  Issue also occurs doing a reverse and retire to create a gapReassign, then reverse if possibleDesktop

found

patch 4

existsexistsfixNCDOThigh

TFS51855

Realign, Cartographic RealignmentRealign then cartographic realignment results in retired routes becoming NaN.  Cartographic realignment of route at new alignment (retired route becomes NaN); Cartographic realignment of route at old alignment (active route becomes NaN); Possibly fixed in 10.4.1 (based on testing at 3rd party vendor site)Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly)

found

patch 4

fixNCDOThigh

 

 

AgencyIssue TypeActivity or Function:IssueWorkaroundModuleVersionEsri StatusResolution TargetHotfixEsri BUG IdentifierESRI TFS IDEsri PriorityRHUG PriorityComments
North Carolina DOTBugRealign, Cartographic RealignmentRealign then cartographic realignment results in retired routes becoming NaN.Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly)Desktop10.3.1 Patch 4In Product Plan10.4.1TFS51855MediumHighCartographic realignment of route at new alignment (retired route becomes NaN); Cartographic realignment of route at old alignment (active route becomes NaN); Possibly fixed in 10.4.1 (based on testing at 3rd party vendor site)
North Carolina DOTBugRetire, Cartographic RealignmentRetire to create gaps then cartographic realignment results in routes becoming NaNUse Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly)Desktop10.3.1 Patch 4In Product Plan10.4.1TFS52078MediumHighRetired routes become NaN
North Carolina DOTBugReassign, Cartographic RealignmentReassign then cartographic realignment results in retired routes becoming NaNUse Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly)Desktop10.3.1 Patch 4In Product Plan10.4.1TFS52077MediumHighRetired and active routes become NaN
North Carolina DOTBugExtend, Cartographic RealignmentExtending a route, and performing a cartographic realignment on the extended portion results in a Not a Number (NaN) calibrationUse Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly)Desktop10.3.1 Patch 4In Product Plan10.4.1BUG-000101941MediumHighRetired routes become NaN
North Carolina DOTBugLaunch a URL (i.e. instance of RCE) from Workflow Manager OnlineArcGIS Workflow Manager for Server opens browser (IE) in server when executing Launch URL step in a client environmentDynamically examine the memory usage and periodically eliminate the ‘zombie’ server processes; alternatively, reboot server.Server10.3.1 Patch 4In Product Plan10.5.1BUG-000102184HighHighCauses server instability. ArcGIS services become unresponsive. Database validation fails for datastores.
North Carolina DOTBugRealign, RetireRealigning a route to create a concurrency followed by retiring the other route to eliminate the concurrency on the same date results in the snapped events getting incorrect measures.Use reassign instead of realign if possibleDesktop10.3.1 Patch 4In Product PlanBUG-000101393TFS51811MediumHigh
North Carolina DOTBugCalibrationVertex measures flip when recalibratingnoneDesktop10.3.1 Patch 4In Product Plan10.4NCDOT case 01888502TFS45251High
North Carolina DOTBugAdd Machine to an ArcGIS Server siteAfter upgrading an ArcGIS 10.3.1 site to 10.5, the Add Machine operation fails with error: "\relational-datastore-types" folder cannot be locatedUsing Windows commands on the config-store file share, create an empty file folder in the config-store named "relational-datastore-types". Proceed normally with adding the new machine.Server10.5.0Not in Current Product Plan
North Carolina DOTBugReassign or RetireRetire or Reassign route to create gap causes the ends at the gap to have same measures even though Euclidean Distance has been setDesktop10.5.0Not in Current Product PlanNCDOT case 01904018MediumThis issue is not in 10.3.1 Patch 4. 
North Carolina DOTBugRealign, Cartographic RealignmentEvents shift downstream of realignment if a cartographic realignment is subsequently performed.Desktop10.5.0Not in Current Product PlanNCDOT case #01906828
Kansas DOTBugIntersection GeocodingThe values in the alternate name table are not read correctly, resulting in incorrect or no matches. Desktop10.3.1In Product PlanBUG-000099047MediumKDOT is using Intersection geocoding to locate crashes to intersectons. Kansas is going live with NG911 and geocoding is critical to that system, which is believed to use ESRI geocoding functions for call routing. Kansas expects 100% geocoding matching on all real physical and MSAG addresses for NG911 call routing.
Kansas DOTBugIntersection GeocodingIntersections using the | delimiter does not match. Use & delimiterDesktop10.3.1Not in Current Product PlanBUG-000099045Low
Kansas DOTBugIntersection GeocodingAddress locator returns false matches for intersectionsDesktop10.3.1Under ConsiderationBUG-000100827MediumHigh priority for Kansas
Kansas DOTBugGeocodingIn a dual range locator, addresses that have a separate letter as part of the street name, geocodes to the wrong street when the separate letter is a compass direction.Desktop10.3.1Implemented10.5.1BUG-000101473Medium
Kansas DOTBugGeocodingStreet names containing certain special characters return a match score less than 100% for perfect matches.Locator match score is less than 100% for street names with special characters even when completely matched. For names that include a period, a period can be added to the following spelling section group under the spelling section of the locator XML file, which will reduce the scoring deduction but may reduce performance:
Section:
<spelling>
...
<character_equivalency_table name="scoring">
...
Change:
<entry from="-' " to="-' " spell="90" cost="0.1" type="group"/>
to
<entry from=".-' " to=".-' " spell="90" cost="0.1" type="group"/>
BUG-000101458: Street names containing certain special characters return a match score less than 100% for perfect matches.
Desktop10.3.1ClosedBUG-000101458Medium"This is a known limitation of the current technology."
Kansas DOTBugGeocodingSome geocoding tools in the geoprocessing Results window do not retain the original inputs. #BUG-000101647 The Single Field radio button selection is not maintained when rerunning the Geocode Addresses tool from the Results window.1. Open the executed tool to rerun it. 2. Browse and re-add the address locator. 3. Select the Single Field radio button. 4. Click OK to rerun the tool.Desktop10.5.0Closed10.6.0BUG-000101778, BUG-000101647Medium
Kansas DOTBugGeocodingX and Y coordinates are written to the geocoded output even when not requested in locator options.DisplayX and DisplayY are controlled by a different property which is not exposed via the UI at this time. We will expose it in a future release. If you would like it disabled not, set "WriteDispXDispYFields" property to "False" at the bottom of the USAddress.lot.xml file located in the %ARCGIS_INSTALL%\Locators folder before creating your locator or update the same property in the locator you have already created.Desktop10.5.0Not in Current Product PlanBUG-000101755MediumDisplayX and DisplayY are controlled by a different property which is not exposed via the UI at this time. We will expose it in a future release. If you would like it disabled not, set "WriteDispXDispYFields" property to "False" at the bottom of the USAddress.lot.xml file located in the %ARCGIS_INSTALL%\Locators folder before creating your locator or update the same property in the locator you have already created.
Kansas DOTBugGeocodingThe composite score field is truncated in the output of locators created on ArcGIS Desktop 10.5. Desktop10.5.0Implemented10.5.1BUG-000101754Medium
Kansas DOTBugGeocodingGeocoded output of a dual-range locator contains the wrong value in the Ref_ID field.Desktop10.5.0Implemented10.5.1BUG-000102859
Kansas DOTBugGeocodingPerformance in creating a dual range locator and geocoding with it is slower on Pro 1.4 than on 10.3.1 on the same system.dont use proPro1.4.0ClosedBUG-000102609The increase in the number of matches is about the same as the increase in the amount of time the geocoding took. This is expected considering the significant increase in the number of matched addresses.
Kansas DOTBugGeocodingBatch geocoding with an US Address-Dual Range address locator using a multiple line input sometimes incorrectly match street intersections to street addresses on a lettered streetThere is a section in the style that allows for unit information to precede the address. In multiline this logic is a bit more liberal and is causing the address to get parsed incorrectly. Users can remove this additional logic from the style to fix this issue. Look for the following which will start around line 22391: <def name="MultiLineUnitAndNumberPrefix"> <alt fallback="true"> <elt ref="HousingUnitType"/> <elt ref="OptNumSeparator"/> <elt ref="AlphaNumericUnit" post_separator="required"/> </alt> <alt fallback="true"> <elt ref="AlphaNumericUnit"/> <elt ref="HousingUnitType" post_separator="required"/> </alt> <alt fallback="true"> <elt ref="NumSeparator" pre_separator="optional" post_separator="optional"/> <elt ref="AlphaNumericUnit" post_separator="required"/> </alt> <!-- Only use if this is not a Street Name locator --> <!-- <alt fallback="true" selector="SupportsWeightedHouseNumber"> <elt ref="wordlist"/> </alt> --> </def> I have commented out the last section (added <!-- before and --> after the beginning and ending alts).Desktop10.5.1ClosedBUG-000106824
Kansas DOTEnhancementGeocodingPlease provide a user interface to manage the inclusion of new fields being written to geocoded output at ArcGIS Desktop release 10.5.Under some circumstances, a 15-character text field "STREETID" is included in the geocoded output of a single or dual range locator. This appears to contain a text representation of the reference ID, when included in the output, unless the reference ID is -1 for an unmatched address; in that case, the StreetID is blank. It's not clear under what circumstances this field is included in the geocoded output.Desktop10.5.0ENH-000102861Many superflous fields are added to the geocoding ressults output from dual range geocoding, which can be confusing for users performing manual examination of unmatched results and confirming that matched results are as expected.
Ohio DOTBugDisplay Route EventsDisplay Route Event tool maps 2 event items with identical log values to 2 different LRS measured vertices (2 events log = 1.335 but 1 gets mapped to 1.335 other is 1.334In LRS processes leading up to Display Route Event tool needs, increase the M-value scale by 1 (chang from 0.001 to 0.0001)Desktop10.3.1Not in Current Product PlanBUG-000102964
Ohio DOTBugUndefined Editing ErrorUpon running a linear overlap validation tool in desktop (built by Transcend Spatial) we are discovering where records are being duplicated behind the scenes. This tool is designed to check specified tables for gaps and overlaps. By design R&H extension should not cause gaps and overlaps to occur and thus there is an underlying flaw yet to be identified.Weekly run of this tool followed by manul editing to correct the issuesDesktop10.3.1Not in Current Product Plan
Ohio DOTBugAdd Calibration PointIdentified a situation where a new calibration point was added along an existing route (around the 1 mile mark) in desktop. As a result of the desktop edit we found in RCE a record (0.00-0.633) in an event table was retired incorrectly. Upon noticing this we removed the retired date to bring back the incorrectly retired record. The next day we discovered there were 2 records in the event table for the same segment (0.00-0.633)Manual delete of the newly duplicated record to retain a single record that correctly exists and isn't retiredRCE/Event Editor10.3.1Not in Current Product Plan
Ohio DOTBugSame Location Calibration Points Identical Measure ValueMultiple Calibration Points at the same location with the same measure deleting 1 of the CP's causes issues1. Turn off the Roads and Highways extension in ArcMap by going to Customize > Extensions > Roads and Highways. Make sure ArcCatalog is closed on that machine as well. 2. Add your CPs to a MXD 3. Verify in the edit log that no timestamped activity was logged for adding the feature to the map. 4. Delete the CPs via the attribute table. You can do this in a geodatabase version and rec/post the deletions if you prefer. 5. Verify again that there is no deletion activity logged in the RH edit log. 6. Save your edits and rec/post as needed. 7. Turn on the Roads and Highways extension.Desktop10.3.1Not in Current Product Plan
Ohio DOTBugSame Location Calibration Points Different Measure ValueMultiple Calibration Points at the same location with different measures deleting 1 of the CP's causes issuesDesktop10.3.1Not in Current Product PlanAttempted workaround for same issue with identical measure values but that workaround does not work. While this solution correctly eliminates the incorrect record from the calibration point table it seems to fail to fully address the R&H tables as the system still considers the remaining record to have the incorrect measure that existed in the deleted record.
Ohio DOTBugModify Measure with leave/re-enter issueWhen modifying a measure on an existing leave/re-enter situation in desktop the system will not allow user to adjust the measure on the re-enter point as it wants to create a non-monotonic route.Desktop10.3.1Not in Current Product PlanWorkarounds attempted but did not work include: modifying the leave point measure first, modifying the reenter point measure to something greater than the leave point measure.
Ohio DOTBugRecalibrate DownstreamWhen using the realign tool and selecting the recalibrate downstream option the updated measure values are not calculated correctly if there is a leave/reenter or overlap situation on the route. Even when the calibration point is specified to use 3 decimal precision, when users open the attribute table it initially shows 3 decimal precision in the from/to fields, however, if users select the from/to fields on records associated with the recalibration downstream process the full 16 decimal precision is shownDesktop10.3.1Not in Current Product Plan

Attachments

    Outcomes