PROBLEM
A shapefile unknowingly containing m-values can lead to unexpected downstream behavior, particularly in workflows that involve format conversions. For example, if a shapefile with m-values is converted to CAD data through a third-party application and then an attempt is made to import the resulting CAD data into a feature class through an ArcGIS Pro geoprocessing tool, the following message can be returned unless the 'Output has M Values' setting is set to 'Disabled' in the geoprocessing tool's 'Environments' tab.
"WARNING 000594: Input features <value> falls outside of geometry domains"
ArcGIS Pro geoprocessing tools that can create a new feature class have the Output has M Values environment setting in their 'Environments' tab that can be adjusted to the values 'Same as Input' (the default value), 'Enabled', or 'Disabled'. A description of this setting's values are referenced below:
While it may be expected that if the 'Output has M Values' setting within a geoprocessing tool is set to 'Same As Input' (if the geoprocessing tool's input does not have m-values) or 'Disabled', then the feature class created through the geoprocessing tool will not have an m-value, that is not the case if the feature class created is specifically a shapefile with z-values.
Due to the storage of m- and z-values being closely connected for shapefiles, a shapefile created through a geoprocessing tool that has z-values will also have m-values, regardless of what value the 'Output has M Values' environment setting is set to within the geoprocessing tool. See the tool reference: Output has M Values (Environment setting)
To prevent a feature class from being created that unknowingly has m-values enabled through a geoprocessing tool, either of the following can be done with the assumption that the input for the geoprocessing tool does not have m-values enabled:
If a shapefile is created through the geoprocessing tool, create a shapefile through the geoprocessing tool that does not have z-values enabled. The workflow to ensure that z-values are not enabled when creating a shapefile through a geoprocessing tool is referenced below:
If z-values must be enabled in the feature class created through the geoprocessing tool, create a feature class through the geoprocessing tool that is stored in a geodatabase as a file geodatabase feature class instead of in a folder as a shapefile. The workflow to ensure that the feature class created through the geoprocessing tool is stored in a geodatabase as a file geodatabase feature class is described below:
next to the parameter to open the dialog box, navigate to a geodatabase in the dialog box, type a name for the feature class next to Name, and click OK to close out of the dialog box.Article ID: 000038535
Get help from ArcGIS experts
Start chatting now