Latest Contributions by RobertGarrity

Hi Tobias, You could use the query builder. See the section entitled "Snapping environment with Build Query" in the following help topic: http://resources.arcgis.com/en/help/main/10.2/#/What_are_network_analysis_objects/00470000003n000000/ Essentially, the query can reference the source features to see floor levels and you can limit which floor to locate on. Best, Robert ... View more

Hi Jesse, If you are using the Add Locations tool, you can expose your Input Locations parameter as a model parameter. Then, in the Properties of the Input Locations parameter, set the data type to RecordSet. You'll also need to specify a schema. To do that, export a Routes feature class from an empty VRP layer you create through ArcMap, then point the RecordSet schema to that saved feature class. (Alternatively, you can create a feature class with just the necessary fields, such as Name, StartDepot, EndDepot and any other properties you want to be able to define as you add routes manually). A second option is to use the Solve Vehicle Routing Problem tool in the Server toolset of the Network Analyst toolbox. That tool is designed for making web services but it has the Route input already set up as a record set. A third option is to use the ArcGIS Online VRP service: http://resources.arcgis.com/en/help/main/10.1/#/What_are_the_ArcGIS_Online_network_analysis_services/0047000001t6000000/. This would be useful if you don't already have a good or comprehensive network dataset. Best, Robertg ... View more

Hello Habtom, It sounds like you have elevation fields set up on your network dataset, but the elevation values aren't matching the way they should. If you go to the Network Dataset Properties dialog box > Elevation tab, the Using Elevation Fields radio button should be enabled if elevation fields are enabled. (If they weren't enabled, you would probably get connections among all the adjacent lines rather than a subset of them.) There should also be two fields listed in the table below the radio buttons, which I'll refer to as the elev fields. Add the source streets feature class to the map and set the symbology to "Arrow at End" to easily see where the to-side (and thus the from-side) of a line is. Use Identify or look at the attribute table to figure out whether the from- and to-ends of the lines have appropriate values. You want roads that connect to have the same elevation values on the ends where they touch. So, for instance, if we assume the lines in your diagram are digitized in the direction of the blue arrows, we would want something like the following: To Z-elevation of Line B-C: 0 From Z-elevation of Line C-D: 0 To Z-elevation of Line E-C: 1 From Z-elevation of Line E-C: 1 This way B-C and C-D connect to one another but not to E-C or C-F. And E-C and C-F connect to one another. Note that if B-C and C-D are above the other lines, you may want to set their connecting elevation values to be 1 and switch the E-C values from 1 to 0 for easier interpretation, but it doesn't really matter for it to work properly. The help files probably do a better job of explaining this than I just did. So you might also want to take a look at the Modeling Elevation section in the following topic: http://resources.arcgis.com/en/help/main/10.1/#/Understanding_connectivity/004700000009000000/ Thanks, Robert ... View more

Hey Justin, Are you setting up prefer/avoid restrictions on your network dataset? If so, the restriction should evaluate to True regardless of whether you want to avoid or prefer the network element. The Restriction Usage parameter that is created by default with any restriction attribute determines whether the restricted elements should be completely prohibited, avoided, or preferred. I realize it sounds odd to prefer a restricted element, but in order to prefer/avoid elements, they need to be 'restricted' first. Going through the following tutorial may help clarify this: http://resources.arcgis.com/en/help/main/10.1/#/Exercise_12_Performing_network_analysis_using_restriction_attributes/0047000001s5000000/ Robert ... View more

Hello Eric, I'm attaching a series of graphics to explain what the problem is for indoor routing and how you may be able to resolve it using Search Query. But in a nutshell, the Z values of 3D line and polygon features are ignored when loaded as barriers. This means the barriers affect any network element that intersects them as well as any elements above or below them. Line and polygon barriers were implemented this way due to technical limitations, or more specifically, due to limitations with 3D spatial operations. A way to get around this is with the Search Query parameter on the Add Locations geoprocessing tool. Write a query to locate your barriers on a specific floor level using a field in the attribute table of the edge source feature class. (This implies that your source features need floor-level attribution for this to work.) Your query should exclude junctions as well. If you are modeling doorways or something similar with junctions, the junction sources would need to have floor-level attribution too, but you can probably get away with building a query that doesn't select any junctions at all. The graphics should help clarify if this isn't too clear. Good to see your making progress on your project. Best, Robert ... View more