<div>Hi Hamish,</div>
<div> </div>
<div>Yes, changing the default grid size fixed my problem. I initially read it as square meters (or assumed), however when i looked at it again i realised my mistake. I have been away most of last week so have not had a chance to progress any further with DEM creation.
</div>
<div> </div>
<div>As far as making the shapefile available it is around 5mb in size. Also i dont really have any where to put it except one of the commercial sites. However i can still make a copy available if you like.</div>
<div> </div>
<div>Thanks,</div>
<div>Ed<br><br> </div>
<div><span class="gmail_quote">On 04/07/07, <b class="gmail_sendername">Hamish</b> <<a href="mailto:hamish_nospam@yahoo.com">hamish_nospam@yahoo.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Edward Tomlinson wrote:<br>> I am having issues importing a shapefile using v.in.ogr<br>><br>> Using basic command
v.in.ogr dsn=shapefile layer=shapefile name<br>> output=elev<br>><br>> getting the following areas for every entry<br>><br>> GRASS_INFO_WARNING(29..,50..): Area size 6.5e-11, area not imported.<br>> ...<br>
> [warning sign] area size 6.5e-11, area not imported<br>> ...<br><br>Reduce v.in.ogr's min_area option.<br><br>min_area Minimum size of area to be imported (square units).<br> Smaller areas and islands are ignored. Should be
<br> greater than snap^2<br> default: 0.0001<br><br><br>> THe shapefile was generated by a Greenstar 2 GPS receiver (John<br>> Deere).<br><br>could you make a small sample available somewhere?<br>
<br><br>> There are many columns in the shapefile (30).<br>><br>> How can i limit the number of columns i read in,<br><br>you can't during import, but you can later with v.db.dropcol<br><br>> and how to set which column is the elevation column (or is ELEVATION
<br>> okay)?<br><br>I am not sure if there is a vector tool to change a 2D vector + numeric<br>column into a 3D vector directly.<br>v.out.ascii + "v.in.ascii z=" would probably do it.<br><br>but most GRASS DEM creation tools will let you specify a 2D vector + elev
<br>column name instead of needing a 3D vector as the input.<br><br><br>> I am assuming it has something to do with the way the shapefile was<br>> genereated and the precision/length of the numeric fields in the<br>
> database???<br><br>As long as the datafile is not corrupt you /should/ be able to work with<br>whatever is in it.<br><br><br>> Also what is a good .dbf viewer for KDE?<br><br>Don't know about KDE, but "dbview -bt" is nice from the command line, and
<br>OpenOffice is probably ok if there are less than a few tens of thousands of<br>entries.<br><br><br>Hamish<br></blockquote></div><br>