The Costs tab shows all the costs configured with the network dataset. You can also select a cost to view how it is configured.
Certain attributes are used to measure and model impedances, such as travel time (transit time on a street) or demand (the volume of garbage picked up on a street). These attributes are apportionable along an edge; that is, they are divided proportionately along the length of an edge. For example, if travel time is modeled as a cost attribute, traversing half an edge will take half the time as does traversing the whole edge: if the travel time to traverse the edge is 3 minutes, it takes 1.5 minutes to traverse half the edge. If you are looking for a 1.5-minute route along this edge, the route feature is created from the first half of the edge feature.
Network analysis often involves the minimization of a cost (also known as impedance) during the calculation of a path (also known as finding the best route). Common examples include finding the fastest route (minimizing travel time) or the shortest route (minimizing distance). Travel time (drive time, pedestrian time) and distance (meters) are also cost attributes of the network dataset.
The Costs tab displays the cost attributes that are available with the network dataset in the upper section, and in the lower section, properties associated with the selected cost are displayed.
If there are warnings or errors in your evaluator, it will be displayed between upper section and lower section. For example, " The evaluator type is 'Same as Default' on these edge source: Street (Along)".
Properties—This section displays how the selected cost is configured. It lists the metadata associated with the cost attribute and the details on how the parameters and evaluators are configured.
Parameters—These are placeholders for values that you can change for a particular analysis. They each have a meaningful default value that is overridden by the user when needed.
Evaluators—Each attribute defined in the network must provide values for each source and direction (along and against for edges) participating in the network. An evaluator assigns values for the attribute of each source and travel direction, and a default evaluator for each element is used for those sources and directions that do not have an assigned evaluator for an attribute.
While travel modes and all attributes should not have leading space, trailing spaces or be an empty string, cost attributes additionally require that they should not have internal spaces either. Since fields are created based on cost attribute names of the network dataset used by the network analysis layer, having internal spaces in cost attributes would cause confusion as it is hard to match cost attributes to related field names. For example, a cost attribute named “My Minutes” in a network dataset would result in a field named: “Attr_My_Minutes” in the table associated with the Stops sub-layer of the Route Analysis layer.
The best practice for editing network attributes in a network dataset is in a project which does not involve layers that use the network dataset. Some editing might get blocked on the network dataset properties dialog box if there are layers in the project that uses this network dataset. It is therefore recommended to create a blank project, add connection to the geodatabase that contains the network dataset, and make edits in this project. When the layers using this network dataset are opened in an ArcGIS Pro session, you won't be able to add, delete, or rename a cost or a restriction attribute. This is to ensure the network dataset schema updates succeed and that the layers using it are initialized properly when opened.