Bad Shp Output Solved!
OK, I found out why my shapefiles were screwed up coming out of kml_xml. The coordinate list must have NO whitespace (or at least, spaces) at the beginning of a coordinate line, and MUST HAVE at least 1 space (maybe other whitespace only tested with 1 space char) at the end of the coodinate line prior to EOL (xOdOa).
If possible, it might be helpful to try to get the coordinate parser more tolerent of whitespace.
scott s.
.
OK, I found out why my shapefiles were screwed up coming out of kml_xml. The coordinate list must have NO whitespace (or at least, spaces) at the beginning of a coordinate line, and MUST HAVE at least 1 space (maybe other whitespace only tested with 1 space char) at the end of the coodinate line prior to EOL (xOdOa).
If possible, it might be helpful to try to get the coordinate parser more tolerent of whitespace.
scott s.
.


Google Earth appears to me to only allow polygon level setting in meter increments. I settled for a 102 meter flatten surrounding my AFCAD airport runways at 102.1 meters and it looks reasonable. I will try sequential flattens later today to better merge into the surrounding areas.





