nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding slope directions to an ITN network dataset.

Liam_

Hi,

I am currently attempting to test the feasibility of a navigation solution that can calculate the best route to a destination based on fuel economy variables. It is my intention to calculate an impedance value based on said variables. One of the variables I have selected is slope as a vehicle travelling uphill will use more fuel then one travelling downhill.

I have downloaded and imported into ArcMap 10.1 the Ordnance Survey ITN. However, I cannot seem to work out a way of getting slope direction from a raster underneath the roads and storing it in such a way that can be used for an impedance calculation.

I have a moderate amount of experience with ArcMap and some programming experience but I could really use the help of an expert!

Thank you,

Liam.

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

Melinda Morang

Hi Liam. You've got yourself a challenging problem!

Since you have elevation data, you can use the Interpolate Shape tool (http://resources.arcgis.com/en/help/main/10.1/index.html#//00q90000006m000000) to add z-elevation to the roads feature class in your network. You could then calculate an average or maximum slope for each line feature and use this, as well as the 3D length, to calculate a new new cost attribute in your network dataset. I'm not sure what advice to give you about how to construct your cost attribute. Consider that each road segment may have some uphill and some downhill parts, some steep parts and some not-so-steep parts. The average slope of the road feature might be zero even if it contains both a steep uphill part and a steep downhill part.

Additionally, please note that you will likely encounter problems anywhere in your road network where you have bridges or tunnels, since your elevation data probably only accounts for the elevation at ground level. If your data already had Z-levels for handling bridges and tunnels, you might be able to find a way to fudge the connectivity to make these work. You might have to manually fix each one.

Liam_

Hi mmorang,

Thanks for getting back to me, I will do as you suggested to extract the slope information I need. Here is my cost equation at present:

[/HR]
Example in pseudo code: -

If RoadSpeed = 30 Then
BaseLitresPerMetre = 0.01

[INDENT]
If RoadHasRoundaBout = True Then
BaseLitresPerMetre = BaseLitresPerMetre * 1.2
End If

If RoadHasLightControlledJunction = True Then
BaseLitresPerMetre = BaseLitresPerMetre * 1.4
End If

If RoadHasTrafficCalming = True Then
BaseLitresPerMetre = BaseLitresPerMetre * 0.8
End If

If RoadGoingUphill = True Then
BaseLitresPerMetre = BaseLitresPerMetre * 1.8
End If

If RoadGoingDownHill = True Then
BaseLitresPerMetre = BaseLitresPerMetre * 0.2
End If

[/INDENT]

End If

[Repeated for different road speed limits]

Cost = RoadLength * BaseLitresPerMetre

[/HR]
The trouble I have is getting the route planner to determine if the road is [RoadGoingDownHill = True] or [RoadGoingUpHill = True]. I'm also not sure of where in the Network Analyst Extension I can place the code above.

Melinda Morang

Hi Liam.

When setting up your network dataset, you will need to set up some cost (impedance) attributes that determine how the network calculates the cost of each edge in the network when solving routes or other analyses.
See http://resources.arcgis.com/en/help/main/10.1/index.html#/Understanding_network_attributes/00470000000m000000/.

These cost attributes are calculated using evaluators. You have many options (including code) for constructing an evaluator.
See http://resources.arcgis.com/en/help/main/10.1/index.html#//00470000000n000000 for more information.

For each attribute in your network, you can give it a different evaluator for the from-to direction and the to-from direction. In other words, the cost of the same network element can be different if it's being traversed in different directions. You will need to know the direction of digitization of your road to make sure you know which direction is which, but it should be easy enough for you to give each road a different cost if it's going uphill or downhill.

RobertBorchert

You could also incorporate some good old Physics here.

Unfortunately I am a number of years out of college but there are basic formulas for calculating how much engergy it takes to go a certain height on an incline. You can factor friction and resistance out as it would be the same up or down.

So if you have the slope your should be able to determine roughly how much energy is needed to get a given mass up a 3% slope to 100 feet. You will then have potential energy at the top to figure in as an energy savings going down the hill.

Hmm you do have variables on engine size, hp etc.

Please keep you findings posted here this sounds interesting and when you do knock it out of the park you will have a great basis for a paper for the user conference.

Liam_

Hi,

Thank you for your replies, both have been a great help!

Re: mmorang
It worked exactly as you explained, the OS ITN network is shipped with fields called Node1 and Node2 - it turned out that the Node1 field is the 'From' node and Node2 is the 'To' node.

I then calculated the slopes for each 'FromTo' and 'ToFrom' situation and calculated and added the appropriate cost modifier to each slope scenario. So a 10% slope "= [TheFuelCostofTheRoad] * 1.20" - representing a 20% increase in fuel costs.

Re: rborchert
Thanks for the idea using the laws of physics, as it has been many years since I studied physics I have calculated the extra costs of travelling up hills from literature.

I found in a paper that an average light duty vehicle travelling up a slope (x) consumed (y) L/Km. There was data from different slope percentages which allowed me to use a polynomial curve to model the cost increase profile. I was then able to use the said profile to estimate the added costs for an average light duty vehicle travelling up various slopes.

Screen Capture of what I described: -

What I am trying to do now is implement a cost matrix according to which road I have come from to what type of road I would like to join: -

Does anyone have any ideas of how I could implement that into the routing mechanism within Arc please?

Thanks again,

Liam.

Melinda Morang

Hi Liam. Unfortunately, the Network Analyst solvers don't have a way of assigning an added cost based on the previous edge traversed. When the solver calculates the cost on an edge or junction, it doesn't know what the previous edge or junction was. So you won't be able to do this automatically.

You could potentially use a turn feature class to add your costs, but you would have to set up the turns manually for each intersection where you want the added cost.

Can you describe more fully what you are trying to do? What's the goal of this part of your project? Maybe we can find a better way to do it so we can avoid this problem.

Liam_

Hi,

Thanks again for your reply, I am trying to make a work around for the fact that I cannot find any traffic light data for the south east of England.

Therefore, where there is a change in road type for example motorway -> minor road; it could be assumed that there would be traffic lights or a similar restriction which would add to the overall cost of the route as it is traversed.

What I might have to do is just add to the cost of the roads where there is roundabouts and leave out traffic lights (and similar road features).

I did have a look at the turn feature class tutorial earlier, but I discounted it as I have every road in the south east of England to model and to calculate the cost of each turn for over a million junctions would be just too greater task.

If there was just a way to include some form of global variable that I could write to, then I could check the value in the field evaluator as each road is calculated.

Thanks again,

Liam.

Melinda Morang

Actually, I think you can use Global Turns for this. Global Turns allow you to specify a different delay for turns between roads of different classes.
http://resources.arcgis.com/en/help/main/10.1/index.html#//004700000030000000

Liam_

Hi,

Thanks for the tip. I've just taken a look at the documentation and although it will add time, my impedance cost values aren't time based. Would there be a way of converting the time added into a percentage increase?

It would be ideal if I could assign say a 30 second delay at certain junctions and then change them to:-

[LitersOfFuelNeededForRoad] = [LitersOfFuelNeededForRoad] * ( ( [TurnDelaySeconds] / 100 ) + 1 )

For example: -

[100] = [100] * ( ( [30] / 100 ) + 1)
[100] = [100] * ( 0.3 ) + 1
[100] = [100] * 1.3
[100] = [130]

Thanks,

Liam.

Melinda Morang

Okay, I think I've got it figured out.

You want to create your own global turn script evaluator that will add a certain number of liters of fuel needed for each type of transition between road types (turn). So, the fuel usage on the edges will stay the same as you have them now, but each transition between edges can add some value, based on the way you want to calculate it.

First, when you create your network dataset, make sure you click the button that tells it you want to model global turns.

Next, set up the global turn evaluator, as follows:
- In the network dataset properties window, go to the Attributes tab.
- For your fuel usage attribute, click Evaluators.
- After the evaluators window pops up, go to the Default Values tab.
- In the Type column next to Turn, click to get a drop-down menu where you can select "Script".
- Click the Evaluator Properties button on the right (looks like a finger pointing at a piece of paper). A dialog will appear where you can write a simple Python or VBScript that says how the solvers should calculate the fuel usage for turns in your network. You should be able to use some if statements to give it a different value based on the road types of the fromEdge and toEdge.

Liam_

Hi,

Thank you again for all your help, here is the code I have used in the script evaluator: -

* SpeedCostTotalRoad is the total cost to transverse the road in litres and is calculated from literature values for average vehicles
* Economy is the name of my route network's cost evaluator.

dim result

If fromEdge.OID.Roadlinks.RoadDesc = "Minor Road" and toEdge.OID.Roadlinks.Nature = "Roundabout" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.20 )

