Latest Contributions by ColinSchut

Thank you for the replies. I have no particular reason to delete it, other than seeing myself or someone else in the future wondering why that point is there along with general cleanliness. Not messing with calibration points directly is probably a good policy though.  ... View more

"Here's where the Referent Points comes into play. Publish a separate map service for this layer that is not LRS-enabled and optionally, using an underlying DB user connection with Event Viewer privileges. When you configure your Event Editor webmap, add that item to your web map along with the LRS web service." Is the only issue I'm having. This allows you to bring the points into the map, but not to use them as a referencing method.  Otherwise this is exactly the workflow I'll be using.  ... View more

This is an excellent and comprehensive answer, thank you Amit. The URL parameters in particular avoid the majority of headaches I was imagining and I already have Portal groups set up to allow this workflow.  We've always had conflict prevention enabled but our lock root version is sde.default. Are there any specific reasons to use a surrogate other than an additional layer of protection for default? For our small group I'm not certain the extra version is necessary and I'd like to keep the administrative overhead to a minimum.  Thanks for the answers everyone, this was extraordinarily helpful. Initial tests have gone very smoothly. ... View more

It had something to do with the new centreline the route was being realigned to. I had collected this line in collector, exported to a gdb and copy and pasted it into the centreline feature class. I don't know the exact issue, but it must have had something to do with projections or units moving it between workspaces. Creating a new clean centreline fixed the problem. ... View more

I believe it's confusing because ideally this is a situation that would never occur at all if an event record has been loaded and route changes created properly over time. Perhaps a better way to put it would be to say that I have an external excel table or old shapefile containing a bunch of historical information that has never been in an lrs. A record in that table has a "Fromdate"  year of 2010 and is still accurate today. Between 2010 and today, that route has had 4 realignments downchain of the event. If I want to improve my historical data and add it to the database by appending it as is, it will create 5 timesliced records that have the same measures (4 of which will be geographically incorrect). I was wondering if there was any way to calibrate those properly while appending them, or if I need slice that data and locate them separately for ever realignment that has occurred on the route before appending. A big task with a big dataset. Anyway Ryan, I always greatly appreciate the help you provide on my questions. This only occurred to me because of some improperly modelled data, and I'm unlikely to bother dealing with historical data like this in the future, I will likely close this soon regardless of any answers I get. ... View more

To clarify a bit this is referring not to doing a route realignment (the events that were active at the time of the realignment updated properly) but extending an event time range over a realignment that has already been done. Event behaviours don't seem to apply because no route changes have occurred in the edit session. So when I did the realignment: Event 1: From Date: 2010/01/01 To Date: 2011/01/01  - Measure 10 to 11 Realignment: 2015/01/01 I now want to change Event 1 to be From Date: 2010/01/01 to To Date: NULL And I get  Event 1: From Date 2010/01/01 To Date: 2015/01/01 - Measure 10 to 11 (Correct) Event 1 From Date 2015/01/01 To Date: NULL -  Measure 10 to 11 (When it should be 11 to 12 for example). ... View more

I asked here specifically because I would expect it to be common behaviour if it's a tolerance issue and wanted to know if others experience the same thing in their ALRS. And why only certain routes and locations? Like I said, I wouldn't have given it a second thought if it were a regular feature class/gdb. That said, I 100% agree it's not a practical issue and consider this closed.  ... View more

Yes it's reproducible, I usually open new document's every time. It's also the same locations as far as I can tell. I did find a new use case, where it's occurring at the junction of two routes. It's fine at the calibration points on either side and the centreline junction is coincident in the case below (though there are also cases where they are not). There are no issues in the database where the second calibrated network has not been created. Again, these errors are all within tolerance, but I'm seeing the below issue on two additional calibrated routes.  ... View more

This is a guess, but could it be Gap Calibration type (Stepping increment, adding increment or adding euclidean distance)? We only have stepping increment gaps and all my types are 2. ... View more