Latest Contributions by RobertGarrity

In ArcGIS, you need a network dataset to perform indoor routing, so you would need to convert your XML data into one or more feature classes, then create a network dataset from the FCs. I've never converted XML data like yours into a feature class, but one approach would be to Use Export XML Workspace Document geoprocessing tool on a dummy feature class. This would give you the necessary XML structure needed to import your XML data into a feature class. Create an XSLT to convert your XML data to an XML file that matches the one output by the Export GP tool. Use Import XML Workspace Document GP tool to convert your data to a feature classes. Once you have your feature classes, you would need to create the network dataset. Best, Robert ... View more

Hi Daniel, You're correct, Network Analyst does support 3D routing, and it requires the paths of the network to be created in a network dataset before performing analysis. For the 2013 Esri User Conference, I set up a 3D routing service to be used by a mobile Android application. The application, which was developed by GIS Inc., used GPS coordinates to determine a location while outdoors and signatures from wifi hot spots while indoors. The xyz coordinates were sent to the service. This meant I had a similar issue to yours: users could be anywhere within a room, and they would need to be routed accordingly. I didn't want a user in the corner of a large room, for instance, to have their location snap to the network in the wrong room and get an inaccurate route. So what I did was create a fishnet with grid cells that were 3 meters wide and that covered the convention center, the adjacent hotels, and the surrounding outdoor area. I created another, slightly larger, fishnet and rotated it so the intersections of both fishnets/grids where coincident. (The second fishnet was slightly larger because it became the hypotenuses of the resultant triangular lattice.) After breaking the lines and creating a network dataset, I could accurately handle any location sent in by the app. Of course there was other processing that was required, such as Buffering walls, then erasing the intersecting fishnets before creating the network dataset. Creating fishnets for each floor in the convention center and the adjacent hotels. Digitizing escalators, stairways, elevators, etc. I also had the main hallway paths digitized. Using soft restriction network attributes, I funneled the routes from the lattice onto the main hallways. The results looked better this way in a cartographic sense. I'm sure there are other ways to solve the same problem, but that's what I did, and it worked. What file format are you trying to import into ArcScene? Thanks, Robert ... View more

Hello fellow geographer, There is a short video in the Network Analyst video series that explains how to properly set up one-way streets. Watching that is probably the easiest way to learn, as long as the language isn't much of a barrier. The video shows how to use TF and FT as field values instead of 0 and 1, but I hope you will be able to look at the examples and make the proper configuration choices in the evaluator you set up to reference zeros and ones. You can also download the Network Analyst tutorial data from arcgis.com. The network datasets in there have one-way street restrictions you can reference. The main thing to know is modeling one-way streets is done by specifying which direction of travel isn't allowed. Best, Robert ... View more

Hello, Sherwin. Point barriers that prohibit travel on edges have existed for a long time. But you're right, at ArcGIS 10.0, line and polygon barriers were added to the mix. Furthermore, point barriers were enhanced to add cost, rather than completely block travel, along an edge. Similarly, line and polygon barriers could either block travel or scale it. Note that point barriers can increase cost by addition and point and line barriers increase by multiplication. So if you want to add cost every time a barrier is crossed, use added-cost point barriers. I figure you're looking at line barriers because you already have line data, so what you'd need to do is find where your lines cross roads, then turn those crossings into points. The Intersect GP tool is one option for that. (Make sure you set the Output Type parameter on Intersect to points). Once you have your points, you can assign added cost values to the points and load them into your network analysis layer. If you already have point data, you wouldn't need to run Intersect of course. You could load the points directly. Best, Robert ... View more

There is another option for you as a 10.0 user...As long as you have 10.0 service pack 5 installed, you can use the GenerateServiceAreas ArcGIS Online geoprocessing service. (10.1 users with service pack 1 can also have this option.) Here is some documentation giving an overview of these kinds of services and on how to get started--this doc is in the 10.1 help, but it is the same for 10.0 sp5: http://resources.arcgis.com/en/help/main/10.1/#/What_are_the_ArcGIS_Online_network_analysis_services/0047000001t6000000/ Once you connect to the service, the tool shows up in the Catalog window of ArcMap. It looks and acts like a GP tool, but it has a high-quality road network dataset built into the ArcGIS Online service, so you don't need to add a network dataset to your map. Once you're connected, add a basemap, add your facilities, then open the tool, which will be in the Catalog window under GIS Servers > arcgis on logistics.arcgis.com > World > ServiceAreas > GenerateServiceAreas. The side-panel help of the tools dialog box should help you along, but let us know if you have any questions. Thanks, Robert ... View more

A restriction does indeed need to evaluate to true or false. 'True' means 'restricted', but each line feature represents two edges, one in the from-to digitized direction and the other in opposite direction. So you're really restricting individual sides of the street rather than the entire street. Here's a link to a video that has a better description of how it works: http://video.arcgis.com/watch/2112/creating-network-datasets-one_dash_way-streets Best, Robert ... View more

Hi Tom, It looks like you may be able to use the Location-Allocation solver, or the VRP solver. It depends on your objective... Do you want to plan routes for drivers on a day-to-day basis, or do you want to figure out how to allocate cattle to processing centers, perhaps due to production-capacity constraints or for strategic planning on where to place processing/distributing centers? If it's for day-to-day routing, you could use the VRP solver. Otherwise, you could use the Location-Allocation solver. My understanding, but I'm not confident I understand correctly, is you need Location-Allocation. If that's right, you could divide the problem into two parts: the first solve would be to choose processing plant locations (load ranches/farms/feedlots as demand points and processing plants as facilities), the second solve would be to choose distributor locations (load processing plants as demand points and distributors as facilities). Can you please elaborate on the problem a little more so I, or someone else, can try to provide a better response? Thanks, Robert ... View more

Hi Karalyn, I tried to reproduce the issue but am unable to do so. I wish I could help you on this, but your best option now would be to contact Esri Technical Support. Robert ... View more

Hello, It sounds like the data became corrupted, which is strange. I can't say how that happened. If you delete the tutorial data and replace it with new data (the data is here), does it work? Also, are you using ArcGIS 10.1? Robert ... View more

Brent, This is what I tried: I downloaded the statewide NJ data. Created a network dataset without doing any pre-processing (i.e., I didn't run Integrate). Used the state plane coordinate system of the original data and any-vertex connectivity. 80+ incidents solved in the Closest facility layer I created (albeit with non-optimal routes due to connectivity issues). Luckily, one of the random locations caused the closest facility solver to fail as you described. The location was at 391014.512, 675271.703 feet. It appears to be a cul-de-sac. Next, I did the following: Ran Integrate on the road data. Rebuilt the network dataset to incorporate the changes. (emphasis added here just for the off chance this step was missed previously.) And set up the same problem but on a new CF layer. The problem was fixed. Can you send the data if you continue to get the same errors? Thanks, Robert ... View more