AnsweredAssumed Answered

RouteTask.SolveRouteAsync Error with curves and barriers

Question asked by LawsonTyler on Aug 30, 2017
Latest reply on Feb 12, 2018 by MBranscomb-esristaff



I recently came across an error while creating routes using RouteTask.SolveRouteAsync(routeParameters). If you include barriers in the routeParameters and one of the barriers intersects a shape containing curves (hasCurves = true), then it will error out and say "Not implemented: operation does not support curves yet".


I have come across this error previously when querying a featureLayer and got around it by using relationships that compare curveless geometries (i.e. envelopeIntersects() instead of Intersects()) however this does not seem to be a valid work-around for this situation since the route needs more precision than that and I have found no way to alter the way it calculates the route to avoid comparisions using curved geometries.


Does anyone know if there is any information on when this functionality (operation supporting curved geometries) might be available?