Latest Contributions by MelindaMorang

That is a possibility, so you just need to experiment a little with the buffer distance until you get what you're looking for.  Or if you have one particularly problematic park, manually edit in some entrance points. ... View more

That doesn't always work well, particularly if your park is very large and rectangular.  Then it will have only 4 vertices at the corners. ... View more

Do you have your street data (ie, you're not working in ArcGIS Online)?  If so, try this: - Add the network dataset's junction feature class to the map.  This is the automatically-generated feature class of network junctions (like intersections) that lives in the same feature dataset as the network. - Do a Select by Location and select all junctions within some very small distance of the park boundaries. - Export the selected junctions to a new feature class.  These selected junctions can serve as a sort of proxy for park entrances.  You can use them as input for your network analysis. ... View more

No, I don't think it would be possible to calculate the max width during the solve.  Since you don't know what road segments were used until the solve is completed anyway, it would still have to involve some kind of post-processing.  The most seamless way to do this would probably be to build a model or a script that both solves the analysis and calculates the width statistics on the results immediately.  Then you just run that model/script to get your results rather than running the Solve tool. ... View more

Okay, so which network is giving you the solution you expect?  2D or 3D?  I wasn't quite sure from your screenshot which is which. Regardless, it appears that the two network datasets don't have the same cost attributes.  The one with the "Add" button not grayed out looks like it has several attributes that make sense.  "speed" is a descriptor which is probably used to calculate the "Time" attribute, which has units of minutes. The other network (the one where the Add button is grayed out for some reason) seems to have an attribute called speed with units of minutes.  That doesn't make sense to me.  Assuming this is the network you set up yourself, then I think you just didn't set up your cost attributes correctly.  Instead of a 5-minute travel time, your service area is solving for 5 some-nonsensical-units. Since you're new to Network Analyst, I encourage you to work through the Network Analyst tutorials.  Hopefully these will clarify how to set up cost attributes and use them in an analysis. ArcGIS Help (10.2, 10.2.1, and 10.2.2) I recommend starting with Exercise 1 and then doing Exercise 5.  Those will be the most relevant for your workflow. ... View more

[Chris, I get automatic notification of all new Network Analyst posts even if my name isn't tagged, but thanks for drawing my attention to this anyway.] Hi James.  What you're describing should work.  When the SA lines are set to Overlapping, you should get duplicates of lines that are traversed more than once if they are reachable from different facilities. For instance, in the simple test case below, the middle area is reachable by both facilities, and the highlighted line is in the Lines output twice, each one marked with a distinct FacilityID. The question is why you aren't getting this expected answer. Do you have more than one Service Area layer in your map?  Are you perhaps adjusting and solving the wrong one and then looking at the results for a different one?  Sometimes that happens if you forget to switch the drop-down layer selector in the Network Analyst window. Are you sure that the reachable area from your two fire stations actually overlaps? If it's not any of that, then I don't know what the problem would be.  Are you able to share your data?  If you could wrap up your network and your layer (with all its settings) in a map package and share it, I could take a look at it. ... View more

For your polygons to be meaningful, it seems like you would need to include some street data.  Pedestrians can leave the bus and walk down a side street, for instance. I really can't tell why your service areas look strange without looking at the data.  Would you be able to post it somewhere? ... View more

Are you using trim for your polygons?  If not, try turning on trim (in the Service Area layer settings) and see if the spikes go away. Are the lines shown in the picture the only lines you have in your network, or do you also have a streets feature class that isn't shown?  If you have streets that aren't shown, perhaps the spikes are due to a connectivity problem with your streets. ~Melinda ... View more

Happy to help! ... View more

Streets that are expected to connect have to have either a) and endpoint or b) a vertex on both street features at the location where they touch, depending on whether your connectivity policy is End Point or Any Vertex.  Please read this doc page to understand what those mean: ArcGIS Help (10.2, 10.2.1, and 10.2.2) If your connectivity is Any Vertex and you just need to do a batch vertex insertion at locations where your streets touch, you can run the Integrate tool.  Make sure you make a back-up copy of your data first, as Integrate actually modifies the input features by moving them slightly.  You can set the tolerance to be small or tiny, though, so it won't move stuff much or at all and will instead just add vertices.  The one problem here is locations where you have an overpass and the crossing streets are actually not supposed to connect.  You might have to manually fix those areas. If your connectivity is End Point, you may have more trouble.  If you split existing features down the middle so that they have end points, you risk messing up attributes that need to be carefully apportioned when the street feature gets split.  For instance, if you have a field called "walktime" and you split a street that has a value of 5 minutes in the walktime field, it would be incorrect for the two split parts of the street to both have a value of 5 minutes.  So, if you have End Point connectivity, you either need to split a lot of features very carefully, or you need to switch to Any Vertex connectivity and run the Integrate tool. ... View more