Two parts to this.
- Fix various errors in eBase before import so that they don't have to be made in two places. The problems are that when eBase trails was split into two parts, a whole trail part and a segment part, some fields were put in the whole trail but they in fact vary by segment.
- Import the data - test import says this should go smoothly once clean