Latest Contributions by MelindaMorang

‎11-01-2022

Okay, well hopefully my suggestions to use the Conflation tools and Intersect will still work for this.

‎10-31-2022

Hello. GTFS trips are not explicitly geographic. A trip is an instance of a vehicle traveling along a specific sequence of stops at a designated time of day. If your GTFS dataset has a shapes.txt file, then the trips will be associated with specific shapes, which are geographic and are intended to map the actual paths traveled by the vehicles between stops. You can add your shapes.txt file to ArcGIS Pro using the GTFS Shapes To Features tool. If you are truly asking for the linear overlapping distance between trips, then I'm not sure how to help you, since many trips may use the same shape, and you would have to do a bunch of joins or other accounting to count the number of trips using each shape and then the overlapping distance between shapes. As far as the overlapping distance between shapes... You might be able to use the Intersect tool to get a line representing only the intersecting portions of multiple shapes. Then you could get the length of that line. The geometry of the features created from shapes.txt might not overlap exactly, though. You might be able to use some of the Conflation Tools to modify the geometry to match better before doing the intersect. Can you tell me more about what you're really trying to do? I might have better suggestions if I understand that. Is this, by any chance for the Directional Miles calculation for the FTA's National Transit Database annual reporting requirement?

‎10-24-2022

Hi again, Ryan. You can't really combine existing network datasets, but you can definitely combine multiple public transit agencies into a single network dataset. The GTFS To Public Transit Data Model tool allows you to input as many different GTFS datasets as you want. You will need a single feature class of street features, so if you have a separate one for each city, you'll need to merge those in advance.

‎10-19-2022

‎10-19-2022

Yes, I confirmed a colleague that data we get from our data vendors that we use for our Streetmap Premium product and the ArcGIS Online services does not contain sufficient bicycle-related attribution for us to do either Item 1 or Item 2. So, Network Analyst is capable of creating cost and restriction attributes for bicycles, but we just don't have the underlying data to create them and provide them to our customers in our data products. Unless the situation with our data vendors changes, there isn't really anything we can do. I'll leave this idea open because it's definitely something we'd like to support, but it's not something I see us being able to do in the short term.

‎10-10-2022

Okay, I got confirmation from a colleague about how SQL is behaving in this case, and my suspicion is correct. Apparently nulls are considered separately, and this is standard behavior for the version/flavor of SQL used in Esri's file geodatabases. As I said before, if all your RestrictPedestrian row values are null, you don't need an expression at all. If you have some null rows, you should include another clause like this: Or use the SQL editor and use: RestrictPedestrians <> 'Y' Or RestrictPedestrians IS NULL I've updated the tutorial with a cautionary note about this, but you won't see the changes until the next Pro release, probably.

‎10-10-2022

