Tidewater (marketing)

Tidewater is a term used by industries and governments[1] to refer to access to ocean ports with international marine services for import and export of commodities. For export, the commodities can be shipped via trucks, trains[2] and/or pipelines[3] to a port, thereby opening the door to more lucrative prices on global markets. Getting to such a port is particularly important for landlocked jurisdictions seeking to expand and diversify markets for natural resources.[4]

Landlocked Athabasca oil sands
Canaport in New Brunswick, Canada is a tidewater petroleum facility

An example of the use of the term "tidewater" can be seen in the debate over exports of oil produced by the Athabasca oil sands. Upon separation from the sand, this bituminous oil, marketed as Western Canadian Select, is forced to sell at the price established for landlocked oil (see: West Texas Intermediate benchmark). If this oil were able to reach "tidewater" for export using oil tankers, it would presumably command a higher price (see: Brent Crude benchmark). Several pipelines have been proposed to bring the oil to "tidewater", including the Keystone XL project (via the Gulf of Mexico), the Enbridge Northern Gateway Pipelines project (via the British Columbia coast), the Mackenzie Valley Pipeline project (via the Beaufort Sea), or the Energy East pipeline project (via the Bay of Fundy).[1][5] The Government of Alberta and the Government of Canada claimed a loss of $C4 – $C30 billion (CAD) in taxes and non-renewable natural resource royalties in 2013. In comparison, Maya crude oil,(Moore et al. 2011:2).[4] a similar product to Western Canadian Select, but located close to tidewater, is reaching peak prices.[2] In the United States, opponents of pipeline projects have expressed concern that pipeline construction and expansion would simply facilitate getting Alberta oil sands products to an American port for export to China and other countries via the Gulf of Mexico and that the resulting expansion in production in Alberta and consumption of fossil fuels worldwide would have a detrimental contribution to greenhouse gases.[6] Canaport is a receiving terminal for crude oil and LNG. There is a proposal to expand it to allow the export of inland oil delivered via pipeline.

gollark: <@!206233133228490752> Sorry to bother you, but keypairs generated by `ccecc.py` and the ECC library in use in potatOS appear to have different-length private and public keys, which is a problem.EDIT: okay, apparently it's because I've been accidentally using a *different* ECC thing from SMT or something, and it has these parameters instead:```---- Elliptic Curve Arithmetic---- About the Curve Itself-- Field Size: 192 bits-- Field Modulus (p): 65533 * 2^176 + 3-- Equation: x^2 + y^2 = 1 + 108 * x^2 * y^2-- Parameters: Edwards Curve with c = 1, and d = 108-- Curve Order (n): 4 * 1569203598118192102418711808268118358122924911136798015831-- Cofactor (h): 4-- Generator Order (q): 1569203598118192102418711808268118358122924911136798015831---- About the Curve's Security-- Current best attack security: 94.822 bits (Pollard's Rho)-- Rho Security: log2(0.884 * sqrt(q)) = 94.822-- Transfer Security? Yes: p ~= q; k > 20-- Field Discriminant Security? Yes: t = 67602300638727286331433024168; s = 2^2; |D| = 5134296629560551493299993292204775496868940529592107064435 > 2^100-- Rigidity? A little, the parameters are somewhat small.-- XZ/YZ Ladder Security? No: Single coordinate ladders are insecure, so they can't be used.-- Small Subgroup Security? Yes: Secret keys are calculated modulo 4q.-- Invalid Curve Security? Yes: Any point to be multiplied is checked beforehand.-- Invalid Curve Twist Security? No: The curve is not protected against single coordinate ladder attacks, so don't use them.-- Completeness? Yes: The curve is an Edwards Curve with non-square d and square a, so the curve is complete.-- Indistinguishability? No: The curve does not support indistinguishability maps.```so I might just have to ship *two* versions to keep compatibility with old signatures.
gollark: > 2. precompilation to lua bytecode and compressionThis was considered, but the furthest I went was having some programs compressed on disk.
gollark: > 1. multiple layers of sandboxing (a "system" layer that implements a few things, a "features" layer that implements most of potatOS's inter-sandboxing API and some features, a "process manager" layer which has inter-process separation and ways for processes to communicate, and a "BIOS" layer that implements features like PotatoBIOS)Seems impractical, although it probably *could* fix a lot of problems
gollark: There's a list.
gollark: Lots of them.

See also

Citations
  1. Hussain 2013.
  2. PR Newswire 2012.
  3. Vanderklippe 2013.
  4. Hackett 2013.
  5. Krugel 2013.
  6. Goodman 2013.

References
  • Goodman, Lee-Anne (22 May 2013). "Republicans aim to take Keystone XL decision out of Obama's hands". The Canadian Press.
  • Hackett, D.; Noda, L.; Grissom, S.; Moore, M.C.; Winter, J. (8 February 2013). "Pacific Basin Heavy Oil Refining Capacity" (PDF). School of Public Policy, University of Calgary. Calgary, Alberta. 6 (8).
  • Hussain, Yadullah (25 April 2013). "Alberta exploring at least two oil pipeline projects to North". Financial Post.
  • Krugel, Lauren (5 February 2013). "New Brunswick an ally in getting landlocked Alberta crude to tidewater". Edmonton Journal vi Canadian Press.
  • "First Nations and Alaskan Tribes show support for Alberta-Alaska rail link". PR Newswire. Vancouver, British Columbia. 14 November 2012.
  • Vanderklippe, Nathan (22 January 2013). "Oil differential darkens Alberta's budget". Calgary, Alberta: Globe and Mail.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.