[GoSparky]

I’m talking about the CivilGEO GeoHECRAS software. It’s not a replacement for Corps software; it’s just a wrapper with additional functionality. The deliverable files are the same.

[GoSparky]

It looks to me like the inflection points are at the bridge internal cross sections, BR U and BR D. Is that not the case?

[GoSparky]

Can you show more of the profile with the xsec points marked for both profiles?

[GoSparky]

I’ve seen this before in bridge models and it’s been caused by the ineffective stations on the downstream cross sections. If the proposed bridge has a wider opening and you keep the same flow expansion angle as you used for the existing bridge, then the downstream ineffectives get moved out, which increases the active flow area and you get a small rise downstream of the bridge where you’d think there should be no changes in a subcritical model (Q=VA).

You’ll also get a rise if the proposed channel is bigger. When you make the area bigger, the velocity goes down and thus the WSEL has to go up. I’ve never had the time to investigate and find out at what point the area gets big enough to not get a rise (and probably every site is different anyway).

Also, if the bridge is overtopping, then you often will get a rise upstream because the proposed bridge is larger (longer or greater deck thickness) and blocks more of the flow than the existing bridge did, which results in an upstream rise.

[GoSparky]

Yes, I think I finally got rid of the messages by saving the geometry file. You have to save it from the geometry window. Just saving the model doesn’t fix it.

[GoSparky]

