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

Make OD Cost Matrix Layer Tool

أداة إنشاء طبقة مصفوفة التكلفة

ArcMap ArcGIS

How to use Make OD Cost Matrix Layer Tool in Arc Toolbox ArcMap ArcGIS??

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

Path to access the toolمسار الوصول الى الأداة

:

Make OD Cost Matrix Layer Tool, Analysis Toolset, Network Analyst Tools Toolbox

 

Make OD Cost Matrix Layer

Makes an origin–destination (OD) cost matrix network analysis layer and sets its analysis properties. An OD cost matrix analysis layer is useful for representing a matrix of costs going from a set of origin locations to a set of destination locations.

يقوم بإنشاء طبقة تحليل مصفوفة شبكة تكلفة أصل - وجهة (OD) وتعيين خصائص التحليل الخاصة بها. تعد طبقة تحليل مصفوفة تكلفة OD مفيدة لتمثيل مصفوفة التكاليف التي تنتقل من مجموعة من مواقع الأصل إلى مجموعة من المواقع الوجهة.

1.    Input Analysis Network أدخل تحليل الشبكة

The network dataset on which the OD cost matrix analysis will be performed.

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

Output Layer Name

Name of the OD cost matrix network analysis layer to create.

Impedance Attribute

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

Default Cutoff (optional)

Default impedance value at which to cut off searching for destinations for a given origin. If the accumulated impedance becomes higher than the cutoff value, the traversal stops. The default can be overridden by specifying the cutoff value on the origins.

Default Number of Destinations to Find (optional)

Default number of destinations to find for each origin. The default can be overridden by specifying a value for the TargetDestinationCount property on the origins.

Start Time (optional)

Indicates the departure time from origins.

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.

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)

·      NO_LINES—No shape will be generated for the output routes. This is useful when you have a large number of origins and destinations and are interested only in the OD cost matrix table (and not the output line shapes).

·      STRAIGHT_LINES—The output route shape will be a single straight line between each of the origin-destination pairs.

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 OD cost matrix network analysis layer to create.

اسم طبقة تحليل شبكة مصفوفة تكلفة OD المراد إنشاؤها.

Impedance Attribute

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

Default Cutoff (optional)

Default impedance value at which to cut off searching for destinations for a given origin. If the accumulated impedance becomes higher than the cutoff value, the traversal stops. The default can be overridden by specifying the cutoff value on the origins.

Default Number of Destinations to Find (optional)

Default number of destinations to find for each origin. The default can be overridden by specifying a value for the TargetDestinationCount property on the origins.

Start Time (optional)

Indicates the departure time from origins.

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.

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)

·      NO_LINES—No shape will be generated for the output routes. This is useful when you have a large number of origins and destinations and are interested only in the OD cost matrix table (and not the output line shapes).

·      STRAIGHT_LINES—The output route shape will be a single straight line between each of the origin-destination pairs.

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.

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

Default Cutoff (optional)

Default impedance value at which to cut off searching for destinations for a given origin. If the accumulated impedance becomes higher than the cutoff value, the traversal stops. The default can be overridden by specifying the cutoff value on the origins.

Default Number of Destinations to Find (optional)

Default number of destinations to find for each origin. The default can be overridden by specifying a value for the TargetDestinationCount property on the origins.

Start Time (optional)

Indicates the departure time from origins.

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.

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)

·      NO_LINES—No shape will be generated for the output routes. This is useful when you have a large number of origins and destinations and are interested only in the OD cost matrix table (and not the output line shapes).

·      STRAIGHT_LINES—The output route shape will be a single straight line between each of the origin-destination pairs.

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.    Default Cutoff (optional) القطع الافتراضي (اختياري)

Default impedance value at which to cut off searching for destinations for a given origin. If the accumulated impedance becomes higher than the cutoff value, the traversal stops. The default can be overridden by specifying the cutoff value on the origins.

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

Default Number of Destinations to Find (optional)

Default number of destinations to find for each origin. The default can be overridden by specifying a value for the TargetDestinationCount property on the origins.

Start Time (optional)

Indicates the departure time from origins.

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.

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)

·      NO_LINES—No shape will be generated for the output routes. This is useful when you have a large number of origins and destinations and are interested only in the OD cost matrix table (and not the output line shapes).

·      STRAIGHT_LINES—The output route shape will be a single straight line between each of the origin-destination pairs.

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 Number of Destinations to Find (optional) العدد الافتراضي لوجهات البحث (اختياري)

Default number of destinations to find for each origin. The default can be overridden by specifying a value for the TargetDestinationCount property on the origins.

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

Start Time (optional)

Indicates the departure time from origins.

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.

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)

·      NO_LINES—No shape will be generated for the output routes. This is useful when you have a large number of origins and destinations and are interested only in the OD cost matrix table (and not the output line shapes).

·      STRAIGHT_LINES—The output route shape will be a single straight line between each of the origin-destination pairs.

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.    Start Time (optional) وقت البدء (اختياري)

Indicates the departure time from origins.

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.

يشير إلى وقت المغادرة من الأصول.

إذا اخترت سمة المعاوقة المستندة إلى حركة المرور ، فسيتم إنشاء الحل وفقًا لظروف حركة المرور الديناميكية في الوقت المحدد هنا من اليوم. يمكن تحديد التاريخ والوقت كـ 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 مساءً.

 

Accumulators التراكم

Hierarchy تسلسل

Output Option خيارات الإخراج

Restrictions قيود

تم شرحهم في أداة سابقة لفهم هذه الفئات اضغط هنا للوصول الى أداة فيهم هذه الفئات مشروحة

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

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

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

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