<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Greetings -<div><br></div><div>I am processing some geotechnical data that is geolocated on a CAD drawing (Bentley dgn is the original pedigree).</div><div>This has been exported as a dxf file and brought into GRASS with v.in.dxf -- no problem.</div><div>The region is set up in state plane coordinates (KY-N) with US survey feet as units.</div><div><br></div><div>When I run v.report on the layer that contains the boring data the file content is displayed, for example:</div><div><br></div><div><div>37|G_PF_SYMB3_PR|text|5B-303|1212081.497014|279650.475464|0</div><div><span class="Apple-style-span" style="text-decoration: underline;">38|G_PF_SYMB3_PR|text|5B-305|1211936.354207|279753.605789|0</span></div><div>39|G_PF_SYMB3_PR|text|5B-306|1211736.052427|279843.95891|0</div><div><br></div><div>Using 5B-305 as an example, when I display the points and query using v.what, it produces:</div><div><br></div><div><div>East: 1212909.91005291</div><div>North: 279431.95238095</div><div><br></div><div>Map: borings </div><div>Mapset: PERMANENT</div><div>Type: Point</div><div>Line: 58</div><div>Point height: 0.000000</div><div>Layer: 3</div><div>Category: 38 </div><div><br></div><div>Driver: dbf</div><div>Database: /Users/stu/grassdata/Kennedy_SPC/PERMANENT/dbf/</div><div>Table: borings_g_pf_symb3_pr</div><div>Key column: cat</div><div>cat : 38</div><div>layer : G_PF_SYMB3_PR</div><div>entity : text</div><div><br></div><div>These coordinates bear little resemblance to the v.report values.</div><div><br></div><div>Opening the dxf file in an editor and poking about, I found what appears to be the data set for 5B-305 (it is the only time 5B-305 appears in the file):</div><div><br></div><div><div>AcDbEntity</div><div> 8</div><div>G_PF_SYMB3_PR</div><div>100</div><div>AcDbText</div><div> 10</div><div>1212909.151125 **</div><div> 20</div><div>279430.832539 **</div><div> 30</div><div>0.0</div><div> 40</div><div>12.0</div><div> 1</div><div>5B-305 **</div><div> 50</div><div>7.581985</div><div> 7</div><div>1 1 Plan</div><div>100</div><div><br></div><div><br></div><div>These correspond fairly well to the values produced by v.what. </div><div><br></div><div>The question for anyone patient enough to still be with me is -- what is v.report reporting? There appears to be no pattern to the dx and dy between the two reports over a reasonable sampling of the borings. </div><div><br></div><div>Partial answer! I was about to hit the send button, but decided first to run a search in the dxf file for the coordinates that are shown in v.report. To my surprise there was one hit:</div><div><br></div><div><div>AcDbEntity</div><div> 8</div><div>G_PF_SYMB3_PR</div><div>100</div><div>AcDbText</div><div> 10</div><div>1211936.354207 <span class="Apple-tab-span" style="white-space:pre"> </span>**</div><div> 20</div><div>279753.605789<span class="Apple-tab-span" style="white-space:pre"> </span>**</div><div> 30</div><div>0.0</div><div> 40</div><div>12.0</div><div> 1</div><div>5B-329<span class="Apple-tab-span" style="white-space:pre"> </span>**</div><div> 50</div><div>7.581985</div><div> 7</div><div>1 1 Plan</div><div>100</div><div><br></div></div><div>The coordinates for 5B-305 in v.report are actually those of 5B-329! So the data appear to be shuffled rather than distorted.</div><div><br></div><div>Thanks for any help you can provide ~</div><div><br></div><div>Stu</div></div></div></div></body></html>