Latest Contributions by MelindaMorang1

Keep in mind that ArcMap is a 32 bit application. The network analysis layers such as OD Cost Matrix layers are in-memory layers. Thus they are limited to the overall 2 GB limit. With ArcGIS 10.0, you can run ArcMAP on a 64 bit OS and then that process can access up to 4 GB RAM. So you can solve larger problems. With the upcoming 10.1 release, the ArcGIS Server is true 64 bit app and can access all the RAM you have and will scale even more. You can export the OD to any supported format such as dbase or file geodatabase. And in that case the output has to obey the limits of that particular format. Note that file geodatabase do not have limits whereas dbase does. That said, how big of an OD are you trying to generate? Does the OD solve work and the export fail due to dbase limits? Note that if you do this in ArcMAP, then it has to create and populate the output lines. That table can grow quite large. If you cannot break up/chunk the OD into smaller ones to solve/combine results, then you should consider using an ArcObjects app (.net?) to create the OD (and tell it not to populate the output lines) and directly query the ODCostMatrix object to dump out the data you need. To break up an OD such as 1000 by 1000, you can solve two 500 by 1000 and combine the results. Jay Sandhu ... View more

To clarify: It's not a web service.  It's a downloadable custom ArcToolbox script tool created with python. The ultimate goal of the tool is to be able to figure out the area reachable by walking and transit from a given point.  To do that, you need to know the network distance between that point and the transit stops you could walk to within the time limit.  However, you also need to know the network distance between the transit stops themselves.  Someone might, for instance, walk for one minute to get to a stop, get on the bus and ride for 10 minutes, get off the bus and walk for 5 minutes to another stop, and then get on a different bus and ride some more until the time runs out.  So, we also need to know the stop-stop network distance to calculate how long it takes to walk between stops. We solve this problem by just calculating one big OD matrix for all the stops, within a cutoff distance.  We've separated this part of the tool so you only need to do it once for any city, and you can calculate many different service areas without having to run the long part over and over.  The OD matrix just sits in an SQL table that the code can refer to. ... View more

If the layer name that you are after is lines, you should be able to just get it with networkAnalystLayerName+'\\Lines' (where networkAnalystLayerName is the name of the layer you are doing the network analyst stuff on) , i.e.: # if NA_Layer is the variable for your network analyst layer arcpy.Solve_na(NA_Layer) lines = NA_Layer + '\\Lines' Then you will probably need to copy features (i.e. arcpy.CopyFeatures_management(lines)) and do your modifications on the output of copy features. ... View more

Yes it is possible. Each origin as the Cutoff_,attribute name> property that can be set. So if you are solving on a length attribute in miles called Length, then the origins attribute table has a field called Cutoff_Length. You can set it individually for each origin. Or better yet, when you do a Load Locations, this property is listed, so simply map it some field on your existing origins point feature class and have it loaded with the origin locations. Similarly the facilities on the service area solver have a Break_<attribute name> property. You can set it how big of a service area you want computed. And again, you can use Load Locations to load it as well. Regards, Jay Sandhu ... View more