In exported CSVs, have lat/lon columns in addition to the existing WKT column

[andrewbt]

Well Known Text is nice, but straight up latitude and longitude can be read directly by many other tools. IE, if you want to upload a CSV to CartoDB or ArcGIS.com or Fusion Tables, or another web mapping service, these won't read or parse a WKT column but they will pay attention to two columns with latitude and longitude.

Yes, shapefiles and KML are alternative export options, but as they currently stand trees and plots exist in the same shapefile but as two different attribute tables, which similarly makes mapping them with non-advanced tools difficult.

[andrewbt]

Also see "Reading CSV containing spatial information" in the OGR docs: http://www.gdal.org/ogr/drv_csv.html

"It is possible to extract spatial information (points) from a CSV file which has columns for the X and Y coordinates..."

[andrewbt]

Actually, another addition to play nice with PostGIS would be to use EWKT instead of WKT:

http://postgis.refractions.net/documentation/manual-svn/ST_GeomFromEWKT.html

[rcheetham]

+! on lat/long columns in the CSV. Almost no one knows how to deal with a
WKT column.

On Thu, Jul 25, 2013 at 2:17 PM, Andrew Thompson
notifications@github.comwrote:

Well Known Text is nice, but straight up latitude and longitude can be
read directly by many other tools. IE, if you want to upload a CSV to
CartoDB or ArcGIS.com or Fusion Tables, or another web mapping service,
these won't read or parse a WKT column but they will pay attention to two
columns with latitude and longitude.

Yes, shapefiles and KML are alternative export options, but as they
currently stand trees and plots exist in the same shapefile but as two
different attribute tables, which similarly makes mapping them with
non-advanced tools difficult.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/155
.