Latest Contributions by PatrickStevens

‎05-23-2018

Without going off and trying it myself, your steps sound correct. Add the street, add an entry in the TMC tables, rebuild. Perhaps a full rebuild is required, instead of an incremental rebuild. Try to trick the build engine into thinking the whole network needs a rebuild, then do a build. Like this: Add an attribute, called whatever you want. Click apply. Delete the attribute you just added. Click apply. Build the network. Then see if the new segment works with your live traffic. I think there might be a problem in the network dataset where updates to the traffic tables don't trigger a full rebuild. Let me know if the above steps work for you.

‎05-14-2018

It looks like your question was edited after I had received it, so I might not have answered your new question. For that one: Is there a list of country or region codes documented somewhere? The 106 you see for San Diego is the country and region code that HERE (the data provider of our tutorial data) uses in their traffic feeds for the San Diego area. But a different traffic feed provider for San Diego might not use 106. Contact your traffic feed provider for the list of countries and regions that they use.

‎05-14-2018

I asked around a bit and I think the TMC information is available from data documentation provided by traffic data providers, which has to be requested from the data providers (like Here or TomTom). So, unfortunately, that kind of documentation isn't available for the tutorial data. Sorry!

‎02-14-2018

If I understand correctly, you would like to discourage turns where possible. I don't think what you are proposing would work with the script evaluator. I think some functionality that might do what you want is the Global Turn Delay Evaluator. The purpose of that evaluator is to discourage turns by applying a cost penalty that makes turning more expensive. That might be your answer. To take a step back, though, why do you want to discourage turns? Is the vehicle that is travelling too big to make many turns? If that is the case, the Global Turn Delay Evaluator seems correct. Or are you getting routes that leave major roads and stair-steps through communities? In this case, the best answer is probably to adjust the travel times along the roads that you prefer.

‎02-14-2018

The network element script evaluators are based on the ArcObjects API. To explain some of the sections of the dialog in your screenshot: Element Variables: These are the objects that you can reference in the code block. For evaluating edges, the only valid element variable is the Edge element itself. In your screenshot, you see Turn, fromEdge, toEdge, and atJunction. These are all network elements associated with a Turn. Types: This changes the available functions in the Element Functions section. For example, select Turn and you get the Angle function. Select Junction and you get the TurnCount function. Element Functions: These are the methods available to work on the chosen element type object. These should correspond to the methods on INetworkEdge2, INetworkTurn2, and INetworkJunction2. I hope this was helpful.

‎11-10-2017

Hmmm... I'll install 10.4 and give that a shot. When you compile does a popup appear that says "Registration Succeeded"? Can you email me a zip of your code and your TrafficProviders.xml? pstevens@esri.com

‎11-07-2017

It all appears to be working for me. I went through the steps and when I opened up ArcMap and the traffic data tool, Custom Provider showed up. Glancing at your screen shots, it looks like the GUID for the provider is different than mine. The one I used was: {929DFEE5-11DC-4BC9-B66F-B493A4470451} You get that GUID from the top of the TrafficProvider.cs file. Make sure your provider GUID matches the one in the code. I hope that fixes it!

‎11-07-2017

I'll download and retry setting up the custom feed. What version of ArcMap are you using? And what version of Visual Studio? Are you using just the code as-is along with the sample data as-is? Or did you make any change or use your own data? Thanks

‎11-06-2017

Hello! The DLL is automatically registered when the sample is compiled. You can see how it works if you open the file CutomTrafficProvider.csproj in Notepad++ or some other text editor. Scroll down to the bottom of the file and there are "BeforeClean"and "AfterBuild" sections telling the project to unregister before building and register after. If you think it might not be working, try to register the DLL manually just to make sure it can. For ArcMap, it would be something like this: c:\ProgramFiles (x86)\Common Files\ArcGIS\bin>esriRegAsm.exe <Path to your DLL> /p:Desktop

‎10-15-2015

Hello! I think the problem might be the value you are trying to set. Instead of using the text "Right side of vehicle", try using the integer enumeration value associated with that text. 0 = Either side of vehicle 1 = Right side of vehicle 2 = Left side of vehicle 3 = No u-turn

‎08-18-2015

