|
POST
|
You can add the Iterate Feature Classes iterator to the end of the model so that will iterate through each feature class and delete them. Set a precondtion that the final output needs to be created before the iterator runs.
... View more
06-08-2012
02:02 PM
|
0
|
0
|
1096
|
|
POST
|
I assume you've checked for leading or trailing spaces in the field names? Is the data available to share?
... View more
06-07-2012
04:52 PM
|
0
|
0
|
5111
|
|
POST
|
Take a look at the tiling options when printing a map about three quarters down the page. You can choose to Tile Map to Printer Paper, which will print multiple sections of the map.
... View more
06-07-2012
08:27 AM
|
0
|
0
|
3062
|
|
POST
|
It appears as though one of the layers in the map has a transparency set on it; the grey polygon with red outline. Correct me if I'm wrong, but this also may be the topmost layer in the table of contents. If so, what's happening is that the layer with the transparency is being rasterized, (or turned into an image), and all layers beneath that layer with the transparency are being rasterized as well, resulting in one Image layer. Take a look at this resource regarding exporting to pdfs, and why layers in the Table of Contents of ArcMap don't match the layers in the PDF. Finally, regarding the "Other" layers in the pdf, I'd suggest you play around with grouping all layout elements by selecting them, right clicking on one element, and clicking Group. This will create one "Other" layer in the pdf.
... View more
06-06-2012
03:19 PM
|
0
|
0
|
2571
|
|
POST
|
Take a look at these two resources; this one is a blog that describes a model that populates a parameter with values in a field, and this one is the link to the model from the resource center geoprocessing gallery.
... View more
06-06-2012
02:38 PM
|
0
|
0
|
7223
|
|
POST
|
Have you considered using an in_memory workspace? If you don't need the intermediate data that are created in the geodatabase, you can set the outputs of the data that would've been written to the geodatabase to an in-memory workspace, i.e. a clip could write to in_memory/clip_result. This clip_result feature layer can then be used in later processes in the model, but after the model finishes, it will be deleted. One thing to note, if this is an intensive model, in that it creates a lot of intermediate data, you might be better off saving to the geodatabase. In that case, take a look at the use of intermediate data to manage data that is not needed after the model completes.
... View more
06-06-2012
01:53 PM
|
0
|
0
|
1096
|
|
POST
|
This page should get you going. If feature templates aren't created automatically when you first start an edit session, you'll have to create them manually. At 10.1, they will always be created automatically.
... View more
06-05-2012
01:16 PM
|
0
|
0
|
557
|
|
POST
|
Use the Add Join tool under Data Management Tools > Joins as many times as you need to perform the join, then use the Feature Class to Feature Class tool under Conversion Tools > To Geodatabase, (you can save it as a shapefile or feature class depending on the location), to create a layer that permanently contains those additional fields. You'll probably have to use the Make Feature Layer tool if you're bringing in a shapefile or feature class as the input Layer Name or Table View.
... View more
06-05-2012
10:39 AM
|
0
|
0
|
613
|
|
POST
|
It sounds as if you'll just want to use the Select by Attribute tool three times in your model to select for the three different feature types. After each individual selection, you'll want to use the Calculate Field tool to calculate whatever values you need to for the inspection date. If you have any selected features in a table, any operation you run will only run on those selected features. The default selection method of NEW_SELECTION will make sure that each successive selection will overwrite the previous one. A rough model showing the process is included below. Is that something that makes sense for your workflow, or are you looking for something else? [ATTACH=CONFIG]14805[/ATTACH]
... View more
05-31-2012
07:55 AM
|
0
|
0
|
2495
|
|
POST
|
Can you share your model so we can take a look at it? I assume you're using an iterator, such as Iterate Feature Class, (which will work with shapefiles), and then building your model off of that. What values are you calculating into the field?
... View more
05-30-2012
04:43 PM
|
0
|
0
|
733
|
|
POST
|
Another method you can use in the future is the Select By Attribute function to select all records in that field that are null, then the Field Calculator to calculate a 0 for those records; if you have records selected in a field, the field calculator will only run on those records.
... View more
05-29-2012
07:49 AM
|
0
|
0
|
2583
|
|
POST
|
As tonylocandro mentioned, it is not recommended or advised to edit a dbf of a shapefile outside of ArcMap, as it is easy to corrupt data. As for saving an Excel sheet as a dbf, in the Catalog window in ArcMap or ArcCatalog, expand the excel sheet to bring up the individual pages. Then, right click on it > Export > to dBase (single). This will allow you to save the Excel sheet as a dbf.
... View more
05-25-2012
08:24 AM
|
0
|
0
|
10544
|
|
POST
|
Take a look at this blog, that describes in detail the benefits of the Make Query Table tool in creating a one to many join.
... View more
05-11-2012
03:50 PM
|
0
|
1
|
802
|
|
POST
|
I was just taking a look at the Excel sheet you provided; when I bring it into ArcMap and look at the field headings, they show values that don't match up with the headings in Excel: [ATTACH=CONFIG]14237[/ATTACH] I copied and pasted all of the cells into a new .xslx file, saved it, and when I brought that table into ArcMap, the field headings came in correctly: [ATTACH=CONFIG]14238[/ATTACH] The points to line and buffer tools worked successfully using point data created from this Excel sheet. Do your field headings look correct when looking at the attribute table from the Excel sheet?
... View more
05-10-2012
08:04 AM
|
0
|
0
|
2712
|
|
POST
|
Take a look at the Iterators for ModelBuilder. The one you're looking for is the Iterate Files iterator, and you can specify to only look for .txt files. It will iterate through each file to use in the rest of the model. Once it's done with that one .txt file, it should jump to the next one in line, and run through the model.
... View more
05-03-2012
02:58 PM
|
0
|
0
|
560
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-26-2016 10:10 AM | |
| 1 | 02-22-2024 07:22 AM | |
| 1 | 06-07-2024 07:11 AM | |
| 3 | 12-12-2024 08:52 AM | |
| 1 | 03-20-2024 12:35 PM |
| Online Status |
Offline
|
| Date Last Visited |
07-01-2025
04:40 AM
|