Reach Lengths – Importing geometry from CSV

[jsholtes]

I’m importing RAS geometry with a CSV file: Station and Elevation format.

I designate the RIVER, REACH, RS, STATION, and ELEVATION columns. Everything seems to import fine expect for the reach lengths, which I would have to go back and populate in the Reach Length Table. Why does RAS not automatically calculate reach lengths from the RS column (River Station)? Can I specify reach lengths in the CSV file elsewhere?

Thanks,
Joel

Addition: I have calculated all three downstream reach lengths (center, right, left) manually and added these via the Reach Length Table in the geometry editor. Saved everything and my geometry data viewer does not show. Why not? Does it need to? I have about 20 cross sections in there, which come up in the XS editor just fine with D/S reach lengths populated.

Here is a screen shot:

[Toby]

Do you have xy coords for you cross sections? If so, add them with the GIS tools in the geom editor -> XS Cut Lines Table. I have also seen when manually adding xs (with no GIS data), that they all get placed over one small point in the geometry and need to be manually moved to see them. Maybe try re-setting the schematic extents, by right clicking in the geom editor to find the xs.

[jsholtes]

“I have also seen when manually adding xs (with no GIS data), that they all get placed over one small point in the geometry and need to be manually moved to see them.”

That is exactly what’s happening with me.

I decided to go back to HEC GeoRAS and import XS cutlines and downstream reach lengths, etc. via the GIS import option in HEC RAS. Then I went back in and populated the station and elevation data individually in RAS. A real pain.

I started with XYZ data from a survey but didn’t have the points on perfectly straight cross sections. So, I did some work in GIS to essentially project those points perpendicularly on to straight XS cutlines I drew. Then used ArcMap’s routing tools to assign stationing.

There has to be a more straightforward way to created geometry from a survey! I guess doing a better job at staying on a line when conducting the survey and importing via CSV with XYZ data…

[Anonymous]

You should try the QGIS plugin, Profile From Points. https://plugins.qgis.org/plugins/ProfileFromPoints/

There is an option to buffer a lines layer and extract points with stationing. There is even a button to copy to the clipboard for HEC-RAS imports. You have to do each xs on its own, by selecting each xs line, but it works pretty well. I can cut xs from LiDAR in GEORAS, then drop in bathymetry data from points. Lots of other ways to use the tool.

[Lex23]

Hi Everyone!

I’d like to ask about this problem that I encountered. I kinda have a similar issue with the original author. However in my case, the cross sections (survey data in CSV file format) appear the way I expect them to be since they have georeference data (northings, eastings, elevation). This was verified when I imported the river network centerlines that I digitized in ArcGIS using HEC-GeoRAS. When I tried to proceed editing the geometry (i.e. adding XS by interpolation), I wasn’t able to do so because it appears that the table for downstream reach lengths doesn’t have values for LOB, Main Channel, ROB.

Doesn’t RAS compute these values? If not, how can I determine those values?
Also, is there a way I can possibly fix this problem without resorting to the process of creating XS in GIS (seeing that I have quite a lot of cross sections and a dendritic riverine)?

I hope someone can shed some me some light. I’m stuck with this issue.

Thank you very much!

PS: The cross section data that I have are surveyed data of the CHANNELS ONLY
PPS: Here are some images to show my problem:

[jsholtes]