Yes, I used your model. The model itself seems fine. I believe what's going on is that the SQL Expression ignores rows with null field values when checking for RestrictPedestrians <> 'Y'. Since all your rows have null values for the field, no rows are returned, and the tool tries to snap the stops to an empty feature layer. You wouldn't think it would work this way since null is not equal to 'Y', but I guess this is how the SQL Expression control works, or maybe SQL more generally. You can test this behavior using the Select Layer By Attribute or Make Feature Layer tools. The reason the tutorial instructs you to use an Expression is that it earlier instructs you to populate the RestrictPedestrians field with values of "Y" and "N" to designate which streets are restricted to pedestrians and which are not. Since your model skips that step, there's no need to use an expression. But, once I confirm the behavior of the SQL Expression with null values, I'll see if I can update the tutorial and the tool doc to make a note of this unintuitive behavior. The network dataset itself, if created using the provided template, will have no problem with the null field values. The only issue is in the Connect Network Dataset Transit Sources To Streets tool when snapping the stops to the street features. (FYI, the Connect Network Dataset Transit Sources To Streets tool was renamed to Connect Public Transit Data Model To Streets in ArcGIS Pro 2.9 and moved to the new Public Transit Tools toolbox. Since your model includes the tool's old name, I presume you're using an older version of ArcGIS Pro. Updating to the latest version is always a good idea so you can get the latest bug fixes and new functionality. Nothing in that particular tool has changed since then, and the old tool names will continue to work in models and scripts, but it's still a good idea to get the latest if you can.)

‎10-10-2022

Okay, I was able to download your data and play with your model this time. I still don't know quite what's going wrong, but it seems like if I just remove the Expression entirely from Connect Network Dataset Transit Sources To Streets, the problem goes away. Since you're adding the RestrictPedestrians field in the model and not populating it with any values, there is no reason to use the expression anyway. When I run your model this way, the stops successfully snap to the streets, and the StopConnectors are created as expected: There are still a small handful of build errors where StopConnectors have no geometry, and this is likely just a few locations where the Streets doesn't cover the area where the Stops are located. I will keep hunting for the root cause of the problem, but I think this should resolve the problem for your specific case.

‎10-07-2022

Yes, the way the Connect Public Transit Data Model to Streets tool works is that it creates a copy of the Stops feature class and uses the Snap tool to snap the copied stops to the streets. It then generates straight lines between the original Stops and the copied StopsOnStreets. But if the copied stops fail to snap to streets, then the Stops feature and its corresponding copy in StopsOnStreets will be spatially coincident. If you want to share your data, I can take a look. You can put in on any fileshare where I can download it, and that should work. If you don't want to make it public, you can send me a private message through Esri Community with the information. I still think the problem is likely to be with the SQL expression you used. If you want to post a screenshot of the tool parameter and the field in your data that was used, that might give me a clue.

‎10-07-2022

Unfortunately, that aprx file by itself isn't helpful. Because the data and all the associated files and stuff are missing, it's not possible to see the toolbox or anything in the map. Anyway, I'm happy to try to help you with this problem. If I understand correctly, when the tool runs, the stops are not getting snapped to the streets, which results in StopConnector features with null geometry (because they are connecting two points that are directly on top of one another). It sounds like this is a true for the entire dataset, not just a few features in select locations. This makes me think you have accidentally used an incorrect SQL query when running the tool. Did you use something there? Or, there could be some problem with spatial references. You said the data draws correctly on the map. Does it match up with with one of Esri's basemaps? (It's not in Antarctica, the ocean, or out in space, is it?) Maybe post some screenshots?

‎10-06-2022

Hello Lixiaona. This looks like a geoprocessing tool error, so the problem is unrelated to the issue described by the other users in this post. The problem they experienced was related to clicking the OK button on the network dataset properties. Please describe the parameters you've used in the tool or post a screenshot of the tool dialog. You might also consider making a fresh post in a new topic because this is a separate problem.

‎09-14-2022

Hello, and thanks for your suggestion. First, just a bit of clarification and explanation: The Network Analyst extension does not provide any "default" travel modes per se. A travel mode is always a configuration of a particular network dataset, a collection of settings to apply that are specific to the data being used for analysis. The available travel modes and the way they behave is exclusively a characteristic of the data and not anything fundamental to Network Analyst itself. That said, Esri provides some out-of-the-box data to users in the form of our Streetmap Premium product (you can purchase a pre-built network dataset) and in our ArcGIS Online services, which use the same data as Streetmap Premium. This data does not currently include a bicycle travel mode. My guess is your idea comes down to adding a bicycle travel mode to this dataset so you can use it out of the box. Is this a correct interpretation of your question? A bicycle travel mode should consist of two primary things: A cost attribute that calculates the travel time along roads and bike paths with a reasonable degree of accuracy A restriction attribute that defines where bikes are not allowed to travel and, optionally, defines preferred bike routes Item 1 can be very challenging to estimate because bike speed depends on a lot of factors that are often not included in source data, such as slope and pavement quality. You could assume a constant bike speed for a very rough estimate, but this is unlikely to be very accurate. Item 2 is generally easier since cities often have this data. I will have to check whether we have any of this information in the data we receive from our data vendors. Please add more information to your idea about what you're really trying to do and what sort of accuracy you expect in the results. Thanks!

‎09-13-2022

This tutorial might help: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/create-a-model-for-route-analysis.htm It explains what it means to expose something as a model parameter, although it doesn't demonstrate the travel mode parameter specifically. Here's the documentation explaining model parameters specifically: https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/modelbuilder/model-parameters.htm

‎09-13-2022

The Make Closest Facility Analysis Layer tool has a travel mode parameter, so you can choose one of the pre-defined travel modes on the network dataset. However, the individual settings within the travel mode (restrictions, u-turn policy, etc.) cannot be individually set. You can expose the travel mode parameter as a model parameter so the user can pick the travel mode from the model tool UI. There are ways to create a custom travel mode using Python or a JSON string. Or you can add travel modes to your Streetmap Premium dataset if there's a specific non-default configuration you want.

‎09-09-2022

Just so you know, the GitHub link I sent will let you download and use the tool directly without having to know any Python. However, that won't help you if you no longer have access to Streetmap Premium and don't want to use ArcGIS Online (which, I agree, wouldn't be a good choice for this size of problem). For breaking up the problem, you could build a model in Model Builder that selects chunks of your data and runs Spatial Join using one of the iterators.

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by MelindaMorang

Re: Find overlapping distance

Re: Find overlapping distance

Re: Can network datasets from different locations be merged?

Re: Default Cycling Travel Mode - Status changed to: Under Consideration

Re: Default Cycling Travel Mode

Re: Connecting Public Transit Stops to Streets - No geometry for any StopConnectors

Re: Connecting Public Transit Stops to Streets - No geometry for any StopConnectors

Re: Connecting Public Transit Stops to Streets - No geometry for any StopConnectors

Re: Connecting Public Transit Stops to Streets - No geometry for any StopConnectors

Re: Connecting Public Transit Stops to Streets - No geometry for any StopConnectors

Re: Problem of using tutorial to create a network dataset

Re: Default Cycling Travel Mode - Status changed to: Needs Clarification

Re: Define Travel Mode in ModelBuilder

Re: Define Travel Mode in ModelBuilder

Re: Service Area Polygon Spatial Join Crashing

Re: TransitNetwork for multimodal analysis?

Re: Network analyst public transit tool Prepare ti...

Re: Network analyst public transit tool Prepare ti...

Re: How do I fill in the blank areas where streets...

Re: Route Solver - Add Locations - Convert Model B...