Difference between revisions of "Map Index"


Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179

Deprecated: Creation of dynamic property PPDStack::$accum is deprecated in /home/dogtaton/public_html/giswiki/includes/parser/Preprocessor_DOM.php on line 803

Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179

Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
From GIS Wiki
Jump to: navigation, search
(Created page with "A map index is used with a grid to locate features in a map. This will describe how to generate the index for the street map. The street map index looks like this: *ABBOT'S L...")
 
m
Line 14: Line 14:
 
Select the dissolved layer for Target Features, select the grid for Join Features, leave it as a 1-to-1 join.
 
Select the dissolved layer for Target Features, select the grid for Join Features, leave it as a 1-to-1 join.
 
In the field map of join features, right click the field with the grid cell id ("Grid_Num" in this example) and open the properties. For Merge Rule select "Join" and for a delimiter enter ", "
 
In the field map of join features, right click the field with the grid cell id ("Grid_Num" in this example) and open the properties. For Merge Rule select "Join" and for a delimiter enter ", "
 +
You might also need to increase the length of the field to accommodate a long list. If you get an error like "ERROR 001156: Failed on input OID 507, could not write value '13K, 13L, 14L, 14M, 14N, 14O, 14P, 15P, 15Q, 16Q, 16R' to output field Grid_Num" then the field was not long enough. I set it to 1000 so it will succeed and then later I'll manually cull the culprits like "PRIVATE DR" and "PUBLIC ALLEY".
 +
 +
Export the table to excel where you can do a lot of tweaking to your preferences and get a good balance of number of columns vs column length in order for the index to fill available space so the text is as large (thereby readable) as possible.

Revision as of 21:59, 2 April 2015

A map index is used with a grid to locate features in a map. This will describe how to generate the index for the street map.

The street map index looks like this:

  • ABBOT'S LN: 17K, 17L
  • ABBY WAY: 15O
  • ACME ST: 15J
  • ACORN BEND: 20L, 20M

It's a list of street names followed by a list of the grid cells that contain the street.

First, dissolve on the feature class being indexed. Dissolve is in the toolbox under Data Management Tools > Generalization. Select the centerline layer for Input Features and select FULNAME for the dissolve field. Other settings can be left as defaults.

Next, do a spatial join of the dissolved class to the grid. Spatial join is in the toolbox under Analysis Tools > Overlay. Select the dissolved layer for Target Features, select the grid for Join Features, leave it as a 1-to-1 join. In the field map of join features, right click the field with the grid cell id ("Grid_Num" in this example) and open the properties. For Merge Rule select "Join" and for a delimiter enter ", " You might also need to increase the length of the field to accommodate a long list. If you get an error like "ERROR 001156: Failed on input OID 507, could not write value '13K, 13L, 14L, 14M, 14N, 14O, 14P, 15P, 15Q, 16Q, 16R' to output field Grid_Num" then the field was not long enough. I set it to 1000 so it will succeed and then later I'll manually cull the culprits like "PRIVATE DR" and "PUBLIC ALLEY".

Export the table to excel where you can do a lot of tweaking to your preferences and get a good balance of number of columns vs column length in order for the index to fill available space so the text is as large (thereby readable) as possible.