Latest Contributions by KyleGonterwitz

‎02-05-2019

in dealing with a similar problem, I've started by defining the segments from which I want to accumulate the counts. In a highway system the segments are usually between the exits and intersections to other highways work for that. I'd create a point somewhere at the center of each highway segment and do some buffers to check that within a distance of those points, I'm only hitting one of the defining counting segments. Might need to move some of those points around if a couple highways are running close parallel to each other. Then I would spatial join and accumulate the counts in the individual overlapping routes to those points. ID join those joint point IDs back to the segments for display and analysis.

Crossing Versions of Roads and Highways · ‎02-01-2019

We tested RH editing tools in ArcMap and quickly discovered that many documented issues are resolved by performing edits with the 10.6.1 desktop version. The issues resolved in 10.6.1 enable us to most expediently proceed in our implemention so we are implementing at 10.6.1. In our testing, the issues are resolved by only changing the desktop environment. We initially edited a 10.4.1 geodatabase version (based on server keycode version) in sql server. In my experience there is usually a few versions of backward compatibility between desktop version and geodatabase version. My latest server keycode is a 10.6.0 so that's what I was enable my SQL server geodatabase. So my question is, what is the risk associated with cross version edits, specifically between 10.6.1 desktop and 10.6.0 gdb version? I remember hearing at one point there was a schema change in the geodatabase... if that is a real thing at which version does that occur?

‎01-30-2019

Here is a long list of things to try regarding slow performance issues in 10.5, mainly revolving around SQL server versions and issues. https://community.esri.com/thread/190605-arcmap-105-slow-performance

‎01-17-2019

This is how KDOT delivered the PM2 Pavement Condition summary data from the data extracted from our HPMS Dashboard for use by our MPOs. here are the threshold values: Then, add this twist: For the tenth mile segment to be “good” all three measures must be “good”. If any two are “poor” then overall it is “poor”. So, first I add fields for the measure "LEVEL", and here is how I interpreted these measures, from 1/good to 3/poor, using the following code for SQL Server management studio. The pavement surface types are the HPMS Coded values, obviously. update [shared].[PM2_2017] set IRI_LEVEL = 0, RUTTING_LEVEL = 0, CRACKING_LEVEL = 0, FAULTING_LEVEL = 0, [PM_LEVEL] = 0 where 1=1 update [shared].[PM2_2017] set IRI_LEVEL = 1 where IRI_VN < 95 AND SURFACE_TYPE_VN NOT IN (0, 1, 11) update [shared].[PM2_2017] set IRI_LEVEL = 2 where IRI_VN >= 95 and IRI_VN <=170 AND SURFACE_TYPE_VN NOT IN (0, 1, 11); update [shared].[PM2_2017] set IRI_LEVEL = 3 where IRI_VN >170 AND SURFACE_TYPE_VN NOT IN (0, 1, 11) update [shared].[PM2_2017] set RUTTING_LEVEL = 1 where RUTTING_VN < 0.2 AND SURFACE_TYPE_VN IN (2, 6, 7, 8) update [shared].[PM2_2017] set RUTTING_LEVEL = 2 where RUTTING_VN >= 0.2 and RUTTING_VN <=0.4 AND SURFACE_TYPE_VN IN (2, 6, 7, 8) update [shared].[PM2_2017] set RUTTING_LEVEL = 3 where RUTTING_VN >0.4 AND SURFACE_TYPE_VN IN (2, 6, 7, 8) update [shared].[PM2_2017] set CRACKING_LEVEL = 1 where CRACKING_percent_VN < 5 update [shared].[PM2_2017] set CRACKING_LEVEL = 2 where CRACKING_percent_VN >= 5 and CRACKING_percent_VN <=10 AND SURFACE_TYPE_VN IN (5); update [shared].[PM2_2017] set CRACKING_LEVEL = 2 where CRACKING_percent_VN >= 5 and CRACKING_percent_VN <=15 AND SURFACE_TYPE_VN IN (10, 3, 4); update [shared].[PM2_2017] set CRACKING_LEVEL = 2 where CRACKING_percent_VN >= 5 and CRACKING_percent_VN <=20 AND SURFACE_TYPE_VN IN (2, 6, 7); update [shared].[PM2_2017] set CRACKING_LEVEL = 3 where CRACKING_percent_VN >10 AND SURFACE_TYPE_VN IN (5); update [shared].[PM2_2017] set CRACKING_LEVEL = 3 where CRACKING_percent_VN >15 AND SURFACE_TYPE_VN IN (10, 3, 4); update [shared].[PM2_2017] set CRACKING_LEVEL = 3 where CRACKING_percent_VN >20 AND SURFACE_TYPE_VN IN (2, 6, 7); update [shared].[PM2_2017] set FAULTING_LEVEL = 1 where FAULTING_VN < 0.1 and SURFACE_TYPE_VN IN (3, 4, 10, 11) update [shared].[PM2_2017] set FAULTING_LEVEL = 2 where FAULTING_VN >= 0.1 AND FAULTING_VN <=0.15 AND SURFACE_TYPE_VN IN (3, 4, 10, 11) update [shared].[PM2_2017] set FAULTING_LEVEL = 3 where FAULTING_VN >0.15 AND SURFACE_TYPE_VN IN (3, 4, 10, 11) update [shared].[PM2_2017] set PM_LEVEL = 1 where IRI_LEVEL =1 AND CRACKING_LEVEL = 1 AND (RUTTING_LEVEL = 1 OR FAULTING_LEVEL = 1) update [shared].[PM2_2017] set PM_LEVEL = 3 where (IRI_LEVEL =3 AND CRACKING_LEVEL = 3) OR (IRI_LEVEL = 3 AND RUTTING_LEVEL = 3) OR (IRI_LEVEL = 3 AND FAULTING_LEVEL = 3) OR (CRACKING_LEVEL = 3 AND FAULTING_LEVEL = 3) update [shared].[PM2_2017] set PM_LEVEL = 2 where IRI_LEVEL != 0 AND IRI_LEVEL != 0 AND (RUTTING_LEVEL != 0 OR FAULTING_LEVEL != 0) AND PM_LEVEL not in (1, 3) the results for each HPMS year are published here on our ArcGIS Online site. http://ksdot.maps.arcgis.com/home/group.html?id=2f2d331c83d64e8882877cad7e18661b#overview This was not the most straightforward mapping I've done, so I thought this would be good to share the formula for how we at KDOT interpret the PM2 rules. Maybe next time I'll parameter this for the HPMS year, but for now I've only done this for two years.

