Closed GoogleCodeExporter closed 9 years ago
This issue was updated by revision r2001.
Add branch to work on this issue
Original comment by shawnlaffan
on 18 Nov 2013 at 2:33
This issue was updated by revision r2002.
Initial code and test.
Generates sensible shapefile, but we need to handle the various combinations
(and point data). Axes should also be the element_name_array values, not the
element_name_coord values.
Original comment by shawnlaffan
on 18 Nov 2013 at 3:18
This issue was updated by revision r2003.
Report element arrays in the dbf, not coords.
Add tests to check generated shapefile matches input.
Original comment by shawnlaffan
on 18 Nov 2013 at 3:41
This issue was updated by revision r2004.
Handle point files.
Original comment by shawnlaffan
on 18 Nov 2013 at 4:07
This issue was updated by revision r2006.
Handle text axes.
Refactor the subtest into a sub for re-use.
Original comment by shawnlaffan
on 18 Nov 2013 at 4:41
2-d is working. Need to handle 3-d data.
Original comment by shawnlaffan
on 18 Nov 2013 at 4:42
This issue was updated by revision r2007.
Add test for 3d data.
Exporting to 3d shapes is off the cars for now. It is messy, and seems not to
be often used. In the case of Biodiverse files one can use extrusion methods
given the relevant z-axis values.
Original comment by shawnlaffan
on 18 Nov 2013 at 5:38
This issue was updated by revision r2008.
Forgot to uncomment the file deletion in the last commit.
Original comment by shawnlaffan
on 18 Nov 2013 at 5:39
This issue was updated by revision r2013.
Merge changes across to trunk.
Original comment by shawnlaffan
on 19 Nov 2013 at 5:28
Original comment by shawnlaffan
on 22 Nov 2013 at 6:01
Need to add vertices in the correct order. Currently it is reversed, and this
causes issues with ArcGIS analyses.
Original comment by shawnlaffan
on 30 Nov 2013 at 11:35
This issue was updated by revision r2058.
Create polygon in the correct order (anticlockwise).
Original comment by shawnlaffan
on 3 Dec 2013 at 3:27
Remaining task is to export a .csv file if the field names exceed 11 characters
(the DBF limit). If they are all shorter than 11 characters than then we can
add the data to the shapefile itself.
Original comment by shawnlaffan
on 5 Feb 2014 at 2:08
Also need to allow point exports. This can be a flag in the export metadata.
Original comment by shawnlaffan
on 5 Feb 2014 at 3:58
See also relevant changes in issue 408.
It supports repeated shape exports for lists.
Original comment by shawnlaffan
on 3 Mar 2014 at 7:43
issue 408 also supports point exports, so this can be merged into it.
Original comment by shawnlaffan
on 3 Mar 2014 at 7:45
This issue was updated by revision r2344.
Delete branch since this issue was merged into issue 408
Original comment by shawnlaffan
on 18 Apr 2014 at 2:09
Original issue reported on code.google.com by
shawnlaffan
on 16 Nov 2013 at 9:34