Latest Contributions by PatrickStevens

I assumed that the script evaluators would have access to time.  It doesn't look like that is case.  I see AttributeValueByName is available, but AttributeValueAtTime is not.  I'll go back and edit that post, so no one gets misled.  Thanks for catching that! Very interesting use-case. It seems like the custom evaluator could handle it, especially if you cache the 14000 restrictions in memory during Initialize, and also during Refresh when you notice that an update has occurred.  Melinda Morang's GTFS evaluator does similar work and can handle much more than 14k in-memory restriction times.  But if that doesn't work, rebuilding the network would be inconvenient but not impossible.  150-200 rebuilds a week on a regional network (as-in, not a nation full of streets), seems doable. As to your request to check out another post on the forum, I'm not sure how to set up directions to work for you, so I sent a note to a co-worker who might be able to better answer your question.  Hope you get your answer soon. ... View more

Since there are no time-aware barriers, perhaps there are a few work-arounds, as you suggest.  You sound like you know what you are doing, but I'll try to give a few suggestions in hopes one triggers a good idea for you. First off, what do your barriers represent?  What is your use-case?  Why do they change so often? The custom evaluator The benefit of the custom evaluator should be that you don't have to rebuild your network in order to update the times on the barriers.  You can use Initialize or Refresh (depending on your usage) to check if the barriers files have been updated, and cache the updated restricted locations. See the transit evaluator for a good example on caching pre-solve.  You can contact Melinda Morang for a copy of the code, I think. Like you mentioned, though, 14,000 locations is quite a few and solve will take a performance hit. Barriers Maybe there is a good way to set this up using barriers.  Are the barriers truly time-dependent, as in, a given network element will be open until 8am, then closed from 8 am until 10am, then reopened after 10?   That will be difficult to truly support with only using barriers.  But you should be able to toggle barriers on/off for a given solve and approximate it. Maybe you could have a feature class of barriers with time ranges for the barriers.  Be sure to use the calculate locations tool on it to make loading into a new analysis layer fast.  For a give solve request, with a specific start time, you could load locations on the barriers class using a query to make sure you only include those barriers that apply for the start time. Restrictions You could have sets of restrictions appropriate for certain times of day, that you can turn on and off.  But, as you mentioned, you would have to rebuild your network each time. I had thought that you could use a script evaluator (python or vb script), and have the evaluator do some extra work to figure out if a given element is restricted or not, based on the time it is traversed. But it appears that script evaluators do not have access to AttributeValueAtTime.  Also, script evaluators can be slow, and they depend on information built into the network. By the way, this is very interesting!  I love seeing this kind of creative usage of the software. ... View more

Hi, Mody!  Can it be translated to Java?  Yes.  How do you do the registration?  Good question!  I have not registered a Java custom evaluator before.  It should be possible, but I'm not sure how. Hopefully, someone with more experience in Java and ArcObjects can answer for you. I found an entry about how the RegTool had been deprecated and as of 10.0 it is recommended to put jars into well known locations.  But I don't know if that will work. ... View more

Time-aware barriers and restrictions are not yet supported "out-of-the-box" for network analyst. However, you can craft a custom evaluator to your own uses to support something similar.  Here is the time-aware restriction evaluator: http://www.arcgis.com/home/item.html?id=dc2e55c6e9c64cb19a5e8e3224032c87 That evaluator uses a CSV local to the network to apply a time window to restrict or allow traversal across network elements. The campus data model also uses a version of this evaluator. ... View more

Hello! Historical traffic can be pretty tough to set up correctly.  It was originally designed to work with vendor data, so getting it working on you own data can be tricky.  Is your ultimate goal custom live traffic?  Or is historical your final step?  Where does your historical data come from? As for setting historical up, here is a list of things that you need to consider: Make sure there is a time zone attribute in your network. Don't have any entries in your historical tables that don't exist as streets in your streets source feature class. In the Streets_Profiles table, make sure there are not duplicates (where one street is listed with the same from and to position twice). Make sure your tables have the same field names, field types, and field lengths as the sample data (for the most part).  Did you start your work from sample data, like San Diego?  Here is a link to it:           http://www.arcgis.com/home/item.html?id=d6bd91b2fddc483b8ccbc66942db84cb Those are just a start.  If we don't find it there, we'll keep trying. ... View more

Very interesting!  Is there a chance I could get a copy of your evaluator to try out here?  You could put it on GitHub, or email it to me pstevens at esri.com. When I try with the Departure Time Evaluator, as long as I have write access to the network dataset, the properties persist fine. Perhaps you could try the Departure Time Evaluator sample to see if it behaves the same way as your evaluator.  If you do that, be sure to unregister your evaluator, because they might be using the same GUID. ... View more

I was able to reproduce the problem on my end using the DepartureTimeEvaluator!  Conclusion      Make sure that you have editing permission on your network.  You should see the APPLY button become enabled on the Network Dataset Properties dialog after you have editing the properties.  If Apply is disabled (note that the "Add.." button will probably be disabled as well), then the properties won't persist. Gritty Details      The secret is the "APPLY" button that you see on the Network Dataset Properties dialog.  If you don't ever see that button enabled, then the properties won't get truly applied.      In my case, I did not have the Network Analyst license turned on.  That made it so I could not truly edit the schema of the dataset.  Once I was able to "Apply" the changes, only then would the properties persist.      The flaw in the evaluator is that there is no check to make sure that you are able to edit the network schema.  That would be tough, as it would involve license checks, schema lock checks, and whatever other checks that could verify editing is available. I hope this solves your problem. ... View more

Hello, Thibaut! Which properties are you trying to access on your evaluator? I downloaded and tested the Departure Time Evaluator and I was able to set and access the Data PropertySet within PropertiesDialog.cs as the evaluator dialog was being used. Is that where you are seeing the problem?  While debugging in PropertiesDialog and btnOK_Click? Also, I'd love to find out what your evaluator is trying to do.  What is your use-case for a custom evaluator? Thanks, Patrick ... View more

Sorry, I don't have a good answer to your question. However, I do not think it is a network analyst issue.  Or, at least, there is not a Network Analyst way of getting the answer you want. You might have some luck trying to find out how to get the azimuth of two points along a line.  You do one point as the location of your vehicle, then use the curb approach to figure out which direction along the line to go to put the second point.  ... View more

Could you email me and we can figure this out together off the forums?  pstevens at esri.com. Once we get an answer, I'll post it back here for all to see.   In the meantime, I'll try again with your data on my test machine. ... View more

Hmmm... The 64bit issue is troubling.   I'll try to figure this out, but it might take time. In the meantime, is disabling background processing a sufficient workaround for now? ... View more

Are you running the tool in the background?  Try turning that off. Go to the Geoprocessing menu item. Choose options Uncheck the box marked Enable for background processing. I think the issue is that the tool is not registered to run in 64bit. ... View more

I posted a fix to the problem here: http://www.arcgis.com/home/item.html?id=e11126ea20e941bd9644046e62e2bdbe Please download it and let me know if there are other issues.   The problem was that a new interface is required at 10.2.2, ITrafficProvider2. Thanks for finding a bug and sorry for any inconvenience! ... View more