Return-Path:
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by sloti25t09 (Cyrus fastmail-fmjessie45994-15732-git-fastmail-15732) with LMTPA;
Wed, 22 Nov 2017 10:54:05 -0500
X-Cyrus-Session-Id: sloti25t09-3307573-1511366045-2-3284218733382418980
X-Sieve: CMU Sieve 3.0
X-Spam-known-sender: no
X-Spam-score: 0.0
X-Spam-hits: BAYES_00 -1.9, FREEMAIL_FROM 0.001, HTML_MESSAGE 0.001,
RCVD_IN_DNSWL_NONE -0.0001, RCVD_IN_MSPIKE_H3 -0.01,
RCVD_IN_MSPIKE_WL -0.01, SPF_PASS -0.001, URI_HEX 1.122, LANGUAGES en,
BAYES_USED global, SA_VERSION 3.4.0
X-Spam-source: IP=’209.85.215.43′, Host=’mail-lf0-f43.google.com’, Country=’US’,
FromHeader=’com’, MailFrom=’com’
X-Spam-charsets: plain=’UTF-8′, html=’UTF-8′
X-Resolved-to: [email protected]
X-Delivered-to: [email protected]
X-Mail-from: [email protected]
Received: from mx3 ([10.202.2.202])
by compute1.internal (LMTPProxy); Wed, 22 Nov 2017 10:54:05 -0500
Received: from mx3.messagingengine.com (localhost [127.0.0.1])
by mailmx.nyi.internal (Postfix) with ESMTP id 1AE3046681
for ; Wed, 22 Nov 2017 10:54:04 -0500 (EST)
Received: from mx3.messagingengine.com (localhost [127.0.0.1])
by mx3.messagingengine.com (Authentication Milter) with ESMTP
id 88D23BE8CEB;
Wed, 22 Nov 2017 10:54:04 -0500
ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=arctest;
t=1511366044; b=oMpX0/ckAp8Czal5mTI43j/S3Hxm+QlXY41w8IikyW7Q2UM
ptVzWt2pyJymf7ysiFKS6zd+VVZ5f1SmkY8WHGWtdf49JvJtOpEAhX/g6xcbmvts
BB251YrW1TiQMlMSUTfbXZ0uStetDVH6rH9/No826R8BcaePIWuBhk5o5PBVEJub
+k2eSgcoHUYCKWgPLD8fMHvWMOoAb6mBYI9JkImP//BR0I+V/VCCQOvED6S7OLYS
EoWSaR+FytfW794ibZeYacCLpM2zXuIcTuBTReYMtLqlh0isunYwCAsPlacJXaxJ
0Vzr9oV5a4S79/HhEbO7Biy/4v5PsayrF0Kh8wg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=mime-version:in-reply-to:references:from
:date:message-id:subject:to:content-type; s=arctest; t=
1511366044; bh=+eadIVgPEgvlB1fvnT5XipQ+WoD0uycPLegNPOat4GA=; b=L
4BfsVnatEp6FzryyzkpuTVNk/nRyMOuXS1jIROeMYWWRtgDufLpu/4j6EmzIDyaS
EFBbGScLd73zjRBajsG7rZ6hH/9Eu8M7KhLJPG76oYMcKNQCq5BRTaynLuFmDHfO
6zY/Irjo1wjcbwgEiuKkee6iZdiHlu0B6M8XBOlpv9xZPurYog/NWx4LcYiVQY4X
jOFVvF3Dokb9dPUolMGsZyJ2Vl9Ey1UHxu1xuQXo7O/MmYpCovocHA+LkjpFw7xj
c/eUuPSwwYYAaCZ2/TNhAZmFJu7UqQePldKPE9BHv/Okz/LUgid+3U3kZTh93m1i
+KFgaAmOcLwHsJvcN8PCA==
ARC-Authentication-Results: i=1; mx3.messagingengine.com;
arc=none (no signatures found);
dkim=pass (2048-bit rsa key sha256) header.d=gmail.com [email protected] header.b=P2yFd7zx;
dmarc=pass header.from=gmail.com;
iprev=pass policy.iprev=209.85.215.43 (mail-lf0-f43.google.com);
spf=pass [email protected] smtp.helo=mail-lf0-f43.google.com;
x-aligned-from=pass;
x-category=clean score=0 state=0;
x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net [email protected] header.b=QftLwmtl;
x-ptr=pass x-ptr-helo=mail-lf0-f43.google.com x-ptr-lookup=mail-lf0-f43.google.com;
x-return-mx=pass smtp.domain=gmail.com smtp.result=pass smtp_is_org_domain=yes header.domain=gmail.com header.result=pass header_is_org_domain=yes;
x-tls=pass version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128
Authentication-Results: mx3.messagingengine.com;
arc=none (no signatures found);
dkim=pass (2048-bit rsa key sha256) header.d=gmail.com [email protected] header.b=P2yFd7zx;
dmarc=pass header.from=gmail.com;
iprev=pass policy.iprev=209.85.215.43 (mail-lf0-f43.google.com);
spf=pass [email protected] smtp.helo=mail-lf0-f43.google.com;
x-aligned-from=pass;
x-category=clean score=0 state=0;
x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net [email protected] header.b=QftLwmtl;
x-ptr=pass x-ptr-helo=mail-lf0-f43.google.com x-ptr-lookup=mail-lf0-f43.google.com;
x-return-mx=pass smtp.domain=gmail.com smtp.result=pass smtp_is_org_domain=yes header.domain=gmail.com header.result=pass header_is_org_domain=yes;
x-tls=pass version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128
Received-SPF: pass
(gmail.com … _spf.google.com: Sender is authorized to use ‘[email protected]’ in ‘mfrom’ identity (mechanism ‘include:_netblocks.google.com’ matched))
receiver=mx3.messagingengine.com;
identity=mailfrom;
envelope-from=”[email protected]”;
helo=mail-lf0-f43.google.com;
client-ip=209.85.215.43
Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by mx3.messagingengine.com (Postfix) with ESMTPS
for ; Wed, 22 Nov 2017 10:54:03 -0500 (EST)
Received: by mail-lf0-f43.google.com with SMTP id i14so18798040lfc.1
for ; Wed, 22 Nov 2017 07:54:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=+eadIVgPEgvlB1fvnT5XipQ+WoD0uycPLegNPOat4GA=;
b=P2yFd7zxpmlvGyfhjT6vKjLre6r20EzQfJ+e+SsLLTgkXhMsFKg+KYssnWV7skXS61
QhlaloBukIEYd9knd3MtHgCzyug42bM6cktgl3p8FDIwJb/9A8ScaIAGv5omS5bshy03
mjnaLKxQWPeMk0Rgp8yc9C8iLpFXa/Y1dUssdzfmONVOM+O6S0PxwRk2LzY1goh7BdTZ
TZbQc04T7fu+FBtu6YS4+a7UQCTYqpvQFtH/g/IovLlyN4EXk2963m6ZMdFfm+4IlqnO
AnKgcWYR8bf7/RT8Rxpj33HNG8OIOzxWkzScvw0jjaMIC/UE69gAbNBEx45mp+dAqHNr
n6Lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=+eadIVgPEgvlB1fvnT5XipQ+WoD0uycPLegNPOat4GA=;
b=QftLwmtlKVvXcTdmvwQ9QsA9lvOQy1ktlhGb4Qo3fKXQdMBlGEzyDdyXVy+R+Ev3hc
90pcqhf6asv7A6+tZh8CmpExmp5j0Pau7633tfaolyFeh5TZRnp5QqLQgLnAsz9NaczX
oRzagXZpRIRRVSkvhCtnIGPkZA0fAj/OoQznnRFrSxq7ixk9ICC2OR3v0JYqKeTtJ+hQ
8URdLQy/qbNxRz1SX78xDzP3Blflg5MIwFFLJ3Rvj5U9In5Q1AcwCrzgGz8ZAJ4jxQ0a
4Our5xTPrXexCBNE+5iAhgU/Ob5DciJ8+OLYCm8Dke8MNhmS4HXwXaHIepmuQq5LPHDk
vLMQ==
X-Gm-Message-State: AJaThX4XpjPJ9ZCEa1hXsS+Ab6jxJMpaIL8AClBjuH4ad8bGloOEytC5
cpcn+wjZJYEfAtkW1qPdSXmedE6gjqm5SCT2Orl7qnn5
X-Google-Smtp-Source: AGs4zMZ/kFuNTJ6CAt9KnHVnCdgydUVkkubR2dkOm3lCdmrwUcXPpOyoSIHuH0t4Lqp7MwClX7jAtprbPcwH1eriv8A=
X-Received: by 10.25.113.15 with SMTP id m15mr4418165lfc.257.1511366040950;
Wed, 22 Nov 2017 07:54:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.199.196 with HTTP; Wed, 22 Nov 2017 07:53:40 -0800 (PST)
In-Reply-To: <[email protected]>
References: <[email protected]> <[email protected]>
<[email protected]> <[email protected]>
<[email protected]>
From: Joel Sholtes
Date: Wed, 22 Nov 2017 08:53:40 -0700
Message-ID:
Subject: Re: Reach Lengths – Importing geometry from CSV
To: “Lex23 [via HEC-RAS Help]”
Content-Type: multipart/alternative; boundary=”089e082e02e8ff1d0c055e9453a4″

