<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Chaitanya - I believe the normalized/laundered message is a non-issue at this point. I only get that message when I repeatedly run my Bash script against the folder of shapefiles - so it's changing the 'filename' column to 'filename_1' when creating a new column.</div><div><br></div><div>I really like your idea of sqlite and will give this a try. Thank you very much _ joe</div><br><div><div>On Nov 29, 2012, at 9:54:49AM, Chaitanya kumar CH <<a href="mailto:chaitanya.ch@gmail.com">chaitanya.ch@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Joe,<br><br>What was the full warning message about the normalized/laundered field name? Field name is modified when the name is longer than 10 characters or when a field with same name exists.<br>Check the name of the newly created field.<br>
<div class="gmail_extra"><br>As per the update command, I don't think the update command is implemented in the ogr sql yet. You can do it in the sqlite format, among other rdbms formats. Use ogr2ogr to convert it to sqlite. update it. convert it back to shapefile.<br>
<br><br><div class="gmail_quote">On Thu, Nov 29, 2012 at 8:58 PM, Joe Larson <span dir="ltr"><<a href="mailto:joe@joelarson.com" target="_blank">joe@joelarson.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>I have tried these three methods to add a filename column while scripting a folder of shapefiles, with a Bash script - which results in `Warning 6: Normalized/laundered field name` & `ERROR 1: SQL Expression Parsing Error: syntax error` messages and NULL values in the created column :</div>
<div><br></div><div>#1<br><br>for f in *.shp;<br><br>do<br><br>name=${f%.shp}<br><br>ogrinfo $f -sql "ALTER TABLE $name ADD COLUMN filename character(10)"<br>ogrinfo $f -sql "UPDATE TABLE $name filename = '$f'"<br>
done;<br><br>#2<br><br>for f in *.shp;<br><br>do<br><br>name=`echo "$f"|sed 's/\.shp$//g'`<br><br>ogrinfo $f -sql "ALTER TABLE $name ADD COLUMN filename character(10)"<br>ogrinfo $f -sql "UPDATE TABLE $name filename = '$f'"<br>
done;<br><br>#3<br><br>for f in *.shp;<br><br>do<br><br>name=`basename $f .shp`<br><br>ogrinfo $f -sql "ALTER TABLE $name ADD COLUMN filename character(10)"<br>ogrinfo $f -sql "UPDATE TABLE $name filename = '$f'"<br>
done;</div><div><br></div><div><br></div><div>There's an example here <a href="http://trac.osgeo.org/gdal/wiki/FAQVector" target="_blank">http://trac.osgeo.org/gdal/wiki/FAQVector</a> called "How do I include the source filename in a field when merging hundreds of shapefiles (Windows)?" I also cannot get this to work - getting "unrecognized fieldname" message.</div>
<div><br></div><div>Perhaps my variable does not work in the Bash SQL statement. I'm not sure what's going on in the Windows example.</div><div><br></div><div>Regards,</div><div>Joe Larson</div></div><br>_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br></blockquote></div><br><br clear="all"><br>-- <br>Best regards,<br>Chaitanya kumar CH.<br>
<br>+91-9494447584<br>17.2416N 80.1426E<br>
</div>
</blockquote></div><br></body></html>