Latest Contributions by KimOllivier

I would think that the designer never expected a file geodatabase would have 9000 featureclasses. So it is likely that a buffer is overflowing. The obvious question is: Why are you modelling your problem with a separate featureclass per route? I regularly build a route system in a single featureclass with 200,000 separate routes, one for each road name. It performs normally. How about building the routes differently? I cannot conceive of any single process that takes longer than a cup of coffee to complete. If it takes longer than than, then interrupt the process and find a better way! I am confident that you could find a way to complete the same work in a few minutes. Do you have indexes for key fields? Are you running geoprocessing tools inside a cursor looping around each feature? Are you processing single routes when you could run a tool that processes them all in one step? ... View more

Yes, if you run from the command prompt you will not be using a Layer and will not have a selection. You will be accessing the featureclass directly because it happens to have the same name. Try renaming the layer different from the featureclass, run in Python window and then run the same script from the command line. It will fail with an error message "no such featureclass". To get the same count you would have to save the layer to a file while it has a selection and then reference that layer file (a definition of a featureclass with selection) in the command line. ... View more

I have found a geoprocessing tool which returns the side : LocateFeaturesAlongRoutes has a postive or negative distance to indicate the left or right side of a route. There is an optional flag to measure the side from the route direction or arc direction. So all you have to do is build a route system with an id of each arc for the route_id and then use it to find the side. ... View more

How do you know that you referenced the layer and not the underlying featureclass? If they have the same name (they do by default) then it might not be clear. ... View more

The standard tool interface has a feature type called 'featureset' (in the dropdown list that has featureclass, layer, string...) This enables you to sketch a graphic on the screen that is passed into the script as a parameter. The input parameter needs a layer template set to use as a symbol reference and to define the shape type : point, line or polygon and any attributes required. When you start the tool (by opening the dialog) you can draw some features and even fill in some attributes. In my script example I create a featureset called 'mpa' in my script and then save it to a featureclass after updating the ID. i then use it to clip some layers and run statistics. online help reference While you could at 10.1 use Add-Ins to track the mouse, it is overkill if you just want to enter a simple polygon, line or a set of points interactively. ... View more

I was quite keen on using in_memory for everything that I thought was small enough, but there are often strange problems, so I have switched to using a scratch file geodatabase for even tiny featureclasses. I recently was called in to debug a system that was failing silently to update a database and the problem went away just by switching from in_memory to a scratch.gdb. I have not been able to notice any difference in total elapsed time, and having fully capable featureclasses in a scratch geodatabase is a big advantage for debugging. You never know when it will be too big. If I want in-memory performance I use Python lists and dictionaries, numpy operators or try to do SQL queries directly in the database. I would still use numpy arrays for spatial operations if they have to be done in_memory. PIL (python image library) was a much better option when manipulating a lot of jpg images before image catalogs. At 10.1 you can use geometry objects for a lot more spatial operations. I suppose that is in-memory of a sort. So I tend to use these instead of a virtual file system. ... View more

I would never attempt to use a CSV file as an input table. There are just too many things to go wrong with the schema. Invalid fields names, incorrect guesses of fields types and null values. There are clearly differences when using the interactive interface in ArcMap, it must do a bit more validation such as checking for indexes. The first thing is to define a schema for the CSV using the Microsoft schema.ini definition. This helps the software stop having to guess the format of the CSV. Then it will load the rows into a nicely defined table with valid field names, instead of all numbers being floats and all strings being 255 characters. Next, copy the temporary virtual "CSV-table" into a Real Database table, such as a file geodatabase using CopyRows, something that can have a primary unique indexed key. Your join key can also be indexed and validated. For example if it is supposed to be an integer, if the field is defined as a float the join will not work. Now your JoinField tool has a chance of working. ... View more

Esri have changed their online geocoding service from free to paid. If we are all moving to the Cloud we will have to pay. The individual search to find a single location remains free which is why it worked on a test. Google do the same except with a few more, free search on a few, but a cutoff at 50,000 addresses. My performance was quoting using my own reference data to build a private locator on a local computer. If you have access to a reference dataset you can build your own locator, but it is so difficult most people would rather buy the service. ... View more

I have the same problem in the PythonWin screen (derived from IDLE with a windows front-end). I right-click to selectAll and then Cut. But it doesn't work in IDLE. Another reason to keep using Pythonwin. ... View more

I am getting the same issue, most of the times it bombs out around the 40K mark.  I am not hitting the file size limit and I have scrubbed the data to ensure there are no bad values.  Any suggestions?  I need to add around 1.4M addresses for my current project. I can happily geocode 1.6M addresses (full addresses) in 25 minutes with no problems in one process on a local PC. Maybe avoid a network share? I hope you are using a 10.x locator? Since you have scrubbed the data, it must be something else. At 10.1 you can tune the locator, memory allocated etc. You might get better performance by sorting on the required fields first. ... View more

Hi Brad, When you pass in an address without a unit designator to the get candidates method, addresses having a unit are ranked the same as an exact match without a unit.  This effectively means that the geocoding operation does not perform correctly for any location having secondary addresses (has units) AND a primary address (no units), such as an apartment building with a office at the primary address.  Roy Earlier in the forum this is exactly what was asked for. You can't please everyone all of the time. I would like this behaviour too, so I am fiddling with the configuration file to change it. ... View more

Yes, that is easy to select. You just have to do your own logic with the selected sets to add or subtract until you are left with the cases you are interested in. If you can logically describe to me what you need, you can create a program to do the same. That is what makes programming so fascinating. First you select intersected features (INTERSECT), and from that subset (using a layer) you select features that are touching (BOUNDARY_TOUCHES). You can then also remove contained polygons from the selection using CONTAINS. In my case I made up a separate selection to identify a group that I did not want (touching but outside) and used an attribute selection to remove them from the intersecting and inside set. It does not matter that an operator selects other cases you are not interested in if you have already selected them out so that you know that those cases do not apply for your set. Try it interactively using the SelectbyLocation option on some samples to get the logic. ... View more

I think your problem will be that a single point does not have an extent so you cannot zoom to it. You will have to create your own extent from the point by choosing a suitable buffer rectangle and zoom to that. ... View more