Update the “Cost” field of the Walkways layer directly through the REST endpoint and immediately reflect those changes in routing results.
After you publish a routing service based on a FGDB network dataset, the routing service locks the FGDB. So editing costs in a network dataset stored in a FGDB is not supported via REST endpoints.
However if your workflow is to allow users to change the costs used when finding routes, this can be achieved by adding an attribute parameter value to your cost attribute that allows changing the costs using a simple function.
For example, Lets say you want the users to adjust the walk time and you have a cost attribute called WalkTime defined in your network dataset. You can have an attribute parameter associated with WalkTime called "Walking Speed (km/h)". The default value for this attribute parameter can be most common for your context like 5 km/hr. The value for WalkTime cost attribute needs to derived from the walking speed and the time walking at a constant speed of 1Km/Hr.
In terms of how this all looks in the network dataset, You need to first define a new cost attribute called "TimeAt1KPH" whose evaluator is based on the length of your line features and a constant. For example, in my screenshot I have the evaluator for TimeAt1KPH set to METERS * 0.06 since my network dataset has a length field called METERS that stores the length in meters.
Once you have defined a TimeAt1KPH cost, you can define a function evaluator for the WalkTime based on the Walking Speed attribute parameter and TimeAt1KPH cost attribute as show in this screenshot
After you rebuild the network dataset and publish the routing service, when calling the REST endpoint of the routing service, you can use WalkTime as your impedance and pass a different value for Walking Speed attribute parameter to change the walk time used by the service. A sample REST request that passes walking speed as 10 km/hr would look like
&stops=-117.3,34.3;-117.31,34.31
&impedanceAttributeName=WalkTime
&restrictionAttributeNames=Walking
&attributeParameterValues=
[
{
"attributeName": "WalkTime",
"parameterName": "Walking Speed (km/h)",
"value": 10
},
{
"attributeName": "Walking",
"parameterName": "Restriction Usage",
"value": "PROHIBITED"
}
]
Hope this helps
Deelesh
