SHP can't handle Z and M value in the same time.

[leaf]

1. Create a shp file and set geometry to point, haselevation to true and hasmeasure to true.

2. Close connection to this shp file and reconnect to it.

3. Describe schema.

Result: Geometry's hasmeasure property value is false.

[leaf]

​http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf

According to SHP specification, Mmin and Mmax is equal to 0.0, if not Measured type. If the shapefile is empty (that is, has no records), the values for Xmin, Ymin, Xmax, and Ymax are unspecified. Mmin and Mmax can contain "no data" values for shapefiles of measured shape types that contain no measures.

However, SHP provider always uses "no data" no matter shp file contrains measured shape types.

[leaf]

The previous submission doesn't fix this defect compeletely. After inserting a new feature without m value, FDO provider will still update values of Mmin and Mmax and it will use "no data" value to override the original value 0.0. It result in geometry value of a geometry property without measure contains m value. So the fix is to check whether the m value of newly added geometry is "no data" value. If yes, don't update values of Mmin and Mmax.