
However I found a way around the problem - in the RouteProperties.xml there are some lines that seemed likely candidates, (see end of message) there they are! the Lat/Long and the UTM coordinates (in the Goofy Google format) with a bit of tweaking I was able to edit them and recover the situation.
The reason for this post is not only to pass on the information to others but also to ask if there's another way to back up that doesn't change the origin? Also how should I have created this route? Its a bit late now I am several weeks in but I may do another and I don't want to fall down the same hole!
Geoff
<Origin>
<sGeoPosition>
<Lat d:type="sFloat64" d:alt_encoding="50FC1873D7724240" d:precision="string">36.8972</Lat>
<Long d:type="sFloat64" d:alt_encoding="AC1C5A643B6F5EC0" d:precision="string">-121.738</Long>
</sGeoPosition>
</Origin>
<MapOffset>
<sMapCoords>
<Easting d:type="sFloat64" d:alt_encoding="000000003077FB40" d:precision="string">112499</Easting>
<Northing d:type="sFloat64" d:alt_encoding="00000000F9284F41" d:precision="string">4.08421e+006</Northing>
</sMapCoords>
</MapOffset>
<ZoneNumber d:type="sInt32">10</ZoneNumber>
<ZoneLetter d:type="cDeltaString">S</ZoneLetter>