search

PDXBES / Z-OLD-besasm-legacy

OLD-Legacy projects
0 stars 0 forks source link

Alts Toolkit: Zero and negative ground elevations appearing for nodes unexpectedly #22

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

Zero and negative ground elevations are appearing for some nodes and
causing Invalid Frame ID errors when EMGAATS is used to deploy the
alternative model.  Where are the ground elevations coming from, since
Kristi indicates she doesn't enter these?

What is the expected output? What do you see instead?

Workaround is to set the ground elevation in the deployed model to
something other than zero, and then redeploy the alternative model.

Original issue reported on code.google.com by ArnelMan...@gmail.com on 4 Mar 2010 at 11:40

GoogleCodeExporter commented 9 years ago

Original comment by ArnelMan...@gmail.com on 4 Mar 2010 at 11:41

GoogleCodeExporter commented 9 years ago 
Node elevations are assigned spatially using the index WshdPts.txt file 
available at:

\\cassio\modeling\Model_Programs\Emgaats\CodeV2.2\NodeTool\data\WshdPts.txt

The index file WshdPts.txt should contain a list of elevation files used to 
populate 
the node ground elevation. Negative or odd values populated into mdl_nodes are 
originating in the source data specified in WshdPts.txt, and these files should 
be 
investigated.

Original comment by john.hen...@gmail.com on 5 Mar 2010 at 12:32

GoogleCodeExporter commented 9 years ago 
Thank you.  The problem coming up is due to alternatives being placed too close 
to
the river, too close to have any proper elevation data.

Will forward a request to generate nonzero river elevation area data to Albert.

Original comment by ArnelMan...@gmail.com on 5 Mar 2010 at 12:53

GoogleCodeExporter commented 9 years ago 
It appears that the problem is caused by unavailability of elevation points in 
certain areas. The elevation of a manhole/node is extracted from point files as 
described by JohnB and ArnelM in previous messages. Arnel has provided me with 
a 
definite node number(ABL496) that was causing the same problem. Further 
checking 
showed that this node is an outfall and located in the river area. Majority of 
the 
point files cover most of the modeling system extents and have been patched 
from 
time to time when needed. The patch for this area has been fixed(see attached 
figure). If you need to check elevation points availability please load the 
seamless 
Mapinfo table: 

 \\Cassio\gis1\MI_DATA\ENVIRON\TOPO\GRD\2004\PtsTbl\ALLDemPts.TAB

Further, if you have an alternative/model that needs some patching for 
elevations, 
please let us know so we can address those appropriately. Furthermore, please 
take 
note that some of the future patches might need qa/qc since they have been 
derived 
from sources that require scrubbing/verification.

Original comment by bes.asm....@gmail.com on 10 Mar 2010 at 12:37

Attachments: