|
POST
|
Okay, there's a lot of stuff going on here. Let's try to break it down into little pieces. 1) Streets_UseThisOne: This feature class is just a copy of whatever original street features you put in in Step 2, with some vertices added. So, what you need to do is to find a reliable feature class of streets for your area of interest. If your original streets were junk, then Streets_UseThisOne will be junk, and your analysis won't be very good. You might be able to find some good street data from the City or other sources, or you could download OpenStreetMap data (which often needs to be cleaned up a little to make sure everything is well connected). 2) Transit lines don't follow the streets: That's correct. They're not supposed to. The TransitLines represent straight-line connections between directly-connected stops and do not attempt to mimic the actual geometry of the routes. So, don't worry about this. 3) Stops not connected to the correct streets: Unfortunately, this is a common problem. The GTFS data contains a simple lat/lon value for each stop and my Step 1 tool just sticks a point in that location. Step 2 has to snap the stop to a street feature so that the transit stuff will be adequately connected to the streets. I have no information to work with besides the lat/lon of the stop, so it just snaps to the closest street feature. Sometimes this isn't the actual street where the stop is located but is instead a side street. Sometimes this is because the original lat/lon was a bit off, and sometimes it's because the side streets are narrower than the main street, so the stop just falls closer to the side street's centerline. You CAN edit the transit stops and lines after running Step 1, but you have to make sure that the transit lines still connect to the stops. What might be easier is to download the Edit GTFS Stop Locations tool, update stop locations that way, and then start your network dataset creation process over again with the updated GTFS stops.txt file. But that could be a lot of work. I don't quite follow what you're talking about regarding the basemap. Hopefully the basemap is accurate, but I can't be completely sure. It might also show station entrance locations (any given station could have several), and GTFS doesn't always have the entrance locations, unfortunately. 4) I don't follow what you're talking about regarding the restaurants.
... View more
05-07-2018
08:35 AM
|
1
|
10
|
2097
|
|
POST
|
If you're unsure of how to run a Service Area analysis, I suggest you run through this tutorial: Exercise 5: Calculating service areas and creating an OD cost matrix—Help | ArcGIS Desktop Actually, this is a particularly good tutorial for you because it also covers the OD Cost Matrix analysis, which might be more appropriate for what you're trying to do. I can't tell for sure what you're trying to do, but if you're trying to identify restaurants within a certain travel time of school, then using OD Cost Matrix is more appropriate than calculating a Service Area and then finding which restaurants fall inside the polygons. OD is more exact. I think what you're asking in part is how you do one analysis for just walking and another analysis for walk+transit. One way to do this is to create a separate WalkTime attribute where transit lines are forbidden (just use -1 in both directions for the evaluator). Or, if you turn the time of day off and just use your transit travel time attribute, it effectively does the same thing because the transit lines won't be used unless a time of day is specified.
... View more
05-07-2018
08:21 AM
|
0
|
0
|
2097
|
|
POST
|
Yeah, this sort of thing was kind of messy before I implemented the installer (just under a year ago). So, if you had an older version, it's not surprising that there were weird conflicts with the toolbox location and possibly the evaluator reference in the registry. Sounds like you've got that part working, though. Phew!
... View more
05-07-2018
08:17 AM
|
0
|
0
|
2097
|
|
POST
|
Sorry it's taken a while to get back to you. Did you ever get this to work? To answer your original questions: 1. If the network dataset template support add attributes by edit the xml? ^ Yes. You can edit the XML template. 3. If so, what’s right way to edit the xml. ^ You should be able to edit it in any way you want, with a text editor manually, with some automated procedure, etc., as long as it remains valid. The original XML template uses single quotes. I don't know if it makes a difference, but it seems like it would be safer to keep it the same as the original. Additionally, I notice that the SpatialReference tag and various other place in the original uses ", but your new template uses an actual " character. This could be a problem also. Try using WinMerge to see the differences between the two files. I really don't know whether this matters, but these differences obscure the actual intentional changes you made, so it's hard for me to find them and see if there is a mistake somewhere there.
... View more
05-04-2018
01:35 PM
|
0
|
0
|
1735
|
|
POST
|
How do you know the Service Area is only 1 mile from your facilities? Is it exactly 1 mile, or just approximately. Might be helpful for you to post a screenshot. Since you said you left most of the network dataset settings as default, I'm guessing there's a problem with the way your Length attribute is configured. You should open up the Evaluators dialog for that attribute and make sure it's configured in a sensible way. See Types of evaluators used by a network—Help | ArcGIS Desktop to understand more about what evaluators are and how they should be configured depending on your desired outcome. The other possibility is that your network's connectivity isn't set up appropriately for your data. You might need to switch your connectivity policy from End Point to Any Vertex. See Understanding connectivity—Help | ArcGIS Desktop
... View more
05-04-2018
11:26 AM
|
0
|
1
|
1778
|
|
POST
|
That appears to have worked correctly. Have you tested your network again yet? Does it work now? In case it's not working: Did you by any chance previously have a different version of ArcMap installed on this machine and an older version of the transit evaluator registered/installed with it?
... View more
05-04-2018
10:26 AM
|
2
|
16
|
2097
|
|
POST
|
Since you got the FDO error with the negative number, it means that the transit evaluator did not "register" properly during installation, so probably there's nothing wrong with your gdb, and you don't need to share it. We just need to figure out why installation didn't work properly. Are you using the latest version of the Add GTFS to a Network Dataset toolbox (ie, downloaded within the last month or two)? http://arcg.is/10jXez If not, please get the latest and try reinstalling. If so, try uninstalling (there should be an item in your Programs and Features Uninstall a Program thing). Then try reinstalling. When the installer finishes its business, expand the message window, right-click, and choose Copy, and then tell me what it says. I'm guessing there's an error in there somewhere.
... View more
05-04-2018
09:46 AM
|
0
|
18
|
2097
|
|
POST
|
Your data's projection shouldn't matter. When you say you "can't open the network in ArcMap at all", did you get a pop-up message with an FDO error with a negative number? If not, what are the symptoms? Possibly something didn't work right when you installed Add GTFS to a Network Dataset, and this makes it so that you can't open the network dataset that uses the special transit evaluator. However, it's pretty hard to tell. Would you be able to share your geodatabase so I can take a look? The best thing to do is to zip the .gdb into a zip file and post it on a file sharing site and send me the link.
... View more
05-04-2018
08:12 AM
|
2
|
20
|
3774
|
|
POST
|
I'm glad it worked, although I can't necessarily explain why. Post again if you encounter further problems.
... View more
05-02-2018
04:57 PM
|
2
|
23
|
3774
|
|
POST
|
Hello, Destiny. You did all the right things to diagnose and try to fix this problem. Indeed, it sounds like a geometry problem with the streets feature class. The actual failure is in the Integrate tool. Someone else reported a similar problem to me a while back. Like you, he ran Check Geometry and Repair Geometry, and it didn't help. We weren't able to figure out the cause of the problem. However, he copied the files to a new geodatabase, and it magically worked after that. If that doesn't work, my suggestion would be to try running the Integrate tool on your street data in ArcMap, just by itself (ie, not inside the Add GTFS to a Network Dataset toolbox). If you're able to reproduce the same error, then this is something you can call Esri Tech Support about (because it's an official supported tool). They can try to debug what's causing the failure.
... View more
04-27-2018
08:35 AM
|
2
|
0
|
3774
|
|
POST
|
Did you test the original network, before you made the template and the modifications? Did that network work? You said the solve failed with the new network. What was the failure message? This will likely give some clue about why it failed.
... View more
04-19-2018
10:24 AM
|
0
|
2
|
1735
|
|
BLOG
|
Going to the Esri UC (July 9-13, 2018)? Here is a list of sessions the might be pertinent to public transit agencies: 2018 UC Transit Sessions.pdf We hope to see you there!
... View more
04-18-2018
04:17 PM
|
0
|
0
|
1173
|
|
POST
|
Only impedance attributes. Oneway is probably a restriction, so that one doesn't count.
... View more
04-10-2018
08:51 AM
|
1
|
1
|
3049
|
|
POST
|
Hello Chris. The fields in your barriers should take the form Attr_[Impedance attribute name]. So if your network has an impedance attribute called "TravelTime", and you are using TravelTime as the impedance attribute for the particular analysis where you will be using the barriers, the correct field would be Attr_TravelTime. Impedance attributes are a property of your network dataset. If you're building your own network dataset, you can give them any names you want. Consequently, there is no set list of possible field names for barriers. The valid values depend on how you've constructed your network dataset. When you create a network analysis layer (like a Route or Service Area layer), the barriers sublayers should already have the appropriate fields in them, so you don't actually have to construct the fields yourself in advance. Just in case it's not totally clear, barriers are NOT part of the network dataset. They are part of the network analysis layer and specific to each analysis.
... View more
04-10-2018
08:03 AM
|
1
|
3
|
3049
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a month ago | |
| 1 | 04-21-2026 08:39 AM | |
| 1 | 04-15-2026 02:24 PM | |
| 1 | 02-03-2026 11:41 AM | |
| 1 | 03-16-2026 08:58 AM |
| Online Status |
Offline
|
| Date Last Visited |
a month ago
|