POST
|
I realize this is somewhat old at this point, but wanted to report that the Microsoft update noted in this article fixed this problem for me: Bug: The error message, "Can't reach this page" is returned when launching help (See Update 1/25/2019 at the bottom of the page)
... View more
02-05-2019
03:44 PM
|
2
|
2
|
2684
|
POST
|
If you don't need to retain any attributes, you can just use the Multipart-to-Singlepart tool after the dissolve-all. If you want to retain the attributes of the features that don't overlap, you can then run a spatial join afterwards, using the buffer polygons as targets and the original points as the join features. There are a couple options on dealing with the merged buffer polygons. Or am I not understanding your question?
... View more
08-13-2018
09:40 AM
|
1
|
0
|
1272
|
POST
|
If I understand your question correctly, you just need to choose Dissolve Type "All" when you do the buffer.
... View more
08-13-2018
08:12 AM
|
0
|
4
|
1272
|
POST
|
You could export the model to python and attach the code. Even more helpful, you could run that code in the python window and provide the results. Also, did you download the data from a site to which you could provide a link? At this point unless I can see exactly what you're doing and what data you're doing it to, I really can't speculate on what might be going on. Maybe someone else has an idea from what you've provided so far, but I would need to see exactly what you're working with.
... View more
06-12-2017
09:36 AM
|
0
|
3
|
737
|
POST
|
To get further on this, I think we're going to have to see your exact job stream. Did the same error appear when you ran the Copy Raster tool, or the next step in your job stream? It's difficult to tell from your posts. You said previously that the error you are getting was: ExecuteError: ERROR 999999: Error executing function. The table name is invalid. No spatial reference exists. The table was not found. [NetCDF_Raster.tif] Failed to execute (CopyRaster). I'm wondering about the "The table name is invalid" part - the problem may not have anything to do with the spatial reference.
... View more
06-09-2017
11:03 AM
|
0
|
6
|
1629
|
POST
|
Have you tried saving the raster layer to an actual raster before running the other processes?
... View more
06-09-2017
09:46 AM
|
0
|
10
|
1629
|
POST
|
Are you able to run the Make NetCDF Raster Tool outside of Model Builder? Might be time to attach a sample of your data and your code. The error message seems to indicate a naming problem.
... View more
06-09-2017
08:35 AM
|
0
|
12
|
1629
|
POST
|
I haven't used netCDF files in quite some time, but the tools to pull out the individual layers are in the "Multidimension Tools" toolbox; you'd want "Make NetCDF Raster Layer". See the article http://desktop.arcgis.com/en/arcmap/10.4/manage-data/netcdf/reading-netcdf-data-as-a-raster-layer.htm. My memory is that when you enter an input netCDF file, you'll see a drop-down list of variables contained in the netCDF file - you'll have to see exactly how the data are organized in your files. Then it's easy to pull that tool into model builder (if you know how to use it, that is).
... View more
06-07-2017
04:14 PM
|
1
|
1
|
1629
|
POST
|
It would take some more work, yes, and I really don't have any more time to spend on this. But you said you already had the section lines, correct? You can just merge the two together and you'll have everything you need.
... View more
05-16-2017
03:33 PM
|
0
|
1
|
1047
|
POST
|
Right, I've used that tool and it works well. But doesn't do what this person is asking, as it doesn't take into account existing PLSS corners...
... View more
05-16-2017
03:22 PM
|
1
|
0
|
889
|
POST
|
Oh, sorry I forgot to tell you - the same thing happened to me. The script works from the XY coordinate fields in the attribute table of your point layer. You'll need to re-calculate geometry on those fields in your test layer, as they are incorrect in the layer you sent.
... View more
05-16-2017
01:51 PM
|
0
|
0
|
1047
|
POST
|
The selection distance should not have the units - it should be numeric. When you set the parameters in your script tool, make the Distance data type "Double", not "Linear unit". That should do the trick.
... View more
05-16-2017
11:54 AM
|
0
|
2
|
2141
|
POST
|
Sorry about that, it was a coding error, updated code attached. I tested with your point layer and it seems to work fine.
... View more
05-16-2017
11:20 AM
|
1
|
4
|
4219
|
POST
|
You'll need to make the distance parameter a bit larger than half the typical side of a quarter-section, which is 2640 ft. Try 3000 ft instead, and it should work fine. The script goes through all section centers (the points labeled 'CNT') and connects the center to each of the quarter-section points (labeled 'QRT'). If the script doesn't find exactly 4 points, it will print a warning, as you saw (in each case it found 0 points because your search distance was too small). When you run it on your full layer, you can use those messages to fine-tune the distance. As I indicated before, the script may not work well if your sections are too far from square. In those cases you would need to connect the points by hand if you use this tool. Also, I edited the script to create quarter and quarter-quarter section lines - the one I posted only created quarter-section lines. I've attached the updated one.
... View more
05-16-2017
09:53 AM
|
0
|
9
|
2141
|
POST
|
I've attached a tool that you can use to create the interior quarter-section lines as I described in my post. In the zip there's a toolbox/script together a sample sections layer, a sample point layer, and mxd. It's a fairly simple script without much error-checking, but the workflow would be the following: 1) Run the script using your point layer as input; it will produce a text file of the interior quarter-section line segments as output. There's a distance parameter that I've defaulted to 1000 that you may need to adjust - the distance units are the same as your input point FC. It should be a bit larger than a typical side of a quarter-section (2640 feet, so I set the default to 1000 because the projection of my input point file had meters as the distance unit). The point of the parameter is that it needs to be big enough to select only the four quarter-section points closest to the section center, and no more. If you have sections that are really wonky, it may not work very well.. 2) To convert the coordinates in the output text file to a FC, use the "XY to Line" tool (Data management/Features) - make sure to set the projection to that of your input point FC. The x- and y- coordinate fields to use should be obvious... 3) Merge these lines into your section lines (which you said you already had), and you'll have your quarter-sections. Let me know if you need any clarification! Chris
... View more
05-12-2017
12:17 PM
|
0
|
11
|
2141
|
Title | Kudos | Posted |
---|---|---|
1 | 07-07-2023 01:40 PM | |
1 | 06-07-2023 04:07 PM | |
1 | 05-18-2023 11:02 AM | |
1 | 02-27-2023 03:41 PM | |
1 | 11-04-2022 04:30 PM |
Online Status |
Offline
|
Date Last Visited |
2 weeks ago
|