#plumbing
5 APIs con questa etichetta
Water Hammer API
Water-hammer (hydraulic-transient) maths as an API, computed locally and deterministically — the surge-pressure, wave-speed and valve-timing numbers a piping or plumbing engineer guards a system with. The surge endpoint applies the Joukowsky equation Δp = ρ · a · Δv: a sudden stop of the flow spikes the pressure by the fluid density × the pressure-wave speed × the velocity change — stopping 2 m/s of water at a ≈ 1200 m/s adds about 24 bar (348 psi), far above the line pressure, which is what bangs the pipes and can split fittings. The wave-speed endpoint gives that pressure-wave speed: a = √(K/ρ) in a rigid pipe (≈ 1,480 m/s for water), slowed in a real elastic pipe to √(K/ρ) ÷ √(1 + (K·D)/(E·t)) — a thin or plastic pipe gives a lower wave speed and a gentler surge, which is why PVC tolerates hammer better than steel. The critical-time endpoint gives 2L/a, the round-trip time of the wave: close a valve faster than this and you get the full Joukowsky surge, slower and the returning relief wave eats into it, so sizing closure times (or fitting a surge tank or air chamber) above the critical time is the standard cure. Everything is computed locally and deterministically, so it is instant and private. Ideal for piping- and plumbing-design tools, pump-station and pipeline-surge analysis, and hydraulic-engineering utilities. Pure local computation — no key, no third-party service, instant. Idealised single-pipe transient. 3 compute endpoints. For steady pipe pressure drop use a Darcy API; for pump head and affinity a pump API.
api.oanor.com/waterhammer-api
Radiant Floor API
Radiant-Floor- und Hydronic-Heizungsmathematik als API, lokal und deterministisch berechnet – die Output-, Rohr- und Durchflusszahlen, mit denen ein Installateur oder Heimwerker einen warmen Fußboden plant. Der Output-Endpunkt gibt die Wärme aus, die ein warmer Fußboden abgibt: etwa 2 BTU/h pro Quadratfuß für jedes °F, das die Bodenoberfläche wärmer als der Raum ist, also liefert ein 85 °F-Boden in einem 70 °F-Raum etwa 30 BTU/h/ft² – etwa 9.000 BTU/h über 300 ft², die Komfortgrenze, da der Boden bei ~85 °F gehalten wird. Der Rohr-Endpunkt gibt das Rohr und die Schleifen für eine Fläche bei einem Abstand an: Feldrohr = Fläche × 12 ÷ Abstand, also benötigt 300 ft² bei 9-Zoll-Abstand 400 Fuß Rohr, aufgeteilt in Schleifen unter ~300 Fuß (zwei 200-Fuß-Schleifen), damit die Pumpe sie durchdrücken kann. Der Durchfluss-Endpunkt gibt die Schleifendurchflussrate für eine Heizlast an, GPM = Last ÷ (500 × ΔT), wobei 500 die Wasserkonstante und ΔT die Vorlauf-Rücklauf-Differenz ist – 9.000 BTU/h bei einer ΔT von 20 °F benötigt 0,9 GPM. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Fußbodenheizungs- und Sanitäranwendungen, Hydronic-Design- und PEX-Layout-Tools, HVAC-Rechner für Auftragnehmer und DIY-Bau-Seiten. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts gespeichert. 3 Compute-Endpunkte. Schätzungen – mit einer vollständigen Wärmeverlustberechnung überprüfen. Für die Gebäudelast eine HVAC-API verwenden; für die Rohrgeschwindigkeit eine Durchflussraten-API.
api.oanor.com/radiant-api
Plumbing Code API
Plumbing-code sizing maths as an API, computed locally and deterministically — the fixture-unit and pipe-sizing numbers a plumber, designer or inspector runs from the code book. The dfu endpoint totals drainage fixture units for a set of fixtures (IPC Table 709.1): pass a list like toilet:2,lavatory:3,shower:1,kitchen_sink:1 and it weights each by its discharge — a toilet is 3, a lavatory 1, a tub or shower 2 — for a total of 13, with a grouped full bathroom counting as 6 rather than the sum of its parts. The pipe-size endpoint gives the minimum building-drain size for a DFU load at a slope (IPC Table 710.1(1)): the smallest pipe whose capacity meets the load, so 50 DFU at a quarter-inch-per-foot fall needs a 4-inch drain, with the reminder that any drain carrying a water closet is a 3-inch minimum. The supply-gpm endpoint reads probable peak water demand off the Hunter curve: diversity means 100 supply fixture units draws only about 54 GPM, not the sum of every fixture running at once — the number you size the water service against. Everything is computed locally and deterministically, so it is instant and private. Ideal for plumbing-design and estimating apps, code-check and permit tools, MEP-engineering calculators, and trade-school aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Based on the IPC — verify against the code adopted in your jurisdiction.
api.oanor.com/plumbing-api
Septic System API
Septic-system sizing as an API, computed locally and deterministically with the typical US onsite-wastewater rules of thumb. The flow endpoint estimates the design wastewater flow for a home from its number of bedrooms (assuming two people per bedroom) or an explicit occupancy, at a default 60 gallons per person per day, returning the daily flow in US gallons and litres. The tank endpoint recommends a septic tank size as the larger of a retention-based size (flow × retention days, default two days) and the typical bedroom-based code minimum (≤3 bedrooms 1,000, 4 bedrooms 1,200, 5 bedrooms 1,500, 6 bedrooms 2,000 US gallons), and tells you which one governs. The drainfield endpoint sizes the soil absorption (leach) field: it divides the daily flow by a soil loading rate — given directly or looked up from a percolation rate in minutes per inch — to get the absorption area, then divides by the trench width to get the trench length, in both imperial and metric. Everything is computed locally and deterministically, so it is instant and private. An estimating aid, not a code-stamped design — always confirm with your local health authority. Ideal for plumbing and septic-installer tools, rural real-estate and land apps, home-building and permitting calculators, and inspection software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is septic / onsite-wastewater sizing; for storage-tank volume and fill level use a tank API.
api.oanor.com/septic-api
API de Dureza del Agua
Matemáticas de dureza del agua como API, calculadas local y determinísticamente. El endpoint convert convierte un valor de dureza entre todas las unidades comunes — partes por millón / miligramos por litro como carbonato de calcio, granos por galón estadounidense, grados alemanes (°dH), grados franceses (°f), grados ingleses o Clark, y milimoles por litro — pasando todo a través de ppm (1 gpg = 17.118 ppm, 1 °dH = 17.848, 1 °f = 10, 1 °Clark = 14.254), y clasifica el resultado. El endpoint classify etiqueta un valor como blanda, moderadamente dura, dura o muy dura en la escala USGS/OMS. El endpoint softener dimensiona un ablandador de agua: a partir de la dureza y el uso de agua del hogar calcula los granos de dureza eliminados por día y la capacidad de granos necesaria entre regeneraciones. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para herramientas de tratamiento de agua y plomería, aplicaciones de acuarios y piscinas, dimensionamiento de electrodomésticos y ablandadores, y software para hogar y laboratorio. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es conversión de dureza del agua; para conversión general de unidades use una API de conversión de unidades y para dosificación de piscinas use una API de piscinas.
api.oanor.com/hardness-api