–089e082e02e8ff1d0c055e9453a4
Content-Type: text/plain; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printable

So RAS plots your XS’s correctly, but doesn’t have downstream reach
lengths? How do these reaches plot longitudinally? That might shed some
light on whether or not RAS “knows” the distance between XS’s.
It’s lame that RAS doesn;t automatically calculate the reach lengths, but
it would not know how to calculate the ROB and LOB distances without more
information from you.

I suggest everyone on this string email HEC to complain about this bug:
http://www.hec.usace.army.mil/software/hec-ras/bug_report.aspx

The only way around this I fear is to bring all of this into GIS than back
into RAS using GeoRAS. Or maybe you can just use GeoRAS to calculate all of
the downstream lengths for you and then paste them back into this empty
table.

1. Export your centerline and XS’s into shapefiles using RAS MApper (In
RAS)
2. Open ArcMap with GeoRAS installed and create a new project (save new
map, create empty centerline and cross section and flow lines shapefiles=
)
3. Start an editing session for these empty shapefiles
4. Bring in the exported XSs and centerline from RASMapper
5. Select (highlight) first the XS’s, Copy, then Paste (using Edit menu
on top bar) into the RAS XS Cultines shapefile. This will populate them.=
Do
the same for the Centerline.
6. Create and draw the overbank flow lines (copying the river centerline=
)
7. Populate the Centerline stationing and XS stationing data
8. Export then import into RAS (Geometry, Import, GIS)
9. Copy and paste Station and Elevation data into each XS (?!?!?!)

