Latest Contributions by MelindaMorang

Hi. I can help you with this. I'm not sure what the "GTFS network analyst tools and guide" is that you mentioned because that link goes to an ArcGIS Online org I don't have permissions to see. However, since your screenshot is ArcGIS Pro, and you have something called LineVariantElements, I am assuming you followed this tutorial or something similar. The reason your screenshot of the Explore Network pane is showing Prohibited for the impedance in both directions is most likely because you don't have a date and time set. If you flip to the Settings subtab, you can set the date and time, and then the Values grid should update to show the public transit impedance for that date and time. If you don't set a date and time for your analysis (and also for the Explore Network pane), the transit lines are treated as restricted. The Public Transit evaluator requires a date and time so it can look up the transit schedules and return the correct value for that time of day. So, the first thing for you to check is that you have set a date and time for your Service Area and Route analysis. There are some details in the tutorial I linked to above about how to do this and how to ensure you've selected a valid date and time for your data. If that doesn't solve the problem, please post again with more details. ... View more

It's hard to say from those screenshots. I meant post your actual data so I could download it and play with it, but if that's not possible, I completely understand. You could also contact Esri Support to share it securely with an Esri expert. In general, there are a couple of reasons why you might see routes that appear incorrect: Our solvers choose whatever options minimize travel time, even under some circumstances when these are not super realistic for a traveler. For example, if the fastest route is to walk for an hour and then ride for 10 minutes because that saves you one minute on your journey compared to walking for 11 minutes and riding for an hour, that's what it will tell you to do. Maybe the time of day and day/date you chose for testing aren't good. Make sure you have reviewed your input data so you know whether you can use a generic weekday or need to use a specific date, and, if you're using a specific date, that you're using a date when all the service is actually running. Your streets could have some connectivity problem. You can review the early parts of the tutorial where you examine your street data for some possible reasons why there might be a problem. Maybe you got a bunch of build errors when you ran Build Network that you didn't address? ... View more

I guess it's possible the overpass/underpass issue is affecting things, although it's hard to say without seeing how your network dataset is configured. Are you able to post your network dataset? I could take a look. ... View more

I presume by "the second step of the process" you mean in the Create Network Dataset wizard in ArcMap. Hmm, I'm not sure why a point feature class wouldn't show up as a valid option in there. Did it end up as a multipoint instead of a normal point, perhaps? Like a transit line had multiple intersections, and both points ended up in the same feature instead of unique features? Oh! I wonder if that was what caused the strangeness with your barriers! ... View more

You should probably start with this tutorial so you can learn how networks are modeled and your various options for calculating network attributes: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/how-to-create-a-usable-network-dataset.htm Side note: We have found that the Tiger Line often isn't very good quality for creating a routable network and requires a lot of work. Depending on your needs and budget, the easiest thing for you to do might be to purchase Streetmap Premium, which includes an already-built high quality network dataset for the entire US. ... View more

Hi DX. There is no technical reason I can think of why an added cost point barrier on one of the TransitLines wouldn't work. Did you make sure to set the BarrierType field in Point Barriers to "Added Cost", or 2? If it's still set to 0, then it's functioning as a restriction barrier and ignoring the added cost. That said, I think there is a larger, more fundamental problem with your approach of attempting to add a time cost to your analysis to model fares. The transit schedules are in a lookup table, and the transit evaluator queries this table for the time of day when the traveler arrives at the initial stop for that segment. The schedules are very specific and exact. Let's say the traveler departs on a bus at 8am along a particular segment where you have placed one of those point barriers. Normally the bus takes 10 minutes to reach the next stop, so when the solver queries the transit schedules to determine the cost to traverse the next segment along the transit line, it will be looking for trips that start at 8:10 along that segment, and it will see that the same bus that the traveler is already on does that, and the traveler will just zoom right through in a logical and realistic manner. But if your point barrier adds 50 minutes to the trip, the traveler now arrives at the next stop at 9:00 instead, and the schedules are queried for 9:00. The transit schedules could be completely different by that point, and the traveler might have to sit and wait for the next bus, or it might find that the most efficient path from A to B is now to walk or ride some other transit line. Modeling monetary cost as time in this situation just isn't going to work. Here is a possible explanation of why you're not seeing a difference in your Service Area. Service Area just searches outward from the Facility to find all possible network segments that are reachable within the time limit, and then it creates a polygon around them. It's possible that all the network segments are reachable either without transit or using some alternative transit lines, so the time delay you put on the one segment didn't make any difference to the total segments reachable. If you have a really dense transit network, this could reasonably happen. Alternatively, if your transit is so infrequent and not timed to correspond to whatever your Service Area start time is, it's possible that the Service Area basically just reflects walking anyway, and the transit wasn't contributing anything in the first place. You said you want to model some kind of "generalized cost", which I presume is some way of measuring the desirability of transit trips or an annoyance factor or something like that, which incorporates not only raw travel time but also fares and maybe some other less tangible costs. I think a better solution might be to create a separate cost attribute on the network to model monetary cost, and then accumulate this attribute while solving optimizing based on travel time. In the results, you can see the unchanged total travel time, but you can also check the accumulated value of the monetary cost according to how many of your point barriers it traversed. Possibly you could extrapolate beyond that to other, more complex cost attributes to accumulate, depending on your needs. I haven't fully thought through how that would work, but I think there are definitely possibilities here. Finally, I presume you have some reason for using ArcMap and the deprecated tools, but you, and anyone reading this, are highly encouraged to migrate to ArcGIS Pro and the built-in tools for public transit analysis there. ... View more

