Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Pages Sidebar" sidebar. Defaulting to "sidebar-1". Manually set the id to "sidebar-1" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "PortfolioSidebar" sidebar. Defaulting to "sidebar-2". Manually set the id to "sidebar-2" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "BlogSidebar" sidebar. Defaulting to "sidebar-3". Manually set the id to "sidebar-3" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "ContactSidebar" sidebar. Defaulting to "sidebar-4". Manually set the id to "sidebar-4" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "SitemapSidebar" sidebar. Defaulting to "sidebar-5". Manually set the id to "sidebar-5" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "PagesSidebar2" sidebar. Defaulting to "sidebar-17". Manually set the id to "sidebar-17" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "PagesSidebar3" sidebar. Defaulting to "sidebar-18". Manually set the id to "sidebar-18" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "PagesSidebar4" sidebar. Defaulting to "sidebar-19". Manually set the id to "sidebar-19" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "PagesSidebar5" sidebar. Defaulting to "sidebar-20". Manually set the id to "sidebar-20" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "PagesSidebar6" sidebar. Defaulting to "sidebar-21". Manually set the id to "sidebar-21" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "PagesSidebar7" sidebar. Defaulting to "sidebar-22". Manually set the id to "sidebar-22" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "PagesSidebar8" sidebar. Defaulting to "sidebar-23". Manually set the id to "sidebar-23" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /var/www/wp-includes/functions.php on line 5167

Deprecated: The called constructor method for WP_Widget in Login_Form_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 4806

Deprecated: The called constructor method for WP_Widget in Custom_Category_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 4806

Deprecated: The called constructor method for WP_Widget in Google_Map_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 4806

Deprecated: The called constructor method for WP_Widget in Latest_Posts_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 4806

Deprecated: The called constructor method for WP_Widget in Subpages_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 4806
Editorial: SC Ports Authority, city of Charleston need to find common ground on cruise ships « Charleston Communities for Cruise Control

Editorial: SC Ports Authority, city of Charleston need to find common ground on cruise ships

By The Editorial Staff Feb 16, 2020

Click to read online

It’s been more than a decade since Charleston and the State Ports Authority began their epic feud over the proper presence of cruise ships next to the city’s historic core. There’s been precious little progress made, and we hope that changes soon.

There’s simply too much at stake beyond the cruise business.

As the S.C. Supreme and the U.S. District courts prepare to rule on aspects of the dispute, both sides should commit to restarting a dialogue about how they can find common ground and reset the important relationship between the state agency and the city. We recognize leadership will be required, and any breakthrough will take each side out of its comfort zone.

Cooperation between the city and state led to the creation of the State Ports Authority in the early 20th century, and its success has been crucial to South Carolina’s modern economy. But the state’s economy also thrives on tourism, and the dramatic success of historic Charleston is one of the leading drivers of that. This success was brought about partly by aggressively regulating many aspects of tourism under the correct belief that Charleston is an attractive place to visit foremost because it is an attractive place to live.

We don’t expect a resolution of the long-standing cruise debate would produce a clear winner or loser in this long-running dispute, partly because its complex nature includes the following issues:

  • Whether there should be a legally binding penalty if the SPA exceeds its voluntary cap of no more than one cruise ship docking at a time, no more than 104 visits a year. The authority has abided by the cap for years and says it has turned down business to do so, but some in the city rightly wonder why, if the authority’s intent is to comply with the limit, it finds such a provision a problem.
  • Whether cruise ship passengers should be taxed more to contribute to the city, where struggles with flooding and sea-level rise have increased dramatically since the cruise ship controversy began. Ports Authority CEO Jim Newsome has argued cruise ships are just another form of maritime commerce, but Mayor John Tecklenburg said, “I respectfully believe that having cruise ships here is more than a maritime business.”
  • Whether the authority should take further steps to reduce cruise ship emissions while in port. Mr. Newsome said low-sulfur fuels have improved the situation, and any decision on shore power is tied up with the following issue.
  • Whether a new cruise ship terminal should be located on Union Pier, near the current, outdated facility. The debate over this facility and what sort of mitigation the state should provide the city to help offset impacts on the Historic District are the basis of the pending lawsuits.

As with most big disputes, there’s fault on both sides. Mr. Tecklenburg has talked about the desirability of a new tax on cruise passengers to help pay for the city’s infrastructure needs, but he has not yet sat down personally with ports officials to make his case. Mr. Newsome and his board have excelled in positioning the Port of Charleston for long-term growth but have seemed insensitive at times to legitimate local concerns. This problem isn’t unique to Charleston. North Charleston Mayor Keith Summey has his own frustration with the authority stemming from issues related to the new Leatherman terminal there.

The time is right for fresh talks, especially as the Ports Authority renegotiates a long-term deal with Carnival Cruise Line, whose ship Sunshine is based here, and as it plans for the future sale of its vast Union Pier site downtown.

There is some validity to the notion that no one wins except the lawyers whenever disputes are settled in court. When the two opposing sides are both arms of government — and accountable to many of the same people — inaction and litigation only increase cynicism about whether our government is really working for us.