موقع GIS for WE نظم المعلومات الجغرافية (GIS) وبرامج ArcGIS

Make Closest Facility Layer Tool

أداة إنشاء طبقة لأقرب الخدمات

ArcMap ArcGIS

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

كيفية استخدام أداة إنشاء طبقة لأقرب الخدمات ؟؟

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.

مجموعة بيانات الشبكة التي سيتم إجراء تحليل أقرب مرفق عليها.

Output Layer Name

Name of the closest facility network analysis layer to create.

Impedance Attribute

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

Travel From or To Facility (optional)

Specifies the direction of travel between facilities and incidents.

·      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).

·      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.

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.

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.

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:

·      Today—12/30/1899

·      Sunday—12/31/1899

·      Monday—1/1/1900

·      Tuesday—1/2/1900

·      Wednesday—1/3/1900

·      Thursday—1/4/1900

·      Friday—1/5/1900

·      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.

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.

·      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.

·      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.

·      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.

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.

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.

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.

Output Path Shape (optional)

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

·      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.

·      TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

·      STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

·      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.

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.

·      ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

·      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.

·      ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

·      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.

Restrictions (optional)

A list of restriction attributes to apply during the analysis.

2.    Output Layer Name اسم طبقة الإخراج

Name of the closest facility network analysis layer to create.

اسم أقرب طبقة تحليل شبكة منشأة يتم إنشاؤها.

Impedance Attribute

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

Travel From or To Facility (optional)

Specifies the direction of travel between facilities and incidents.

·      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).

·      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.

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.

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.

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:

·      Today—12/30/1899

·      Sunday—12/31/1899

·      Monday—1/1/1900

·      Tuesday—1/2/1900

·      Wednesday—1/3/1900

·      Thursday—1/4/1900

·      Friday—1/5/1900

·      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.

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.

·      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.

·      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.

·      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.

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.

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.

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.

Output Path Shape (optional)

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

·      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.

·      TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

·      STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

·      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.

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.

·      ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

·      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.

·      ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

·      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.

Restrictions (optional)

A list of restriction attributes to apply during the analysis.

3.    Impedance Attribute جدول المعاوقة

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

جدول التكلفة التي سيتم استخدامها كمعاوقة في التحليل.

Travel From or To Facility (optional)

Specifies the direction of travel between facilities and incidents.

·      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).

·      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.

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.

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.

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:

·      Today—12/30/1899

·      Sunday—12/31/1899

·      Monday—1/1/1900

·      Tuesday—1/2/1900

·      Wednesday—1/3/1900

·      Thursday—1/4/1900

·      Friday—1/5/1900

·      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.

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.

·      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.

·      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.

·      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.

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.

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.

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.

Output Path Shape (optional)

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

·      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.

·      TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

·      STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

·      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.

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.

·      ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

·      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.

·      ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

·      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.

Restrictions (optional)

A list of restriction attributes to apply during the analysis.

4.    Travel from or To Facility (optional) السفر من أو إلى مرفق (اختياري)

Specifies the direction of travel between facilities and incidents.

يحدد اتجاه السفر بين المرافق والحوادث.

• TRAVEL_FROM - اتجاه السفر من المرافق إلى الحوادث. تستخدم إدارات الإطفاء عادةً هذا الإعداد ، نظرًا لأنها معنية بالوقت المستغرق للانتقال من محطة الإطفاء (المنشأة) إلى موقع الطوارئ (الحادث).

• TRAVEL_TO — اتجاه السفر من الحوادث إلى المرافق. عادةً ما تستخدم متاجر البيع بالتجزئة هذا الإعداد ، نظرًا لأنها معنية بالوقت الذي يستغرقه المتسوقون (الحوادث) للوصول إلى المتجر (المنشأة).

باستخدام هذا الخيار ، يمكن العثور على منشآت مختلفة على شبكة ذات قيود أحادية الاتجاه وممانعات مختلفة بناءً على اتجاه السفر. على سبيل المثال ، قد تكون المنشأة على بعد 10 دقائق بالسيارة من الحادث أثناء السفر من الحادث إلى المنشأة ، ولكن أثناء السفر من المنشأة إلى الواقعة ، قد تستغرق الرحلة 15 دقيقة بسبب اختلاف وقت السفر في هذا الاتجاه .

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.

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.

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:

·      Today—12/30/1899

·      Sunday—12/31/1899

·      Monday—1/1/1900

·      Tuesday—1/2/1900

·      Wednesday—1/3/1900

·      Thursday—1/4/1900

·      Friday—1/5/1900

·      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.

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.

·      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.

·      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.

·      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.

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.

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.

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.

Output Path Shape (optional)

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

·      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.

·      TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

·      STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

·      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.

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.

·      ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

·      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.

·      ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

·      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.

Restrictions (optional)

A list of restriction attributes to apply during the analysis.

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.

قيمة المعاوقة الافتراضية التي عندها تتوقف عن البحث عن مرافق لحادث معين. يمكن تجاوز هذا التقصير من خلال تحديد قيمة القطع للحوادث عندما يكون اتجاه السفر من الحوادث إلى المرافق أو عن طريق تحديد قيمة القطع في المرافق عندما يكون اتجاه السفر من المنشآت إلى الحوادث.

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.

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:

·      Today—12/30/1899

·      Sunday—12/31/1899

·      Monday—1/1/1900

·      Tuesday—1/2/1900

·      Wednesday—1/3/1900

·      Thursday—1/4/1900

·      Friday—1/5/1900

·      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.

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.

·      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.

·      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.

·      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.

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.

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.

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.

Output Path Shape (optional)

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

·      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.

·      TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

·      STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

·      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.

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.

·      ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

·      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.

·      ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

·      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.

Restrictions (optional)

A list of restriction attributes to apply during the analysis.

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.

العدد الافتراضي للمرافق الأقرب للبحث عن كل حادث. يمكن تجاوز القيمة الافتراضية عن طريق تحديد قيمة للخاصية TargetFacilityCount على الحوادث.

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:

·      Today—12/30/1899

·      Sunday—12/31/1899

·      Monday—1/1/1900

·      Tuesday—1/2/1900

·      Wednesday—1/3/1900

·      Thursday—1/4/1900

·      Friday—1/5/1900

·      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.

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.

·      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.

·      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.

·      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.

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.

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.

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.

Output Path Shape (optional)

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

·      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.

·      TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

·      STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

·      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.

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.

·      ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

·      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.

·      ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

·      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.

Restrictions (optional)

A list of restriction attributes to apply during the analysis.

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.

يحدد الوقت والتاريخ اللذين يجب أن تبدأ فيهما المسارات أو تنتهي عندهما. يعتمد تفسير هذه القيمة على ما إذا كان وقت استخدام اليوم قد تم تعيينه ليكون وقت البدء أو وقت الانتهاء للمسار.

إذا اخترت سمة المعاوقة المستندة إلى حركة المرور ، فسيتم إنشاء الحل وفقًا لظروف حركة المرور الديناميكية في الوقت المحدد هنا من اليوم. يمكن تحديد التاريخ والوقت كـ 14/5/2012 10:30 صباحًا.

بدلاً من استخدام تاريخ معين ، يمكن تحديد يوم من أيام الأسبوع باستخدام التواريخ التالية:

• اليوم - 12/30/1899

• الأحد - 12/31/1899

• الاثنين - 1/1/1900

• الثلاثاء - 1/2/1900

• الأربعاء - 1/3/1900

• الخميس - 1/4/1900

• الجمعة - 1/5/1900

• السبت - 1/6/1900

على سبيل المثال ، لتحديد أن السفر يجب أن يبدأ في الساعة 5:00 مساءً. في يوم الثلاثاء ، حدد قيمة المعلمة كـ 1/2/1900 5:00 مساءً.

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.

على سبيل المثال ، لتحديد أن السفر يجب أن يبدأ في الساعة 5:00 مساءً. في يوم الثلاثاء ، حدد قيمة المعلمة كـ 1/2/1900 5:00 مساءً. وقت استخدام اليوم (اختياري)

يشير إلى ما إذا كانت قيمة معلمة الوقت في اليوم تمثل وقت الوصول أو المغادرة للمسار أو المسارات.

• START_TIME - يتم تفسير الوقت من اليوم على أنه وقت المغادرة من المنشأة أو الحادث. عند اختيار هذا الإعداد ، يشير الوقت من اليوم إلى أن المحلل يجب أن يجد أفضل طريق في وقت المغادرة.