That last step is a doozy. You might avoid this by conducting all of the
steps up to 7, then copy the XS downstream and LOB/ROB reach length data
from the attributes table and paste it into the empty RAS table you show
here.

On Wed, Nov 22, 2017 at 2:12 AM, Lex23 [via HEC-RAS Help] < [email protected]> wrote:

> Hi Everyone!
>
> I’d like to ask about this problem that I encountered. I kinda have a
> similar issue with the original author. However in my case, the cross
> sections (survey data in CSV file format) appear the way I expect them to
> be since they have georeference data (northings, eastings, elevation). Th=
is
> was verified when I imported the river network centerlines that I digitiz=
ed
> in ArcGIS using HEC-GeoRAS. When I tried to proceed editing the geometry
> (i.e. adding XS by interpolation), I wasn’t able to do so because it
> appears that the table for downstream reach lengths doesn’t have values f=
or
> LOB, Main Channel, ROB.
>
> Doesn’t RAS compute these values? If not, how can I determine those
> values?
> Also, is there a way I can possibly fix this problem without resorting to
> the process of creating XS in GIS?
>
> I hope someone can shed some me some light. I’m stuck with this issue.
>
> Thank you very much!
>
>
> PS: Here are some images to show my problem:
>
>
> ——————————
> If you reply to this email, your message will be added to the discussion
> below:
> http://hec-ras-help.1091112.n5.nabble.com/Reach-Lengths-
> Importing-geometry-from-CSV-tp3334p4815.html
> To unsubscribe from Reach Lengths – Importing geometry from CSV, click
> here
> <http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?macro=
=3Dunsubscribe_by_code&node=3D3334&code=3DanNob2x0ZXNAZ21haWwuY29tfDMzMzR8N=
Tc4Mjg2MDUz>
> .
> NAML
> <http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?macro=
=3Dmacro_viewer&id=3Dinstant_html%21nabble%3Aemail.naml&base=3Dnabble.naml.=
namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.v=
iew.web.template.NodeNamespace&breadcrumbs=3Dnotify_subscribers%21nabble%3A=
email.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble=
%3Aemail.naml>
>

–=20
Golden, Colorado
919.265.8250
joelsholtes.wordpress.com

–089e082e02e8ff1d0c055e9453a4
Content-Type: text/html; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printable

So RAS plots your XS's correctly, but doesn't have=
downstream reach lengths? How do these reaches plot longitudinally? That m=
ight shed some light on whether or not RAS "knows" the distance b=
etween XS's.

It's lame that RAS doesn;t automatically calculate=
the reach lengths, but it would not know how to calculate the ROB and LOB =
distances without more information from you.=C2=A0

I=
suggest everyone on this string email HEC to complain about this bug:=C2=
=A0http://www.hec.usace.army.mil/software/hec-ras/bug_report.aspx

=

The only way around this I fear is to bring all of this=
into GIS than back into RAS using GeoRAS. Or maybe you can just use GeoRAS=
to calculate all of the downstream lengths for you and then paste them bac=
k into this empty table.

1. Export your centerline and XS&#3=
   9;s into shapefiles using RAS MApper (In RAS)
