Latest Contributions by AmitHazra

I am able to reproduce this behavior as well. Please contact Esri Technical Support for more assistance.  -Amit Esri Transportation LRS Team   ... View more

Hello @MirekGroen  I'm going to offer you an alternative method for triaging this issue. May I suggest you use the ArcGIS Pro Diagnostic Monitor functionality to review the network traffic to see whether you are able to append routes through the Pro GP to your LRS-enabled service. In Pro, try Cntrl+Alt+M. Then you can watch the network traffic log to determine what interactions are taking place. For instance, here I have an FGDB locally with one route in it (Feature class: RouteLoader) that I intend to Append to my branch versioned LRS service: Append Routes: ArcGIS Pro Diagnostic Monitor:   Note that the uploadItem created has the network and the centerline copied into it and has the new recordset in both: Hopefully, this gives you a starting point to resolve your Append Routes issue. If all else fails, please reach out to our technical support staff. -Amit -Esri Transportation LRS Team       ... View more

Hello Kevin - This post piqued my interest because I've been working with customer data in Pro for years and have never seen this issue arise. I reached out to Tech Support and the Product Manager to see if they would share the data you submitted to us with me. After reviewing your FGDB and the case notes there are a few observations I would like to share with you along with a workaround: 1) It seems rather than modifying/upgrading your existing Roads and Highways Armap-based LRS GDB you instead created a new LRS and new LRS network possibly using a mix of ArcMap-based feature classes with our Create New [LRS] and [LRS Network] GP tools (mixing and matching objects). This step is not necessary for migrating to ArcGIS Pro (and in your case could even cause errors). In any event since it seems you are simply testing the tools there are some things you need to be aware of. When you run Create LRS the minimum schema Route Id fields (CLS and Calibration_Point) will be set to text(255) - this will come into play later. I also noted that your M tolerance in the network feature class you have is 0.0000001 Mile (US Survey) based on an XY tolerance 0.001 meters.. Can you elaborate on your process for creating the network feature class and registering it with the LRS as this tolerance wouldn't work with our Create LRS Network from Existing Dataset GP. 2) The LRSN_Milepoint network you configured is set to Autogenerated Route Id but the field length is set to text(9). This is not in alignment with CLS/CP Route Ids. Armed with that information I made the following changes to the FGDB you submitted and did not run into any errors when registering the Ev_RIS_AccControl event: 1) Change the LRSN_Milepoint Route_Id field to text(255) 2) Run Modify LRS Network - Change the network configuration to Single-field Route Id 3) Run Create LRS Event from Existing Dataset - Success I can appreciate that our tools should not be crashing ArcGIS Pro but instead providing a warning/stop that you have a misconfigured LRS. The Product Team should look into that. I am curious as to whether you have tried to run Modify LRS to upgrade your ArcMap LRS. You could take a cut (default version) of your current ArcMap GDB and copy it to an FGDB and run the Modify LRS to evaluate the upgrade to Pro. Amit Esri Transportation LRS Team ... View more

@AlexanderShields_AZ I will echo my colleague's post with regard to functionality expected in ArcGIS Pro Location Referencing Realign edits. Here is an example where I am filling in a gapped route with a new centerline:   Please check that you have the correct centerlines selected and chosen. You may also test a simple touching extend or touching realign to see if the issue is related to the not-touching scenario you depicted in your original post. -amit@esri   Esri Transportation LRS Team        ... View more

Unfortunately, the underlying API calls to applyEdits does not occur until after you click Run. Therefore, you'll need to consider alternative methods to validate/construct your Route Name field. amit@esri  | Transportation LRS Team ... View more

Hello - Can you confirm you are trying to leverage an ArcMap 10.7.1 published service with an ArcGIS Enterprise GIS Server 10.9.1 licensed with Location Referencing Solutions for Server? If you are, this is an unsupported configuration. Once you migrate ArcGIS Enterprise to 10.9.1 you will need to upgrade your LRS GDB to our ArcGIS Pro-based model and republish services using ArcGIS Pro.  Please reference our migration resource document: https://community.esri.com/t5/arcgis-roads-and-highways-questions/migrating-from-arcmap-to-pro-3-1/m-p/1262252#M334https://community.esri.com/t5/arcgis-roads-and-highways-documents/migrating-road-and-highways-data-from-arcmap-to/ta-p/920363 -amit@esri  | Esri Transportation LRS Team ... View more

Hello -  Can you verify whether the GDB connected user you have specified for the connection to the LRS network and events has read access to the Lrs_* business tables (Lrs_metadata, Lrs_EventBehavior, Lrs_Locks etc)... -amit@esri  ... View more

Correct - versioned workflows require UTC for publishing but you can change the local time through the server. ArcGIS Pro-based editing works fine but there does seem to be an issue with an Event Editor that the product team is investigating, -amit@esri ... View more

Hi Masao - There were some Enterprise LRS issues related to Event Editor and UTC dates that were not apparent in ArcGIS Pro based editing workflows (which is what I tested in the previous response). The product team is looking into those issues now and I'll have a follow up for you soon. -amit@esri ... View more

Hello Masao There are two ways to set your service to local time rather than UTC. You can either update the specific map services Date Field Settings in the service parameters or you can set the ArcGIS Server date defaults in the ArcGIS Server Administrator if you have the privilege. Although the document is a little dated these patterns are outlined in the following technical resource document here. I tested configuring pacific Time (US & Canada) with values adjusted for DST using ArcGIS Enterprise 11 and can confirm these parameter settings are still applicable. -amit@esri  Esri Transportation LRS Team ... View more

Please review our resource documentation on Preparing the LRS for editing. Specifically, you must enable temporality for all LRS elements in the map you intend to publish as an LRS-enabled feature service.   -amit@esri ... View more