Return-Path: Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by sloti1d2t14 (Cyrus 3.1.5-761-gc103c9b-fmstable-20190103v1bis) with LMTPA;
Wed, 16 Jan 2019 13:36:42 -0500
X-Cyrus-Session-Id: sloti1d2t14-3404949-1547663802-2-16615122058528103913
X-Sieve: CMU Sieve 3.0
X-Spam-known-sender: no
X-Spam-score: 1.3
X-Spam-hits: HTML_MESSAGE 0.001, ME_ZS_CLEAN -0.01, RCVD_IN_DNSWL_NONE -0.0001,
SPF_HELO_PASS -0.001, SPF_PASS -0.001, URI_HEX 1.313, LANGUAGES en,
BAYES_USED none, SA_VERSION 3.4.2
X-Spam-source: IP=’40.107.77.124′,
Host=’mail-eopbgr770124.outbound.protection.outlook.com’, Country=’US’,
FromHeader=’com’, MailFrom=’com’, XOriginatingCountry=’US’
X-Spam-charsets: plain=’us-ascii’, html=’us-ascii’
X-Resolved-to: [email protected]
X-Delivered-to: [email protected]
X-Mail-from: [email protected]
Received: from mx1 ([10.202.2.200])
by compute1.internal (LMTPProxy); Wed, 16 Jan 2019 13:36:42 -0500
Received: from mx1.messagingengine.com (localhost [127.0.0.1])
by mailmx.nyi.internal (Postfix) with ESMTP id 0C82013085
for ; Wed, 16 Jan 2019 13:36:41 -0500 (EST)
Received: from mx1.messagingengine.com (localhost [127.0.0.1])
by mx1.messagingengine.com (Authentication Milter) with ESMTP
id 77BB96D4643;
Wed, 16 Jan 2019 13:36:41 -0500
ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=fm1; t=
1547663801; b=XQVlYwkJ1tOfDt35QQgTOubPp5wu1mBN0ePYtYViTk1emSDso6
JHrCFczX7Cy2RtQdJFr/yOmXEeLZrbnVQVUKdu0PJTXlw40YU7DBaBzf3v3pRrX1
cEuXVwi44Y4XfoSWQ0puDH5/DqKK//ayRarPiruxo23YFum458lpfbOSh80pndqb
I13ttCxArGHcfKRXasTNSaNNfqdEZ5KSIvMsOxkm9D9+vmRrvkXu6UDCZ8pNIeaA
5BeGPcMt2VDpxQcgamJMoSWw+JrNSFXEv11/d15PpJsvmCkQKcq15Kz1zpX4D6UY
m+SFgH2hvmrAlSx95xS+s7uRYBO2V7fAScqQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=from:to:subject:date:message-id
:references:in-reply-to:content-type:mime-version; s=fm1; t=
1547663801; bh=ydM1g0xswHTQu/UDjY9rKf9RGvjnnmB2GNRUpAj8t5c=; b=V
VHNfpLfrYFcLyhiKBbHDQv3pSDweybBqFlrV+BR0gBknexmyDqWAukKRFYu3ue5c
o+dOlYL6zJ8BNC+DPW+zqAFz3sial5JLV4NLlj5y3hkLrFWkFLoOuuCkWAM4BYs3
VT3+2ZhzcgN/aH70cj5eT3dPBCEWJRdaelUvqiEhfnFUs8I/gXLMbrWPlovs6Cct
PBZ6xM/ylAAz1ncF6y3+lhVXukrypLhS/ThF0la0m+lC9p7S2zjzUaVY4bvkWinx
n6Ag/WixrKXS8dm1WRUofi53rQtramLiXuHe2aq+KiRt9xDj1L3WraFlnwilrYjG
9i6KtSJoK7XnTPPmq6XHA==
ARC-Authentication-Results: i=1; mx1.messagingengine.com; arc=none (no signatures found);
dkim=pass (1024-bit rsa key sha256) header.d=stantec.onmicrosoft.com
[email protected] header.b=sJphFcgj
header.a=rsa-sha256 header.s=selector1-stantec-com x-bits=1024;
dmarc=none policy.published-domain-policy=none
policy.applied-disposition=none policy.evaluated-disposition=none
(p=none,d=none,d.eval=none) policy.policy-from=p
header.from=stantec.com;
iprev=pass smtp.remote-ip=40.107.77.124
(mail-eopbgr770124.outbound.protection.outlook.com);
spf=pass [email protected]
smtp.helo=NAM02-SN1-obe.outbound.protection.outlook.com;
x-aligned-from=pass (Address match);
x-ptr=fail smtp.helo=NAM02-SN1-obe.outbound.protection.outlook.com
policy.ptr=mail-eopbgr770124.outbound.protection.outlook.com;
x-return-mx=pass header.domain=stantec.com policy.is_org=yes
(MX Record found);
x-return-mx=pass smtp.domain=stantec.com policy.is_org=yes
(MX Record found);
x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES128-SHA
smtp.bits=128/128;
x-vs=clean score=0 state=0;
x-zs=clean
Authentication-Results: mx1.messagingengine.com;
arc=none (no signatures found);
dkim=pass (1024-bit rsa key sha256) header.d=stantec.onmicrosoft.com
[email protected] header.b=sJphFcgj
header.a=rsa-sha256 header.s=selector1-stantec-com x-bits=1024;
dmarc=none policy.published-domain-policy=none
policy.applied-disposition=none policy.evaluated-disposition=none
(p=none,d=none,d.eval=none) policy.policy-from=p
header.from=stantec.com;
iprev=pass smtp.remote-ip=40.107.77.124
(mail-eopbgr770124.outbound.protection.outlook.com);
spf=pass [email protected]
smtp.helo=NAM02-SN1-obe.outbound.protection.outlook.com;
x-aligned-from=pass (Address match);
x-ptr=fail smtp.helo=NAM02-SN1-obe.outbound.protection.outlook.com
policy.ptr=mail-eopbgr770124.outbound.protection.outlook.com;
x-return-mx=pass header.domain=stantec.com policy.is_org=yes
(MX Record found);
x-return-mx=pass smtp.domain=stantec.com policy.is_org=yes
(MX Record found);
x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES128-SHA
smtp.bits=128/128;
x-vs=clean score=0 state=0;
x-zs=clean
X-ME-VSSU: VW5zdWI9aHR0cDovL2hlYy1yYXMtaGVscC4xMDkxMTEyLm41Lm5hYmJsZS5jb20vdGVtcG
xhdGUvTmFtbFNlcnZsZXQuanRwP21hY3JvPXVuc3Vic2NyaWJlX2J5X2NvZGUmbm9kZT02
NjczJmNvZGU9YkdsellTNXNZWFYyWlhKQWMzUmhiblJsWXk1amIyMThOalkzTTN3eE1USX
hOVFF5TkRZeg
X-ME-VSCause: gggruggvucftvghtrhhoucdtuddrgedtledrgeehgdduudehucetufdoteggodetrfdotf
fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu
rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefhvffuth
ffkfhfjghitgggsegrtddtredttddvnecuhfhrohhmpedfnfgruhhvvghrpdcunfhishgr
fdcuoehlihhsrgdrlhgruhhvvghrsehsthgrnhhtvggtrdgtohhmqeenucffohhmrghinh
epnhgrsggslhgvrdgtohhmnecukfhppeegtddruddtjedrjeejrdduvdegpdegrdefgedr
hedvrddufeegpdhfvgektdemmegsleefheemfhelfegumegsgedvjeemheekudegnecurf
grrhgrmhepihhnvghtpeegtddruddtjedrjeejrdduvdegpdhhvghloheppfetofdtvddq
uffpuddqohgsvgdrohhuthgsohhunhgurdhprhhothgvtghtihhonhdrohhuthhlohhokh
drtghomhdpmhgrihhlfhhrohhmpeeolhhishgrrdhlrghuvhgvrhesshhtrghnthgvtgdr
tghomhequcfukfgkgfepvddtuddukeenucevlhhushhtvghrufhiiigvpedt
X-ME-VSCategory: clean
X-ME-ZSResult: clean
Received-SPF: pass
(stantec.com: Sender is authorized to use ‘[email protected]’ in ‘mfrom’ identity (mechanism ‘include:spf.protection.outlook.com’ matched))
receiver=mx1.messagingengine.com;
identity=mailfrom;
envelope-from=”[email protected]”;
helo=NAM02-SN1-obe.outbound.protection.outlook.com;
client-ip=40.107.77.124
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770124.outbound.protection.outlook.com [40.107.77.124])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
(No client certificate requested)
by mx1.messagingengine.com (Postfix) with ESMTPS
for ; Wed, 16 Jan 2019 13:36:38 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=stantec.onmicrosoft.com; s=selector1-stantec-com;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=ydM1g0xswHTQu/UDjY9rKf9RGvjnnmB2GNRUpAj8t5c=;
b=sJphFcgjjxv4fvumJZm1Yiu+W58HeMCK7znPUhaT1E/XTs2iPJrV616swN8E9HCVbZA2LLB76oTMcT+77tw/8O68S56qOWBBLCmrUj+lrRiLKYjo8kuEhvaHoXkCNSlTds319K/pyvvdaBv2qbxk7+Z9z+zxCMlKCeO4IuObWY0=
Received: from DM6PR06MB4460.namprd06.prod.outlook.com (20.176.113.150) by
DM6PR06MB4857.namprd06.prod.outlook.com (20.176.120.21) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.1516.18; Wed, 16 Jan 2019 18:36:35 +0000
Received: from DM6PR06MB4460.namprd06.prod.outlook.com
([fe80::b935:f93d:b427:5814]) by DM6PR06MB4460.namprd06.prod.outlook.com
([fe80::b935:f93d:b427:5814%6]) with mapi id 15.20.1537.018; Wed, 16 Jan 2019
18:36:35 +0000
From: “Lauver, Lisa” To: “MinutemanModeler [via HEC-RAS Help]”
Subject: RE: Warning: Count for bucket 0 exceeds maximum 32 bit value
Thread-Topic: Warning: Count for bucket 0 exceeds maximum 32 bit value
Thread-Index: AQHUraBazMs2QH10uU6BOxARcafrOqWyOOfA
Date: Wed, 16 Jan 2019 18:36:35 +0000
Message-ID:

