Re: [GRASS-user] Date import: setting projection units

2017-09-27 Thread Helmut Kudrnovsky 
Rich Shepard wrote
> Trying to import an OpenFileGDB with the following parameters:
> 
> Layer name: WQStandards_BeneficialUseDesignations
> Geometry: Multi Line String
> Feature Count: 764329
> Extent: (607675.393548, 81930.638752) - (2554273.406512, 1355726.104279)
> Layer SRS WKT:
> PROJCS["NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet",
>  GEOGCS["GCS_North_American_1983_HARN",
>  DATUM["NAD83_High_Accuracy_Reference_Network",
>  SPHEROID["GRS_1980",6378137.0,298.257222101]],
>  PRIMEM["Greenwich",0.0],
>  UNIT["Degree",0.0174532925199433]],
>  PROJECTION["Lambert_Conformal_Conic_2SP"],
>  PARAMETER["False_Easting",1640416.7],
>  PARAMETER["False_Northing",0.0],
>  PARAMETER["Central_Meridian",-120.5],
>  PARAMETER["Standard_Parallel_1",45.84],
>  PARAMETER["Standard_Parallel_2",47.34],
>  PARAMETER["Latitude_Of_Origin",45.34],
>  UNIT["Foot_US",0.3048006096012192]]
> 
>I created a new location (Washington-LCC):
> 
> name: unnamed
> proj: lcc
> lat_1: 45.83
> lat_2: 47.33
> lat_0: 23
> lon_0: -120.5
> x_0: 0.1640416
> y_0: 0
> no_defs: defined
> datum: nad83harn
> ellps: grs80
> towgs84: 0.000,0.000,0.000
> 
> but the units are meters, not feet. I don't see where I can specify
> projection units when creating the location. Do I edit the
> PERMANENT/PROJ_UNITS file?
> 
> TIA,
> 
> Rich
> 
> ___
> grass-user mailing list

> grass-user@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-user

Another possibility is to let GRASS define the correct location parameters
by the dataset itself.



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Date import: setting projection units

2017-09-27 Thread Helmut Kudrnovsky 
Rich Shepard wrote
> Trying to import an OpenFileGDB with the following parameters:
> 
> Layer name: WQStandards_BeneficialUseDesignations
> Geometry: Multi Line String
> Feature Count: 764329
> Extent: (607675.393548, 81930.638752) - (2554273.406512, 1355726.104279)
> Layer SRS WKT:
> PROJCS["NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet",
>  GEOGCS["GCS_North_American_1983_HARN",
>  DATUM["NAD83_High_Accuracy_Reference_Network",
>  SPHEROID["GRS_1980",6378137.0,298.257222101]],
>  PRIMEM["Greenwich",0.0],
>  UNIT["Degree",0.0174532925199433]],
>  PROJECTION["Lambert_Conformal_Conic_2SP"],
>  PARAMETER["False_Easting",1640416.7],
>  PARAMETER["False_Northing",0.0],
>  PARAMETER["Central_Meridian",-120.5],
>  PARAMETER["Standard_Parallel_1",45.84],
>  PARAMETER["Standard_Parallel_2",47.34],
>  PARAMETER["Latitude_Of_Origin",45.34],
>  UNIT["Foot_US",0.3048006096012192]]
> 
>I created a new location (Washington-LCC):
> 
> name: unnamed
> proj: lcc
> lat_1: 45.83
> lat_2: 47.33
> lat_0: 23
> lon_0: -120.5
> x_0: 0.1640416
> y_0: 0
> no_defs: defined
> datum: nad83harn
> ellps: grs80
> towgs84: 0.000,0.000,0.000
> 
> but the units are meters, not feet. I don't see where I can specify
> projection units when creating the location. Do I edit the
> PERMANENT/PROJ_UNITS file?
> 
> TIA,
> 
> Rich
> 
> ___
> grass-user mailing list

> grass-user@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-user

You can define a GRASS  location also by a proj4 string.

Have a look at

https://epsg.io/102749

how the proj4 string may look for your data



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Date import: setting projection units

2017-09-27 Thread Rich Shepard 

  Trying to import an OpenFileGDB with the following parameters:

