I discovered that the shapefile reader (specifically in the AttributeTable class) does not allow exponent notation (e.g. "1.23e04") in floating point fields. I'm not sure if this is officially supported by the dbf file format, but I did run across a shapefile that contains these (see attached for a sample).
The solution is quite simple: add NumberStyles.AllowExponent to the number styles parameter in the parse statements. Since this is for reading only, it does not matter if officially supported or not. It will not affect reading or writing of "correctly" formatted shapefiles.
The solution is quite simple: add NumberStyles.AllowExponent to the number styles parameter in the parse statements. Since this is for reading only, it does not matter if officially supported or not. It will not affect reading or writing of "correctly" formatted shapefiles.