Hello Melinda, Thanks for the suggestion and the post! I think this is a great idea and will allow some options where we have experienced issues with points that fail. I like the classification of the result as using closest, that allows a solve while notifying that it may not be the best solve. I am still concerned about the impact of points that still fall outside of the range specified (for instance if it is set to 500 feet and a suitable edge is not found). To be honest, the biggest issue we have is the failure to produce a solve if any of the input points are not valid. The option to Ignore Invalid Locations resolves this problem but our users are not happy since the failures can alter the results, i.e. removing locations that are required for the solve. Conversely, if the option to ignore these invalid locations is false, then any collection of points with any single or multiple invalid locations will not run, only error out. Is there a way to report a failure with the Ignore Invalid Locations as false and still solve for the remainder of the locations? Perhaps return the point that was invalid so the end user knows which one was failing?
... View more