ElseIf fromEdge.OID.Roadlinks.RoadDesc = "Local Street" and toEdge.OID.Roadlinks.Nature = "Roundabout" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.20 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "B Road" and toEdge.OID.Roadlinks.Nature = "Roundabout" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.20 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "A Road" and toEdge.OID.Roadlinks.Nature = "Roundabout" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.20 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "Motorway" and toEdge.OID.Roadlinks.Nature = "Roundabout" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.20 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "A Road" and toEdge.OID.Roadlinks.RoadDesc = "Minor Road" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.50 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "A Road" and toEdge.OID.Roadlinks.RoadDesc = "Local Street" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.50 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "A Road" and toEdge.OID.Roadlinks.RoadDesc = "B Road" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.50 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "Motorway" and toEdge.OID.Roadlinks.RoadDesc = "Minor Road" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.50 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "Motorway" and toEdge.OID.Roadlinks.RoadDesc = "Local Street" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.50 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "Motorway" and toEdge.OID.Roadlinks.RoadDesc = "B Road" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.50 )


ElseIf fromEdge.OID.Roadlinks.RoadDesc = "Motorway" and toEdge.OID.Roadlinks.RoadDesc = "A Road" then
result = "Economy" + ( fromEdge.OID.Roadlinks.SpeedCostTotalRoad * 0.50 )
END IF