References: <[email protected]>
<[email protected]>
In-Reply-To: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
[email protected];
x-originating-ip: [4.34.52.134]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics:
1;DM6PR06MB4857;6:qWqKUUEEDmOxY0LDoZCoyt/KL5Aqx04tnI62bnorAm/pxuUbd4Qab/zu2mqLOaqVf0O2w3Un5V2OQa1kC+xJm/bgWMvIi3XJGN+TaqphBjCG8/YVQQ2t8SLKkgGOaOHzdITwyA2QVD5ftyud8WYxFIst+iREkDD/EZaPcgEF1GFkdGf45TkK3JVIz2497XfxijuNvzOuOZmaVqGBRQxoCpcnYqr1wSZ3rgqaV3k9Kkemd/1aX641kSbVw4Vdh7gD7Y5ylzjuIqKqwGQdMOGSUIGC/+hSOmOdhk5xTeJJrNRDBeIaRknfA8YV7OC4PxVE4duC3YulZD9++IcudUD52vrHREEqrZ/d8ffrDisYRdMTYGSFkpoO0IolsMEk/DabJ/bi0R6MdZCfjpNoU7OwgrVJU47e1Rer4k5MWwYW/q6NCnfQfCjivDBuLVxujkoPW1W1pSMqpwBl+mdSFc2DVw==;5:wjEpal4Kyg2tPuVE54GJbReikeX6PuUNfjWrSRyWPJg6CFekxKwLYpQY+3teNZp0Qmk9rD81hQksTnP0G0yd5Xp5pKTApzUqLKf68in1hTvwN224WCAfWakUH/R5jfCcmC0gAFF8mM54Peqvy/9pMzWyprOmFvvfMB+3Pa+YPe3Pu5V6a0dtCNkAJhnd6S9EWkqvCGEQcIqYxq9mA0sI+A==;7:pa6mPusvarfQMME39f8OGadS4iBFBqQilJ9uSRBoF4xscJ7CoXxLiT0GoRfz8jDfbAlOIIYcHjE435y+9xsOJU9Sq8krQ3ChMv6R2TYqKcQcQPwUFQ8PM+LFW9NSammSSRFupHBOGRs0r8tuzGXzPw==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 78761b0a-87bb-4e9c-fd26-08d67be18b85
x-microsoft-antispam:
BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(5600109)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020);SRVR:DM6PR06MB4857;
x-ms-traffictypediagnostic: DM6PR06MB4857:
x-microsoft-antispam-prvs:

x-forefront-prvs: 091949432C
x-forefront-antispam-report:
SFV:NSPM;SFS:(10019020)(366004)(376002)(39860400002)(396003)(136003)(346002)(199004)(189003)(74316002)(8936002)(6116002)(790700001)(3846002)(2906002)(229853002)(66066001)(71190400001)(71200400001)(33656002)(606006)(8676002)(81166006)(81156014)(5660300001)(7066003)(99286004)(14444005)(68736007)(6436002)(86362001)(55016002)(256004)(4744005)(486006)(966005)(21615005)(7696005)(476003)(446003)(6506007)(478600001)(14454004)(25786009)(6246003)(7736002)(54896002)(9686003)(236005)(11346002)(97736004)(186003)(106356001)(316002)(6306002)(102836004)(53546011)(26005)(105586002)(76176011)(136015008)(53936002)(10126004);DIR:OUT;SFP:1102;SCL:1;SRVR:DM6PR06MB4857;H:DM6PR06MB4460.namprd06.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:1;MX:1;
received-spf: None (protection.outlook.com: stantec.com does not designate
permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info:
B++yEKPIUc9C4BsULPHVrH5I2g0t6MTOWGCJs950dYbtSAJ8/vfggghPZSofpaWq8YKICN8BfbzDBv0gbCMBVJLdYKzOAQBBgn8ukIK87NTwed3OYNmlB8+Kl47aYZbEaWaeTQOXkCTcITYH14IPB/H7x6v21tvP1ScqsB7hjZddhwlHhMqmh0xodx2S89xn1521edKnKekhIjO03GRRXm+K8fE+h0pZ7kQcBrd3A6LiUH4PM4Xb1UUO0zBWvOEPtQMiz/mJv3DXU/MDNs70AkOsdAtjzkFcbCsGhOLgrvriWTYIef5TaMwoo/vW6pCG61+dWwSLVbUH4o5kHc8dJm9bjW9ANoDMPjNNhwWwxM9h2BRBa4Sn0BudO+S5BXrQ+3fXZ4eFU9vlWN9YtA0Kjwmque4v3lYk6nPoy4NsP2s=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
boundary=”_000_DM6PR06MB4460BE690DCB4C8F569D801DEF820DM6PR06MB4460namp_”
MIME-Version: 1.0
X-OriginatorOrg: stantec.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 78761b0a-87bb-4e9c-fd26-08d67be18b85
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Jan 2019 18:36:35.7394
(UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 413c6f2c-219a-4692-97d3-f2b4d80281e7
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR06MB4857

–_000_DM6PR06MB4460BE690DCB4C8F569D801DEF820DM6PR06MB4460namp_
Content-Type: text/plain; charset=”us-ascii”
Content-Transfer-Encoding: quoted-printable

No, I was unable to resolve this error or even find out exactly what it mea=
nt. But the model seemed to run fine despite the error. And the reviewers=
were not concerned about it either.

Lisa

From: MinutemanModeler [via HEC-RAS Help]
Sent: Wednesday, January 16, 2019 6:35 AM
To: Lauver, Lisa Subject: Re: Warning: Count for bucket 0 exceeds maximum 32 bit value

Any luck resolving this issue?
I am having a similar error except my program is indicating “bucket 255”.
Thanks
________________________________
If you reply to this email, your message will be added to the discussion be=
low:
http://hec-ras-help.1091112.n5.nabble.com/Warning-Count-for-bucket-0-exceed=
s-maximum-32-bit-value-tp6673p7044.html
To unsubscribe from Warning: Count for bucket 0 exceeds maximum 32 bit valu=
e, click here<http://hec-ras-help.1091112.n5.nabble.com/template/NamlServle=
t.jtp?macro=3Dunsubscribe_by_code&node=3D6673&code=3DbGlzYS5sYXV2ZXJAc3Rhbn=
RlYy5jb218NjY3M3wxMTIxNTQyNDYz>.
NAML<http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?mac=
ro=3Dmacro_viewer&id=3Dinstant_html%21nabble%3Aemail.naml&base=3Dnabble.nam=
l.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble=
.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-na=
bble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespac=
e-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleName=
space-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.Nabble=
Namespace-nabble.view.web.template.NodeNamespace&breadcrumbs=3Dnotify_subsc=
ribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_inst=
ant_email%21nabble%3Aemail.naml>

–_000_DM6PR06MB4460BE690DCB4C8F569D801DEF820DM6PR06MB4460namp_
Content-Type: text/html; charset=”us-ascii”
Content-Transfer-Encoding: quoted-printable

No, I was unable to resolve this error or =
even find out exactly what it meant.  But the model seemed to run fine=
despite the error.  And the reviewers were not concerned
about it either.

 

Lisa

 

 

From: MinutemanModeler [via HEC-RAS Help] &lt=
;ml+[email protected]>

Sent: Wednesday, January 16, 2019 6:35 AM
To: Lauver, Lisa <[email protected]>
Subject: Re: Warning: Count for bucket 0 exceeds maximum 32 bit valu=
e

 

Any luck resolving th=
is issue?
I am having a similar error except my program is indicating "bucket 25=
5".
Thanks

---

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

http://hec-ras-help.1091112.n5.nabble.com/Warning-Count-for-bu=
cket-0-exceeds-maximum-32-bit-value-tp6673p7044.html

To unsubsc=
ribe from Warning: Count for bucket 0 exceeds maximum 32 bit value,

click here.
NAML

–_000_DM6PR06MB4460BE690DCB4C8F569D801DEF820DM6PR06MB4460namp_–

[GoSparky]

I’m running 5.0.5 and I’m still having this problem. My override regions were not recognized. Or to be more specific, the software recognizes the polygons but does not use the override values I assigned.

The Supplemental User’s Manual says that the Override Regions layer table is editable, but I have been unable to do this. It won’t let me edit the “Manning’s n” column, which is blank. Does anyone know how to do this?

[GoSparky]

Sounds like you need to put in a stream junction. See chapter 6 of the Users Manual and Example 10 in Applications Guide.

[GoSparky]

Hi Chris. I found this archived post when searching for info on cross sections with lids. Why is RAS not the best tool for modeling tunnels or pipe flow? And what would be better? SWMM?
(I’m trying to model a ‘basin/weir/box culvert/outflow weir’ in a WTP, so a simple culvert editor like HY-8 is not sufficient.)

thanks,
Lisa

[GoSparky]

When you do pier scour, you use the velocity at the first cross-section upstream of the bridge, not BR U or BR D. You should be able to see the velocity distribution at that cross-section and get the flow velocity approaching each pier. Or, if the channel can shift, it’s best to use the maximum velocity “slice” from the upstream cross-section for your pier scour calcs.

[GoSparky]

Return-Path: X-Original-To: [email protected]
Delivered-To: [email protected]
Received: from mail.stantec.com (mail.stantec.com [207.34.120.71])
by mwork.nabble.com (Postfix) with ESMTP id 2E944166B2DB
for ; Mon, 9 Mar 2015 08:07:36 -0700 (PDT)
Received: from CD1001-M370.corp.ads ([fe80::a1bc:d8be:baa4:c85e]) by
CD1001-M62.corp.ads ([::1]) with mapi; Mon, 9 Mar 2015 09:07:23 -0600
From: “Lauver, Lisa” To: “Chris G. [via HEC-RAS Help]”
Date: Mon, 9 Mar 2015 09:07:22 -0600
Subject: RE: Easiest way to edit the geometry schematic?
Thread-Topic: Easiest way to edit the geometry schematic?
Thread-Index: AdBYNoOoPOe0iw8CTVa9gFE9968I+ACRDRWg
Message-ID:
References: <[email protected]>
<[email protected]>
In-Reply-To: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary=”_000_FB9C51233ACC1747A2D60B649C0E2BF703319F41D1CD1001M370cor_”
MIME-Version: 1.0

–_000_FB9C51233ACC1747A2D60B649C0E2BF703319F41D1CD1001M370cor_
Content-Type: text/plain; charset=”us-ascii”
Content-Transfer-Encoding: quoted-printable

Thank you Chris!

Lisa

From: Chris G. [via HEC-RAS Help] [mailto:[email protected]=
e.com]
Sent: Friday, March 06, 2015 10:54 AM
To: Lauver, Lisa
Subject: Re: Easiest way to edit the geometry schematic?

In the geometry schematic, hover your mouse cursor over the point where you=
would like each vertex in your “copied” cross sections to be. There’s a x=
-y coordinate readout in your geometry schematic on the lower right. Recor=
d those points. You may have to zoom in pretty close to get the precision =
in your coordinate points that you’d like. Then go to GIS Tools…XS Cutli=
nes Table, and enter in those coordinate points for each of your copied cro=
ss sections.
Chris G.
@RASModel
http://www.therassolution.com<http://www.therassolution.com>

________________________________
If you reply to this email, your message will be added to the discussion be=
low:
http://hec-ras-help.1091112.n5.nabble.com/Easiest-way-to-edit-the-geometry-=
schematic-tp1400p1401.html
To unsubscribe from Easiest way to edit the geometry schematic?, click here=
<http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?macro=
=3Dunsubscribe_by_code&node=3D1400&code=3DbGlzYS5sYXV2ZXJAc3RhbnRlYy5jb218M=
TQwMHwxMTIxNTQyNDYz>.
NAML<http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?mac=
ro=3Dmacro_viewer&id=3Dinstant_html%21nabble%3Aemail.naml&base=3Dnabble.nam=
l.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble=
.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-na=
bble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespac=
e-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleName=
space-nabble.view.web.template.NodeNamespace&breadcrumbs=3Dnotify_subscribe=
rs%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_=
email%21nabble%3Aemail.naml>

–_000_FB9C51233ACC1747A2D60B649C0E2BF703319F41D1CD1001M370cor_
Content-Type: text/html; charset=”us-ascii”
Content-Transfer-Encoding: quoted-printable

Thank=
you Chris!

&nbsp=
;

Lisa

 

 

From:<= /b> Chri=
s G. [via HEC-RAS Help] [mailto:[email protected]] Sent: Friday, March 06, 2015 10:54 AM
To: Lauver, LisaSubject: Re: Easiest way to edit the geometry schematic?=

 

I=
n the geometry schematic, hover your mouse cursor over the point where you =
would like each vertex in your "copied" cross sections to be. &nb=
sp;There’s a x-y coordinate readout in your geometry schematic on the lower=
right.  Record those points.  You may have to zoom in pretty clo=
se to get the precision in your coordinate points that you’d like.  Th=
en go to GIS Tools…XS Cutlines Table, and enter in those coordinate point=
s for each of your copied cross sections.  

Chris G.
@RASModel
http://www.therassolution.com

 

---

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

http://hec-ras-help.109111=
2.n5.nabble.com/Easiest-way-to-edit-the-geometry-schematic-tp1400p1401.html=

To unsubscribe from Easiest =
way to edit the geometry schematic?, c=
lick here.
NAML=

=

–_000_FB9C51233ACC1747A2D60B649C0E2BF703319F41D1CD1001M370cor_–

[Author]

Posts