[GRASS-user] v.neighors error:region do not overlap

Hi,

I need to run v.neighbors on multiple datasets for the identic region (extend and resolution). One dataset has observations outside of this region, and causes an error: “ERROR: Input vector and computational region do not overlap.” However, viewing the extend in v.info and r.info (see below) and overlaying the layers in the GUI, I see overlaps for 90% of my points. Is this expected behavior or do I miss something? (GRASS70 from Repos, OS:Ubuntu 15.04)

#Code
r.in.gdal in=“./00_REFERENCE/reference_map.tif” out=region_ref --o
g.region rast=region_ref

v.neighbors in=pt out=pt_dens300 size=600 meth=count --overwrite

#extract of “v.info pt”:
| Location: CH_1903+
| Title:

Map scale: 1:1
Map format: native
--------------------------------------------------
Type of map: vector (level: 2)
Number of points: 10278 Number of centroids: 0
Map is 3D: No
Number of dblinks: 1
Projection: Swiss. Obl. Mercator
N: 1309490.94577888 S: 1060967.94534242
E: 2906024.04080627 W: 2424801.03992381
Digitization threshold: 0

#extract of “r.info region_ref”:

Location: CH_1903+
Type of Map: raster Number of Categories: 0
Data Type: CELL
Rows: 8912
Columns: 14016
Total Cells: 124910592
Projection: Swiss. Obl. Mercator
N: 1297000 S: 1074200 Res: 25
E: 2834800 W: 2484400 Res: 25
Range of data: min = 1 max = 999

On Wed, Jul 29, 2015 at 4:40 PM, patrick s. <patrick_gis@gmx.net> wrote:

Hi,

I need to run v.neighbors on multiple datasets for the identic region
(extend and resolution). One dataset has observations outside of this
region, and causes an error: "ERROR: Input vector and computational region
do not overlap." However, viewing the extend in v.info and r.info (see
below) and overlaying the layers in the GUI, I see overlaps for 90% of my
points. Is this expected behavior or do I miss something? (GRASS70 from
Repos, OS:Ubuntu 15.04)

#Code
r.in.gdal in="./00_REFERENCE/reference_map.tif" out=region_ref --o
g.region rast=region_ref

Just to be sure, please post

g.region raster=region_ref -p

I generated a location with epsg:2056 (is that the right one for
CH_1903+ ?) and there is indeed map overlap.
But just to be sure that the computational region is right, too.

Markus

<big><small>Hi Markus

thanks for your answer. epsg:2056 is correct for CH_1903+; 
And here the print you ask for, comming out of mapset in location 1903+</small>.

Patrick
</big>

#g.region raster=region_ref -p
projection: 99 (Swiss. Obl. Mercator)
zone: 0
datum: ch1903
ellipsoid: bessel
north: 1297000
south: 1074200
west: 2484400
east: 2834800
nsres: 25
ewres: 25
rows: 8912
cols: 14016
cells: 124910592

···

On 01.08.2015 23:56, Markus Neteler wrote:

On Wed, Jul 29, 2015 at 4:40 PM, patrick s. [<patrick_gis@gmx.net>](mailto:patrick_gis@gmx.net) wrote:

Hi,

I need to run v.neighbors on multiple datasets for the identic region
(extend and resolution).  One dataset has observations outside of this
region, and causes an error: "ERROR: Input vector and computational region
do not overlap." However, viewing the extend in v.info and r.info (see
below) and overlaying the layers in the GUI, I see overlaps for 90% of my
points. Is this expected behavior or do I miss something? (GRASS70 from
Repos, OS:Ubuntu 15.04)

#Code
r.in.gdal in="./00_REFERENCE/reference_map.tif" out=region_ref --o
g.region rast=region_ref

Just to be sure, please post

g.region raster=region_ref -p

I generated a location with epsg:2056 (is that the right one for
CH_1903+ ?) and there is indeed map overlap.
But just to be sure that the computational region is right, too.

Markus

UPDATE:

The error of v.neighbors does not appear when importing points only for a region: "v.in.ogr -r"

So definitely a problem of v.neighbors.

Patrick

On 01.08.2015 23:56, Markus Neteler wrote:

On Wed, Jul 29, 2015 at 4:40 PM, patrick s. <patrick_gis@gmx.net> wrote:

Hi,

I need to run v.neighbors on multiple datasets for the identic region
(extend and resolution). One dataset has observations outside of this
region, and causes an error: "ERROR: Input vector and computational region
do not overlap." However, viewing the extend in v.info and r.info (see
below) and overlaying the layers in the GUI, I see overlaps for 90% of my
points. Is this expected behavior or do I miss something? (GRASS70 from
Repos, OS:Ubuntu 15.04)

#Code
r.in.gdal in="./00_REFERENCE/reference_map.tif" out=region_ref --o
g.region rast=region_ref

Just to be sure, please post

g.region raster=region_ref -p

I generated a location with epsg:2056 (is that the right one for
CH_1903+ ?) and there is indeed map overlap.
But just to be sure that the computational region is right, too.

Markus