Identify Routes Experience Builder widget Enterprise 11.3 not showing measures

[MirekGroen]

Hi Community,

We have been building a Experience Builder App with the new Roads and Highways widgets released with Enterprise 11.3. Using the Identify Routes widget gives an unexpected result:

It is not able to give us the Start, End and Current measures for the selected route. When using the same tool Identify Routes in ArcGIS Pro, on the exact same dataset, it is showing the measures:

In ArcGIS Pro (3.3.2) i tested both on the feature classes in the enterprise geodatabase and the published feature service - both are working.

The Experience Builder widget has worked before - but seems to be very unstable. Since a few days it doesn't matter which browser I use - Google Chrome, Edge, Brave, Safari - none of them can show the measures.

I don't know where the issue is coming from. Has anyone any thoughts on this?

[AyanPalit]

@MirekGroen Does this occur on just a few routes? Suggest that you use the REST API and use the browser developer tools to troubleshoot.

Sample: https://roadsandhighwayssample.esri.com/roads/samples/GeometryToMeasure/GeometryToMeasure.html

REST API: https://developers.arcgis.com/rest/services-reference/enterprise/geometry-to-measure/ 

This will allow you to check if the Geometry to Measure is returning results. If not, troubleshoot the service, like republish if necessary.  

[MirekGroen]

@AyanPalit Thanks for your quick response.

We are using these services and they work fine. Here are two screenshots which shows that both geometryToMeasure and measureToGeometry are working:

[AyanPalit]

@MirekGroen Great - thanks for validating the Geometry to Measure operation on the LRS service. Since, that's working there must be something in the LRS widget configuration.

You can use the widget and monitor the results, using the browser developer tools to troubleshoot. You may also test configuring another widget to validate all the settings are correct. 

[MirekGroen]

@AyanPalit  I have run some tests and checked the browser developer tools. I found something suspicious. - the widget is using the geometryToMeasure service, but when inspecting the url I found that the TemporalViewDate parameter is set to the FromDate value of the object. Should the TemporalViewDate value not correspond to the current date and time?

[AyanPalit]

@MirekGroen I believe the widget inherits the default Time Properties from the webmap layer. So you may want to revisit the layer Time Properties at the webmap level. For additional control, consider configuring the Timeline widget

[vegasjack]

I’ve faced similar issues with the Identify Routes widget. Here are a few things to check:

1. Data Permissions: Ensure the same permissions apply in Experience Builder.
2. Widget Configuration: Double-check settings and layer references.
3. Updates: Look for any known bugs or updates with 11.3.
4. Browser Console: Check for error messages in the developer console (F12).
5. Community Feedback: Post in the Esri Community for additional insights.

Hope this helps!

[MirekGroen · Accepted solution]

The solution for this issue is a correct conversion of datetime to a unix timstamp before appending routes. Unix timestamps don't contain information about time zones and is per definition in UTC. Our data is in UTC+1 (or UTC+2 during Daylight saving time), but were converted to a timestamp, without first convert to UTC time. The results is that the Experience Builder App is asking for a GeometryToMeasure 1 (or 2) hours before the route was existing and returns a RouteShapeEmpty error.