‎01-14-2019

A non-python intensive method would be to use arctoolbox, data management, features - "feature vertices to points" to collect all vertices as points, then calculate geometry fields/add XY on the points, then export the result to a shapefile or a csv table. It will have the format you described, feature to vertex will give you an attribute(s) or ID relating to the original polygon FID in the vertex points.

‎01-14-2019

System Aliases for everyone.... System aliases to UNC paths for connection files, system alias on databases, registered connections in server, map services, application configurations... Update stuff and have network admins transfer system aliases to the updated environment.

‎01-14-2019

Very impressive solutions presented here! It definitely gets complicated when dealing with versioned data. There is also this option, an arc tool to add an incrementing ID field in an enterprise geodatabase Add Incrementing ID Field—Data Management toolbox | ArcGIS Desktop In Oracle and SQL server this tool performs the functions of creating a sequence and a trigger for you.

bug - calibration edit in 10.4.1 · ‎01-10-2019

I updated calibration point measures to recalibrate my route. I saved edits, which end-dated my route and caused the route measures to go NAN. I unretired the route, ran the Generate Route GP tool, and got this error message. Executing: GenerateRoutes RailRoutes Start Time: Thu Jan 10 14:33:57 2019 Network Layer: RailRoutes Network definition query: (FromDate is null or FromDate<=CURRENT_TIMESTAMP) and (ToDate is null or ToDate>CURRENT_TIMESTAMP) Regenerating route shapes in RailRoutes Network... Total number of features to update: 1 Processing Route UP_ATCHISON YARD (1 out of 1). Error populating network feature class This type of cursor does not support this operation. For example, calling UpdateRow on a read-only cursor. Failed to execute (GenerateRoutes). Failed at Thu Jan 10 14:34:00 2019 (Elapsed Time: 2.29 seconds) Then I tried to regenerate all routes using the catalog "generate route" in the ALRS and got this more detailed error message. Any ideas?

‎01-08-2019

