[GRASS-dev] v.clip and latlon?

[Michael Barton]

So some tests.

v.clip seems to work fine with the NC demo data both in State Plane and Latlon.

Back to the LatLon location for gshhs coastline data.

I was able to use v.select to get the equivalent of a clip using an area created with the region. v.clip on this subset does not work and produces an empty map. If I convert it to lines (v.type), then v.clip works. If I re-convert the lines map to boundaries again, v.clip again produces an empty map.

When I do any of these operations, I get a warning of a number of 'incorrect boundaries'. Running v.build doesn't seem to make any difference. Given all this, I'm assuming that the incorrect boundaries (whatever these are) are the problem with clipping this data set. v.select works but v.overlay does not for some reason.  It is a very large data set, so I can't really make it easily available--though it is the widely available coastline data that can be downloaded by anyone.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















On Nov 25, 2018, at 7:12 PM, Vaclav Petras <wenzeslaus at gmail.com<mailto:wenzeslaus at gmail.com>> wrote:



On Sun, Nov 25, 2018 at 6:16 PM Michael Barton <Michael.Barton at asu.edu<mailto:Michael.Barton at asu.edu>> wrote:
Can do. Wanted to check first so as not to duplicate anything (search in Trak leaves much to be desired).

I agree, but mostly because there is this hard split between full text search and query. The is no "fuzz search" so when somebody just misspells the name of the module, then there is no help. Other than that, I'm usually quite successful in finding things with one or the other (the trick for the full text search is to leave checked only the type(s) you really need).

I might first try it on a vector from the NC demo data to make sure that it works there (or not).

Sounds good! Thanks.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20181126/dcc4fd48/attachment.html>