Locate Features Along Routes Reverting to 'Point' within Model

453
5
Jump to solution
11-30-2023 05:51 AM
Labels (2)
RandyMcGregor_BMcD
New Contributor III

I have a model that contains the Locate Features Along Routes Tool. It is set to create a line event, but it keeps reverting to 'Point' and the model fails. I have set "line" as the EventType in the model. How do I get this setting to 'stick'?

RandyMcGregor_BMcD_1-1701352239440.png

Thank you,

Randy McGregor

 

0 Kudos
2 Solutions

Accepted Solutions
DuncanHornby
MVP Notable Contributor

This does seem like a bug, I can replicate the issue too. Set it as line then it defaults back to point. If you want this fixed you need to contact ESRI support and log it as a bug and point them to this thread.

 

I did do the following, exposed the output event table properties as a parameter, this allowed the tool to run, that might help? 

DuncanHornby_0-1701702143819.png

 

View solution in original post

0 Kudos
RandyMcGregor_BMcD
New Contributor III

Thanks! Yes, appears to be a bug. Exposing it as a variable - without requiring the user to update - it seems to work. I thought I had tried that, but I did it just know and it worked. Thank you very much. I thought I had tried that without success, but doing it now works.

View solution in original post

0 Kudos
5 Replies
DuncanHornby
MVP Notable Contributor

Without showing your model this is hard to answer, best shot in the dark guess is you have an element in your model that you are feeding into that parameter and that's overriding it?

0 Kudos
RandyMcGregor_BMcD
New Contributor III

Thanks for the reply. That is a  good suggestion, but every time I put a Locate Features Along Routes tool in a model, this happens. Right now, I expose the option to select "Line" and "FMEAS" and "TMEAS" even though it's redundant. The model always runs in polygon inputs and the output is always linear.

 

It's the first tool in the model. In the image below, the Input Features are polygons and the output Event Table Properties have defaulted to point and thrown an error due to the fact that point will not work. 

RandyMcGregor_BMcD_0-1701696866830.png

 

0 Kudos
RandyMcGregor_BMcD
New Contributor III

To test, I created a model with nothing but the LFAR tool, with a polygon input:

RandyMcGregor_BMcD_1-1701697047879.png

I saved the model, then reopened it:

RandyMcGregor_BMcD_2-1701697094330.png

 

 

 

0 Kudos
DuncanHornby
MVP Notable Contributor

This does seem like a bug, I can replicate the issue too. Set it as line then it defaults back to point. If you want this fixed you need to contact ESRI support and log it as a bug and point them to this thread.

 

I did do the following, exposed the output event table properties as a parameter, this allowed the tool to run, that might help? 

DuncanHornby_0-1701702143819.png

 

0 Kudos
RandyMcGregor_BMcD
New Contributor III

Thanks! Yes, appears to be a bug. Exposing it as a variable - without requiring the user to update - it seems to work. I thought I had tried that, but I did it just know and it worked. Thank you very much. I thought I had tried that without success, but doing it now works.

0 Kudos