Latest Contributions by KyleGonterwitz

What is your desired/allowable level of accuracy?  Three UTM zones covers about 1/3 of the USA, and does introduce a lot of distortion.  So how much distortion is too much for you? I just posted this idea (with LRS in mind specifically) for the exact reason/problem you are having.  GIS Design Support for NSRS 2022 and Low Distortion Projection Zones  If you have only one route, you could potentially find or define a projection that would satisfactorily minimize distortion for that route.  Probably your best option is to segment the route shapes between projections at a state level, build a bunch of LRS routes and calibration points then use those to calibrate the whole route with attributes as opposed to shape length definition, but then again, what is your desired/allowable level of accuracy?   Upvote my idea and maybe someday you could use GIS and LRS for something like this with Surveying level accuracy, distortion a couple 10's of parts per billion.  You can't eliminate distortion but you are asking the right question to minimize distortion for sure. ... View more

Pro team may be going in the direction of burial more of the measure stuff into symbology rather than a layer property...  Given the intelligent menu system of pro, I think that a good approach option to pro incorporation may be an intelligent menu that activates when the layer is activated and the layer is recognized as having m values.  From that menu linear reference tool options could be chosen.  ... View more

upon first review of the process to draw measured hatches along lines, that works really well and has a lot of options, it's just buried in there with the many symbol options of pro.  That link was helpful but it could use more screenshots, the terminology used in that link to achieve this is so specific to pro (but was very well worded and I could easily figure it out).  Also, what can be done to keep the hatched labels from drawing upside down?  I set my text angle at 270 to get my hatch labels right-side up. ... View more

good description of the idea, I changed it.  Great info on the hatching capability, I will look at that, thanks. ... View more

I do it like this because I use LRS.  With this script I can use my routes with measures to create points at different increments for different LRS Reference Methods: pydot/HatchFake.py at master · KDOTGIS/pydot · GitHub  ''' Created on Jul 14, 2015 This script will create route events as points along the route features at specific increments the points can be symbolically displayed as route hatches for web mapping @author: Kyle Gonterwitz with, as always the amazing help from Dirk Talley @contact: Kyleg@Ksdot.org ''' #import arcpy from arcpy import (AddField_management, MakeFeatureLayer_management, CreateTable_management,da, Exists, AddXY_management, TruncateTable_management, Append_management, MakeRouteEventLayer_lr, Delete_management, FeatureClassToFeatureClass_conversion, env) #set the geodatabase parameters for the input route data env.overwriteOutput = True wsPath = r"Database Connections\shared@SQLGIS_cansys_gis_dev.sde" #enter the workspace path that has the data owner login StatefcRoutes = r"\\gisdata\arcgis\GISdata\Connection_files\RO@sqlgisprod_GIS_cansys.sde\GIS_CANSYS.SHARED.SMLRS"  # State Route feature class with begin/end attribs CountyfcRoutes = r"\\gisdata\arcgis\GISdata\Connection_files\RO@sqlgisprod_GIS_cansys.sde\GIS_CANSYS.SHARED.CMLRS"  #County Route Feature Class with begin/end attribs #State and County are the Two main Linear Referecing Methods used by KDOT which will be hatched StateOutTable = "SMHatch" CountyOutTable=  "CMHatch" StateFields = ["LRS_Route", "BEG_STATE_LOGMILE", "END_STATE_LOGMILE"] CountyFields = ["LRS_KEY", "BEG_CNTY_LOGMILE", "END_CNTY_LOGMILE"] #this field sets the hatch separation/spacing.  For a hatch point every 1/10 of a mile, enter 0.1.  For a hatch every 1/100th of a mile, choose 0.01.  #for mapping in KanPlan 1/10 mile seems plenty sufficient, and will create about 108,000 points for each LRM.  #1/100 would create 1,080,000 points which might suffer from use of in-memory processing, already this script takes a few minutes to run for each LRM HatchSep = 0.1 countyLRM = [CountyfcRoutes, CountyOutTable, CountyFields] stateLRM = [StatefcRoutes, StateOutTable, StateFields] LRMethod = [countyLRM, stateLRM] for method in LRMethod:     print "creating hatches for " + str(method[1])     #add route table as feature layer     if Exists("RouteLyr"):         Delete_management("RouteLyr")     else:         pass     MakeFeatureLayer_management(method[0], "RouteLyr", "DIRECTION in (  1 ,  2 )")     #create event table in memory     mem_table = "HatchEvents"     if Exists(r"in_memory\\"+mem_table):         print str(mem_table) +"already existed, deleting"         Delete_management(r"in_memory\\"+mem_table)     else:         print "Creating table for processing route increments of " + str(HatchSep)             CreateTable_management("in_memory", mem_table)     mem_table = r"in_memory\\"+mem_table     AddField_management(mem_table, "RouteID", "TEXT")     AddField_management(mem_table, "LogMile", "Double")         for row in sorted(da.SearchCursor("RouteLyr", (method[2]))): # @UndefinedVariable         LRSKEY = row[0]         if LRSKEY == (LRSKEY):              # use this loop to test the script against a single route             iter0 = row[1]             #print row[0]+ ' from '+str(row[1])+' to '+str(row[2])  #print the current LRS Key             #set the begin and end parameters from which to create incremental values             if HatchSep == 0.1:                 round_dec = 1             elif HatchSep == 0.01:                 round_dec = 2             else:                    round_dec = 0                 print "check hatch separation value"             minlog = round(row[1], round_dec)             if minlog > row[1]:                 minlog = minlog - HatchSep             else:                 pass             maxlog = round(row[2], round_dec)             if maxlog < row[2]:                 maxlog = maxlog + HatchSep             else:                 pass             #set the starting point for the route segment             itermile = minlog             #now loop between the start and end logmiles for each route segment, and insert the step increment into the event table in memory             while itermile <= maxlog and itermile >= minlog:                 #print str(itermile)                 with da.InsertCursor(mem_table, ("RouteID", "LogMile")) as insert:# @UndefinedVariable                     insertfields = [LRSKEY, itermile]                     insert.insertRow(insertfields)                 itermile = itermile + HatchSep             del minlog             del maxlog             MakeRouteEventLayer_lr("RouteLyr", method[2][0], mem_table, "RouteID POINT LogMile", "HatchPoints_events", "", "ERROR_FIELD", "ANGLE_FIELD", "NORMAL", "COMPLEMENT", "LEFT", "POINT")     #add XY points, later on these coordinates can be used to hyperlink to google street view, bing maps, etc.  Make sure we are in NAD83 Lat/Long CRS here.     AddXY_management("HatchPoints_events")     try:         Delete_management(wsPath+'//'+method[1])         FeatureClassToFeatureClass_conversion("HatchPoints_events", wsPath, method[1], "LOC_ERROR = 'NO ERROR'")     except:         TruncateTable_management(wsPath+'//'+method[1])         Append_management("HatchPoints_events", wsPath+'//'+method[1])     cleanup = [mem_table, "RouteLyr", "HatchPoints_events"]     for layer in cleanup:         Delete_management(layer)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

