Latest Contributions by KyleGonterwitz

Esri once shared a script to classify self-intersecting polylines, what it does is work out the type of self intersect types like "Branch, Alpha, Barbell, Lollipop" etc.  It was really helpful for us in cleaning up our network for Roads and Highways.  I'm sure it must be available somehow, Clive do you know what I'm talking about? ... View more

https://docs.microsoft.com/en-us/sql/relational-databases/collations/collation-and-unicode-support?view=sql-server-2017 ... View more

What's your RDBMS- SQL Server, Oracle, Other?  I think Oracle can be configured with case sensitivity, and you can change the configuration to allow case insensitivity.  Could also be related to the encoding. ... View more

For County LRM: For State LRM (designated state highways only): I have some SQL that will partition distinct road name parts by city and county to row number local route IDs into a 4 or 5 character route ID, I'd be glad to share it if anyone has an appetite for looking at SSMS update query statements.  Once that Route ID is assigned for locals, we dissolve connected segments, and partition by route ID to calculate unique ID's for local gapped routes from row numbers. We had about 6 routes with more than 100 gapped route ID segments in our local roads so we manually changed some of those route IDs to keep the unique ID to two characters. ... View more

Hi Colin, there was some interesting discussion on the multiple LRM topic in the RHUG meeting yesterday.  Sounded like a few states would use multiple LRMs, and right now keeping them in sync is a manual effort. In the next RHUG meeting I think Esri will deomonstrate derived LRM networks in Pipeline location referencing.  I think switching units of measure from miles to kilometers is one potential use case, another is having multiple LRMs spanning across city, county, and/or state borders.  Once the LRMs are in sync I think the LRM to LRM conversion tool is one way to translate events between multiple LRMs, the LRS Rest Service might be another way. ... View more

Nice Poster Ryan!  I like how NCDOT has incorporated source documentation attributes, facility exclusion types, the HPMS Sample events, and the widening event. If you have complete address ranges in that street name event, that is incredibly progressive for a DOT in my opinion and very impressive.  I think I remember talking with you or Erin about that a couple years ago and I am impressed by the depth of LRS knowledge of the average non-DOT GIS professional in North Carolina.  Having glanced at this, these would be my questions for discussion: Do routes increase in the direction of address increase and/or is left/right is based on address range direction or route direction?  Do you use Collector or Survey123 for HPMS sample inventory?  It looks like this model would support either of those solutions fairly well.   ... View more

Nicole, That would be great, I guess we didnt have a chance to talk about this.  I did discuss some of those questions between making that presentation and presenting and gave the following answers for the other states: I found out: WV does extensively utilize lookup tables and maintains 1:1 coordination between domains and lookup tables in their practice. Arizona migrated to Roads and Highways from a LRS that was referent based, and as such they do heavily utilize referents and are constantly pushing for more development and support of referent based methods for geo-locating and reporting.  I eventually figured out OTT means "open to traffic" and I think having that date attribute on geometric events like lanes is a wonderful idea. I mentioned in the presentation they also have some date attributes for HPMS submittal items from traffic count and pavement management systems, which is also a good idea since those separate systems need to be integrated into a HPMS submittal while representing counts or pavement collected and processed on a network as-of a not current network, sometimes that collection and processing is representative of a highway network that is a year old or more by the time it is integrated into HPMS.   Arizona also keeps a paint attribute and domain in certain paint-relevant events like auxillary lanes, bicycle lanes, channelizations, and medians, and I think I heard James mention they have a pretty precise paint striping GIS polyline layer which I think is awesome and supporting evidence that Arizona DOT is really going great things. ... View more

It would be very useful to split a highway segment in the collector app.  Ideally the split policy duplicate vs default would be set to duplicate or the UI would allow the user to choose an override to the split policy.   This would be very useful for collecting or adding data along a segment between highway intersections such as lane changes, lane width changes, shoulder changes, median changes, etc.   ... View more

My original post here was a sort of comment about the python functions being called/named differently than the toolbox tools or the documented names.  You might try importing the locref lib, then try: from locref import RelocateEvents RelocateEvents(in_network, event_name, last_invoked_time, lrs_time, last_lrs_time, output_format, export_file, out_features, include_event_geometry) ... View more

There's always more than one way to do something in GIS... I have developed a python scripting "style" where I explicitly import the functions I use from arcpy - rarely do I ever start a script with: import arcpy Rather, I would script : from arcpy import ListFeatureClasses, DeleteField_management, env,  and as I script I would explicitly import each of the functions I need for the script either globally or within a function definition.   It's not right or wrong, It's just how I do it.  It's probably be cause I originally learned fortran and they beat "Implicit None" into me... plus importing all of arcpy takes many more milliseconds, and I have things to do other than import all of arcpy all the time.   So, for me, I prefer from locref import GenerateRoutes, RelocateEvents as opposed to the method arcpy.ImportToolbox("C:\Program Files (x86)\ArcGIS\LocationReferencing\Desktop10.6\ArcToolbox\Toolboxes\Location Referencing Tools.tbx") in order for my method to work however, I need to make sure the locref library in that toolbox location is in my python path for the interpreter environment I am using.   ... View more