Select to view content in your preferred language

Why flow direction tool shows Hooghly River as flowing north?

5636
7
07-21-2020 12:40 PM
JamieVanTassell
Emerging Contributor

Hello,

I am using the Hydrology tools in ArcGIS Pro to delineate urban watersheds in Kolkata. I have noticed that when I use the Flow Direction tool, some of the values of the Hooghly River (alternatively spelled Hoogli or Hugli) are coded to point north (value of 64). The river winds it way southward until it reaches the Bay of Bengal, however, so the map is not accurate. I have attached an image to show these results.

I am using 30-m resolution because I am unable to purchase higher resolution data at this time. This may be the reason for the inaccurate results.

Is there a way to re-code this information so that the flow direction raster is accurate for the Hooghly River?

Thank you!

-Jamie

0 Kudos
7 Replies
MatthewDriscoll
MVP Alum

Jamie, did you use the "Fill" tool before using the "Flow Direction"?

0 Kudos
JamieVanTassell
Emerging Contributor

Yes, I did.

0 Kudos
MatthewDriscoll
MVP Alum

Is there a place where I can download the original 30m raster?  I will have some time to test it out if you would like. 

0 Kudos
JamieVanTassell
Emerging Contributor

I used EarthData to download the DEM. It requires creating an account.

Earthdata Search

Thank you!

Jamie

0 Kudos
JamieVanTassell
Emerging Contributor

Hello Matthew,

I hate to be a pest, but have you been able to test the original raster? I am very motivated to find out why the Flow Direction tool codes a portion of the river as running north and how I might be able to fix this. Your help would be greatly appreciated with this!

Many thanks,

Jamie

0 Kudos
MatthewDriscoll
MVP Alum

Sorry I had to get IT to bypass a firewall issue.  I just tried it and got the same results as you.

I found a different DEM and it is having the same results.

0 Kudos
JamieVanTassell
Emerging Contributor

Hi Matthew,

Thank you for running the analysis and getting back to me on this! Do you have any thoughts as to why this is happening? Is it just a result of using 30-m resolution data?

Do you know if there is a way to correct the coding?

Thank you,

Jamie

0 Kudos