Latest Contributions by TedKowal

Your route system should be based upon your segments.....  So if there is a discrepancy then either one layer is "Wrong" or the two are not related to each other.  Without knowing the specifics, my suggestion is to create a Route system based upon your "segmented" layer using the same route name on the segments.  You can use the option to accumulated lengths of each segment.  The final result would be your own route layer upon which you can event map based upon accumulated mileage that would agree with the segmented on (because you built the layer based upon it) Generally speaking you should only have one "Route".  This will be a measured feature aka (contains the cumulative mileage).  In my case I deal with roads.  I have only one "Route" for any particular road.  Generally it starts at a 0 point (not always) and accumulates measures to its end point.  Now if I want and particular "milepost" I can simply event map any point against the "Route" feature.  If I want a line segment, I event map the beg and end points against the route for the line segment.  Now I understand that sometime there is a need to have multiple routes definitions.  I employ actually 3.  The primary route feature is defined by the Dual Centerines of each road, On roads going in opposite directions "aka divided highway".  In addition we employ a single centerline representation as well as a straight line diagram representation.  Although we have 3 route system, they are very carefully designed all based upon our primary definition. All Intersection, cumulative mileages are all exactly the same and agree with each other.  The route name is carefully designed for example take State Route 836 -- In our primary route system its name is 83600000E or 83600000W its length is 36 miles.  In the Single Centline LRS (Linear Referencing System) aka "Route" layer, the same route is named 83600000CL its length is 36 miles.  For out Single Line diagram it is a straight line that is exactly 12 inches long that we create a route of 36 miles on it. Its route name is the same as single centerline.  No matter what route layer I use or "Mix Match"  I have strict rules that apply -- for names and length.  So when I mix & match knowing the Lengths all match for each route all I have to do is programatically deal with the route name differences.  Example -- Project Engineer gives me some points from his plans -- engineering plans are based off of single centerline.  -- Finance want quantities and representation based upon google maps imagery -- (Dual Centerline).  All I do is create, being a VB guy is create a simple script changing the single line name to the double and iterate for both directions....   EB = Left(Single Centerline Name,8) & "EB"  and similarly the same for the WB side.  Then event map it against our Primary route system Sorry about the wall of text but it appears you have two LRS systems that are defined much differently and you are trying to use them together.  That cannot really happen unless you define yet another blending the rules for both.  My suggestion is to use one for your analysis.  If the "segmented" one is more accurate for uses then combine all the segments together under one route name....   What is linear referencing?—Help | ArcGIS for Desktop  https://magtug.files.wordpress.com/2011/11/2007-09_linear_referencing_in_arcgis_enterprise_deployments-x.pdf  ... View more

As Randy Burton  mentioned... your  "<" in the carbon field must be escaped.  In Vbscript there is no escape character as in python, for vb you must double quote the field that has the character(s) that need escaping.   [Location]& vbcrlf & "<CLR blue = '255'>" & [GW_Elevati] & "</CLR>" & vbcrlf & "" & [Carbon_tet]& """ # Or use the vb escape function .... vbcrlf & escape([Carbon_tet]) ‍‍‍‍‍‍ ... View more