Hello. Network Analyst is used specifically in creating a routable network designed to model travelers optimizing their journeys from Point A to Point B, and other related analysis. I don't think this is what you're trying to do, so I'm going to move this question to a different forum where hopefully you can get some answers. ... View more

Hmm, your question doesn't really give enough information to determine what's going on. Also, although you said you're using 10.8.1 (a version number which would correspond to ArcMap), your screenshot is from ArcGIS Pro. Maybe you meant ArcGIS Pro 2.8.1? Probably the best thing for you to do is to run through this Route tutorial: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/route-tutorial.htm This will help you understand what all the settings do and how to interpret the results, and maybe this will give you enough to figure out your problem or at least narrow down your question. ... View more

No, that's almost certainly not the problem here. The place where the code is erroring out is before it even touches the network dataset. The code is just trying to select a subset of the origins to use for each chunk as is failing for some inexplicable reason. ... View more

Sigh...I'm so sorry, Eli. I am completely befuddled by this problem. I have absolutely no idea what's going on. Thank you for testing with more than one origin. The OBJECTID <= 1 AND OBJECTID >= 1 query expression definitely looked odd, so it was a good thought you had to test with more than one origin. Too bad that didn't end up being the issue. Typically if there were a problem with one of the input parameters, the Make Feature Layer tool would generate a more specific error, like “ERROR 000732 Input Features: Dataset <blah> does not exist or is not supported” or “ERROR 000358: Invalid expression”. Your logs are showing that the tool returns  “ERROR 000816: The tool is not valid”, which doesn't even make sense in this context. I sent a query to the person here at Esri who "owns" the Make Feature Layer tool. Maybe he can shed some light on what circumstances would cause the tool to return this error. In the meantime, I think your best option is to revert back to using the slower ArcMap version. I'm so sorry! One last thing to check on your end, if you haven't already: Can you run the Make Feature Layer tool on your origins at all, just normally within an ArcGIS Pro session? Does the tool work at all? If it doesn't, then at least we've found our issue. The best thing to do in that case is probably a) uninstall and reinstall Pro and try again, and if that doesn't help, call Esri Support and ask them why a core tool is not working on your machine. Actually, for that matter, you could try uninstalling and reinstalling Pro anyway, just in case. Or hang on until Pro 2.9 is released in a week or two and see if that fixes it...? ... View more

I think, based on the error message, there has to be something wrong with the origins_where_clause. Like somehow, the code has created a where clause that for whatever reason is invalid. I don't know how it would do that, but if we can see what the where clause is, that will help. ... View more

Oh, I think this might be my bad. Maybe try this instead: self.logger.debug(str(origins_where_clause)) self.logger.debug(str(self.origins)) self.logger.debug(str(self.input_origins_layer))  Maybe the new failures are caused because LOGGER doesn't know how to convert those things to strings and print them. At this point I'm not sure what else to check besides this. I don't think having your data on a different drive or partition is going to make any difference.  ... View more

Yeah, unfortunately, for the reasons I described above, I don't think the flooding scenario will behave nicely with transit routing. The schedules are stored in lookup tables, and so the start time for one segment along the route wouldn't know about delays in the previous legs. Or if the bus can't even get through the flooded area at all, it would never arrive to serve the stops after the flooded area in reality, but the software doesn't have a way to know that. It just isn't going to do what you want it to do. Is the flood in a predictable area so the transit system already has well-defined protocols in place for when the flooding occurs? Like, do they just know that whenever the area is flooded, Route 10 gets diverted and Route 11 goes only to Stop M and doesn't continue on to N-Z? If that's the case, you can build that into your network. If you can figure out how to either model those changes in GTFS or in the Public Transit Data Model tables themselves, then you can turn on and off specific lines and runs using the supported attribute parameters: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/public-transit-evaluator.htm#ESRI_SECTION1_9FF9489173C741DD95472F21B5AD8374 Basically, you could have one version of Route 10 for non-flood days and a different version for flood days. You would create a travel mode for non-flood days that turns off flood-Route-10 and a different travel mode for flood days that turns off normal-Route-10. Does that make sense? I know that won't be easy to model unless your transit agency already provides the data like this. ... View more