• END_TIME - يتم تفسير "الوقت من اليوم" على أنه وقت الوصول إلى المنشأة أو الحادث. يكون هذا الخيار مفيدًا إذا كنت تريد معرفة وقت المغادرة من أحد المواقع بحيث تصل إلى الوجهة في الوقت المحدد في "الوقت من اليوم".

• NOT_USED - عندما لا يكون للوقت من اليوم قيمة ، فإن هذا الإعداد هو الخيار الوحيد. عندما يكون للوقت من اليوم قيمة ، فإن هذا الإعداد غير متاح.

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.

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.

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.

Output Path Shape (optional)

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

·      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.

·      TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

·      STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

·      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.

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.

·      ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

·      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.

·      ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

·      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.

Restrictions (optional)

A list of restriction attributes to apply during the analysis.

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.

قائمة جدول التكلفة التي سيتم تجميعها أثناء التحليل. سمات التراكم هذه للإشارة فقط ؛ يستخدم حلال فقط جدول التكلفة المحددة بواسطة معلمة جدول المعاوقة لحساب المسار.

لكل جدول تكلفة يتم تجميعها ، تتم إضافة خاصية Total_ [معاوقة] إلى المسارات التي يتم إخراجها بواسطة المحلل.

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.

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.

Output Path Shape (optional)

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

· 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.

· TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

· STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

· 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.

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.

· ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

· 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.

· ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

· 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.

Restrictions (optional)

A list of restriction attributes to apply during the analysis.

10. Use Hierarchy in Analysis (optional) استخدام التسلسل الهرمي في التحليل (اختياري)

• تم التحديد - استخدم سمة التدرج الهرمي للتحليل. يؤدي استخدام التسلسل الهرمي إلى تفضيل الحلول للحواف ذات الترتيب الأعلى على الحواف ذات الترتيب الأدنى. تكون الحلول الهرمية أسرع ، ويمكن استخدامها لمحاكاة تفضيل السائق الذي يختار السفر على الطرق السريعة عبر الطرق المحلية عندما يكون ذلك ممكنًا - حتى لو كان ذلك يعني رحلة أطول. يتم تمكين هذا الخيار فقط إذا كانت مجموعة بيانات شبكة الإدخال تحتوي على سمة التدرج الهرمي.

• غير محدد - لا تستخدم سمة التدرج الهرمي للتحليل. ينتج عن عدم استخدام التسلسل الهرمي مسارًا دقيقًا لمجموعة بيانات الشبكة.

يتم تعطيل المعلمة إذا لم يتم تحديد سمة التدرج الهرمي في مجموعة بيانات الشبكة المستخدمة لإجراء التحليل.

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.

Output Path Shape (optional)

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

· 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.

· TRUE_LINES_WITHOUT_MEASURES—The output routes will have the exact shape of the underlying network sources.

· STRAIGHT_LINES—The output route shape will be a single straight line between each paired incident and facility.

· 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.

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.

· ALLOW_UTURNS—U-turns are permitted at junctions with any number of connected edges. This is the default value.

· 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.

· ALLOW_DEAD_ENDS_ONLY—U-turns are prohibited at all junctions, except those that have only one adjacent edge (a dead end).

· 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.

Restrictions (optional)

A list of restriction attributes to apply during 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.

قبل الإصدار 10 ، سمحت لك هذه المعلمة بتغيير نطاقات التسلسل الهرمي لتحليلك من نطاقات التسلسل الهرمي الافتراضية المحددة في مجموعة بيانات الشبكة. في الإصدار 10 ، لم تعد هذه المعلمة مدعومة. إذا كنت تريد تغيير نطاقات التدرج الهرمي لتحليلك ، فقم بتحديث نطاقات التدرج الهرمي الافتراضي في مجموعة بيانات الشبكة.

12. Output Path Shape (optional) شكل مسار الإخراج (اختياري)

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

يحدد نوع الشكل لمعالم المسار التي يتم إخراجها بواسطة التحليل.

• TRUE_LINES_WITH_MEASURES - سيكون لمسارات الإخراج الشكل الدقيق لمصادر الشبكة الأساسية. علاوة على ذلك ، يتضمن الإخراج قياسات المسار للإشارة الخطية. تزداد القياسات من المحطة الأولى وتسجيل الممانعة التراكمية للوصول إلى موضع معين.