I think this would be possible using something like: Created on July 10, 2014 @author: kyleg ''' import arcpy, os #workspace to search for MXDs startplace = r"F:\Cart\projects\KanPlan\MXD\Public" arcpy.env.workspace = startplace Workspaces = arcpy.ListWorkspaces("*", "Folder") for Workspace in Workspaces: arcpy.env.workspace = Workspace print str(Workspace) #list map documents in folder mxdList = arcpy.ListFiles("*.mxd") #set relative path setting for each MXD in list. for mapdoc in mxdList: #print the mapdocument name print " " print "MAPDOCUMENT "+str(mapdoc) mapdocu = Workspace+"/"+mapdoc mxd = arcpy.mapping.MapDocument(mapdocu) #Print the layer name of each layer in each mapdocument, and the layer properties of each layer for lyr in arcpy.mapping.ListLayers(mxd): if lyr.supports("SERVICEPROPERTIES"): servProp = lyr.serviceProperties print " Layer name:" + lyr.name +" at " + servProp.get('Connection', 'N/A') #print " Service Type: " + servProp.get('ServiceType', 'N/A') print " Service Type: " + servProp.get('Database', 'N/A') #print " Service Type: " + servProp.get('Server', 'N/A') print " Service: " + servProp.get('Service', 'N/A') print " Version: " + servProp.get('Version', 'N/A') print " User name: " + servProp.get('UserName', 'N/A') #print " Authentication: " + servProp.get('AuthenticationMode', 'N/A') #print " Workspace path: "+ lyr.workspacePath #print " Feature Dataset: "+ lyr.datasetName print "------------------------------------------------" else: pass ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ only take out the layer name code and print the mxd name and version. mxd SaveAsCopy can be done in the loop to export to a specific version.

Re: Bug List from RHUG · ‎01-04-2019

Ive added some of the release announcements and was going to start doing these listed bugs one by one. I think it would make sense (to me) use a matrix tracking system for bugs at reported version vs fixed version, many of the bugs reported in our lists have potentially been fixed. I was going to work on a more trackable format, like this: ID TFS Reported by Activity Issue Workaround Version 10.3.1 Version 10.4 Version 10.4.1 Version 10.5 Version 10.5.1 Version 10.6.1 Version 10.7 BUG-000101699 New York State DOT Export Network Service The 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. reported patch 4 verified verified verified resolved BUG-000110742 North Carolina DOT Realign Realigning a route to create a gap calibrates the To Measure on event incorrectly reported BUG-000106791 North Carolina DOT ArcMap Symbology Creating a layer from the Create Layer From Selected Features option does not honor the selection and displays all the features. reported resolved BUG-000108601 53113 North Carolina DOT Export Network Service Tool 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 reported resolved BUG-000106993 TFS #54450 North Carolina DOT Reverse Reverse Route causes calibration point measures to change beyond 6 decimal places. Manually edit calibration point and recalibrate downstream reported resolved NCDOT case 01889567 North Carolina DOT Relocate Events Service Relocate 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. reported reported hotfix BUG-000101392 TFS51810 North Carolina DOT Extend, Realign Extending 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 route Use reassign instead of extend if possible reported patch 4 verified verified verified resolved

‎01-04-2019

Esri Support Esri Roads and Highways for Server 10.6 (10.6.1) Summary This Location Referencing: Roads and Highways for Server patch addresses an issue where Event Editor assigns the lock to ::AnonymousWebUser for the first edit each day if Portal for ArcGIS is set up with enterprise logins. Description Issues Addressed with this Patch Esri Roads and Highways Server BUG-000117260 Event Editor assigns the lock to ::AnonymousWebUser for the first edit each day if Portal for ArcGIS is set up with enterprise logins. Installing this Patch Login with a Windows Administrator account. Select and download the files. Checksum (Md5) Server ArcGISLocRef10.6.1Patch1Server.msp e24ba73dc16c0b8c41a2c42510d9a4ea Double-click the msp file to start the install process. When Setup starts, follow the instructions on your screen. Note: Installing this patch will automatically restart your ArcGIS Services.

‎01-04-2019

Esri Support Esri Roads and Highways for Server 10.6 (10.6.1) Esri Support - Product Details : Esri Roads and Highways for Server 10.6 (10.6.1) Product Life Cycle and Issues Addressed https://support.esri.com/en/Products/Enterprise/GIS-Server-Extensions/esri-roads-and-highways-for-server/10-6#downloads?id=7570 This document was generated from the following discussion: Roads and Highways 10.6 (10.6.1) Announcement

‎01-04-2019

ArcGIS Location Referencing 10.5.1 Announcement This page contains the list of issues addressed at the release of ArcGIS Location Referencing 10.5.1 specifi . . . https://support.esri.com/en/download/7513

‎01-04-2019

#Esri Roads and Highways 10.5 Announcement This page contains the list of issues addressed in the upcoming release of Esri Roads and Highways 10.5. https://support.esri.com/en/download/7458

‎01-04-2019

originally reported by North Carolina DOT https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDExMDc0Mg==

Online Status	Offline
Date Last Visited	‎10-09-2025 11:47 AM

My Ideas

Latest Contributions by KyleGonterwitz

Re: How to sum overlapping segments of routes created by Network Analyst Route tool solver

Crossing Versions of Roads and Highways

Re: Long MXD load time with Roads and Highways desktop extension installed

FHWA PM2 Pavement Condition from HPMS

Re: Array of Coordinates

Re: Promoting services from Test/staging to Production

Re: Auto-Increment Field within SDE

bug - calibration edit in 10.4.1

Re: Managing and Identifying .MXD File Versions in a mixed 10.1 10.2 10.3 environment

Re: Bug List from RHUG

Re: Roads and Highways 10.6 (10.6.1) Announcement

Roads and Highways 10.6 (10.6.1) Announcement

ArcGIS Location Referencing 10.5.1 Announcement

Esri Roads and Highways 10.5 Announcement

BUG-000110742 - Realigning a route to create a gap calibrates the To Measure on event incorrectly.

Re: DGN to GIS with Affine Processor

Re: ArcPro-Roads and Highways Event: What is best ...

Re: Seeking Guidance: Building a Master Road Netwo...

Re: What Should an Event Layer Be?

Re: Asset extraction using JPEG street imagery

Roads and Highways User Group (RHUG)