Latest Contributions by KyleGonterwitz

‎04-01-2019

The idea is to add information to the route network in the LRS Data Model as appropriate to model the grade elevation of highway intersections. One way to achieve this would be to add elev_begin and elev_end to the centerline and to the route network, where the values would consist of either the interpolated Z values or enumerated grade (0 - at grade, 1 first overpass, 2 second overpass intersecting over 1 first overpass, etc) integer values. This information would be used to model and cartographic display the appropriate over/under for grade separated interchanges, as well as to help define the spatial/logical relationship of intersections between at-grade and grade-separated. This information would especially be helpful in visualization and routing to be derived from the LRS data model, considering all events registered to the route network should belong to the routes at the proper network elevation level, especially including tunnels and bridges as linear events, which further serve to indicate the route over/under relationship.

LRS Edit Log Table User Name Field · ‎04-01-2019

When creating a LRS data model in the Roads and Highways extention, the Lrs_Edit_Log table is a minimum schema object of the Roads and Highways LRS Data Model. The Lrs_Edit_Log table has field "UserName", type "String" with field length 272. The idea is to change the string length to 255. Why? Just because 255 is the shapefile/dbase limitation I suppose. If anybody has a name longer than 255 characters first I apologize, second, you should use a shorter user name when editing roads and highways database. It will also help with field validation based on a 255 length text field as a validation rule.

‎03-21-2019

Currently, creating routes in Roads and Highways requires careful selection of centerlines one at a time. It would be easier if multiple centerlines could be selected at one time, and ordered logically/spatially. It would also be useful to have the selection mimic geometric network tracing selection functionality, selecting the shortest path along a looped network between begin and end points, and allowing for blocking if the selection of shortest path does not follow the intended centerline pattern.

‎03-21-2019

As far as I can tell, the ALRS items can only be created in the Geodatabase outside the feature dataset, then moved into the feature dataset, and that only works when the feature Dataset M tolerance matches the network tolerance. Creating a feature dataset with a different M tolerance than the network, and it will likely be different by default, then moving the network and affecting the ALRS Network M tolerance seems like not a good idea. The Feature Dataset M tolerance needs to match the network M tolerance so it would be a nice feature to be able to create the ALRS in the feature dataset. Also perhaps in the process of creating a new feature dataset in the presence of a route network, the route network M tolerance would be the default for the feature dataset.

‎03-21-2019

Create a GP tool to register an event feature class to the ALRS in a roads and highways geodatabase. Currently this can only be done by a right-click menu option.

‎03-21-2019

Create a geoprocessing tool that performs this function. This function is currently run by right-clicking on the ALRS in a Roads and Highways enabled geodatabase.

‎03-21-2019

Use case - add inventory item in collector, then immediately sync that inventory item into survey 123 for condition survey of that new inventory item - all in disconnected environment.

‎03-21-2019

Use case - add inventory item in collector, then immediately sync that inventory item into survey 123 for condition survey of that new inventory item - all in disconnected environment.

Re: GIS-T RHUG SIG Meeting · ‎03-21-2019

Thought of the day March 21 2019. I am working on rectifying the RHUG enhancement list with the ArcGIS Ideas. I'm not taking into consideration the work that the Esri team has been building into the current and future releases based on the latest enhancement list, so a straight conversion could generate a lot of useless content. So, I propose we take some time during the meeting to hash out listed enhancements as ideas, and to gather new ideas as well. Working together in the SIG meeting, DOT "hand in hand" with Esri, I think we can efficiently convert the listed enhancements to useful ideas for the product development team. That would have the additional benefit of assignment of ownership to the idea contributor. In the meantime, I recommend adding any new ideas or old ideas you may have to the ArcGIS Ideas page ArcGIS Ideas and tag the idea with "RHUG" as well as any other relevant tags - desktop, server, event, route, etc. That would give us a head start for the GIS-T SIG meeting, as well as allow for contributions by interested parties unable to be present with us at GIS-T. The https://community.esri.com/groups/roads-and-highways-user-group-rhug/pages/rh-enhancement-requests has been updated to provide a link to current ideas based on tags potentially relevant to this user group.