• TRUE_LINES_WITHOUT_MEASURES - سيكون لمسارات الإخراج الشكل الدقيق لمصادر الشبكة الأساسية.

• STRAIGHT_LINES - سيكون شكل مسار الإخراج عبارة عن خط مستقيم واحد بين كل حادث مزدوج ومنشأة.

• NO_LINES - لن يتم إنشاء أي شكل لمسارات الإخراج.

بغض النظر عن نوع شكل الإخراج الذي يتم اختياره ، يتم دائمًا تحديد أفضل مسار بواسطة مقاومة الشبكة ، وليس المسافة الإقليدية أبدًا. هذا يعني أن أشكال المسار فقط مختلفة ، وليس الاجتياز الأساسي للشبكة.

13. U-Turn Policy (optional) السياسة (اختياري)

سياسة U-Turn عند التقاطعات. يعني السماح بالدوران على شكل حرف U أنه يمكن للحل أن يستدير عند تقاطع طرق ويتضاعف مرة أخرى في نفس الشارع. نظرًا لأن التقاطعات تمثل تقاطعات الشوارع والطرق المسدودة ، فقد تتمكن المركبات المختلفة من الالتفاف عند بعض التقاطعات ولكن ليس عند البعض الآخر - يعتمد ذلك على ما إذا كان التقاطع يمثل تقاطعًا أو طريقًا مسدودًا.

لاستيعاب ذلك ، يتم تحديد معلمة نهج U-turn ضمنيًا من خلال عدد الحواف المتصلة بالوصلة ، والتي تُعرف باسم تكافؤ الوصلة. القيم المقبولة لهذه المعلمة مذكورة أدناه ؛ يتبع كل منها وصف لمعناها من حيث تكافؤ الوصلات.

• ALLOW_UTURNS - يُسمح بالدوران على شكل حرف U عند التقاطعات مع أي عدد من الحواف المتصلة. هذه هي القيمة الافتراضية.

• NO_UTURNS - يحظر الدوران U في جميع التقاطعات ، بغض النظر عن تكافؤ الوصلات. لاحظ ، مع ذلك ، أن المنعطفات U لا يزال مسموحًا بها في مواقع الشبكة حتى عند اختيار هذا الإعداد ؛ ومع ذلك ، يمكنك تعيين خاصية CurbApproach الخاصة بموقع الشبكة الفردي لمنع انعطاف U هناك أيضًا.

• ALLOW_DEAD_ENDS_ONLY - يحظر الدوران للخلف في جميع التقاطعات ، باستثناء تلك التي لها حافة مجاورة واحدة (طريق مسدود).

• ALLOW_DEAD_ENDS_AND_INTERSECTIONS_ONLY - يُحظر استخدام المنعطفات على شكل حرف U عند التقاطعات حيث تلتقي حافتان متجاورتان تمامًا ولكن يُسمح بها عند التقاطعات (التقاطعات ذات ثلاثة حواف متجاورة أو أكثر) والنهايات المسدودة (التقاطعات ذات حافة متجاورة واحدة بالضبط). غالبًا ما تحتوي الشبكات على تقاطعات خارجية في منتصف أجزاء الطريق. يمنع هذا الخيار المركبات من الدوران للخلف في هذه المواقع.

إذا كنت بحاجة إلى سياسة U-turn محددة بشكل أكثر دقة ، ففكر في إضافة مقيِّم لتأخير الانعطاف العالمي إلى سمة تكلفة الشبكة ، أو تعديل إعداداتها إن وجدت ، وإيلاء اهتمام خاص لتكوين المنعطفات العكسية. انظر أيضًا إلى إعداد خاصية CurbApproach لمواقع الشبكة الخاصة بك.

14. Restrictions (optional) قيود (اختياري)

A list of restriction attributes to apply during the analysis.Restrictions (optional) A list of restriction attributes to apply during the analysis.

قائمة جدول التقييد المطلوب تطبيقها أثناء التحليل.

 اليك صفحه ومجموعة على الفيس بوك لتعلم أكثر بما يخص نظم المعلومات الجغرافية (GIS) و برنامج ArcGIS Pro من خلال هذه الروابط:

مجموعة على الفيس بوك ArcGIS Pro من هنا.

مجموعة على الفيس بوك GIS for WE - ArcGIS Pro من هنا.

صفحة الفيس بوك GIS for WE من هنا.