|
POST
|
The presentation is interesting. The coding reminds me of back-in-the-day with Workstation ArcInfo! Chris Donohue, GISP
... View more
01-17-2017
12:35 PM
|
0
|
4
|
2974
|
|
POST
|
A quick "heads up" in case this is a new type of analysis for you - set aside time beforehand to determine what level of accuracy will be acceptable given your project needs and then during the analysis definitely ground truth your results. It is not uncommon with this type of analysis to mis-classify large amounts of data. Expect to do several iterations as the process gets refined. I'd start with a small plot where you already know what trees exists there and see what the analysis says it is, then tweak the settings/process to improve the results. Also, there always will be some level of error. The question that will need to be answered is what level of error is acceptable. Chris Donohue, GISP
... View more
01-17-2017
09:42 AM
|
1
|
0
|
3551
|
|
POST
|
To better understand what is going on, between when the mxd worked correctly in finding the data and when it didn't, can you elaborate on what happened? Was the mxd saved to a different location than previous? Was the data you are trying to link to moved? Are you on a different computer? Are you on a network? If so, are you using a different username/permissions? "None of the above" - No changes were made; instead the mxd was closed, then reopened but now the links are broken. Any other changes that you can think of? Chris Donohue, GISP
... View more
01-17-2017
09:26 AM
|
1
|
0
|
3346
|
|
POST
|
Another option is following Add Field to tag on a Calculate Field (Data Management) tool and then populate the field using the appropriate expression in the tool. Calculate Field—Data Management toolbox | ArcGIS Desktop Chris Donohue, GISP
... View more
01-15-2017
08:53 AM
|
0
|
0
|
1237
|
|
POST
|
A general suggestion - the City I work at automates this by running a Python script at night which Reconciles all versions so as to update them to Default. If any Conflicts arise, it stops and sends a message to the SDE Administrator notifying them of which versions had Conflicts. It is then up to the individual Version owners to resolve these Conflicts. Maybe you could implement the same process? I don't have the Python code for this, but hopefully some GeoNet users can point you towards a sample copy. Chris Donohue, GISP
... View more
01-15-2017
08:47 AM
|
1
|
3
|
1549
|
|
POST
|
In think Dan Patterson has the key. Be sure to check the point location (optional) settings in the tool for the one that matches your need. Also, note that an Advanced license level is required to run the tool. Feature Vertices To Points—Help | ArcGIS Desktop Some other thoughts: If you need to clean up your line data first, consider running a Integrate and then Dissolve in preparation for Feature Vertices to Points. Note that what settings you use for each of these will depend on how your data is organized. Integrate—Data Management toolbox | ArcGIS Desktop Dissolve—Data Management toolbox | ArcGIS Desktop Note that if there are two or more geoprocessing tools that need to be run in sequence that they can be run together using Modelbuilder or Python. What is ModelBuilder?—Help | ArcGIS for Desktop A quick tour of Python—Help | ArcGIS for Desktop Also, Geodatabase Topology can be of help in getting the linework coincident. Designing a geodatabase topology—Help | ArcGIS for Desktop Then of course, the final tool, once points have been derived Create Thiessen Polygons—Help | ArcGIS Desktop Chris Donohue, GISP
... View more
01-14-2017
08:47 AM
|
2
|
3
|
2893
|
|
POST
|
Not sure if this was already mentioned as a potential solution, but I'll throw it out. This will work if each feature that needs to be merged to another is be assigned the same value in an attribute field. The result of this tool will be a new (dissolved) layer as an output. For example, if I have several polygons that are coded "LDR" and several that are coded "MDR", they can be merged by running this tool, with the result being a "LDR" polygon and a "MDR" polygon. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Dissolve (Data Management) Chris Donohue, GISP
... View more
01-13-2017
11:09 AM
|
2
|
0
|
4287
|
|
POST
|
I think Dan is on the likely issue. Also, a question - is the line layer (streets?) being used as the Input Features (optional) when running the tool? Doing so will cause grids to just be created where the lines are. If things are still going awry, can you post a screenshot of your tool settings input just before running the tool. Chris Donohue, GISP
... View more
01-13-2017
11:03 AM
|
1
|
0
|
3132
|
|
POST
|
What appears to be needed is a the use of an In-line variable in the Calculate Field tool so you can use the result of the Get Field Value. You will have to code this manually - it won't be available by pulldown. So in your Expression in the Get Field Value tool, it would look something like this: fieldname = %Vel% The key is the percentage symbols on either side of the variable. In the model you posted, the output of the Get Field Value was called Vel, so one can tap its value by using %Vel%. From the Get Field Value tool help: The Get Field Value tool gets the first value from a table of the specified field, and the value is then used as an in-line variable in the expression of the Calculate Field tool to find the percentage area of each polygon. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Examples of Modelbuilder-only tools ArcGIS Help (10.2, 10.2.1, and 10.2.2) - A quick tour of Inline Variable Substitution Chris Donohue, GISP
... View more
01-12-2017
11:31 AM
|
0
|
0
|
2758
|
|
POST
|
My very first thought would be that it is a casting issue. However, that's just a guess. Can you post a screenshot of what the Calculate Field Dialog box information is? I.e. what information was input. Can you provide a screenshot? Chris Donohue, GISP
... View more
01-12-2017
09:33 AM
|
0
|
5
|
2758
|
|
POST
|
I believe these are the ones bharold-esristaff is referring to. Though I didn't see an explicit comment in the instructions that it would block export, just that it would block display. Maybe there is more to this than what is currently in the Help? Generate File Geodatabase License—Help | ArcGIS for Desktop Generate Licensed File Geodatabase—Help | ArcGIS for Desktop Chris Donohue, GISP
... View more
01-12-2017
07:40 AM
|
1
|
2
|
3127
|
|
POST
|
I don't know for sure if this is the case for your issue, but usually I find if I get "failure to draw" errors it is because I goofed on the Definition Query. For example, typically this happens as the Definition Query was originally set for a File Geodatabase and the data I want to draw is now in SDE, so the fieldname of Shape.Area bombs out as it should be SDE's Shape.STArea() (or whatever is appropriate for the geometry type used in SDE, be it STGeometry, SDEBinary, etc). So I'd check first your definition query for the specific field names to see that they match what is in the data in its current incarnation. Chris Donohue, GISP
... View more
01-06-2017
11:17 AM
|
2
|
2
|
13146
|
|
POST
|
There are several ways to convert lines to polygons. How it can be done varies by software/licensing: What version of the software to do have? What license level? Also, what have you tried? One option is to use the Feature to Polygon (Data Management) geoprocessing tool. However, this requires an Advanced license level. ArcGIS Help 10.1 One guess on what you are running into - I suspect one complication may be that the cased lines result in an "open ended" form, so some of the polygon creation methods fail as they don't know how to span the gaps. Chris Donohue, GISP
... View more
01-06-2017
08:59 AM
|
1
|
0
|
3718
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-18-2015 12:04 PM | |
| 1 | 09-29-2015 12:41 PM | |
| 1 | 11-29-2018 07:51 AM | |
| 1 | 05-08-2018 02:07 PM | |
| 1 | 07-26-2016 07:53 AM |
| Online Status |
Offline
|
| Date Last Visited |
08-03-2022
01:39 PM
|