Another vote for this. Working on a pretty simple survey with two repeatable sections. Have lines and polygons for only some of the data, at varying levels.

I need 3 CSV's for the non spatial elements, 3 SHP files for the lines, 3 SHP files for the polygons, and to import / export/ import them multiple times to build children with geometry under parents without geometry. The process doesn't work

I already have all the WKT strings in geometry fields in the csv's. It'd be so much easier if the import used this. After all that's what gets exported

Please implement this one! It would make importing child records so much easier when using advanced geometry. Right now you have to use shape files to import advanced geometry, but then there is a problem where you can only attach one shape file geometry at a time (point, polygon or line) so it makes importing parents and children of mixed geometries extremely extremely clunky. (see the feature request I lodged for 'seamlessly moving records from one fulcrum app to another' for a full description of this scenario). This problem would be avoided if we could just use a csv to import our point, lines and polygon geometries for parents and children all at once. If you need another test case to work out how to implement this, I have a simple test source and destination app and would be very happy to chat further! (llf@platypus.org.au)

Would be great to be able to provide/overwrite geometry with WKT coords, whether they are polygon, line, or point (could do all three types at once with WKT).