3D Analyst Tools ArcToolbox

Make Closest Facility Layer Tools

How to use Make Closest Facility Layer Tool in Arc Toolbox ArcMap ArcGIS??

Make Closest Facility Layer

Make Closest Facility Layer

Path to access the tool

:

Make Closest Facility Layer Tool, Analysis Toolset, Network Analyst Tools Toolbox

 

Make Closest Facility Layer

Makes a closest facility network analysis layer and sets its analysis properties. A closest facility analysis layer is useful in determining the closest facility or facilities to an incident based on a specified network cost.

1.    Input Analysis Network

The network dataset on which the closest facility analysis will be performed.

2.    Output Layer Name

Name of the closest facility network analysis layer to create.

3.    Impedance Attribute

The cost attribute to be used as impedance in the analysis.

4.    Travel from or To Facility (optional)

Specifies the direction of travel between facilities and incidents.

1. TRAVEL_FROM—Direction of travel is from facilities to incidents. Fire departments commonly use the this setting, since they are concerned with the time it takes to travel from the fire station (facility) to the location of the emergency (incident).
2. TRAVEL_TO—Direction of travel is from incidents to facilities. Retail stores commonly use this setting, since they are concerned with the time it takes the shoppers (incidents) to reach the store (facility).

Using this option can find different facilities on a network with one-way restrictions and different impedances based on direction of travel. For instance, a facility may be a 10-minute drive from the incident while traveling from the incident to the facility, but while traveling from the facility to the incident, it may be a 15-minute journey because of different travel time in that direction.

5.    Default Cutoff (optional)

Default impedance value at which to stop searching for facilities for a given incident. This default can be overridden by specifying the cutoff value on incidents when the direction of travel is from incidents to facilities or by specifying the cutoff value on facilities when the direction of travel is from facilities to incidents.

6.    Number of Facilities to Find (optional)

Default number of closest facilities to find per incident. The default can be overridden by specifying a value for the TargetFacilityCount property on the incidents.

7.    Time of Day (optional)

Specifies the time and date at which the routes should begin or end. The interpretation of this value depends on whether Time of Day Usage is set to be the start time or the end time of the route.

If you have chosen a traffic-based impedance attribute, the solution will be generated given dynamic traffic conditions at the time of day specified here. A date and time can be specified as 5/14/2012 10:30 AM.

Instead of using a particular date, a day of the week can be specified using the following dates:

1. Today—12/30/1899
2. Sunday—12/31/1899
3. Monday—1/1/1900
4. Tuesday—1/2/1900
5. Wednesday—1/3/1900
6. Thursday—1/4/1900
7. Friday—1/5/1900
8. Saturday—1/6/1900

For example, to specify that travel should begin at 5:00 p.m. on Tuesday, specify the parameter value as 1/2/1900 5:00 PM.

8.    Time of Day Usage (optional)

Indicates whether the value of the Time of Day parameter represents the arrival or departure time for the route or routes.

1. START_TIME—Time of Day is interpreted as the departure time from the facility or incident.When this setting is chosen, Time of Day indicates the solver should find the best route given a departure time.
2. END_TIME—Time of Day is interpreted as the arrival time at the facility or incident. This option is useful if you want to know what time to depart from a location so that you arrive at the destination at the time specified in Time of Day.
3. NOT_USED—When Time of Day doesn't have a value, this setting is the only choice. When Time of Day has a value, this setting isn't available.

9.    Accumulators (optional)

A list of cost attributes to be accumulated during analysis. These accumulation attributes are purely for reference; the solver only uses the cost attribute specified by the Impedance Attribute parameter to calculate the route.

For each cost attribute that is accumulated, a Total_[Impedance] property is added to the routes that are output by the solver.

10. Use Hierarchy in Analysis (optional)

• Checked—Use the hierarchy attribute for the analysis. Using a hierarchy results in the solver preferring higher-order edges to lower-order edges. Hierarchical solves are faster, and they can be used to simulate the preference of a driver who chooses to travel on freeways over local roads when possible—even if that means a longer trip. This option is enabled only if the input network dataset has a hierarchy attribute.
• Unchecked—Do not use the hierarchy attribute for the analysis. Not using a hierarchy yields an exact route for the network dataset.

The parameter is disabled if a hierarchy attribute is not defined on the network dataset used to perform the analysis.

11. Hierarchy Rank Settings (optional)

Prior to version 10, this parameter allowed you to change the hierarchy ranges for your analysis from the default hierarchy ranges established in the network dataset. At version 10, this parameter is no longer supported. If you want to change the hierarchy ranges for your analysis, update the default hierarchy ranges in the network dataset.

12. Output Path Shape (optional)

Specifies the shape type for the route features that are output by the analysis.

1. TRUE_LINES_WITH_MEASURES—The output routes will have the exact shape of the underlying network sources. Furthermore, the output includes route measurements for linear referencing. The measurements increase from the first stop and record the cumulative impedance to reach a given position.
2. TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.
3. STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.
4. NO_LINES—No shape will be generated for the output routes.

No matter which output shape type is chosen, the best route is always determined by the network impedance, never Euclidean distance. This means only the route shapes are different, not the underlying traversal of the network.

13. U-Turn Policy (optional)

The U-Turn policy at junctions. Allowing U-turns implies the solver can turn around at a junction and double back on the same street. Given that junctions represent street intersections and dead ends, different vehicles may be able to turn around at some junctions but not at others—it depends on whether the junction represents an intersection or dead end. To accommodate this, the U-turn policy parameter is implicitly specified by how many edges connect to the junction, which is known as junction valency. The acceptable values for this parameter are listed below; each is followed by a description of its meaning in terms of junction valency.

1. ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.
2. NO_UTURNS—U-turns are prohibited at all junctions, regardless of junction valency. Note, however, that U-turns are still permitted at network locations even when this setting is chosen; however, you can set the individual network location's CurbApproach property to prohibit U-turns there as well.
3. ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).
4. ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY—U-turns are prohibited at junctions where exactly two adjacent edges meet but are permitted at intersections (junctions with three or more adjacent edges) and dead ends (junctions with exactly one adjacent edge). Often, networks have extraneous junctions in the middle of road segments. This option prevents vehicles from making U-turns at these locations.

If you need a more precisely defined U-turn policy, consider adding a global turn delay evaluator to a network cost attribute, or adjusting its settings if one exists, and pay particular attention to the configuration of reverse turns. Also, look at setting the CurbApproach property of your network locations.

14. Restrictions (optional)

A list of restriction attributes to apply during the analysis.