In the popup configuratior  for the latest version of pro, there is an option to add text to the popup, then at the bottom of the configurator, a button for expressions. Click that button, then there is another button that says "new".  Click NEW then we get this window: In this expression builder, there are only text, number, and date functions.  also in this expression builder, the SHAPE field is not presented as an actionable field.   So, looks like a "cant be done" for now in pro.  To the ideas page! ... View more

My data is a hosted feature service for the collector app.  I don't want to have to calculate attribtues in the hosted feature service layer each time a point is added or moved or set up some nonsense CDC process to do this. I dont actually need the lat/long in the popup, what I really need is the lat/long as URL tokens behind an image to link to google maps, bing maps, and most of all, mapillary at a particular location and scale.  If I could get the coordinates in the popup I can get them in a url expression I think, but the popup would be an easy test to see that yes, it can be done.   I will look at the math solution there Håkon Dreyer maybe I can get that to work with the point[() function?  That is nice to know, I figured a mathematical projection calculation might be part of a solution. Maybe I will take this to the Ideas page.   ... View more

Had some issues yesterday morning.  Saw the health was ok for hosted feature services but iffy on geoenrichment.  Next time I will report this issue.   ... View more

Just FYI, another way to remove the right most string in VB is to use the String Reverse method, remove first string using left or mid, then use the string reverse again. This is a method I have found handy for classifying Schools into Elementary, Junior High, Middle, and High Schools, because a list of schools usually has a format like "MARTIN LUTHER KING JR ELEMENTARY SCHOOL" or "JEFFERSON MIDDLE SCHOOL" so the string reverse method gives you an easy way to work from the right to left by reversing the characters so you are actually working left to right, without having to count characters or string parts.  Just make sure to reverse the text again so you arent showing anybody information that looks like "LOOHCS ELDDIM NOSREFFFEJ" ... View more