<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Starting with v2.1, ogr2ogr supports
args X_POSSIBLE_NAMES, Y_POSSIBLE_NAMES which are strings with
allowed wildcards (eg, Lon* ), or you can use field_1, field_2,
etc to explicitly give the position of lat/lon.<br>
It's explained on the <a moz-do-not-send="true"
href="https://gdal.org/drivers/vector/csv.html">driver page.</a>
This <a moz-do-not-send="true"
href="https://gis.stackexchange.com/a/276607/4449">StackExchange
</a>post shows csv to shapefile conversion and included Windows
command line syntax for looping over files in a directory.<br>
<br>
On 11/15/2022 12:58 PM, Hugh Kelley wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOrcXHFH8RA4LhS-KrufiPVEL7TgQeHQnZxjGsQuEeWr8JhBjg@mail.gmail.com">
<div dir="ltr">
<div>David, this was my first thought when i saw this question
as well.</div>
<div><br>
</div>
<div>however, I didn't look for very long but I haven't seen a
way to tell ogr2ogr to read columns in a csv as the lat/lon
and write those as points to the shapefile. I generally write
a csv to postgres as a non-spatial table and then process the
lat lon columns with postgis. <br>
</div>
<div><br>
</div>
<div> Are there arguments for ogr2ogr that can do this?</div>
</div>
</blockquote>
<br>
</body>
</html>