Latest Contributions by KyleGonterwitz

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. ... View more

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. ... View more

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.    ... View more

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. ... View more

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. ... View more

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. ... View more

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. ... View more

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 ... View more

here is a roundabout way to delete the identical records keeping the one with the lowest (minimum) object ID, demonstrated with my sloppy python copied from the results tab.   arcpy.Merge_management(inputs="CPNewMeasEndEventsY;CPNewMeasEndEventsX;CPNewMeasEventsY;CPNewMeasEventsX", output="C:/temp/routeparts.gdb/CalibrationPoints_MultipartLocals") arcpy.FindIdentical_management(in_dataset="CalibrationPoints_MultipartLocals", out_dataset="C:/temp/routeparts.gdb/cp_identicals", fields="RID;MEAS;POINT_X;POINT_Y;Measure", xy_tolerance="", z_tolerance="0", output_record_option="ONLY_DUPLICATES") arcpy.Statistics_analysis(in_table="cp_identicals", out_table="C:/temp/routeparts.gdb/cp_identicals_to_delete", statistics_fields="IN_FID MIN", case_field="FEAT_SEQ") arcpy.AddJoin_management(in_layer_or_view="CalibrationPoints_MultipartLocals", in_field="OBJECTID", join_table="cp_identicals", join_field="IN_FID", join_type="KEEP_COMMON") arcpy.SelectLayerByAttribute_management(in_layer_or_view="CalibrationPoints_MultipartLocals", selection_type="NEW_SELECTION", where_clause="1=1") arcpy.AddJoin_management(in_layer_or_view="CalibrationPoints_MultipartLocals", in_field="cp_identicals.FEAT_SEQ", join_table="cp_identicals_to_delete", join_field="FEAT_SEQ", join_type="KEEP_COMMON") arcpy.SelectLayerByAttribute_management(in_layer_or_view="CalibrationPoints_MultipartLocals", selection_type="REMOVE_FROM_SELECTION", where_clause="cp_identicals_to_delete.MIN_IN_FID = cp_identicals.IN_FID") arcpy.RemoveJoin_management(in_layer_or_view="CalibrationPoints_MultipartLocals", join_name="cp_identicals_to_delete") arcpy.RemoveJoin_management(in_layer_or_view="CalibrationPoints_MultipartLocals", join_name="cp_identicals") arcpy.DeleteFeatures_management(in_features="CalibrationPoints_MultipartLocals") ... View more

I had similar problems after os upgrades on some servers, part of the problem for me was running tools as admin user made it difficult to troubleshoot running something as that user.   ... View more