Illuminance & Uniformity Analyzer

Read the tool instructions in Markdown and the request/response schemas in OpenAPI. These public calculation APIs run the same models as the web and offline calculators. No account, API key or Turnstile is required.

• Illuminance & Uniformity Analyzer — Full tool instructions (Markdown)
• OpenAPI contract
• Agent site index

Illuminance & Uniformity Analyzer

POST /api/tools/v1/illuminance
Content-Type: application/json

Analyze recorded illuminance on one horizontal rectangular area, sampled at equal-area cell centres. This is measurement analysis, not a lighting simulation. Supply every physical input explicitly in metres and lux. It does not use a phone sensor, invent readings or assess compliance, calibration or measurement uncertainty.

illuminance

Measured illuminance and uniformity

The example is illustrative: an 8 m by 6 m rectangle, a horizontal plane 0.75 m above the floor, 6 columns by 4 rows and 24 readings. illuminanceLux is row-major, top row first, left to right; its length must equal rows × columns. A1 is the top-left cell centre, x increases right and y increases down. Null is unmeasured; zero is a recorded value. Set either target to null when it is not supplied; do not infer defaults from a room name.

{
  "widthM": 8,
  "depthM": 6,
  "measurementHeightM": 0.75,
  "columns": 6,
  "rows": 4,
  "illuminanceLux": [
    520,
    548,
    564,
    582,
    560,
    534,
    486,
    522,
    550,
    574,
    566,
    540,
    472,
    508,
    539,
    562,
    553,
    524,
    255,
    482,
    520,
    542,
    530,
    500
  ],
  "targets": {
    "averageLux": 500,
    "uniformityMinAvg": 0.6
  }
}

To review in the page, save result.project as JSON and use Open project. It contains the same engineering facts and empty site/operator/calibration fields; fill those locally. links.share is null: project metadata is not encoded in a public URL. The browser can print/save PDF, export all points as CSV, download a project, and produce an offline HTML copy. API input does not accept personal or site records; the API does not persist readings. Project files are separate from API requests and have their own format/version. CSV values use metres and lux. The lowest measured point does not establish the continuous-area minimum.

Request limits and errors

Send uncompressed application/json with strict types and no query parameters. Indoor lighting bodies are limited to 16 KiB; driver-match bodies to 16 KiB; battery bodies to 16 KiB; voltage bodies to 16 KiB; resistor bodies to 16 KiB; DMX bodies to 1024 KiB and 1000 fixtures; pixel bodies to 64 KiB, 64 run rows, 128 outputs and 2000000 channels. DALI bodies are limited to 64 KiB, 24 rows and 512 devices. Illuminance bodies are limited to 16 KiB and 400 planned points. Photometry bodies are limited to 1024 KiB with up to 4 files and 16 by 721 query directions per file. Lighting-cost bodies are limited to 64 KiB with up to 20 groups in each scenario. Body reading expires after 5 seconds. Complete success JSON is bounded to 4 MiB. GET/HEAD return 405; OPTIONS returns 204. Source responses are no-store. Anonymous browser CORS permits POST/OPTIONS and Content-Type with credentials omitted.

Tool POST requests and ordinary page requests share 120 requests per 60 seconds per IP/Cloudflare location; mitigation lasts 60 seconds. Heavy tool use can temporarily block pages from the same source. This is not an independent or globally exact API quota. Inquiry/search use their existing separate rule. Tool POST requests do not inherit the company-page or verified-bot exemption.

Cloudflare can return 403/429/5xx before the application, sometimes as HTML without CORS or Retry-After. Check HTTP status and Content-Type before parsing JSON. A browser may see only a network error. Do not present an error or an older result as a successful new calculation.