‎03-20-2019

I do hatching in AGOL with points. I have a script to create "fake hatches", here is a link to that script: pydot/HatchFake.py at master · KDOTGIS/pydot · GitHub ArcPro supports hatching in this manner: Draw measured hatches along lines—ArcGIS Pro | ArcGIS Desktop I have not tested publishing from Pro to AGOL with hatch symbols. I'm upvoting this idea.

Re: GIS-T RHUG SIG Meeting · ‎03-20-2019

a "mastermind group" might be a potential approach to the meeting format. Users can prepare for the meeting by submitting written problem statements of solvable challenges. Then the group members with ideas or experience with similar problems can advise. It's pretty much what we do anyway.

Re: GIS-T RHUG SIG Meeting · ‎03-19-2019

One thought - the introductions at the last GIS-T RHUG SIG took a long time. It was fun to meet everyone and learn a little about everyone's favorite band but maybe this time we can skip the introductions and get right to the DOT vs Esri arm wrestling match.

‎03-19-2019

Good article, there is a lot of material out there on the web to read on this topic. It comes down to this: creators of GIS data at the local level create data in a projection. Cartographers use a projection. Surveyors use a coordinate system. Hopefully, the cartographic projection and the surveyors coordinate systems are based on a similarly defined datum. The common datum should support the accurate measurement coordinate system, and a multitude of projections appropriate for the cartographic needs based on the extent of the earth displayed in the map. With definition of low distortion projection systems in the GRAV-D datum, surveyors and mappers can work together in the same projection as a coordinate system. As a state practitioner of GIS involved in engineering and construction, I am attracted to the idea of maintaining a shape-length-based linear referencing system of highways (or other linear networks) defined in the multiple (20) low distortion projection systems in my state, and rolling them up into the ArcGIS applications (desktop, web based, etc) seamlessly. In other words, I would like to be able to print my statewide map in my statewide conformal projection (eat my cake), while keeping my data defined in the 20 separate low distortion projections (have it too) in order to maintain the most accurate shape length definition at the topographic surface. I'd like the software do this for me out of the box without having to develop this solution myself.

‎03-19-2019

A fish route or alpha route is defined as a highway having a planimetric shape resembling a fish or the greek letter α. These routes frequently occur in highway system interchanges where a route curves with a relatively small radius to pass over or under itself, often in conjunction with a larger, grade separated interchange. The idea is to support this configuration of highways in the Esri Roads and Highways location referencing extension without the need for a workaround solution. Currently, the position of Esri is that the alpha routes are supported IF the introduces a small gap in the route where the intersection would occur at the grade separation. The position of the Roads and Highways users is that this workaround is crude, it doesn't meet our definition of support for the shape of these highway designs, and it results in other data processing challenges.

‎03-06-2019

I stopped the processing Monday morning, compressed and the A/D table counts went back down to zero, appears no harm (or benefit) was done. Ryan I will take your advice and try to uniquely ID the gapped segments more thoroughly. The Route name is not part of the route ID but the route ID is based on an enumerated list of street names and cities in a county, it shouldn't be too difficult to enumerate the dissolved-unsplit gapped segments to uniquely identify the parts. I assume the the database log files associated with MSSQL are what I should be checking, and the LRS edit logging is out of my control. Kyle

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

My Ideas

Latest Contributions by KyleGonterwitz

Add Elevation Attributes to Default LRS Data Model Schema

LRS Edit Log Table User Name Field

Ability to choose multiple centerlines at once for editing

Allow for creation of ALRS elements in Feature Dataset

Register Event Feature class GP Tool

Remove Centerline Geometry Duplication GP tool

Re: Combining Survey 123 and Collector

Re: Combining Survey 123 and Collector

Re: GIS-T RHUG SIG Meeting

Re: AGOL Symbology Hatching

Re: GIS-T RHUG SIG Meeting

Re: GIS-T RHUG SIG Meeting

Re: GIS Design Support for NSRS 2022 and Low Distortion Projection Zones

Support Alpha/Fish Route in Roads and Highways

Re: bulk calibration of gapped local roads

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)