Hi @M_c3d
You have to go back to the SOURCE of the Object Data and that means going back to the shapefile itself, more specifically, the shapeifle's database file (dbf). Trying to look at the MAPIMPORT procedure and the data it captures is not the strategy that'll produce the desired results.
Is it possible to upload the shp, dbf, prj and shx so the elevation DATA can be thoroughly evaluated? If there's an m representing meters, or a tick mark such as ' (apostrophe) then you're looking at a STRING (text). In reality, though, the elevation value is numeric so integers or real (decimal) numbers without any extra characters is the 'data-type' topographic contours need.
While inside the shapefile's dbf, the 'DATA COLUMN' will need to be modified or edited to EXCLUDE the offending characters so the value can be numeric instead of string. Of course, this is all speculation since you haven't uploaded the dbf. It just seems easier to get rid of those extra characters in the database file as opposed to editing the object data after it's been captured during MapImport.
Once the elevations have been changed from string to numeric, then you can use Alter Properties function that's included in the MapImport command. The Alter Properties portion of mapimport will not only import the ESRI topographic contours as vanilla polylines, but it'll raise those contours to their proper elevations too.
Change the data (actually change the data-type) and the MapImport procedure, along w/ Alter Props, will perform flawlessly.
Chicagolooper
