Latest Contributions by MelindaMorang

Right, the layer is broken, but the underlying feature class holding the data is okay.  You can just use that feature class or copy it elsewhere.  You can add it to the map as a separate standalone layer. In the map, right-click the Polygons sublayer and choose Properties. When the Properties dialog opens, click Source on the left. Check the table for the filepath to the geodatabase where the data is stored and the name of the feature class.  It will be called something like SAPolygons28e168.  (The feature classes are named automatically, so it will contain some random alphanumeric characters.)  Also look at the Feature Dataset because the feature class is actually in there.  So the full path will be something like <path>\MyProject.gdb\ServiceAreaSolver1bqfp70\SAPolygons28e168 You can access this file geodatabase in the Catalog pane.  It's probably best if you copy that polygons feature class somewhere else and rename it so you don't forget what it is. ... View more

Hi Rachel.  I'm not really surprised that this isn't working.  The Add Locations tool doesn't have access to the schema information about the output of Model 1, so it can't construct the field mapping reliably.  I'm not really sure how you could get this to work.  Maybe you could put all of it in one model, and if it was validated or run once, Add Locations might be able to figure it out.  But in general I think this strategy is pretty iffy, and I wouldn't recommend it. If you can change your combo_ID fields to RouteName in advance, that might make it work because the field mapping will happen automatically. Regarding the impedance attribute - that's included in the Travel Mode now.  If you don't like the defaults of the travel modes already included in your network dataset, you can make a new travel mode and use that. If you're frustrated with the model workflow and just need an easy way to get costs for known origin-destination pairs, you can download and use a sample tool we have here: https://github.com/Esri/large-network-analysis-tools  This toolbox contains tools designed primarily for solving very large network analysis problems, but you could still use the known OD pair tool with a small problem.  It will probably serve your needs out of the box. To use this tool, download the latest version using the Releases link on the far right: You will want to use the "Solve Large Analysis With Known OD Pairs" tool.  The tool's documentation is included in the link above. ... View more

Okay, this was a fun little challenge.  I created a script and Python Toolbox that will add a GShapeID field to the LineVariants table populated with the GTFS shape_id (attached).  You should be able to run the tool or use the script directly in a Python workflow.  I think it should be pretty straightforward, but let me know if you have any questions. The script matches up stop sequences in the GTFS stop_times.txt file and the LineVariantElements feature class from the Public Transit Data Model and uses the relationships between the various tables to figure out the shape_id associated with each LineVarID.  If for some reason it can't find a matching stop sequence, it just leaves the GShapeID field blank (I've seen this in cases where a LineVariantElement was deleted because it had null geometry - something the GTFS To Public Transit Data Model tool does automatically to avoid network dataset build errors.) The script currently does not have any data validation and relies on good input data. Please let me know if this works for you. I will consider enhancing the GTFS To Public Transit Data Model tool to populate the GShapeID field automatically in a future release of ArcGIS Pro.  I'll leave a comment here if that happens. ... View more