patel1684

The Best Practice for Authoring a MXD

Blog Post created by patel1684 on Sep 3, 2016
  1. Setting map document properties:

    The Map Document Properties dialog box contains fields and options that help you make your map document more usable.

    Click on

    File>Map document Properties

    Fill all related details.

     

        You can define how path references are maintained in your document by checking or unchecking Store relative pathnames to data source.

  2. Prepare data:

    The layers and tables that you add to the map document will be exposed by the service.

    Data must be from shapefile, file geodatabase and enterprise geodatabase.

    Data must have a valid spatial reference defined for it.

    Data spatial index provide quick rendering while use in map service.

    All data must be from a single database.

    Feature classes that use binary storage (such as SDEBINARY or OGCWKB) cannot be used.

    If you want to edit the data through a feature service, connecting users must be granted the required privileges—insert, update, and/or delete.

    For read-only feature services, the tables that participate in the feature service must contain a unique integer column to be used as an object identifier.

    Query layers published to a feature service can contain data from only one table; the query cannot join data from other tables.

     

     

  3. Tips on improving map display performance:

    As an ArcMap user, it's always important to explore ways to increase the display performance of your interactive map documents.

    Using the Analyze Map tool to analyze and improve display performance.

    The Analyze Map tool helps you to improve the drawing performance of your ArcMap documents by generating a list of potential display performance issues.

    Each problem description guides you to suggest updates that you can make to your map layer to address the issue and improve map-drawing performance.

    Steps: Click File > Analyze Map on the main menu

    The Prepare window with its list of Errors, Warnings, and Messages will be displayed.

    Using basemap layers to precompute your map display.

    Basemap layers are flexible and easy to manage. They manage themselves automatically so little work is required to define them in your map documents. Essentially, you can add and remove the layers in your basemap layer as needed.

     

  4. Documentation for Layers and Map:

    Layers used in create map document have metadata information like
    Tags.
    Summary.
    Description.
    Credits.
    Use limitations.
    Extent.
    Scale Range.

     

     

  5. Compact database:

    Monitor the size and performance of local geodatabases.

    As performance degrades, compact the database.

    Schedule a regular cycle for compact the database.

     

  6. Optimize ArcMap table of content:

    Empty layers negatively affect redraw and refresh rates, remove empties.

    Turn off unnecessary layers for visualization.

    Keep symbology simple by using basic colors and symbols, complexity increases redraw performance.

    Limit fills if possible complex fill patterns have a detrimental effect.

    Avoid using advanced drawing options.

    Optimize selectable layers.

    Manage selectable layers based on extraction.

    Queries are generated against the database for all selectable layers.

     

     

  7. Avoid external data sources:

    Create an ancillary dataset and load necessary support data.

    Keep all data in the same spatial reference.

    If unavoidable, generate spatial indices for external files, sample shapefiles, and ccoverages

     

  8. Avoid joins and relationships:

    Often unavoidable some models rely on establishing these table relationships.

    Try adding the tables that participate in the join / relationship to ArcMap.

    If used during a collection task, remove join/ relationship when possible.

     

  9. Scale suppression:

    Reduce layers drawn at smaller scales limit admin boundaries, cell boundaries, and so on.

    Manage scale based on the representative scale.

     

  10. Monitor MXD size and performance:

    MXDs may become fragmented or excessively large.

    Periodically perform a Save as command and save a new version of the MXD.

    Performing a Save as command removes unnecessary information from the MXD.

    If an MXD becomes corrupted, attempt to salvage it using the MXD Doctor.

     

  11. Optimize spatial indexing:

    Update the spatial indices to enhance spatial query performance.

     

     

  12. Keep data on local machine:

    If necessary, try to keep client and server on the same operating system generation.

    Easiest to remove network issues.

     

  13. Spatial performance tips:

    Avoid complex symbology.

    Create indexes for fields used in queries symbology and labeling.

     

Outcomes