Latest Contributions by RachelApplebaum

Hi Emma, I want to make sure I'm understanding the problem, though, so I'm going to recap what I think you're asking about: You have your own network dataset that was given to you by someone else. It has 3 cost attributes: Minutes, TravelTime, and Miles. Presumably Miles is based on the shape length (though with no pictures of that cost attribute setup, I can't be sure), Minutes is based on a field that was calculated by some equation with distance (unknown if shape length or something else) and the speed limit, and TravelTime is not mentioned (or unknown; usually when I see TravelTime it uses traffic info [that's how SMP and ArcGIS Online do it] but I doubt you have historical traffic info with this network). When you solve using the Miles cost as the impedance, the route makes sense and fairly closely matches what Google Maps gives you for shortest time route. But when you solve with Minutes as the impedance, the route is a lot longer and doesn't look correct.   My first thought upon seeing the pictures is that there is a problem with the calculation of the costs somewhere in the data. I'd look at the FT_ and TF_Minutes field values on the centerlines and check that they make sense. Pick a few random streets and divide the shape length by the speed limit (make sure you keep the unit conversion correct) and see if those numbers match what's in the FT_ and TF_Minutes fields. For a more circumspect review, pick streets that are on and around the path that's return when solving with Miles as the impedance. Do the Minutes values for those streets make sense? My guess is that somewhere, maybe on a few streets or maybe everywhere, the Minutes values aren't correct; they are too large, and that's what's making the route solver take a longer path when solving using Minutes. I'd also double check how the Miles attribute is set up. If it's not using the Shape field directly, double check the numbers and make sure that it was calculated correctly. To inspect the network attributes directly, you can use the Explore Network tool https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/explore-network.htm . Or look directly at the attributes on the street centerlines. Whichever works best for you. Regards, Rachel ... View more

Hi Emily, Based on that error, I'm guessing you're using our ArcGIS Online Routing Services to create these service area polygons. When using the ArcGIS Online Routing services, there are limits to the number of inputs or size of requested output. For the Service Area Routing Service, there is a 15 min or 15 mi cutoff limit when you are requesting detailed polygons. https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/credit-consumption-and-analysis-limits.htm#ESRI_SECTION2_A56B7F96629540E0BB787272B9C8EFE0 If you would like a larger cutoff, then you can switch to generating generalized polygons, which are gnerated quickly and are fairly accurate. Or, if you have your own local network dataset, then you can use that as the network datasource. In that case, there are not hard limits on the size or number of polygons you can generate in a single solve. If you are not using ArcGIS Online Routing Services as your network datasource but are still getting that error, please let me know and we can dig into this further 🙂 Regards, Rachel ... View more

Does this happen after every time you run the model? And would you be able to share your model (or a screenshot of it)? Also, if you close and reopen Pro after seeing the issue, does it continue to flip the cost/impedance in Explore Network? Does it happen for every edge? Does it happen with junctions and/or turns as well? Could you share a screenshot of the settings page from Explore Network? I'd like to see what travel mode settings it is using. ... View more

Hi @ReginaldoPaderon2 , This looks like it might be related to ND connectivity. Use can use the Explore Network tool in Pro to look at the connectivity of the edges in that intersection area. When selecting an edge with Explore Network, all connected edges should be highlighted in a bluish-purple color. Make sure that all roads you expect to be connected are highlighted like that. The Connectivity tab will also list all of the connected elements. There could also be some attribution issues, like maybe oneways aren't attributed correctly? (I've definitely done that a few time [or more]). Use the Travel Attributes data grid to check things like oneway attribution or cost values. I'm probably biased, being that I'm on the Network Analyst team, but I think Explore Network is pretty darn handy for things like this. -Rachel ... View more

Hi Jamal, You are correct; in the Field Script (or Element Script) evaluator dialogs, there is currently no list of fields (for Field Script evaluators) or network attributes (for Element Script evaluators). We have plans to improve the experience of creating Field Script and Element Script evaluators and to make it more similar to other expression editors, such as Calculate Field. I don't have an estimated time of arrival on when it will happen, but it is a high priority project for us. Regards, Rachel ... View more

Haven't forgotten this. We're still looking into the enterprise portal part.  ... View more

No, there isn't a way to customize directions or how they're displayed at this time. Also, I'm still investigating the issue in enterprise portal. Would you be able to tell me what version of portal you're using? ... View more

I noticed that in the screenshot of Pro that you provided, the one in dark theme, below the directions instructions, there's a part for Events, and that's where the landmarks get reported. When you expand Events, does that show the correct reporting of the landmarks? In some sample data, I copied some system junctions to a new feature class, gave them names, and set them up as landmarks. When I solved a route for that area, I did see the landmarks reported under the Events expander.   I'm not sure what's going on with the directions in the enterprise portal, so I'll continue to look into that. ... View more

Ah, ok. Let me do some testing here. I can reproduce that situation fairly easily. Hopefully I can reproduce the results just as easily. ... View more

Ah, ok. Are the Gates_Source_features and the Gates_Landmarks feature spatially coincident? ... View more

Are you able to remove the gates as junction sources in the ND? We don't recommend having landmarks as edge or junction sources and it could be causing some issues.  If that doesn't work, would you be able to post a sample of the data, with a network dataset and a route through a gate, showing that it's not generating the direction? ... View more

Are the gates set up as a turn or confirmation landmark? That might be what's going on. If they're set up as Turn landmarks, then if they're at the intersection of 2 edges that constitute a straight "turn" (within a 30 degree azimuth, I believe) then you might not be getting them used in the directions. Also make sure that you have the label field set up for them, so that it's reporting the right info. To check the type of landmark, look at the Guidance column.   ... View more

Hi Jamal, The SA polygon symbology is based on the ToBreak field. It shows in the table of contents as 'Cutoff' because there is a symbol group set up in Symbology Pane. It's named 'Cutoff' because that is what the parameter on the analysis layer is called. If you would like it to be called something else, you can change the name to something else from that control in the Classes tab of the Symbology pane. -Rachel ... View more

Hi Bill, This is not my area of expertise, so unfortunately I can't help. But Colin Lawrence‌ should be able to help! -Rachel ... View more