Latest Contributions by DrewFlater

Hi Martin, Can you check your system environment variables for a PYTHONPATH variable and report the value if that key exists? To get to environment variables: 1. hit windows keyboard key + pause key to open System dialog 2. On the left side of the window hit "Advanced system settings" 3. on the bottom of the dialog that opens click "Environment variables..." 3. Look in both the user and system variables for PYTHONPATH ... View more

Martin, You mentioned you have Python 3.4 installed -- is this the "Python 3.4.1 for ArcGIS Pro" installation that is described here or an installation you downloaded and installed from python.org?? Thanks, Drew ... View more

Hi Ann, please contact Technical Support and provide the model to them so that we can get the error identified and addressed. Thanks ... View more

Adam, please contact Technical Support so they can identify what is different about your configuration and get this addressed. Thank you ... View more

You can accomplish this by stringing together a few geoprocessing tools. First use Select Layer By Attribute to select all of the business of your desired type. Next you can use the Generate Near Table (Analysis) tool with your house point as input and your selected businesses as the Near Features. Uncheck the option towards the bottom to "Find only closest feature". Now you have the distance from your house to all of the selected businesses. Just look in the table, sorted by NEAR_DIST to see which business is the closest, and you can run Summary Statistics (Analysis) to determine what is the average/MEAN distance. If you want to do this process for your home and many types in your business layer you will need to set up a model to iterate based on unique values in a field. You can search for "Iterate Field Values" in the ModelBuilder documentation to learn more. Good luck! Drew ~Esri ... View more

The issue has been resolved in 10.1 Service Pack 1. You can read about SP1 and download it here http://support.esri.com/en/downloads/patches-servicepacks/view/productid/160/metaid/1913#choose-product Good luck! Drew ... View more

Hello Matt, I'm glad you got that bit working. I was also going to suggest that you can check out this extension shared on ArcGIS.com: ArcPhoto. It provides a lot of interesting functionality all centered around mapping digital photos. Drew ... View more

Hello Matt, according to the tool help there are two requirements for attaching the photos to the feature class: 1. You must have at least a Standard license (Basic license does not support attachments). 2. The output feature class must be in a geodatabase of at least version 10. Do you meet these requirements? Thanks, Drew ... View more

Hi Stacywood, Will you please describe more about how the projection is wrong? Are the points on the map in a location that you do not expect? If you could provide one sample image (and the city/area where you think it should draw on the map) I would be happy to look into the problem. All the best, Drew -Esri ... View more

This is a known issue with both the Append (management) and Merge (management) tools, which we will attempt to address as soon as possible -- you can follow the issue by using the identifier NIM081084. Both tools support table views and feature layers, but the bug prevents a table view made from a feature class from being appended or merged with a table. You can append or merge a table view made from a table with another table. For the time being, the recommendation above to copy your table view to a temporary table using the Copy Rows (management) tool is the best solution. You can even copy to the in_memory workspace so that you don't have to consider cleaning up this intermediate data. Regards, Drew - Esri ... View more

A quick note before my response: for the 10.1 release, 5 new tools have been added to the Data Management Tools toolbox for adding and managing attachments. This will make working with attachments in general much easier, especially when doing batch jobs. With that said, the issue of attachments not being carried over to new geoprocessing outputs has not been addressed, so a workflow like I describe below will still be necessary and applicable. Learn more about the Attachment toolset Geodatabase attachments are stored as BLOBs in a table which is connected to your feature class via a relationship class. You can find this associated table and relationship class in the same geodatabase as your feature class (they are named the same as the feature class, but with __ATTACH and __ATTACHREL suffixes). Like you have observed, when a geoprocessing tool creates a new output from the feature class, as the Project (management) tool does, the attachments associated with the input feature class are not carried over to the output feature class. Here are a few steps you can do to "re-relate" the attachment table that stores the attachments with your new output feature class. 1. Add a Long Integer field to the input named 'IN_FID', and calculate it equal to the input's ObjectID field. We want to keep track of these original ObjectIDs since the attachments relationship class uses ObjectIDs as key fields, and many geoprocessing tools may reorder ObjectIDs, especially in the case where there are some values missing. 2. Run the desired geoprocessing tool, like Project (management). 3. Right-click the output feature class and create/enable Attachments. This will create an empty __ATTACH table and a relationship class relating that table to the output feature class. 4. Delete the output__ATTACHREL relationship class. 5. Use the Append (management) tool to append the original feature class' __ATTACH table into the output feature class' __ATTACH table. The __ATTACH table is where the attachments are actually stored (in a BLOB field) so appending these records is a key step. Input Dataset = input__ATTACH; Target Dataset = output__ATTACH. 6. Right-click on the output geodatabase and select to create a new relationship class. The origin will be your output feature class, and the destination will be the output__ATTACH table (the target dataset from Append). This relationship class should be Composite, 1 - M, with No messaging and no additional attributes. Select IN_FID as the primary key field, and REL_OBJECTID as the foreign key field. That's all! Your output feature class will now have the same attachments as your input. Let me know if you have any questions, and good luck! Drew - Esri ... View more

I'm very sorry for the difficulty everyone is having with the slow-downs for the Feature Class To Feature Class (Conversion) tool. As has been indicated above, Esri knows about a performance issue with this tool that was introduced in 10.0 SP2. In that service pack, new functionality was added so that when geodatabase data with attribute domains is converted to shapefile (which does not support domains), a new field is added to the output shapefile to maintain the domain description information. The short story of the problem is this additional step of adding the domain description text causes large increases in processing time. This issue is being worked on in 10.0 Service Pack 5, and will provide significant improvements in performance. In addition to the performance improvements, in the 10.1 release, a new geoprocessing environment is added so that you can control if domain description information should be maintained in the output. People on this board have replied with some good workarounds -- you can use the ArcMap Export function, or use the Copy Features (Management) geoprocessing tool to copy your geodatabase data to shapefile -- neither of these methods will maintain domain descriptions so performance will be superior. Good luck to everyone, Drew -Esri ... View more

There is a sample tool called Divide At Line that you can download from the Geoprocessing Model and Script Tool Gallery. Divide At Line This essentially does a few overlay operations to split the geometries and attributes at either a drawn line or a line layer. The attributes in the output will be divided proportionally by the area of the new geometries divided by the area of the original geometry. A key part of this analysis is the use of the Ratio policy option of the Make Feature Layer (Management) tool. You can learn about that here. Good luck! Drew -Esri ... View more

An easy way to share data is to use the Package Layer (management) tool to convert your feature class/layer to a file that you can email or upload. I'm glad that you've found a workaround, but if you can provide your data I would still like to investigate the problem. Thanks, Drew ... View more