Error: map section is not entirely within the tile
Solution or Workaround
PUTTILE returns this message:
map section <coverage> is not entirely within the tile
It then bails out and returns to the Librarian prompt.
The coverage does not lie entirely within the rectangle defined by the BND of the tile's polygon in the .../DATABASE/INDEX coverage.
The fuzzy tolerances for the .../DATABASE/INDEX and PUTTILE input coverage should be similar. PUTTILE uses only the .../DATABASE/INDEX fuzzy tolerance to determine if features are within the tile boundary.
1. Run ARC RESELECT on the .../DATABASE/INDEX coverage:
Code: Arc: RESELECT TILENAME CN 'name_of_tile'
2. Run ARC TOLERANCE to set the fuzzy tolerance for the reselected coverage and the PUTTILE coverage to be the same as the .../DATABASE/INDEX coverage tolerance.
3. Run ARC CLIP on the PUTTILE coverage:
4. PUTTILE the clipped coverage.
Note: This error can occur with LIBRARIAN commands that copy data into the library or do the LIBRARIAN data housekeeping such as PUTTILE, ADDLAYER, INSERT, REPLACE and VERIFYLAYER.
Warning: Increasing the fuzzy tolerance of the .../DATABASE/INDEX coverage can cause features to be lost. LIBRARIAN commands often use the .../DATABASE/INDEX coverage fuzzy tolerance to process LIBRARIAN data. For help in determining appropriate fuzzy tolerances, see the "ARC/INFO Data Model, Concepts, & Key Terms" User's Guide, Appendix A: Coverage processing tolerances".
If you need to determine what feature(s) is outside the tile boundary, do the following.
1. Run ARC DESCRIBE to list all feature types in the coverage.
2. Use ARCPLOT commands to set the HIDDENSYMBOL be a distinct line symbol.
3. Set the map extent to be the PUTTILE coverages boundary coordinates.
4. Use ARCPLOT commands to display the .../DATABASE/INDEX coverage in one color. Then display each feature in some other color. You may need to zoom and pan along the tile boundaries to see the problem.
Optionally, use REBOX to recalculate the PUTTILE coverage boundary. The problem may be that the coverage.bnd has been manually reset and no-longer reflects the actual coverage boundary.