Select to view content in your preferred language

Discrepancy between result in ArcGIS Pro and ArcMap Transform Route Event tool

143
7
Thursday
gisuser12
Emerging Contributor

Upon running the Transform Route Event tool on ArcGIS Pro, the attribute table is empty. However, there is result returned on ArcMap after running Transform Route Event tool. Does anyone encounter the same issue and know how to resolve the issue?

This issue seems to persists using another set of data.

0 Kudos
7 Replies
DanPatterson
MVP Esteemed Contributor
0 Kudos
gisuser12
Emerging Contributor

@DanPatterson Yes, I am aware that the Make Route Layer tool could create a temporary feature layer and there is result in the attribute table upon testing. But inherently, Make Route Layer tool and Transform Layer tool are different. 

Is there any explanation on the discrepancy in the Transform Route Event tool between ArcMap and ArcGIS Pro when using the same dataset and inputting the same parameter? Is this a ArcGIS Pro performance issue or if this is a bug? I have tested on Pro 3.6 beta 2 but the issue persists...

0 Kudos
DanPatterson
MVP Esteemed Contributor

I see no explanation as to the differences in the documentation or on the public facing support site

Esri Support Search Results

It could be raised in the Beta site if it isn't closed yet, or put in a request to Tech Support would be your best option.


... sort of retired...
0 Kudos
AyanPalit
Esri Regular Contributor

@gisuser12 The linear referencing tools from ArcMap were redeveloped in Pro with little to now change in the logic. Are you able to share a data sample including the routes and event tables?

Ayan Palit | Principal Consultant Esri
0 Kudos
gisuser12
Emerging Contributor

Hi @AyanPalit,

Are you able to share your email address/ a link for me to share the data with you?

0 Kudos
gisuser12
Emerging Contributor

Hi @AyanPalit

I have sent you a private message for the testing data. Thank you

0 Kudos
AyanPalit
Esri Regular Contributor

@gisuser12 Thanks, I could reproduce the issue using the sample provided. I made a change to use the same data type of TEXT(50) for routes but that didn't change the behavior. I suggest logging a Tech Support Case.

Ayan Palit | Principal Consultant Esri
0 Kudos