Latest Contributions by ChrisDonohue__GISP

A possibility - If you have ArcGIS 10.2 (or later), there is a handy new tool that allows one to change field names of an existing feature class. Alter Field (Data Management) http://resources.arcgis.com/en/help/main/10.2/index.html#//001700000198000000 As always when working with field names, be careful that you adhere to naming conventions and consider what effects the naming will have on downstream uses. Chris Donohue, GISP ... View more

That clarifies it. Can you post an image of your model schematic?  I'm curious why the new fields would not be carried over.  Seeing the model components may help in identifying what is going on. ... View more

To clarify what you want, is the goal to not have certain fields transferred from the input to the output? Chris Donohue, GISP ... View more

Here's a guess based on something different between the ArcGIS help code example and your code: Instead of: arcpy.env.workspace = Workspace Use: env.workspace = Workspace Based on ESRI's sample code in: Checking for the existence of data http://resources.arcgis.com/en/help/main/10.1/index.html#//002z0000001p000000 I'm not an expert on Python; but maybe that one syntax change may resolve the issue. Chris Donohue, GISP ... View more

Neil and Chad have some good points to consider for anyone doing analysis.  What they mention are essentially best practices in organizing data for analysis.  By doing these best practices, one will avoid many headaches and help insure the results you get are valid. To summarize: 1.  Start out by making sure all the inputs have projections and coordinate system before anything else.  If they already have a projection, but it is not he one desired, use a process to convert them to the one desired.  As Chad alludes to, avoid the pitfall of assigning a desired projection to something that already has a projection - instead, use one of the several methods to convert from the current projection to the desired one. 2.  Expanding on what Neil mentioned, it's usually best to take a feature class with joined data and combine it into one dataset before running analysis.  Take the joined dataset and create a new feature class from it.  This new feature class will permanently have the joined data in it, eliminating potential issues due to the Join.  Then check the result.  Note that it is common for issues in field names to crop up here, so checking it (and then editing your input Excel table to resolve them, if needed) is important.  For example, look out for field names in Excel that contain restricted characters, have spaces, are very long, etc.  Also, check that the data types are as expected.  For example, did a string field become a number type when it should of stayed string?  The bigger reason for doing this is that it identifies potential common issues before the model runs and blows up, or returns unexpected results. Chris Donohue, GISP ... View more

Another idea - I can't tell from your diagram, but is the Clip tool used the "Clip (Data Management)", not one of the other "Clip" tools?  There are several Clip tools, but the Data Management one is the specific one that does rasters and probably the one to use. ... View more

Sounds like a projection issue.  I don't know the exact issue going on, but here are some things to try to help isolate the issue: 1.  Check the projection and coordinate system of your Kriging output to see if it is what you expected.  If the Kriging result came out without a projection, you may have to define a projection for it. 2.  Check also the Data Frame projection and coodinate system to see what it is. 3.  Check the clip shapefile to see what it is. Chris Donohue, GISP ... View more

Another way to differentiate the three - use the same dataset (with the complete data/all your oil/gas operators), but use a "Definition Query" to limit it to each individual operator. To do this: 1.  Add the data into ArcMap 3 times. 2.  Right-click on the first dataset in the Table of Contents 3.  Click on the "Definition Query" tab. 4.  Click the "Query Builder" button. 5.  From the top part, double-click on the field for the Operators. 6.  Click once on the equal sign button. 7.  Click once on the "Get Unique Values" button. 8.  Int he middle window, double-click on this operator name. 9.  Repeat on the other two copies (in ArcMap) for the other two operators. Why do this instead of making 3 copies, you might ask?  The reason is for data integrity - you only have to worry about editing one dataset if there are any changes need to be made to the data in the future. ... View more

What the software is doing is by default coloring every combination of the two fields as its own color.  And if there are many combinations, it will sometimes re-use colors, adding to the chaos. The simplest way to resolve this is to manually recolor all your combinations.  Tedious and time consuming, yes, but workable. The more elegant way is to write code in Python that automatically assigns the color and size according to your criteria.  I have seen that done, so know it is possible, but have not done that particular challenge myself.  It would take some time to research the specific coding needed to make this happen and then test it, but it might be worth it if you forsee doing this symbolization with many times with many files. ... View more

As Dan mentioned, the underlying code is protected. However, ESRI does expose some of it, so people can do development. Historically, the restrictions ESRI has have changed over time, so it might be best to contact ESRI Tech Support and ask where things are at for your particular situation. ... View more

I dont' know if this will specifically work for Buffer 3d, but if you are looking for Python code for a tool, you can often get it from running the tool, then exporting the Python Snippet.  Check out Dan Patterson's posts (part-way down) in this recent thread - he details how to do this: https://community.esri.com/thread/116880 Another avenue might be to delve into the world of ArcObjects.  However, that is a more formidible environment than Python for most, and has a much steeper learning curve. One potential issue - in the past ESRI has stated that they do not expose all of their code, so be aware that there are some processes that may not be available. Chris Donohue, GISP ... View more

And I need to ask, in case I missed an obvious issue, is the data already developed into a feature class or shapefile?  If not, that would have to happen before it can be symbolized. ... View more