Longshore sediment transport rate calculator
Longshore sediment transport is the net alongshore movement of beach sand and gravel driven by waves that break at an angle to the shoreline.
Run — free
Coastal engineers, geomorphologists, and shoreline managers estimate that rate with the CERC formula, which links breaking wave height and the wave approach angle at breaking to a bulk transport rate used in sediment budgets, inlet bypassing studies, and groin or breakwater impact screening. This longshore sediment transport rate calculator accepts breaking wave height in metres, the approach angle in degrees relative to the shore-normal, and an optional CERC coefficient K (default 0.39), then returns the signed transport rate, its absolute value, and the intermediate sin(2α) term so you can audit the result. Negative wave height is rejected as invalid input rather than silently flipped. The same pure analytic module powers the free browser widget and the API path, so classroom checks and production notebooks never disagree on the CERC arithmetic.
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/earth/longshore-transport \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"breaking_wave_height":1.5,"wave_angle_deg":15}'const res = await fetch("https://api.kit.forhosting.com/earth/longshore-transport", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"breaking_wave_height": 1.5,
"wave_angle_deg": 15
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/earth/longshore-transport",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"breaking_wave_height": 1.5,
"wave_angle_deg": 15
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/earth/longshore-transport", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"breaking_wave_height":1.5,"wave_angle_deg":15}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"breaking_wave_height":1.5,"wave_angle_deg":15}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/earth/longshore-transport", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"breaking_wave_height": 1.5,
"wave_angle_deg": 15
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "earth.longshore_transport",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |