NJ Fishing Advertise Here at New Jersey's Number 1 Fishing Website!


Message Board


Prime spots in jeopardy - NJFishing.com Your Best Online Source for Fishing Information in New Jersey


Message Board Registration       FAQ

Go Back   NJFishing.com Your Best Online Source for Fishing Information in New Jersey > NJFishing.com Salt Water Fishing
FAQ Members List Calendar Mark Forums Read

NJFishing.com Salt Water Fishing Use this board to post all general salt water fishing information. Please use the appropriate boards below for all other information. General information about sailing times, charter availability and open boats trips can be found and should be posted in the open boat forum.

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #8  
Old 02-27-2015, 05:45 AM
Dino's Avatar
Dino Dino is offline
NJFishing.com Ambassador
 
Join Date: Sep 2009
Posts: 602
Default Re: Prime spots in jeopardy

Quote:
Originally Posted by Reel Class View Post
WOW

My question is why can't they just take sand from the miles of flat, unmitigated sand up and down the beach which isn't on a lump or high spot?

...I really don't get the rationale!!!

Apparently the reason why an inshore lump stays a lump, stays higher than the surrounding bottom, and doesnt get flattened down by currents, is because the larger grain sand is built up there. thats exactly the sand the Corps wants because it (just like when it was on the lumps), won't get washed away as fast. that seems to be the problem, they dont want the finer grain sand from the random open bottom.. they want the large grains from the lumps which are sensitive habitat for fish and crucial for fishermen.. kind of sux !
Reply With Quote
 


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 09:50 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.