This little toolbox is a thing of beauty. Been looking for a tool like this for years. Works in 10.3.
I did not have the sequential value problem described such as 2,24,15,3,8. It worked fine and now I have text that I can create custom indexes without all the dissolving and joining and then editing in excel.
Thanks so much for this. A big timesaver!
Hope someone is working on the suggestion also mentioned to create not only the page number index but also a page internal grid such as JOHN DOE ST Page 1 C2, D2, Page 2 A2.
Blessed are the programmers who make a cartographer's life easier.
I have come up with a simple solution to the dreaded Create Street Index. Just read the README to see how it works. I do hope this helps.
I am dealing with a similar issue and have found that the Spatial Join tool does what your tool does. Then you simply create a report to display the Index Table.
My problem is that I need more than the page number. I need to have not only the page; but, the grid reference.
EXAMPLE
Facility Page/Grid
Fire Departments 22 (A3), 31(D1), 6(G6), 8(C1)
In addition, the data for the grid i.e. the columns and the rows (A2 etc,) is in the layer properties at the beginning of the Table of Contents.
Any help would be greatly appreciated.
Lance
In regards to capturing the page and index grid on the page "Page 5, D2"... what I have done in the past is when I create my page layout (using the data driven page tools) I also create a second grid with a page size that matches the in-page grid. It take a little work to attribute that grid with a "column" value ("A" through "D" or whatever) and a "row" value (1, 2, 3...). Then I actually capture my street name text as annotation, convert to a point, and overlay my detailed grid.
This gives me an index value of the actual label on the map, not just the feature itself. Indexing just the road feature is sort of "cheating" in cartography. But I admit, it's a whole lot easier to index the feature to a page, and I have done it too.
This is a great tool. Although I must be missing a step somewhere in the workflow if anyone would like to comment. The problem with the output is that even though a file is created with a field that joins street names to a page grid based on the grid square number, or page number, that field is populated with only one page number. Some streets cover multiple pages. What I need is that field to contain the page numbers covered by each street, whether it be one page number or several page numbers. In the join output field properties there is a dropdown list called merge rule with several options (First, Last, Sum, Mean, Median, Mode, Count, etc) I have tried each one and none seem to create the output file with a field in the attribute table where the page number will display more than one page associated with the grid .. example. Main Street will be on pages 34, 35, 36, 37 the output file will only display 34. Even if you run mean, median, mode and then merge fields together that does not work. Also, doing that will not work for all of the features in the table where lines cover four or more pages, there would still be need for a significant amount of manual entry to correct remaining records, kind of would defeat the purpose of the tool. Any suggestions? Thanks.
Ryan,
One thing to try is on the "Field Map of Join Features" on the "PageNumber" field (or whatever your particular field name is. make sure you set the output field properties. Right click on the PageNumber, select type "text" on on properties make sure you set length large enough to encompass your potential range of values. I typically use 100 and set the "Allow NULL Values" to "Yes". Set the "Merge Rule" to "Join" and I use a comma "," as the delimiter to separate the page number value results.
I typically open the resulting dbf up in Excel and clean up a little, usually with the concatenate function and then do the actual index page layout in Powerpoint and export to PDF to insert into my mapbooks.
Hope I understood your question and that this helps.
Mike
Please see below..
Sincerely,
Scott Jackson –Dir. of Geospatial Services
Heart of Georgia Altamaha RC
5405 Oak Street, Eastman, GA 31023
(478) 374-4771 | (478) 374-0703 fax
<mailto:jackson@hogarc.org> jackson@hogarc.org
<http://www.hogarc.org/> www.hogarc.org / <http://www.hogarc.org/> www.hogarcmaps.org
Michael and Scott, thank you both. Scott, thank you for such a great tool. I followed the work flow and it worked perfectly! ESRI is definitely missing out not having this in toolbox. Michael, I usually run the same clean up with my indexes also in excel before placing them in adobe, great on this one though, no duplicates in the output.
You might take a look at this idea that has been posted on the ArcGIS Ideas page.
Indexing Capability for ArcGIS 10 Mapbooks (data driven pages)
-Timothy