2. Open ArcMap with =
   GeoRAS installed and create a new project (save new map, create empty cente=
   rline and cross section and flow lines shapefiles)
3. Start an editing=
   session for these empty shapefiles
4. Bring in the exported XSs and c=
   enterline from RASMapper
5. Select (highlight) first the XS's, Cop=
   y, then Paste (using Edit menu on top bar) into the RAS XS Cultines shapefi=
   le. This will populate them. Do the same for the Centerline.
6. Create=
   and draw the overbank flow lines (copying the river centerline)
7. Po=
   pulate the Centerline stationing and XS stationing data
8. Export then=
   import into RAS (Geometry, Import, GIS)
9. Copy and paste Station and=
   Elevation data into each XS (?!?!?!)

That last step is=
a doozy. You might avoid this by conducting all of the steps up to 7, then=
copy the XS downstream and LOB/ROB reach length data from the attributes t=
able and paste it into the empty RAS table you show here.

=

On Wed, Nov 22, 2=
017 at 2:12 AM, Lex23 [via HEC-RAS Help] <ml+s1091112n4815=
[email protected]> wrote:

" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Hi Everyone!

I'd like to ask about this problem that I encountered. I kinda =
have a similar issue with the original author. However in my case, the cros=
s sections (survey data in CSV file format) appear the way I expect them to=
be since they have georeference data (northings, eastings, elevation). Thi=
s was verified when I imported the river network centerlines that I digitiz=
ed in ArcGIS using HEC-GeoRAS. When I tried to proceed editing the geometry=
(i.e. adding XS by interpolation), I wasn't able to do so because it a=
ppears that the table for downstream reach lengths doesn't have values =
for LOB, Main Channel, ROB.

Doesn't RAS compute these values? If not, how can I determine t=
hose values?=20

Also, is there a way I can possibly fix this problem without resorting =
to the process of creating XS in GIS?

I hope someone can shed some me some light. I'm stuck with this=
issue.

Thank you very much!

PS: Here are some images to show my problem:

=09
=09
=09

---

If you reply to this email, your message =
will be added to the discussion below:

http://hec=
-ras-help.1091112.n5.nabble.com/Reach-Lengths-Importing-geometry-=
from-CSV-tp3334p4815.html

=09
To unsubscribe from Reach Lengths – Importing geometry from CSV, click here.
NAML

=
—

Golden, Colorado

919.265.8250

=

joelsholtes.wordpress.com

–089e082e02e8ff1d0c055e9453a4–

[Lex23]

Hi!

I was able to save the cross sections and centerlines from RAS into shapefiles using RAS Mapper. However, I can’t seem to follow steps 5 to 7. Did you mean that I need to copy the values in the attribute table of the exported shapefiles into the attribute tables of RAS layers I created in ArcGIS?

If yes, I don’t think I can do the simple copy and paste because the two layers have different fields in their respective attribute tables. I tried the other methods as well (i.e. join option), but the resulting layer doesn’t have rows because the the RAS Layers I created in ArcGIS don’t have values in the table.

Am I doing it the correctly the way you outlined it? Did this method worked for you before?

Thanks a lot for the response!

[cameron]

He is basically saying you need to use GeoRAS to calculate the reach lengths.

Since you say the survey data points you have are just for the channel and no overbanks, then the LOB and ROB should be the same as the channel.

It appears from your table that you have cross-section stationing for your cross-sections. If these are correct, then you could just copy the cross-section names into excel, subtract each row from each other to get a distance between cross-sections, and then paste it all into that table.

[Lex23]

Right! Thanks a lot Cameron for making me realize it. My mind was a jumble because I’ve been trying to work with (basically) 2 types of geometric data – channel only, channel+floodplain. I overlooked and totally missed the fact that LOB&ROB only matter when working with cross sections of the channel and floodplain. Whew!

Anyway, just a quick question. For a river that is segmented into lower and upper reach because of a tributary, is the reach length of the most downstream XS (of both the upper reach and tributary) measured from the node/junction? Or is it from the XS directly ‘next downstream’ to it (which is the most upstream XS of the upper reach)?

Thanks a lot!!! 🙂

[PaoloP]

To create a RAS geometry fully georeferenced with banks, and downstream distance check this:

https://shop.m3eweb.com/home/30-ras-geometry-maker.html

[Author]

Posts