I have rebuilt the network, but it's not quite working as it should

I get the errors:

Error: The evaluator failed to return a value. [Attribute: Economy, Default Turns, OID = -1, EID = -1]
Error: Network element evaluator error. [Script Control Error -2147352319]

I have looked online, but I cannot find any guides on the use of the fromEdge.OID. variable. Have I missed something out?

Thanks again,

Liam.

Melinda Morang

Hi Liam. I'm afraid I was incorrect in my earlier post. You can't actually use the default turn script evaluator effectively unless you have actual turn features drawn into your network. If you are going to use this method, you will have to manually create all the turn features. As you mentioned before, this would undoubtedly be quite laborious.

As for why your code isn't working, it's a syntax problem. In your if statements, you would need to use something like this:
fromEdge.AttributeValueByName( "RoadClass" )
Also, you won't be able to just call "Economy" by itself. That value is meaningless unless associated with a particular edge element. As I mentioned before, you can't update the cost of the edge element itself based on the next edge in the route because the route doesn't know what the next edge is going to be. The reason I suggested the turns is that turns are the only cost-associated element that has information about the edge elements it's connected to.

So, unfortunately, this doesn't leave you with a lot of good options. If you know ArcObjects, you could build your own custom evaluator, but this is not an easy process. And, again, you can't use a custom evaluator to determine the cost of an edge based on the next edge in the route because the solver itself does not know what the next edge is going to be.

I'm really sorry I don't have a better answer for you.

Melinda Morang

Ack, sorry, I did some more experiments, and I now see that, in fact, you CAN do what I was suggesting. You don't have to have a turn feature class with every turn digitized in to use a custom script evaluator for global turns. It WILL work the way I originally suggested. I think if you just fix your syntax, you should be good to go.

In the mean time, I'll see what I can do about us getting some better documentation for this subject. If I work here and can't figure it out, we clearly didn't do a very good job.

Liam_

Hi,

Thank you again for your reply. As my project deadline is approaching fast, I have had to abandon my junction cost matrix and instead I have just added a +20% cost to routes that transverse a roundabout. At this stage, the project outcome is just a measure of the feasibility of using economy routing in vehicle satellite navigation systems (although I could list many other applications!).

This would not have been an issue if there was freely available point data for the locations of traffic controlled signals for the United Kingdom. Having said that, should I have some time at the end of my project, I shall return to the problem and attempt to refine the analysis following your latest advice.

Thank you again for all your help, I will post my solution here should I get it working for the benefits of others attempting similar tasks.

Thanks again,

Liam.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.