POST
|
I have noticed that selection is iffy when you zoom in to extreme scales.
... View more
12-20-2011
07:53 AM
|
0
|
0
|
2062
|
POST
|
Sam, I think you could still use the Attribute Assistant. It works as an add-in and uses a couple of tables that you add to your map. Here is the documentation pdf. The tables are DynamicValue and GenerateID. The pdf explains what fields need to be in each table. There is a post here that states what the field names need to be in the GenerateID table (I had trouble with the field names not working). The pdf explains how the different value methods work. You may need to use a combination of methods to get what you need. I use it to generate new ids for my address points and populating the street name, direction, city, zip fields. It took me a while to get it to work, but once I did it was worth the effort.
... View more
12-20-2011
07:22 AM
|
0
|
0
|
520
|
POST
|
Is your layer selectable? You can right click on the layer go to selection and choose "Make this the Only Selectable Layer" or you can change the Table of Contents view to list layers by selection and change it there. Hope that helps
... View more
12-16-2011
09:38 AM
|
0
|
0
|
2062
|
POST
|
You can use the Attribute Assistant's Generate ID function. I use it when I create a new address point. The Attribute Assistant is an add-in that is part of the local government templates. Try here.
... View more
12-16-2011
07:24 AM
|
0
|
0
|
520
|
POST
|
Brad and Bruce, Is there any progress with bug NIM061830? I checked the bug page and it listed the status as "New" but it was posted over a year ago. I am having trouble with my locator created in ArcGIS 10 using the long chord of curves to place geocoding results instead of on the curve. I really don't want to replace all of those curves with vertices. Is this something that is fixed in SP3? Thanks, Jeff
... View more
12-07-2011
08:48 AM
|
0
|
0
|
345
|
POST
|
You need to do them one at a time. You select the line you want the other line to extend to, then you click the line that you want extended, using the tool. Hope that helps.
... View more
10-07-2011
01:28 PM
|
0
|
0
|
371
|
POST
|
Try the Check Geometry tool or the Repair Geometry tool.
... View more
10-07-2011
01:12 PM
|
0
|
0
|
280
|
POST
|
Are you sure you weren't using the Reshape Polygon tool?
... View more
10-07-2011
01:08 PM
|
0
|
0
|
583
|
POST
|
Also make sure that you have 0 records selected or the field calculator will only calculate values for the selected records. I can't tell you how many times I have put in a script and had it run without any errors but it didn't look like any of the field values were changed. They were changed, just the values for the selected records.
... View more
10-07-2011
12:57 PM
|
0
|
0
|
610
|
POST
|
Right click on the field and choose "Field Calculator", select the Python radio button at the top and make sure the Show Codeblock box is checked. Then select and copy lines of code in the first code block below and put them in the Pre-Logic Script Code block. rec=0 def autoIncrement():
global rec
pStart = 10000 #adjust start value, if req'd
pInterval = 1 #adjust interval value, if req'd
if (rec == 0):
rec = pStart
else:
rec = rec + pInterval
return rec If you copy from the above code block, it should keep the proper indentation. Then select and copy the below code and paste it into the box below YOURFIELDNAME = autoIncrement() That should run and get you the results you need. If not, you probably are trying to put a number in a text field or something. I have attached a screen capture of what my field calculator dialog looks like.
... View more
10-07-2011
12:55 PM
|
0
|
0
|
610
|
POST
|
Use the TRIM function. In a new column click on the first cell and click on the Insert Function button in the formula bar (fx). Enter TRIM in the search field and select TRIM from the results. Then enter the cell reference or choose the cell selector (grid looking tool to the right of the argument entry box). Then click OK. You can copy and paste that formula to the rest of the cells in that column. But I think you will then have to select the entire contents of that column you just created and copy it. Then go to the next empty column at the top and right click then select "Paste Special" and select "Values" from the choices. Then you can delete the column with the formula in it and what you have left is a column with the trimmed text values. ArcMap probably won't handle a formula in a cell. Hope that helps.
... View more
10-07-2011
12:12 PM
|
0
|
0
|
3470
|
POST
|
You might need to rebuild the locator. Right click on the locator and choose "Rebuild". I hope that helps.
... View more
10-07-2011
11:59 AM
|
0
|
0
|
250
|
POST
|
Thanks everyone for your help. Thanks for that link Dale, that is what I needed to get what I was calling a return value. I created a derived output string parameter for my script tool and added this line to the end of my script: arcpy.SetParameterAsText(0, fileName). Thanks again.
... View more
08-17-2011
09:02 AM
|
0
|
0
|
735
|
POST
|
Thanks for the quick responses. After looking into the output parameter, I have added my script to the model as a script tool and created an output parameter as a string type. The file name is hard coded into the script, so I don't have any parameters in the script. Do I need to create one for the setParameterAsText? Can you point me to some examples of what the a script with an output parameter looks like and I can figure out how to plug it into the model? Thanks again for the quick replies.
... View more
08-11-2011
02:25 PM
|
0
|
0
|
735
|
POST
|
I have a similar thing that I do in model builder that you could export as a script. When I do parcel updates, I get a new ownership table that I compare to the old one to find new records and changes in fields like acres parcel numbers and physical addresses. 1-Join the new table to the old table based on the common id 2-Make a table view with an expression selecting new records and records that have fields that don't match, also limit the view to show only relevant fields. 3-Create a new table and populate it with the rows of the table query. I first do a join based on the new table to the old table using the common ID field to join them together. I do that with the Add Join tool in the Joins subtoolbox in the Data Management toolbox. I then run the resulting table through the Make Table View tool in the Layers and Table Views subtoolbox of the Data Management toolbox. When I run that tool I specify a query that will select the new records (OldTableCommonID IS NULL) and any changed fields (NewTableField <> OldTableField) all of these connected by the OR logical operator. I also limit the table view to the four fields that I am comparing. I then create a new table with the Create Table tool in the Table subtoolbox of the Data Management toolbox. I base the fields of the new table on the table view created in the previous tool by having the table view be the input for the Template Table Name option in the Make Table tool. I then use the Append tool in the General subtoolbox of the Data Management toolbox to populate the new table using the records from the table view. I then go a step further by adding a field to the new table that would show which field has the change. I populate it by doing the Calculate Field tool in the Fields subtoolbox of the Data Management toolbox. That description is probably more than you needed, but I hope it helps
... View more
08-11-2011
01:48 PM
|
1
|
0
|
1337
|
Title | Kudos | Posted |
---|---|---|
1 | Friday | |
1 | 02-12-2024 07:49 AM | |
2 | 02-09-2024 09:52 AM | |
1 | 12-06-2023 08:12 AM | |
1 | 11-09-2023 09:03 AM |
Online Status |
Online
|
Date Last Visited |
27 seconds ago
|