Hydraulic conductivity converter
0.00001 m/s of hydraulic conductivity is 3.6 cm/h: switch a K value between eleven metric and US units while you read a borehole log, a packer test or a liner specification, with no textbook appendix. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Numeric hydraulic conductivity
- 0.00001
- Source unit
- m/s
- Target unit
- cm/h
- Result
- 3.6
- From label
- meters per second
- To label
- centimeters per hour
- Base ms
- 0.00001
A hydraulic conductivity converter turns a soil or aquifer K value written in one unit into another without hunting textbook appendices or rewriting spreadsheet formulas.
Supported units and how the conversion is computed
The converter accepts hydraulic conductivity K under stable canonical codes that hydrogeologists, geotechnical engineers, and environmental modelers use every day. SI and cgs length-per-time forms are m/s for meters per second, cm/s and mm/s for centimeters and millimeters per second, m/h, cm/h, and mm/h for the same lengths per hour, and m/d for meters per day.
US customary forms are ft/s and ft/d for feet per second and feet per day on the international foot, in/h for inches per hour, and gpd/ft2 for US gallons per day per square foot—the flux-style unit still common in American well and aquifer reports.
One centimeter per second is exactly one hundredth of a meter per second; one centimeter per hour is that quantity divided by thirty-six hundred; one meter per day is one over eighty-six thousand four hundred; one foot equals exactly zero point three zero four eight meters; one US liquid gallon is exactly two hundred thirty-one cubic inches, so gpd/ft2 maps to meters per second through the product of that volume, the square of the international foot, and the length of a day in seconds.
Because the intermediate is always meters per second, converting A to B and B to A is consistent up to the published rounding of twelve decimal places, and there is no pairwise matrix that can drift out of sync when a new unit is added later.
Where a quick K conversion saves time
Use the free in-browser hydraulic conductivity converter when you need a quick meters-per-second to centimeters-per-hour, feet-per-day to gpd-per-square-foot, or millimeters-per-second to meters-per-day check while reading a borehole log, packer test, grain-size chart, landfill liner specification, MODFLOW parameter file, or textbook table that mixes unit systems. Open the page, enter the number and units, and copy the result without installing a spreadsheet, a unit library, or a desktop calculator pack.
Source inputs follow the same retention rules as other KIT parse items, and results are safe to cache because the algorithm is fully deterministic. Authors shipping mobile apps or chatbots can map the result and formula fields directly into cards that show both the number and the conversion path engineers and regulators expect on paper.
What you can do with it
Borehole logs and packer tests
Normalize field K from cm/s or ft/d into m/s for SI models and reports without hand factors or mixed spreadsheets.
US aquifer and well reports
Convert gpd/ft² and feet per day into meters per second for MODFLOW and international collaboration with exact US gallon factors.
Geotech liners and drainage design
Switch clay and gravel K between mm/s, cm/h, and m/d when specifications and lab sheets disagree on units.
FAQ
Which hydraulic conductivity units does this converter support?
m/s, cm/s, mm/s, m/h, cm/h, mm/h, m/d, ft/s, ft/d, in/h, and gpd/ft2 (US gallons per day per square foot).
How do you convert meters per second to centimeters per hour?
The engine multiplies by the exact m/s factor for the source and divides by the cm/h factor (0.01 m per 3600 s). Example: 1e-5 m/s becomes 3.6 cm/h.
How is gpd/ft² converted to m/s?
The intermediate is always meters per second, then scaled to the target unit.
What happens if I send an unknown unit?
The message names the field and lists supported units. Validation failures are not charged.
Is the hydraulic conductivity converter free?
The browser tool runs free on your device.
Related tools
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/conv/hydraulic-conductivity \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":0.00001,"from":"m/s","to":"cm/h"}'const res = await fetch("https://api.kit.forhosting.com/conv/hydraulic-conductivity", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 0.00001,
"from": "m/s",
"to": "cm/h"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/hydraulic-conductivity",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 0.00001,
"from": "m/s",
"to": "cm/h"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/hydraulic-conductivity", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":0.00001,"from":"m/s","to":"cm/h"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":0.00001,"from":"m/s","to":"cm/h"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/hydraulic-conductivity", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 0.00001,
"from": "m/s",
"to": "cm/h"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.hydraulic_conductivity",
"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. |
Technical notes
The browser tool runs free on your device; the prepaid API charges $0.002 per successful item when pipelines need the same contract from servers and automation.
Supported units and how the conversion is computed
Friendly aliases such as meters per second, centimeters per hour, feet per day, gallons per day per square foot, gal/day/ft2, and gpd/sq ft are normalized case-insensitively so forms and APIs can pass either short codes or full names. Every request multiplies the input by the exact meters-per-second factor for the source, then divides by the factor for the target.
Request shape, response fields, and unknown-unit errors
The error message names the bad field and lists the supported set so clients can correct forms without guessing. Zero converts cleanly to zero in every target unit. Send a JSON body with three required fields: value as a finite non-negative number, from as the source unit string, and to as the target unit string. Aliases amount, quantity, and k are accepted for value; unit_from and source for from; unit_to and target for to. On success the response echoes the canonical from and to codes, human-readable from_label and to_label strings, the converted result, the intermediate base_ms quantity in meters per second, a dimensionless conversion_factor equal to the ratio of the two unit factors, a short formula line suitable for UI display, the method tag hydraulic_conductivity_si, and the fixed list of units_supported. Missing value, non-finite numbers such as NaN or Infinity, negative values, missing unit fields, and any token that does not map to a supported unit fail with invalid_input and are not charged after the engine rejects the request. Identical inputs always yield identical JSON because the path is pure arithmetic with no randomness, no remote lookup, and no dependence on the wall clock, which makes the endpoint safe to pin in continuous-integration goldens and SDK contract tests. Extreme magnitude pairs remain well-defined as long as IEEE double precision can represent the intermediate product; typical aquifer K values from clay through gravel sit comfortably inside that range.
Browser use, API pricing, and everyday workflows
Switch to the prepaid API when a hydrogeology LIMS, geotechnical report generator, environmental compliance pipeline, irrigation drainage model, or groundwater software plugin must convert K at scale under a stable KIT contract at $0.002 per successful item; validation failures that raise invalid_input do not consume balance after rejection. Pair this endpoint with general length or flow converters when a product pipeline needs those families as well, or call it alone when search traffic is specifically for hydraulic conductivity conversion—soil K, aquifer transmissivity companions, and gpd/ft2—rather than a general unit switchboard.