Layer name: WQStandards_BeneficialUseDesignations
Geometry: Multi Line String
Feature Count: 764329
Extent: (607675.393548, 81930.638752) - (2554273.406512, 1355726.104279)
Layer SRS WKT:
PROJCS["NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet",
GEOGCS["GCS_North_American_1983_HARN",
DATUM["NAD83_High_Accuracy_Reference_Network",
SPHEROID["GRS_1980",6378137.0,298.257222101]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Lambert_Conformal_Conic_2SP"],
PARAMETER["False_Easting",1640416.7],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",-120.5],
PARAMETER["Standard_Parallel_1",45.84],
PARAMETER["Standard_Parallel_2",47.34],
PARAMETER["Latitude_Of_Origin",45.34],
UNIT["Foot_US",0.3048006096012192]]

  I created a new location (Washington-LCC):

name: unnamed
proj: lcc
lat_1: 45.83
lat_2: 47.33
lat_0: 23
lon_0: -120.5
x_0: 0.1640416
y_0: 0
no_defs: defined
datum: nad83harn
ellps: grs80
towgs84: 0.000,0.000,0.000

but the units are meters, not feet. I don't see where I can specify
projection units when creating the location. Do I edit the
PERMANENT/PROJ_UNITS file?

TIA,

Rich

___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

2017-09-27 Thread Moritz Lennert 

On 27/09/17 21:03, Markus Metz wrote:



On Wed, Sep 27, 2017 at 4:07 PM, Moritz Lennert 
> wrote:

 >
 >
 >
 > Le 27 septembre 2017 13:11:54 GMT+02:00, Johannes Radinger 
> a écrit :

 > >Hi,
 > >
 > >I have a GRASS vector network that represents a river network (with
 > >many
 > >first order tributaries) and that has additional connected nodes that
 > >represent sampling sites.
 > >
 > >I'd like to extract a minimum subnetwork of the full network that still
 > >connects a set of selected nodes (e.g. identified by their cat).
 > >However,
 > >network edges (i.e. river segments) that are not necessary to connect
 > >the
 > >sampling points should be excluded in the new subnetwork. Is there a
 > >function or process in GRASS GIS to extract such a subnetwork that
 > >fully
 > >connects a set of selected nodes?
 >
 > not sure but maybe v.net.spanningtree ?

v.net.spanningtree calculates a tree covering all nodes in the network, 
not only selected nodes, therefore v.net.spanningtree does not apply here.


If you connect only the selected nodes to the network, wouldn't that 
work ? Or does v.net.spanningtree consider all connections between lines 
as nodes ?


Moritz
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

2017-09-27 Thread Markus Metz 
On Wed, Sep 27, 2017 at 4:07 PM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:
>
>
>
> Le 27 septembre 2017 13:11:54 GMT+02:00, Johannes Radinger <
johannesradin...@gmail.com> a écrit :
> >Hi,
> >
> >I have a GRASS vector network that represents a river network (with
> >many
> >first order tributaries) and that has additional connected nodes that
> >represent sampling sites.
> >
> >I'd like to extract a minimum subnetwork of the full network that still
> >connects a set of selected nodes (e.g. identified by their cat).
> >However,
> >network edges (i.e. river segments) that are not necessary to connect
> >the
> >sampling points should be excluded in the new subnetwork. Is there a
> >function or process in GRASS GIS to extract such a subnetwork that
> >fully
> >connects a set of selected nodes?
>
> not sure but maybe v.net.spanningtree ?

v.net.spanningtree calculates a tree covering all nodes in the network, not
only selected nodes, therefore v.net.spanningtree does not apply here.

Markus M

>
> Moritz
>
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

2017-09-27 Thread Stefan Blumentrath 
Sorry, there is: https://grass.osgeo.org/grass72/manuals/v.net.allpairs.html

From: grass-user [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of 
Johannes Radinger
Sent: onsdag 27. september 2017 13.12
To: GRASS user list 
Subject: [GRASS-user] Extract subnet from grass vector network based on 
selected nodes

Hi,

I have a GRASS vector network that represents a river network (with many first 
order tributaries) and that has additional connected nodes that represent 
sampling sites.

I'd like to extract a minimum subnetwork of the full network that still 
connects a set of selected nodes (e.g. identified by their cat). However, 
network edges (i.e. river segments) that are not necessary to connect the 
sampling points should be excluded in the new subnetwork. Is there a function 
or process in GRASS GIS to extract such a subnetwork that fully connects a set 
of selected nodes?

Cheers,
Johannes
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

2017-09-27 Thread Markus Metz 
On Wed, Sep 27, 2017 at 1:11 PM, Johannes Radinger <
johannesradin...@gmail.com> wrote:
>
> Hi,
>
> I have a GRASS vector network that represents a river network (with many
first order tributaries) and that has additional connected nodes that
represent sampling sites.
>
> I'd like to extract a minimum subnetwork of the full network that still
connects a set of selected nodes (e.g. identified by their cat). However,
network edges (i.e. river segments) that are not necessary to connect the
sampling points should be excluded in the new subnetwork. Is there a
function or process in GRASS GIS to extract such a subnetwork that fully
connects a set of selected nodes?

You could try v.net.steiner. A Steiner tree is probably overkill for a
river network, but it should work.

Markus M
>
> Cheers,
> Johannes
>
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

2017-09-27 Thread Moritz Lennert 


Le 27 septembre 2017 13:11:54 GMT+02:00, Johannes Radinger 
 a écrit :
>Hi,
>
>I have a GRASS vector network that represents a river network (with
>many
>first order tributaries) and that has additional connected nodes that
>represent sampling sites.
>
>I'd like to extract a minimum subnetwork of the full network that still
>connects a set of selected nodes (e.g. identified by their cat).
>However,
>network edges (i.e. river segments) that are not necessary to connect
>the
>sampling points should be excluded in the new subnetwork. Is there a
>function or process in GRASS GIS to extract such a subnetwork that
>fully
>connects a set of selected nodes?

not sure but maybe v.net.spanningtree ?

Moritz


___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Extract subnet from grass vector network based on selected nodes

2017-09-27 Thread Stefan Blumentrath 
Hei Johannnes,

Maybe looping over the different possible combinations of nodes using 
https://grass.osgeo.org/grass72/manuals/v.net.path.html does the job?

Cheers
Stefan

From: grass-user [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of 
Johannes Radinger
Sent: onsdag 27. september 2017 13.12
To: GRASS user list 
Subject: [GRASS-user] Extract subnet from grass vector network based on 
selected nodes

Hi,

I have a GRASS vector network that represents a river network (with many first 
order tributaries) and that has additional connected nodes that represent 
sampling sites.

I'd like to extract a minimum subnetwork of the full network that still 
connects a set of selected nodes (e.g. identified by their cat). However, 
network edges (i.e. river segments) that are not necessary to connect the 
sampling points should be excluded in the new subnetwork. Is there a function 
or process in GRASS GIS to extract such a subnetwork that fully connects a set 
of selected nodes?

Cheers,
Johannes
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] Extract subnet from grass vector network based on selected nodes

2017-09-27 Thread Johannes Radinger 
Hi,

I have a GRASS vector network that represents a river network (with many
first order tributaries) and that has additional connected nodes that
represent sampling sites.

I'd like to extract a minimum subnetwork of the full network that still
connects a set of selected nodes (e.g. identified by their cat). However,
network edges (i.e. river segments) that are not necessary to connect the
sampling points should be excluded in the new subnetwork. Is there a
function or process in GRASS GIS to extract such a subnetwork that fully
connects a set of selected nodes?

Cheers,
Johannes
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] OpenFileGDB input error

2017-09-27 Thread Even Rouault 
> > You can force a curve geometry to its linearized version (curves are
> 
> approximated with segments) with:
> > hGeom = OGR_G_ForceTo(hGeom,
> 
> OGR_GT_GetLinear(OGR_G_GetGeometryType(hGeom)))
> 
> Thanks for the hint!
> 
> I'm looking for a way to support non-linear geometries in v.in.ogr. Is
> there any advantage of using OGR_G_ForceTo() instead of
> OGR_G_GetLinearGeometry()?

Ah, I just forgot the existence of OGR_G_GetLinearGeometry(). Might be indeed 
more 
obvious to use. Both use ultimately the same mechanisms for linear 
approximation.
The main difference being that OGR_G_GetLinearGeometry() returns a new object, 
whereas 
OGR_G_ForceTo() transforms in place.

Evven

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] OpenFileGDB input error

2017-09-27 Thread Markus Metz 
On Mon, Sep 25, 2017 at 7:26 PM, Even Rouault 
wrote:
>
> On lundi 25 septembre 2017 19:19:26 CEST Markus Metz wrote:
>
> > [...] OGR calls these
>
> > geometries multi-surfaces.
>
>
>
> Actually it is defined by
>
> OpenGIS Simple Feature Access Part 1 : Common Architecture,v 1.2.1 :
>
> http://portal.opengeospatial.org/files/?artifact_id=25355
>
>
>
> > Investigating a bit more, I found curve-polygons
>
> > within these multi-surfaces. Curve-polygons are in turn not ordinary
>
> > polygons, but defined by curves, and v.in.ogr (most GIS software in
>
> > general) does not support curves.
>
> >
>
>
>
> The relevant GDAL RFC is
>
> https://trac.osgeo.org/gdal/wiki/rfc49_curve_geometries
>
> Support for curves in FileGDB is more recent.
>
>
>
> You can force a curve geometry to its linearized version (curves are
approximated with segments) with:
>
>
>
> hGeom = OGR_G_ForceTo(hGeom,
OGR_GT_GetLinear(OGR_G_GetGeometryType(hGeom)))
>
Thanks for the hint!

I'm looking for a way to support non-linear geometries in v.in.ogr. Is
there any advantage of using OGR_G_ForceTo() instead of
OGR_G_GetLinearGeometry()?

Thanks,

Markus M
>
> Even
>
>
>
> --
>
> Spatialys - Geospatial professional services
>
> http://www.spatialys.com
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user