Hello! I'm happy to try and help. Your questions are a bit vague, so perhaps we can start by getting some specifics. What exactly are your trying to do? Is your goal to apply real-time traffic to a network dataset? If so: Is this your own network data or data you purchased? What format is the network data in? Are you purchasing real-time traffic or is this from an internal organization? If purchasing, who are you purchasing it from? Or are you trying to set up your own historical traffic? What platform are your working on? Windows, linux? What software are you working with? Server, Desktop, Runtime, ArcObjects, Pro? What version of the software are you working with? 10.0? 10.3.1? Any other details you have would be great to hear.

‎08-13-2015

One additional quick note, based on what you wrote: "I know one of the options is to input a Line barrier like the 49th parallel across or a poly barrier, but it would be simpler to just filter on an attribute already in the HERE dataset" If you have edit access to the network dataset, then you could add a restriction attribute and use that to stop traversal into the US. But, if you cannot edit the data itself, then you will have to use a line restriction, or some similar solution that affects the analysis layer and not the network itself. The definition query, if you are discussing what I think you are, will only affect where the facilities locate along the network. Once the facilities have been located, there is no place to add a query that will restrict travel along the streets.

‎08-13-2015

I'm not sure it is possible to restrict the US streets from a service area solve where the locations are in Canada, unless you have a copy of the data that excludes the US. One possible solution would be to add a polyline restriction barrier along the US/Canada border in your analysis. If the facility locations are all in Canada, then the service area will not be able to traverse into the United States.

‎07-31-2015

Sure, I'd be happy to send it along. Unfortunately, I can't figure out how to post a zip or 7z here to the forums. Could you email me and I'll send it? As a 7z, it is only 22 KB. My email is pstevens at esri.com. I tried to use GeoNet's upload file option, but it gives me the less-than-helpful message, "You are not allowed to create or update this content".

‎07-31-2015

Hi, Thomas! I've been discussing this issue with colleagues. We came up with a solution we think might work. 1. Make all of the junctions you want to ALLOW u-turns as user-defined junctions. You can select that set of system junctions, export it as a feature class in the same feature dataset as your network, then add it as a source to your network. 2. Add a descriptor attribute to your network called something like uturn_restricted_at_junction. a. Set the descriptor to boolean b. Set the default junction evaluator value to a constant of true c. Set the source junction evaluator value for your user junctions to a constant of false 3. Make a restriction attribute on your network called something like restricted_uturns a. Set the type to boolean b. On the default evaluator for turns, set it to script and add this python script: In the pre-logic script code, put: def SetValue(): is_restricted = False if fromEdge.EID == toEdge.EID: is_restricted = atJunction.AttributeValueByName( "uturn_restricted_at_junction" ) return is_restricted if the value = part, put: SetValue() 4. Make sure you already have a turn feature class in your network. For my toy network, I added an empty one. Seems like a turn source is required to get this to work, even if there is nothing in the source feature class. Then, test that it works! I tried this on a toy network and it worked. Uturns at my user junctions were allowed and uturns at my system junctions were not allowed. You can test it by adding a stop near a test junction on the right side on the edge. Set the curbapproach for the stop to right. Then, add a second stop farther away from the test junction, so that the route has to leave stop1 towards the junction and the quickest route would be a uturn at the test junction back to stop2. I hope all of this makes sense. Good luck!

Online Status	Offline
Date Last Visited	‎10-19-2021 04:18 PM

My Ideas

Latest Contributions by PatrickStevens

Re: Where to Subscribe to Live Traffic Data and Adding Another Provider

Re: Where to Subscribe to Live Traffic Data and Adding Another Provider

Re: Where to Subscribe to Live Traffic Data and Adding Another Provider

Re: Script evaluators element variables

Re: Script evaluators element variables

Re: Converting Historic\Live Traffic Data into ESRI format (DTF?)

Re: Converting Historic\Live Traffic Data into ESRI format (DTF?)

Re: Converting Historic\Live Traffic Data into ESRI format (DTF?)

Re: Converting Historic\Live Traffic Data into ESRI format (DTF?)

Re: Problem with curbapproach

Re: DTF

Re: Service Area limited by Country using HERE NA Streetmap Premium?

Re: Service Area limited by Country using HERE NA Streetmap Premium?

Re: U-turn policy question

Re: U-turn policy question

Re: Getting properties from a custom evaluator

Re: U-turn policy question

Re: Rebuilding Network Dataset

Re: Script evaluators element variables

Re: Script evaluators element variables