Packaging layers with ArcMap joins and relates
Check the Save Picture as Part of Document check box and click OK.Ĭomputer-aided design (CAD) layers are always copied into the data package, and they will not be converted to the chosen format.Right-click the picture in ArcMap and point to Properties.Pictures inserted into a map document that reference the file on disk will not be packaged however, if you save the picture as part of the document, it will be packaged. When you publish the map, the picture will be embedded in the published map. If no path is present, the ArcReader Identify and Hyperlink tools will look for the hyperlink file in the published map's folder. If your hyperlink attribute contains the file name, you can place the file in the same directory with the published map. You could also create hyperlink paths prior to publishing that are specific to the data package you plan to create. The hyperlinks will also need to be updated to reflect the file location in the data package.
If you are using hyperlinks that reference files, the files will have to be copied into the data package manually. Packaging layers with file-based hyperlinks Clipping the raster could change the minimum and maximum values and cause all the colors to shift. Some renderers stretch colors across the minimum and maximum values of the raster. Packaging raster layers with the clip settingĬolors can shift when rasters are clipped. In these cases, an underscore is used to replace the reserved character or is added to the reserved name.įor example, LANDCOV# is converted to LANDCOV_ when packaged as a shapefile. Some data formats support field names that contain characters or names that are not supported in another data format. If field truncation occurs and causes field names to be the same, the last character will be replaced with a number. Unique field namesĪll fields must be unique. If you view the map in ArcReader, field truncation may not be evident, because the Identify tool displays the field alias. If you package data to a format that supports a shorter character length, the fields will be truncated.
Geodatabases have a 31-character limit (30 in geodatabases in Oracle or DB2). Shapefiles are limited to 10 characters for a field name. The following situations may cause the field name to change. If a layer is symbolized on a field that is modified, the layer symbology will display with default symbols. Packaging attribute fieldsīe aware of the following limitations that do not cause packaging errors but may cause unexpected symbol rendering in the map. The following types of limitations do not cause error messages or warnings. The loss or modification of some cartographic functionality may occur. It is important to keep in mind that all the parts of one data type may not be interchangeable with the parts of another data type. There are a number of things to be aware of when packaging published maps, ranging from data conversion incompatibilities to unsupported functionality in the map.
0 kommentar(er)
