POST
|
I am having the same problem. Many of my MXDs no longer have the "default" I set them to, but have reset themselves to the default.gdb in my home directory.
... View more
11-10-2015
12:50 PM
|
0
|
0
|
734
|
POST
|
The same thing just happened to me, after numerous successful runs. There were no special characters in path or name. Working wiht FGDB rasters. I rebooted and ran the model again, and it worked. So I supsect another ArcGIS moment or momentary Network blip
... View more
06-03-2014
08:20 AM
|
0
|
0
|
442
|
POST
|
I am combing multiple rasters and having problems joining stand-alone tables to get the descriptive attributes. I have separated this into several models because two of the input GRIds and stand-alone tables change with each run, and there 7 runs. Setting these up as parameters that I could change just did not work. In model builder, it does not "see" the field in the combined rasters until it has run and made the combined raster. The attributes show as Band1-bandx. Even though some of the attributes will be the same, when the model is run on another set, it flags it as an error when I enter the expected attribute. What an I doing wrong? I Guess I could create a model that combines the rasters, then a second model that joins the attributes.
... View more
05-28-2014
11:37 AM
|
0
|
0
|
360
|
POST
|
Thank you for the explanation and the suggestion for stand alone tables. The stand alone tables are working, just another step or two in the process. I also found the suggestions for stand alone tables on another post. So it sounds as if I'd be better off by making all of the VAts with descriptive attributes stand alone, then join them as needed when combining the GIRDs. Actually only one of the inputs is raster to begin with, everything else is Vector. Its just that when we converted the raster to vector, then tried to overlay it with other vector data, the process blew up after a few hours
... View more
05-15-2014
10:55 AM
|
0
|
1
|
2553
|
POST
|
Exporting VATs to independent tables then joinig those tables back to combined GRIDs worked:) Somtimes if I did a join directly back to the GRID, I would only get the column names of the joined table, but none of the values. It would be nice if the Combine function or others allowed you to keep descriptive attributes
... View more
05-15-2014
10:17 AM
|
0
|
0
|
1328
|
POST
|
Is this also the solution for a simple combine with rasters with descriptive attributes? I need to combine/overlay 8 or 9 rasters. The combine works fine, but I lose the descriptive attributes, and have to get them back into the combined grid with a Join operation. A little tedious, but it works, usually. I just had a join fail. It added all the fields a join would add, but the records were all NULL for the joined items. So I did a virtual join, and calculated the null values to the the values in the joined table. I would do this in vector, but it keeps blowing up (maybe it is the network here, but this also happens on a local drive). Only one of the datasets started out as raster, which was vectorized, but doing these as polygons fails, immediately or after several hours. So the vector data all had to be rasterized. Combing the rasters takes about 2 minutes.
... View more
05-15-2014
09:39 AM
|
0
|
0
|
2553
|
POST
|
I have a problem with auto complete polygon in 10.2.1. It is in a topology. The auto complete creates an error / completes incorrectly. Polygons are adjacent to areas outside the polygon, and sometimes those outside areas extend skinny fingers into the polygon, creating a void. In 9.x and 10.0 I was able to use autocomplete polygon to fill in that "finger". Now when I try it, it seems to capture all of the void area outside the polygon, not just the "finger" The only solution I found was to create a new feature with the free-hand or rectangle create feature tool, then merge the new feature into the exsiting polygon.
... View more
04-14-2014
02:49 PM
|
0
|
0
|
559
|
POST
|
ArcGIS 10.2. I am having a problem with ArcMap or ArcCatalog crashing when I try to validate topology. Only one rule - must not overlap, 139 features,2.4 MB. I have tried zooming in to just a few features, as well as really zooming in to an area where I suspect there is overlap. Have tried network location, C drive, network licenses, checkout licenses, creating new GDBs and new topology. I have also tried a repair geometry, then running the topology check. I will try to find a another computer - maybe there is something "wrong" with the one I am using. This also happened in 10.0 SP4, but seemed more random. Usually validate worked, but sometimes decided to crash consistently for several days
... View more
04-03-2014
06:59 AM
|
0
|
0
|
681
|
POST
|
I am having a problem with Validate Topology - ArcMap Crashes, with "unexpected Problem caused.....". Arc 10.2 Windows 7. I only have one rule - must not overlap. It is a buffer of selected streams, dissolved. 136 features in the buffer. Only one feature in the GDB, 2.7 MB. I have tried several approaches - zooming in to one or two features, really zooming in to an area I suspect has an overlap, creating a new GDB, importing the feature and creating a new topology. I have also tried validating in ArcCatalog after creating a new topology. I also tried a check out license vs a network license and moving the data from Network to Local drive. I also did a repair geometry then tried to validate.
... View more
04-03-2014
06:49 AM
|
0
|
0
|
1052
|
POST
|
I got this error message when trying to cut a polygon "The Cut Polygons task could not be completed. An Unknown error has occurred". Using 10.0 SP4. I zoomed out a little more, and cut the polygon in a different placed, and it worked. Even better, it got rid of the topology error I was trying to fix. The topology error was rather strange. It got picked up as a gap, but when I created a feature from it it had a value of "0" for the shape properties. I did a check geometry, then a repair, but those Null areas remained. We are having network issues and I was getting other oddball error messages with topology, so I copied the FGDB to the harddrive, but not seeing much improvement in fixing/finding errors. The area I am working on is quite large with a wide range of shapes& sizes of polygons.
... View more
02-21-2014
06:49 AM
|
0
|
0
|
5438
|
POST
|
I have been experimenting with higher tolerances, both in geoprocessing operations used to create data and in topology checks, it helps. I have not tried integrate, and will try that as well. The validate "not doing anything" is really strange, almost as if I did not really click on the button. Once in an edit mode I'll opt to validate, and the validating "status" (?) bar never shows. When I open the errors table and search, none are found. At first I thought this happened because there were no errors, but that is not the case. Getting validate to "work" ranges anywhere from removing/re-adding the topology toolbar, to stopping/restarting the edit session, to stopping/restarting ArcMap, to recreating the topology rules, to rebooting, to waiting and hoping that tomorrow is a better day. The extent of the data sets I am working with: Top 2781031.158307 m , Right -1079966.152815 m, Bottom 2208890.238787 m, Left -1715664.866530 m
... View more
09-11-2013
08:37 AM
|
0
|
0
|
1902
|
POST
|
I am experiencing the same problem, fixing numerous topology errors very slow and sometims does very strange things. Using Windows 7, ArcGIS 10.0 Sp4. Almost 1000 overlapping polygons which I either need to create features and dissolve (everything is the same for a particular attribute) or subtract and hav even more holes in the data. The layer was created by appending two sets,created by different organizations, and many of the polygons share borders . Yesterday with a different layer , creating features from topology errors, it took over an hour to create features for 1500 overlaps. When done, I discovered that it had also calculated a numeric field and a character field as well. It calculated the character field with Chinese and Japanese (according to google translate). Also have problems with validate topology not doing anything. No rrors, but it does not do anything
... View more
08-27-2013
08:08 AM
|
0
|
0
|
1902
|
POST
|
I've completed what I need to do for the time being, but will try your suggestion when things slow down, it would definitely be more efficient than the step-by-step approach I ended up using. I was trying these operations both in Windows 10.0 SP4 with data on the network and in windows 10.1 (Sp?) with data on the local hard drive. The 10.1 usually worked, while 10.0 usually failed. 10.0 also failed to load tables into a newly created FGDB table - both directly from GRIDs and from ascii output from those GRIDs - it just did not "see" them. 10.1 worked. In raster calculator it would be nice to be able to chose the "Lookup" function (and other functions) so that "case" is not an issue, as well as being able to select the "item" to use in the lookup.
... View more
06-26-2013
06:43 AM
|
0
|
0
|
590
|
POST
|
"Lookup" usually fails in raster calculator, even when I run the same process from "results". Here is the process I'm trying to run in raster calculator. If it worked, I'd like to string together the 10 rasters I am working with. lookup("veg2_p34_Weiser","veggie_minus_Tall") Can I use lookup to mosaic rasters? The reason I do not want to use mosaic, is that cannot specify the item to use in mosaic ( or at least I have not found the sytax), and I'm getting frustrated having to create new GRIDs with the value from the item I want to use
... View more
06-25-2013
07:19 AM
|
0
|
0
|
590
|
POST
|
Having the ability to use attributes in Raster Calculator would be really nice, why was it taken away? I don't care if it is the old "dot" syntax or some other syntax. Please bring it back, soon. I need to merge/mosic 11 GRIDs which presumably do not overlap, but might a little around the edges as as artifact of how they were created. Mosaic does not let me use an item either. Two text items have to be used for the desisred attributes in the GRIDs. So I've concatenated the two fields into a new field, then added added a new field for an integer crosswalk of the concatenated fields. I plan to mosaic the GRIDs after adding & calculating the two new fields in all of them, thne using the "lookup" function to create new grids with value = newfield, hten mosaic. What a lot of work. Is there an easier way ? ( speaking of merge, the merge function was really nice too, why was it disappeared?)
... View more
06-19-2013
01:25 PM
|
0
|
5
|
12139
|
Title | Kudos | Posted |
---|---|---|
1 | 03-13-2012 11:11 AM | |
1 | 10-04-2012 08:04 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|