|
POST
|
So you are developing a web app to show information about the public transit system, but you are not trying to create a passenger-facing routing, app, correct? Interesting. This is not a use case I'd anticipated for the Public Transit Data Model. I might be able to find a way to link the output of GTFS Shapes To Features to the data model, but I'll have to think about it and do some experiments.
... View more
07-20-2022
08:08 AM
|
1
|
0
|
4617
|
|
POST
|
Hello. I think what you're asking is how you can make the geometry of the LineVariantElements look like your shapes.txt file so that the transit lines appear to follow their actual geographic paths instead of simple straight-line connections between stops. Is that correct? If so, there is no need to do this. The Public Transit evaluator in the network dataset does not care about the geometry of the LineVariantElements. It looks up the travel times in the various Public Transit Data Model tables. There are several reasons we don't use the geometry from shapes.txt for the network dataset: The shapes.txt file is optional, so we can't rely on it being there. Often the shapes derived from a shapes.txt file are messy or inaccurate (or missing). Good connectivity with stops is essential in a network dataset, and the data from shapes.txt does not have a straightforward relationship with stops. You should not try to use your network dataset and its LineVariantElements feature class for visualization. It is designed specifically for analysis. But, I would be interested to understand your goal - what are you actually trying to do? To answer your specific questions: From your screenshot of the output of GTFS Shapes To Features, it looks like most routes have multiple shapes. For instance, route_id A_562 has four shape_ids: 10, 11, 12, 9. The GTFS shape_id is not used in the LineVariants table. One reason is that shape_id can be a string, and we chose to use numeric values as IDs for our Public Transit Data Model. Also, although we provide tools to convert from GTFS to the Public Transit Data Model, you could instead use some non-GTFS source of transit data. Also, as I said before, the shapes.txt file is optional. So, you should not consider the ID field in LineVariants equivalent to the shape_id field in shapes.txt, but you are correct that LineVariants are conceptually equivalent to shapes. But...yeah, there is no good way to join the LineVariants table to the output of GTFS Shapes To Features. If you tell me more about what you're trying to do, I might be able to give more useful advice.
... View more
07-19-2022
08:34 AM
|
0
|
0
|
4636
|
|
POST
|
That's probably doable, although you might want to split it up with one cutoff value per solve. The analysis settings you use impact performance significantly. For instance, High Precision polygons are much slower to generate than Standard, so it really depends on your analysis needs. If you get the Mobile Map Package version of Streetmap Premium, you will get better performance than with the file geodatabase version.
... View more
07-06-2022
08:28 AM
|
0
|
1
|
2356
|
|
POST
|
No, there are no input limits when you use a local network dataset on disk. Input limits are imposed only by services. (That said, if you have a ludicrous number of inputs, you may at some point run into memory and CPU issues, so you might still need to chunk the problem for that reason.)
... View more
07-06-2022
07:56 AM
|
0
|
3
|
2357
|
|
POST
|
You should not include the Shops and Warehouses in the network dataset as "Source Feature Classes". Only roads and things you travel on should be part of the network. Your shops and warehouses should be used as analysis inputs. You add those to your network analysis layer as input Origins and Destinations. Then, the network is used to model travel from each origin to each destination. But the network itself should work with any input data, not just the shops and warehouses. It sounds like you're experiencing some pretty big challenges here. If you call Support, they can help guide you through the workflow and answer all your questions as they come up. They can do a lot more than we can do here in this forum.
... View more
06-29-2022
12:10 PM
|
0
|
0
|
2703
|
|
POST
|
So you created your own network dataset, and you're not using the one provided by the tutorial? If so, I suspect that's the problem. Something in the way you've created your network dataset is probably not working right. I'm not entirely sure what you mean by "When creating one I ordered it to use all of the layers I have loaded (several ones including roads, buildings, points of interests, shops, and warehouses". When you create a network dataset, it should include only roads and other lines that can be traveled on. You should not include buildings or points of interest in the network itself. If you've done that, and then you also try to use those as inputs to the network analysis, the analysis inputs may locate on features in the network that aren't connected to anything. Here is a tutorial all about how to create a network dataset: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/how-to-create-a-usable-network-dataset.htm If you're still having trouble, you will probably need to reach out to Esri Support, and they can walk you through the process or examine the network you've created.
... View more
06-29-2022
09:56 AM
|
0
|
2
|
2708
|
|
POST
|
Hello. I can't quite tell from your question, but are you working through this tutorial? https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/od-cost-matrix-tutorial.htm Here are a couple of ideas: Are you sure you loaded the destinations? Open the attribute table for the Destinations sublayer of your OD Cost Matrix layer. Is there anything in it? Are the Origins and Destinations actually in the right geographic area? Maybe you accidentally loaded something else. You can zoom to each sublayer to see where they are on the map. Is your OD Cost Matrix layer using the right network dataset? Maybe when you created the layer, you forgot to update the network data source, so it's referencing one of the other tutorial datasets. If none of those are the problem, please post more details about your workflow and what you've tried so far.
... View more
06-29-2022
08:05 AM
|
0
|
4
|
2713
|
|
POST
|
The configuration of impedance attributes on a network and what they represent depends entirely on the data. What network dataset or service are you using? I'm guessing you're using Streetmap Premium or the ArcGIS Online Service, but I can't be sure.
... View more
06-28-2022
12:06 PM
|
0
|
1
|
3151
|
|
IDEA
|
Sounds great! I'm glad Copy Traversed Source Features will give you what you need without any software changes, so I am closing this request as "Already Offered". For those of you who upvoted this idea, if your needs are not met, please respond here to explain your use case.
... View more
06-21-2022
08:00 AM
|
0
|
0
|
3480
|
|
IDEA
|
Hi again. I spoke to my colleague, and we have another suggestion that may also serve your needs. If you include your bridges in a table of Reference Landmarks, you can retrieve the point locations and time along that route that each bridge was traversed from the DirectionPoints feature class created when directions are generated. It's not clear from your question how you are performing the analysis, but the DirectionPoints output is available as a retrievable output type from the arcpy.nax solver objects. For a network analysis layer, it can be found in the layer's analysis feature dataset where the data for the sublayers is stored. If neither of the above suggestions (Copy Traversed Source Features or reference landmarks) give you what you need, we might consider adding support for specific new road class values, such as for bridges. However, it's very unlikely that we would support any user-defined road class value, since we would not be able to determine what directions text should be used to properly describe traversal of that road class type.
... View more
06-20-2022
10:30 AM
|
0
|
0
|
3519
|
|
IDEA
|
Hello @SimonLynch. Thank you for your suggestion. I am not entirely sure whether updating the Directions output is really the best way to solve your problem. I have asked a colleague who's an expert in this area to have a look at your suggestion and share his thoughts. In the meantime, I wonder if you have ever used the Copy Traversed Source Features tool and whether the output of this tool may serve your needs. Essentially, you first solve a route, and you get a single feature showing the path taken. Then, you run Copy Traversed Source Features, and it returns all the individual network edges, junctions, and turns that were traversed by the route, including the ObjectIDs of the features that were used. Depending on how your network is modeled, this might directly give you the information you need, or you might be able to join this table with some attributes from your network source features to determine which bridges were traversed and in what order. @LukePaine2 and @monmon, I would be interested to understand whether this would serve your needs as well or why you upvoted this idea (if you have some different use case).
... View more
06-20-2022
08:44 AM
|
0
|
0
|
3521
|
|
POST
|
Yes, check out Esri's Streetmap Premium product: https://www.esri.com/en-us/arcgis/products/arcgis-streetmap-premium/overview
... View more
06-20-2022
07:52 AM
|
0
|
5
|
2368
|
|
POST
|
Hello again. Just wanted to follow up on a part of this thread. I have created a downloadable script tool that adds transit information to the output of Copy Traversed Source Features, including the Run ID, ride time, wait time, and transit trip arrival and departure time to each transit segment. The tool runs a post-process that queries the Public Transit Data Model tables to make a good guess as to which transit runs were used for each segment based on the constraints of the analysis settings and the arrival and departure times for that segment. This isn't a terribly efficient way to solve the problem, but it gets the job done. Please consider this a prototype. Definitely let me know if the tool doesn't return the output you want or if you experience any problems. I would like to get this behavior into the core software at some point, and feedback on this prototype will be very valuable in doing so. Note that this functionality is not yet integrated into the Route version of the Calculate Travel Time Statistics tool like we discussed above. That's up next on my plate but will require some surgery on that tool. I'll report back here when I've done that. Download the tool from ArcGIS.com or GitHub. (This download includes several tools; the new one is called Copy Traversed Source Features With Transit.)
... View more
06-17-2022
08:50 AM
|
0
|
0
|
4008
|
|
POST
|
Hello again. Just wanted to follow up on part of this thread. I have created a downloadable script tool that adds transit information to the output of Copy Traversed Source Features, including the Run ID, ride time, wait time, and transit trip arrival and departure time to each transit segment. The tool runs a post-process that queries the Public Transit Data Model tables to make a good guess as to which transit runs were used for each segment based on the constraints of the analysis settings and the arrival and departure times for that segment. This isn't a terribly efficient way to solve the problem, but it gets the job done. Please consider this a prototype. Definitely let me know if the tool doesn't return the output you want or if you experience any problems. I would like to get this behavior into the core software at some point, and feedback on this prototype will be very valuable in doing so. Download the tool from ArcGIS.com or GitHub. (This download includes several tools; the new one is called Copy Traversed Source Features With Transit.)
... View more
06-17-2022
08:37 AM
|
0
|
0
|
3734
|
|
POST
|
Hello again. Just wanted to follow up on this thread. I have created a downloadable script tool that adds transit information to the output of Copy Traversed Source Features, including the Run ID, ride time, wait time, and transit trip arrival and departure time to each transit segment. The tool runs a post-process that queries the Public Transit Data Model tables to make a good guess as to which transit runs were used for each segment based on the constraints of the analysis settings and the arrival and departure times for that segment. This isn't a terribly efficient way to solve the problem, but it gets the job done. Please consider this a prototype. Definitely let me know if the tool doesn't return the output you want or if you experience any problems. I would like to get this behavior into the core software at some point, and feedback on this prototype will be very valuable in doing so. Download the tool from ArcGIS.com or GitHub. (This download includes several tools; the new one is called Copy Traversed Source Features With Transit.)
... View more
06-17-2022
08:12 AM
|
0
|
0
|
4521
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 06-12-2026 01:53 PM | |
| 1 | 04-21-2026 08:39 AM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|