Latest Contributions by BarbaraSieg

From the SMP PDF "ArcGIS® StreetMap™ Premium Custom Roads—ArcGIS Pro 2.4" (and 2.5): "For each consecutive release of the StreetMap Premium Custom Roads product, you should always maintain your data within one of the three feature classes: Custom_Streets, Custom_Streets_Override and Custom_Turns. Editing of Routing_Streets or other feature classes and tables associated with the StreetMap Premium Custom Roads network dataset is against the terms and use of the product license." Your changes should be confined to the custom elements. ... View more

In the field map control of the tool, right-click a field name > Properties and change the field name and its alias in that dialog. ... View more

See the Help topic "Tool layers based on your model and script tools": http://resources.arcgis.com/en/help/main/10.1/index.html#/Tool_layers_based_on_your_model_and_script_tools/00210000003p000000/ "The capability to create a tool layer was removed at version 10.1. Tool layers in ArcMap documents created prior to version 10.1 can still be used in 10.1." From this information, you won't be able to add tool layers to a map in 10.1. ... View more

In the toolbox script object, set the parameter property "MultiValue" to Yes. This turns the input into a multi-value control and maintains the data type. ... View more

Models have a state that is maintained when you run from the Model Builder window. Intermediate data is preserved between model runs, etc. Running a model from a toolbox is not the same; refer to the "Running models" topic and its associated links in the 10.1 Help:   http://resources.arcgis.com/en/help/main/10.1/index.html#/Running_models/002w0000005m000000/ Within Model Builder, you may need to delete intermediate data and re-validate the model. ... View more

You can update layer properties with python scripting, but only as a blanket override of all layer properties at once. This means you will need a layer file on disk or another layer in a map (could be the same map or a different map) with the desired symbology to be applied to the target layer. First try it out manually to see if you get the desired results in the layer properties > symbology > Import command before writing a script. See the Help docs for the Python syntax and examples:   http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/UpdateLayer/00s30000003p000000/ Exporting to JPG:   http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/ExportToJPEG/00s300000038000000/ If applying a layer file to the existing layer doesn't do what you need, then you won't be able to do it with Python scripting, but you can always do it with ArcObjects code. ... View more

The capability to do this in Python does not exist in 10.0. However, in 10.1, there is a Python function UpdateLayertime:   http://resourcesbeta.arcgis.com/en/help/main/10.1/index.html#/UpdateLayerTime/00s300000064000000/ that allows you to replace the time properties of a layer with the time properties of a different layer or layer file. This can be done whether or not the target layer is time-enabled. ... View more

You'll need a table with the following two fields in it: 1. OwnerID from some field in the parcel shapefile attribute table that has the same value for all occurrences of that owner. 2. Permit number, as a numeric or string field, whatever suits your purposes. Is there such an OwnerID in the parcel shapefile attribute table? If not, you'll need to add a field and populate it with a value unique to each owner, otherwise there's no way to automate the task. It could be the owner name, for instance, or some other ID value. Owner name may not be spelled exactly the same for every occurrence of that owner, so it may not be a good field to use. If there is no suitable field, you'll have to create one. In this as in most map automation tasks, the major effort is in preparing the data. Once the necessary data exists, the operations on the data are generally straightforward. If you have such a separate table (with OwnerID and Permit number) external to the shapefile, fine. If you don't have such a table, you can create one from the parcel attribute table: In a map, open the parcel attribute table and export the table from the table options menu as a new stand-alone table to DBF or geodatabase format. In the exported stand-alone table, you can delete all the fields except the OwnerID, or you can leave some fields if desired. There are probably multiple records for some owners. In ArcView 10, use the Delete Identical tool on the exported table:   http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Delete_Identical/001700000053000000/ This removes all but one record for each unique OwnerID. Then add a field for the Permit number and populate it manually. Now you have a table with one record for each unique Owner ID. The next step is to Join the stand-alone table ("Tbl") to the shapefile on the OwnerID field: that is, in ArcMap, right-click the parcel layer > Joins & Relates > Join > Join attributes from a table. In the Join wizard, the field in the layer is the OwnerID, the table to join to this layer is Tbl, and the field in Tbl to base the join on is the OwnerID field in that table. Set the option to keep all records. If you are running 10.0, validate the join. In any version, allow the tool to create an index on the join field, if asked. View the joined layer attribute table. At the right side of the table you'll see the fields from Tbl. A join is in effect within the map but does not permanently alter the shapefile attribute table. If you want to save those fields in the shapefile attribute table, do one of two things: 1. Right-click the joined layer > Data > Export Data, and export the joined layer to a new shapefile or feature class in a geodatabase. Or: 2. Add a field (same data type as the Permit field) to the parcel layer attribute table. Use Field Calculator to copy the values from the joined Permit field into the new field, then remove the join. ... View more

For information on dbf tables, view the Help documentation for creating a new dBase table:   http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Creating_a_new_dBASE_table/005600000005000000/ This references another topic on adding fields:   http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/by_adding_a_field_in_ArcCatalog/005600000006000000/ For fields in dBase tables, "A field's name must be no more than 10 characters in length...", so if there is no other reason to create the table as a dbf, create it instead as a geodatabase table. Also, where is the dbf being created? The script workspace is a gdb, and the table name has no qualifying path. ... View more