[{"slug":"sensing","category":"core","lenses":["field","platform"],"title":{"ja":"センシングを、明日の作業に変える","en":"Turn sensing into tomorrow’s work"},"dek":{"ja":"RGB・マルチスペクトル・熱画像。測れることと、判断できることを分ける。","en":"RGB, multispectral and thermal imaging: separate measurements from decisions."},"guide":{"ja":"赤い場所が病気とは限らんのよ。まず畑で確かめる場所を決めようや。","en":"A red patch is not a diagnosis. First decide where to check on the ground."},"sections":[{"title":{"ja":"指標は、診断の入口","en":"An index is a starting point"},"body":{"ja":"NDVIは近赤外と赤の反射の差を、その和で割った植生指標じゃ。葉の状態を調べる手がかりにはなるが、単独で原因や処方を決めるものではない。NASAの解説を入口に、画像の色と農学的な診断を分けて考えよう。","en":"NDVI compares near-infrared and red reflectance using (NIR − red) / (NIR + red). It is a vegetation indicator, not a standalone diagnosis or prescription. NASA explains its measurement basis; agronomic interpretation still requires context."},"kind":"evidence"},{"title":{"ja":"撮影の前に、問いをひとつ","en":"Start with one decision"},"body":{"ja":"本ガイドの提案は「見たい画像」より先に「変えたい判断」を書くこと。欠株を探すのか、雑草を確認するのか、灌水を見直すのか。必要な解像度・撮影時期・現地確認点・納品期限がそこで変わる。全面を高精細に撮る費用と、衛星で候補を絞って部分撮影する費用を比べる。","en":"Our proposed workflow starts with a decision: locate missing plants, confirm weeds or inspect irrigation. This determines resolution, timing, ground samples and delivery deadline. Compare full-field high-resolution capture with satellite screening followed by targeted drone inspection."},"kind":"design"},{"title":{"ja":"時系列を比べられる状態にする","en":"Make dates comparable"},"body":{"ja":"圃場ID、作物、生育段階、撮影日時、センサー、校正方法、日照、処理バージョンを同じ記録に結ぶ。自動で色の範囲を変える地図は、昨日との比較を誤らせることがある。固定スケールと品質フラグを併記し、雲影・水面・欠測は異常と混同しない。","en":"Link field ID, crop stage, acquisition time, sensor, calibration, lighting and processing version. Use comparable map scales and quality flags. Separate shadows, water and missing observations from genuine change; do not silently recolor each date."},"kind":"design"},{"title":{"ja":"納品は、確認場所と次の一手","en":"Deliver a location and next action"},"body":{"ja":"農家向けの一枚には「北側の畝を確認」「いつまでに」「根拠写真」「まだ分からないこと」を載せる。原画像や指数は詳細として残す。確認した結果を戻してもらい、誤検知と見逃しを次の解析に反映する。解析だけで施肥量を自動確定する設計にはしない。","en":"The farmer-facing output should name the location, deadline, evidence photo and uncertainty. Keep raw imagery and indices available as detail. Collect ground-check outcomes to track false alarms and missed issues. Do not automatically authorize fertilizer application from an image score."},"kind":"design"},{"title":{"ja":"他の畑で当たるかを、別に試す","en":"Test whether the model transfers"},"body":{"ja":"INIFAPの飼料トウモロコシ研究は、画像から窒素を推定しても、生育段階を分けた追加検証が必要と述べとる。掲載の81%は説明した分散で、診断の正答率ではない。研究圃場での当てはまりと、新しい畑で使えることは分けて読むんじゃ。","en":"INIFAP’s forage-maize study recommends further validation by growth stage. Its 81% result is explained variance, not diagnostic accuracy. Fit within a research field should be distinguished from performance on a new farm."},"kind":"evidence"},{"title":{"ja":"受け入れ条件は、画像の美しさより使える範囲","en":"Accept usable coverage, not attractive imagery"},"body":{"ja":"ここからは本ガイドの設計提案じゃ。発注時に「対象圃場のどの部分を、いつまでに、何の判断に使うか」を決め、撮影範囲と解析可能範囲を別々に納品させる。樹冠の影、画像の継ぎ目、ぼけ、位置ずれを欠測として表示できるかも検収する。地上の既知点と画像の位置差を測り、許容差は見回り用と部分散布用で個別に合意する。境界が不明な場所をゼロ値で埋めてはいけん。画像ファイルが開くだけでは合格にせず、現地担当者が地図から確認場所へたどり着けるかまで試そう。再撮影が必要なら、その費用と納期も最初の契約に含める。","en":"Our proposed acceptance process begins with the area, decision and delivery deadline. Require separate maps of captured coverage and usable analytical coverage. Check whether shadows, stitching defects, blur and positional uncertainty appear as missing data. Measure displacement from known ground points and agree tolerances separately for scouting and targeted application. Unknown boundaries must not be filled with zero values. Acceptance should include a field worker locating the indicated inspection point, rather than merely opening an image file. Agree the cost and deadline for any necessary repeat flight before commissioning."},"kind":"design"},{"title":{"ja":"警報がない場所にも、確認点を置く","en":"Inspect areas without alerts too"},"body":{"ja":"検証点を赤い場所だけから選ぶと、見逃しが分からん。提案する検証では、警報あり・警報なしの両方から場所を選び、同じ生育段階で現地を確認する。病害、乾燥、欠株など、今回判定したい状態の定義も先にそろえる。モデルを作るために使った地点は、最終評価用と区別して記録する。誤警報は余分な見回り時間、見逃しは対応の遅れとして数え、画像一枚の正解率だけで判断せんことじゃ。別の圃場や年で試していない場合は、その範囲を表示する。担当者が結果を修正したら、元の推定と理由を消さずに残す。","en":"Checking only red areas cannot reveal missed problems. Sample both alerted and non-alerted locations and inspect them at a comparable growth stage. Define the condition being assessed—disease, water stress or missing plants—before judging performance. Distinguish locations used to develop the model from those reserved for final evaluation. Record false alarms as additional scouting work and misses as delayed responses, rather than relying solely on image-level accuracy. Display whether other farms or years have been tested. When a reviewer corrects an estimate, preserve the original output and the reason."},"kind":"design"},{"title":{"ja":"一枚の行動票を、解析の出口にする","en":"End the analysis with an action record"},"body":{"ja":"架空の記録例なら「圃場A、北側区画、要確認、水ストレスか病害か未確定、担当者が次回灌水判断前に点検」と書ける。表示を簡単にするとは、不確かさを隠すことではないんよ。農家向け画面は場所・期限・担当・確認結果を中心にし、根拠画像と処理版は詳細へ置く。確認後は「灌水設備を修理」「経過観察」「画像不良」のように閉じ方を選べる設計にする。別サービスへ渡す場合も圃場ID、観測日時、単位、保留理由を一緒に出力する。美しい地図を受け取ったのに誰も動かない状態を、未完了の仕事として見えるようにするんじゃ。","en":"An illustrative record could read: “Field A, north block; inspection required; water stress versus disease unresolved; assigned worker to inspect before the next irrigation decision.” Simplicity must not hide uncertainty. Center the farmer’s view on location, deadline, owner and outcome, with imagery and processing versions available as detail. Let the reviewer close the task as irrigation repair, continued observation or poor imagery. Exports to another service should retain field ID, observation time, units and the reason for a hold. A delivered map with no assigned follow-up should remain visible as unfinished work."},"kind":"design"}],"checklist":{"ja":["判断したい問いを定義","校正と撮影条件を記録","現地確認で原因を検証","納品後の行動を記録"],"en":["Define the decision","Record calibration and capture conditions","Validate causes on the ground","Record the action taken"]},"sources":[{"title":"NASA — Measuring Vegetation (NDVI & EVI)","url":"https://science.nasa.gov/earth/earth-observatory/measuring-vegetation-ndvi-evi/"},{"title":"UN Handbook — UAV applications in agricultural statistics","url":"https://fao-eostat.github.io/UN-Handbook/uav_agriculture.html"},{"title":"INIFAP / Nitrogen — Spectral Index-Based Estimation of Total Nitrogen in Forage Maize","url":"https://pdfs.semanticscholar.org/50f1/963c7753fa7b95f4e1dbb55b8d4d2cf7abc5.pdf"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"spraying","category":"core","lenses":["field","business"],"title":{"ja":"農薬散布は「飛べる」と「効く」を分ける","en":"Spraying: flying well and treating well"},"dek":{"ja":"飛行許可、薬剤の適用、付着、ドリフト、効果を一つずつ確かめる。","en":"Check aviation, product authorization, deposition, drift and efficacy separately."},"guide":{"ja":"飛んで戻っただけでは仕事は終わらん。必要な場所に届いたか、そこが大事じゃ。","en":"A completed flight is not a completed treatment. Check what reached the target."},"sections":[{"title":{"ja":"何をもって成功とするか","en":"Define treatment success"},"body":{"ja":"Virginia Techは、散布の成果を機体設定、校正、液滴、風などの条件と結びつけて説明し、ドリフトと付着の両方を見る必要を示している。実際の運用では製品ラベルと地域の規則が優先される。機種の最大速度を、そのまま適切な散布速度とは考えない。","en":"Virginia Tech links application quality to calibration, droplet characteristics, weather and aircraft settings. Deposition and drift both matter. Actual operations must follow the product label and local rules; advertised maximum speed does not establish a suitable application speed."},"kind":"evidence"},{"title":{"ja":"三つの確認を独立させる","en":"Maintain three independent checks"},"body":{"ja":"本ガイドでは、航空上の条件、農薬の適用条件、周辺への配慮を別の確認欄にする。適用作物・病害虫・使用方法・使用回数・収穫までの期間は、当該地域の登録とラベルで確認する。「飛行可」だけを緑色にして全体の実施可否と誤認させない。","en":"Our checklist separates aviation conditions, pesticide authorization and surrounding exposure. Confirm the registered crop, target, method, number of treatments and harvest restrictions from the applicable label. An aviation green light must not imply permission for the whole operation."},"kind":"design"},{"title":{"ja":"試験区で確かめてから広げる","en":"Validate before scaling"},"body":{"ja":"製造元の手順と地域の指導に沿い、飛行高度、速度、実効散布幅、流量を記録して付着を評価する。水感紙の結果だけで生物学的な防除効果を断定しない。作物の上部・内部、風下側、境界付近を分け、無処理区や従来法との比較を設ける。","en":"Following manufacturer procedures and local agronomic guidance, record height, speed, effective swath and flow. Deposition cards alone do not prove biological control. Compare canopy zones, downwind edges and reference treatments; retain untreated controls where appropriate."},"kind":"design"},{"title":{"ja":"中断と再開を記録する","en":"Record interruption and restart"},"body":{"ja":"補給後の再開点、散布済み範囲、残量、風の変化を記録する。ルートを再計算するときも二重散布を防ぐ履歴を残す。周辺への飛散、漏れ、体調不良などがあれば作業を止め、地域の事故対応手順に従い、原因確認まで再開しない。","en":"Record restart location, treated area, remaining product and weather changes. Replanning must preserve the treatment history to prevent overlap. Stop for drift, leaks or exposure concerns and follow local incident procedures before deciding whether work can resume."},"kind":"design"},{"title":{"ja":"付着と空中への移動を、別に測る","en":"Measure deposition and airborne movement separately"},"body":{"ja":"INTAとバルカルセの研究者が示すドリフト評価では、地上に落ちた量と空中を移動する量を別の採取系で調べ、気象も同時に記録する。水感紙は補助的な情報じゃ。紙に付着が見えないことだけを理由に、飛散なしとは判定できん。","en":"The INTA–Balcarce drift protocol separately samples deposited and airborne material while recording weather. Water-sensitive cards provide complementary information. An absence of visible deposits on a card does not establish zero drift."},"kind":"evidence"},{"title":{"ja":"タンクの帳尻と、圃場の帳尻を照合する","en":"Reconcile the tank and field records"},"body":{"ja":"本ガイドでは、受入量、追加補給、終了時残量、回収・洗浄へ移した量を一つの資材帳簿に残す設計を勧める。液量と有効成分量を混同せず、製品名・ロット・単位も保つ。一方、圃場帳簿には処方の版、対象面積、散布したと推定する範囲、確認できない範囲を残す。両者に差が出たら、計器誤差、漏れ、記録漏れ、残液などを調べる入口になる。ただし消えた量をすべてドリフトと呼ぶことはできん。流量計が故障しているのに予定値だけで実績を埋めると、監査できない帳簿になる。推定値には推定である印を付けよう。","en":"Our proposed material ledger records receipts, refills, closing residue and material transferred for recovery or cleaning. Keep liquid volume distinct from active-ingredient quantity, retaining product, lot and units. A separate field ledger should preserve prescription version, target area, estimated treatment coverage and uncertain coverage. Differences prompt investigation of measurement error, leaks, missing entries or residue; they cannot all be classified as drift. Filling an actual-use log with planned values after a flow-meter failure destroys its audit value. Mark estimates explicitly."},"kind":"design"},{"title":{"ja":"中断区間を、二つの位置で復元する","en":"Reconstruct interruptions with two kinds of position"},"body":{"ja":"飛行軌跡と吐出の状態は別物として保存する。位置の線がつながっていても、ポンプ停止中の区間は処理済みではないし、送信が途切れた区間は未処理とも断定できん。架空の記録なら「任務S17、計画版3、区画C、通信断、吐出確認待ち」と保留にする。再開担当者は最後に確認できた散布区間、残液、現在の条件を照合して引き継ぐ。不明区間へ自動で上塗りする設計にはしない。再処理が必要か、どう扱えるかは製品条件と農学担当者の判断へ戻し、誰が確認したかを残すんじゃ。","en":"Store flight trajectory separately from discharge state. A continuous track does not mean treatment occurred while a pump was off, and a communications gap does not prove that treatment stopped. An illustrative record could be “Mission S17, plan version 3, block C; communications gap; discharge confirmation pending.” Before restart, the responsible person reconciles the last confirmed treatment segment, remaining material and current conditions. Do not automatically reapply over uncertain segments. Decisions about retreatment return to the applicable product conditions and agronomic reviewer, with the reviewer identified in the record."},"kind":"design"},{"title":{"ja":"検収を、作業当日と効果確認日に分ける","en":"Separate operational acceptance from efficacy review"},"body":{"ja":"検収表は、当日の記録がそろったかと、後日の防除結果が目的を満たしたかを分ける提案じゃ。付着の評価位置は上部・内部・端部などを事前に決め、比較区には同じ方法で観測を置く。効果確認の時期は対象と評価計画に合わせ、作業者の都合だけで変えない。同じ日に別の防除や灌水を行ったなら、その履歴も添える。例えば機体を変えると同時に薬剤と評価日も変えた比較では、差を機体だけの効果とは言えん。請負契約も「飛行完了」「記録確認」「効果評価」を分けると、再調査や是正を誰が担当するかが明確になる。","en":"Our proposed acceptance sheet separates completeness of the operational record from later treatment efficacy. Predefine deposition assessment locations, such as outer canopy, interior and edges, and observe reference areas consistently. Schedule efficacy review around the target and evaluation plan, rather than operator convenience. Include other treatments and irrigation in the history. If aircraft, product and assessment date all change together, the difference cannot be attributed solely to the aircraft. Separate flight completion, record acceptance and efficacy evaluation in a service contract so responsibility for investigation and correction is clear."},"kind":"design"}],"checklist":{"ja":["ラベルと登録条件を確認","飛行・散布の法的条件を別々に確認","付着と効果の検証計画","中止・再開点と残液を記録"],"en":["Verify label and registration","Separate aviation and application checks","Plan deposition and efficacy validation","Record stops, restart points and remaining liquid"]},"sources":[{"title":"Virginia Tech — Spray Drones: Technology, Regulation and Field Operations","url":"https://www.pubs.ext.vt.edu/SPES/spes-819-spray-drones-in-agriculture-technology-regulation-and-field-operations.html"},{"title":"FAA — Dispensing Chemicals and Agricultural Products (Part 137)","url":"https://www.faa.gov/uas/advanced_operations/dispensing_chemicals"},{"title":"INTA — Desarrollan un protocolo para estandarizar la medición de deriva","url":"https://www.argentina.gob.ar/noticias/desarrollan-un-protocolo-para-estandarizar-la-medicion-de-deriva"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"spreading","category":"core","lenses":["field","business"],"title":{"ja":"肥料・種子をまく、その後まで設計する","en":"Fertilizer and seed: design beyond spreading"},"dek":{"ja":"散布精度だけでなく、発芽・定着・養分収支までつなぐ。","en":"Connect distribution quality with emergence, establishment and nutrient balance."},"guide":{"ja":"まいた量が同じでも、育ち方は同じとは限らんけえね。","en":"Equal spreading rates do not guarantee equal establishment."},"sections":[{"title":{"ja":"液体散布と粒剤散布を分ける","en":"Separate liquid and granular operations"},"body":{"ja":"設計上、液体のL/haと粒剤のkg/haを別の量として管理する。種子は質量だけでなく粒数、発芽率、処理方法が関わる。湿度や粒径が異なる材料へ切り替える際は、同じ設定の流用を避け、メーカーの校正手順と現場の計測を組み合わせる。","en":"In the proposed data model, keep L/ha and kg/ha distinct. Seed also requires count, germination and treatment information. Revalidate settings when material size or moisture changes, using manufacturer calibration procedures and field measurements."},"kind":"design"},{"title":{"ja":"処方と実績を二つ残す","en":"Keep prescription and actual application"},"body":{"ja":"処方マップは予定、散布ログは実績じゃ。版番号と単位、座標系、適用日を持たせる。面積が小さくなる境界や旋回部では、指示量と実際の吐出の差を確認する。土壌試験・作付計画・収量記録をもとに農学担当者が処方を承認する設計を勧める。","en":"A prescription is a plan; an application log is an observation. Version both with units, coordinate reference and validity date. Check boundary and turning effects. Have an agronomic reviewer approve prescriptions using soil tests, cropping plans and yield records."},"kind":"design"},{"title":{"ja":"播種後の費用を忘れない","en":"Count the work after seeding"},"body":{"ja":"直播の比較表には整地、水管理、鳥害、除草、補植、収穫時の均一性を入れる。ドローンの作業時間だけを移植作業と比べても、経営上の結論は出ない。試験区の出芽率と最終収量を追い、一作の総費用と売上の差で評価する。","en":"Compare establishment systems over the whole season: preparation, water, birds, weeds, replanting and harvest uniformity. Flight time alone is not a fair comparison with transplanting. Track emergence and final yield in trial plots, then compare total seasonal cost and revenue."},"kind":"design"},{"title":{"ja":"適期にまけても、定着するとは限らん","en":"Timely broadcasting does not guarantee establishment"},"body":{"ja":"グエルフ大学の立毛大豆への小麦播種試験では、収穫前にまける利点がある一方、地表の種子が乾き、発芽後に枯れる例も報告された。空から届ける工程を短くできても、種子と土、水分の関係まで解決したことにはならんのじゃ。","en":"University of Guelph trials broadcast wheat into standing soybean before harvest. They also reported surface seeds drying and seedlings failing after germination. Earlier delivery does not resolve seed–soil contact and moisture requirements."},"kind":"evidence"},{"title":{"ja":"材料のロット変更を、校正変更として扱う","en":"Treat a material change as a calibration change"},"body":{"ja":"以下は運用設計の提案じゃ。同じ品名でも、種子処理、粒径、混合比、保管状態が違う材料を、前回と同じ吐出設定で済ませない。材料IDとロット、使用した装置、設定、確認者を対応させる。製造元の手順に沿った校正では、吐出した総量だけでなく、回収容器ごとの量や粒数を記録し、中央に集中して端が薄くなる分布を見逃さんようにする。混合種子は全体の重さが合っていても、成分ごとの分布が合うとは限らん。異なる材料の残留が疑われる場合は、その確認と適切な清掃を完了してから次のロットへ移る設計にする。","en":"The following is an operational design proposal. Do not reuse discharge settings without checking changes in treatment, particle size, mixture or storage condition, even for the same product name. Link material and lot IDs to the device, settings and reviewer. Under the manufacturer’s calibration procedure, record quantities or seed counts in individual collection containers as well as the total. This helps reveal concentrated centers and thin edges. A correct total mass of mixed seed does not establish correct distribution of each component. Resolve suspected residual material and complete the appropriate cleaning before releasing the next lot."},"kind":"design"},{"title":{"ja":"三段階の成績を、別の分母で残す","en":"Keep three outcomes with distinct denominators"},"body":{"ja":"撒き出し、出芽、定着を一つの成功率へまとめないことを提案する。投入した種子数の推定、出芽した株数、評価日に生き残った株数では分母も意味も違う。発芽試験の値と圃場の出芽率も区別し、調査日、調査枠の面積、場所、残渣や水分の状態を残す。植生画像の緑色が増えていても、目的作物か雑草かは現地で確かめる。平均だけでなく、苗が抜けた帯や再播種が必要な区画を地図に戻すんじゃ。最後は収量と後続作業まで確認し、空からの分布が良好だったという結果を、栽培体系全体の成功に読み替えない。","en":"We propose separate measures for release, emergence and establishment. Estimated seed input, emerged plants and plants surviving to the assessment date have different denominators and meanings. Distinguish laboratory germination from field emergence, recording date, sampled area, location, residue and moisture condition. An increase in green imagery still requires field confirmation of crop versus weeds. Map missing bands and areas needing reseeding rather than reporting only an average. Review final yield and subsequent work before describing good aerial distribution as success for the entire cropping system."},"kind":"design","table":{"headers":{"ja":["段階","記録するもの","それだけでは言えないこと"],"en":["Stage","Record","What it does not establish"]},"rows":{"ja":[["吐出・分布","容器別の量、材料ロット","発芽・定着"],["出芽・定着","面積当たり株数、評価日","最終収量"],["一作の評価","収量、追加作業、総費用","翌年・他地域の同じ成果"]],"en":[["Release and distribution","Quantity per container; material lot","Germination or establishment"],["Emergence and establishment","Plants per area; assessment date","Final yield"],["Season review","Yield, additional work and total cost","Identical results elsewhere or next year"]]}}},{"title":{"ja":"まき直しを含めて、作業サービスを検収する","en":"Include corrective work in service acceptance"},"body":{"ja":"架空の作業台帳なら「圃場B、材料ロットL2、処方版4、補給量は計量済み、終了時残量は未確認、北端の分布は再調査」と書く。残量が未確認なら総量の検収は保留し、飛行ログがあるだけで全域の作業を承認せん。農家と請負業者は、どの時点までを業務に含めるか、分布不良と発芽不良を誰が調べるかを事前に合意する。降雨待ちのため実施日が変わった場合は、処方と栽培計画を再確認する。代替の地上機械や手作業を選ぶ費用も比較に入れ、最初の播種料金が安くても、補植や除草で一作の支出が増える例を見逃さんことじゃ。","en":"An illustrative ledger could state: “Field B, material lot L2, prescription version 4; refill weighed; closing residue unconfirmed; north-edge distribution requires review.” Hold total-quantity acceptance until residue is reconciled; a flight log alone does not approve coverage. Agree which stages the service includes and who investigates distribution or emergence failures. If waiting for rain changes the date, reconfirm the prescription and cropping plan. Compare ground-machine and manual alternatives as well. A low initial seeding fee can still produce higher seasonal expenditure if replanting or weed management increases."},"kind":"design"}],"checklist":{"ja":["材料ごとの校正","L・kg・粒数を区別","処方と実績を保存","出芽から収穫まで追跡"],"en":["Calibrate per material","Distinguish volume, mass and seed count","Keep planned and actual application","Track emergence through harvest"]},"sources":[{"title":"Virginia Tech — Spray Drones: Technology, Regulation and Field Operations","url":"https://www.pubs.ext.vt.edu/SPES/spes-819-spray-drones-in-agriculture-technology-regulation-and-field-operations.html"},{"title":"UN Handbook — UAV applications in agricultural statistics","url":"https://fao-eostat.github.io/UN-Handbook/uav_agriculture.html"},{"title":"University of Guelph — Could Drone Seeding Solve a Key Ontario Crop Rotation Challenge?","url":"https://www.uoguelph.ca/alliance/research-impact/could-drone-seeding-solve-crop-rotation-challenge"}],"updated":"2026-10-30","readingMinutes":4},{"slug":"delivery","category":"core","lenses":["field","business","platform"],"title":{"ja":"収穫物と資材を運ぶ、農地の物流","en":"Agricultural logistics, from inputs to harvest"},"dek":{"ja":"斜面・分散圃場・時間制約。飛行の前後にある荷役まで含める。","en":"Include loading, handover and return journeys in the logistics system."},"guide":{"ja":"空の道だけ速くても、荷積みで詰まったらいけんのよ。","en":"A fast flight cannot fix a loading bottleneck."},"sections":[{"title":{"ja":"輸送単位から逆算する","en":"Start with the shipment unit"},"body":{"ja":"本章は導入設計の提案じゃ。収穫箱、苗、肥料、道具では重さだけでなく形、重心、破損許容、衛生条件が違う。人が歩く往復を減らすのか、道路の迂回を減らすのかを決め、空路に適した区間を切り出す。","en":"This chapter proposes a planning method. Harvest boxes, seedlings, fertilizer and tools differ in shape, balance, damage tolerance and hygiene. Identify whether the goal is fewer walking trips or avoiding road detours, then isolate the segment suited to aerial transport."},"kind":"design"},{"title":{"ja":"往復と荷役で処理量を測る","en":"Measure a complete round trip"},"body":{"ja":"評価単位をkg/飛行からkg/作業時間へ変える。積込、確認、往路、荷下ろし、復路、充電待ちを全部入れる。帰りが空荷でも時間と電力はかかる。現地で受け取れる担当者がいない時間帯は、機体の追加では改善しない。","en":"Measure kilograms per working hour, including loading, checks, outbound travel, unloading, return and charging. Empty returns still consume resources. Additional aircraft cannot solve periods when no recipient is available."},"kind":"design"},{"title":{"ja":"品質と引き渡しの記録","en":"Record condition and handover"},"body":{"ja":"発送者と受取者、品目、箱数、重量、時刻、受取確認を結ぶ。落下や荷崩れ、荷姿変更、天候待機は別のイベントとして残す。生鮮品は温度や打撲の許容を荷主と合意する。運搬可否、吊下げ、目視外飛行などの条件は国別に確認する。","en":"Connect sender, recipient, item, count, weight, timestamps and acceptance. Log damage, changes and weather holds separately. Agree temperature and bruising limits for produce. Check the jurisdiction’s rules for carriage, suspended loads and any beyond-visual-line-of-sight operation."},"kind":"design"},{"title":{"ja":"運べた実証と、続けられるサービスを分ける","en":"Distinguish a transport demonstration from a viable service"},"body":{"ja":"農林水産省が紹介する当別町の2020年実証は、集荷場の混雑と積み降ろし負担を出発点にしとる。資料では技術と費用の検証を今後の課題としている。飛行できた事実だけで、定期サービスの採算や、その後の商用化まで証明したことにはならん。","en":"MAFF’s account of the 2020 Tobetsu demonstration starts with collection-point congestion and handling burdens. It leaves further technical and cost assessment outstanding. Successful carriage alone does not prove recurring-service economics or subsequent commercialization."},"kind":"evidence"},{"title":{"ja":"受取側の能力を先に測る","en":"Measure receiving capacity first"},"body":{"ja":"ここからは物流設計の提案じゃ。荷積み、受け取り、箱の整理、計量、受領入力の各工程を時間で測り、飛行経路とは別に能力を置く。架空の例で受取工程が一箱に5分かかり、担当者が一人なら、休止なしでも上限は毎時12箱じゃ。そこへ機体を足しても受取能力は増えん。これは算数上の上限で、実際には確認や休憩、天候待ちなどを含めて見直す。収穫が集中する時刻を聞き、平均量でなく一番混む時間帯の到着を並べる。受取可能の確認を出発条件に組み込むが、通信が来ないことを空きスペースがある証拠にしてはいけん。","en":"The following is a logistics design proposal. Time loading, receiving, box handling, weighing and receipt entry separately from flight. In an illustrative scenario, one receiver taking five minutes per box has a mathematical ceiling of twelve boxes per hour without pauses. More aircraft do not increase that receiving capacity. Actual performance must account for checks, breaks and weather holds. Ask when harvesting peaks and schedule arrivals for the busiest period, not only average demand. Require confirmed receiving availability before dispatch; missing communication is not evidence of an empty receiving area."},"kind":"design"},{"title":{"ja":"品質の検収は、引渡し前後を対にする","en":"Pair condition checks before and after handover"},"body":{"ja":"生鮮品では、出発前から傷んでいたものと輸送中の損傷を区別できる記録を勧める。箱ID、内容、梱包状態、出発時の外観、到着時の確認結果を結び、荷主が必要とする場合は温度履歴も保持する。許容する傷や温度の条件は品目と荷主の基準で決め、どの作物にも同じ数値を当てはめない。抜き取り検査なら対象箱を事前の方法で選び、都合のよい箱だけ見ない。受領した数量と、販売可能として受け入れた数量を分けると、運べた重量が多いのに売れる収穫物が減る反例も把握できる。判定保留の箱を通常出荷へ自動で流さんようにするんじゃ。","en":"For fresh produce, preserve evidence that distinguishes pre-existing defects from transport damage. Link box ID, contents, packaging, departure condition and arrival inspection; retain temperature history where the shipper requires it. Agree damage and temperature criteria for the commodity rather than applying one universal threshold. Use a predefined sampling method instead of inspecting convenient boxes. Separate received quantity from saleable quantity accepted. This captures cases where higher transported weight accompanies more unmarketable produce. Boxes awaiting a condition decision should not automatically enter ordinary dispatch."},"kind":"design","table":{"headers":{"ja":["引渡し項目","記録例の形式"],"en":["Handover field","Illustrative format"]},"rows":{"ja":[["荷物の同一性","箱ID／品目／数量／送り主"],["状態","出発確認／到着確認／保留理由"],["責任の移動","受取担当／確認時刻／承認状態"]],"en":[["Shipment identity","Box ID / item / quantity / sender"],["Condition","Departure check / arrival check / hold reason"],["Transfer of responsibility","Receiver / confirmation time / acceptance state"]]}}},{"title":{"ja":"空箱の帰りと、運休の日も設計する","en":"Design the return flow and interruption day"},"body":{"ja":"帰り便に空箱や道具を載せれば必ず得、とは決めつけん。積み替え時間、荷姿変更、衛生上の区分、受取担当者を含めて便ごとに判断する提案じゃ。収穫物と資材を扱う設備は、汚染を持ち込まない荷役・清掃の手順も必要になる。運休時には、どの荷物を待たせ、どれを陸送へ切り替えるかを鮮度と納品約束から決める。代替車両の呼出費や待機した人の時間も一日の費用へ入れる。配送状況は「飛行終了」ではなく「受領確認」「品質確認」「未解決」を分け、航空機のログだけで荷主への完了通知を出さない設計にするんじゃ。","en":"A return load of empty boxes or tools is not automatically beneficial. Our proposal evaluates handling time, packaging changes, hygiene separation and receiving staff for each trip. Facilities handling both produce and inputs need suitable handling and cleaning procedures to avoid contamination. On interruption days, determine which shipments can wait and which require road transport based on freshness and delivery commitments. Include vehicle callout costs and idle labor in the day’s economics. Distinguish flight completion, receipt, condition acceptance and unresolved issues; aircraft logs alone should not trigger a completed-delivery notice to the shipper."},"kind":"design"}],"checklist":{"ja":["往復サイクルを実測","荷役担当者を確保","品質と受領条件を合意","中断時の陸送代替を用意"],"en":["Measure round-trip cycles","Assign loading and receiving staff","Agree quality and acceptance","Plan a ground alternative"]},"sources":[{"title":"FAO AgriTech Observer #2 — Drones for smallholders","url":"https://www.fao.org/digital-villages-initiative/europe/news-and-articles/news-and-articles-detail/agritech-observer--2--drones-for-smallholders---six-lessons-on-what-works-in-practice/"},{"title":"MAFF — ドローンによる農作物運搬実用化に向けた実証実験を実施","url":"https://www.maff.go.jp/j/kanbo/smart/attach/pdf/drone_topics-12.pdf"}],"updated":"2026-10-30","readingMinutes":4},{"slug":"turnaround","category":"operations","lenses":["field","business"],"title":{"ja":"バッテリーと液剤交換が、一日の面積を決める","en":"The turnaround determines the working day"},"dek":{"ja":"飛行・補給・冷却・充電・洗浄を、一つの工程として組む。","en":"Treat flying, refilling, cooling, charging and cleaning as one process."},"guide":{"ja":"機体を増やす前に、どこで待っとるか計ってみようや。","en":"Before adding aircraft, measure where the waiting happens."},"sections":[{"title":{"ja":"最大飛行時間では計画できない","en":"Plan beyond advertised endurance"},"body":{"ja":"Purdueの現場ガイドは、搭載量、電池状態、地形、経路、天候で電池の持ちが変わり、補給と充電の計画が必要と説明している。満載の往路を長くとる配置は、作業に使える余力を減らす。","en":"Purdue’s field guide explains that load, battery condition, route, terrain and weather affect endurance. Refill and recharge logistics matter; long loaded transit can consume capacity before useful work begins."},"kind":"evidence"},{"title":{"ja":"並行できる仕事と、できない仕事","en":"Separate parallel and sequential tasks"},"body":{"ja":"提案するタイムスタディでは、着陸から再離陸までを秒単位で分解する。安全確認、液剤取扱い、電池交換を同じ担当者が行うなら、それらを都合よく並列計算しない。清潔な電池作業と薬液取扱いの動線を分け、メーカー手順・保護具・衛生条件を守る。","en":"Measure landing-to-relaunch activities. Tasks performed by one person cannot be counted as concurrent. Separate clean battery handling from chemical handling, using manufacturer procedures, appropriate protection and hygiene rules."},"kind":"design"},{"title":{"ja":"充電器の台数より供給能力を見る","en":"Model the whole energy supply"},"body":{"ja":"冷却時間、充電時間、電源容量、発電機の連続出力、ケーブル、周囲温度を確認する。機体だけを増やせば、充電と給水に待ち列ができる。工具、予備部品、日陰、洗浄水、廃液の処理まで現場設営図に入れる。","en":"Check cooling and charging time, available power, sustained generator output, cables and ambient conditions. More aircraft can create charging and water queues. Include tools, spare parts, shade, cleaning water and approved waste handling in the staging plan."},"kind":"design"},{"title":{"ja":"実効能力の見方","en":"Read effective capacity"},"body":{"ja":"ツールの概算は「一 sortie の処理面積 × 60 ÷（飛行分＋地上分）」じゃ。これは補給待ちのない単機の近似で、移動や天候中断は別に引く。バッテリー数の表示も余裕なしの理論最小として扱い、実機の熱条件や予備機を代替しない。","en":"The calculator uses area per sortie × 60 / (flight minutes + ground minutes). This is a simplified single-aircraft estimate without queues; travel and weather reduce it further. Its battery count is a theoretical minimum, not an operational recommendation."},"kind":"design"},{"title":{"ja":"操縦器と測位装置にも、地上時間がある","en":"Ground time includes controllers and positioning equipment"},"body":{"ja":"ブラジルのUfesは、作業時間に加え、液の準備、移動、エネルギー、機体・操縦器・測位装置の充電を調べて実費を求めとる。大きな電池だけ数えても、一日の停止理由は見えん。補助機器も含む工程の記録が出発点じゃ。","en":"Ufes records preparation, travel, energy use and charging for the aircraft, controller and positioning equipment when assessing real costs. Counting only flight batteries misses other causes of interruption."},"kind":"evidence"},{"title":{"ja":"電池を個体で追い、使える状態を共有する","en":"Track individual batteries and their release state"},"body":{"ja":"ここからは本ガイドの提案じゃ。電池IDごとに、使用中、冷却・点検待ち、充電中、使用可、隔離の状態を残し、誰がいつ変更したか分かるようにする。充電表示が満杯でも、それだけで次の飛行へ出してよいとは扱わない。温度や外観、端子などの判定は製造元の手順と機体条件に従い、異常を疑う電池は通常の列から外す。ラベルが読めないと履歴を照合できんので、記録不能を黙って飛ばさないことも大切じゃ。機体の記録と電池の記録を結ぶと、特定の個体だけ戻りが早い場合に、作業条件の違いと個体の問題を切り分けて調査できる。","en":"Our proposed workflow records each battery’s ID and state: in use, awaiting cooling or inspection, charging, released, or isolated. Preserve who changed the state and when. A full-charge display alone must not authorize another flight. Apply manufacturer procedures and aircraft conditions to temperature, appearance and connection checks, removing suspect units from the normal queue. An unreadable ID prevents reconciliation and should not silently bypass recordkeeping. Linking aircraft and battery records also supports investigation when one battery repeatedly returns early, separating operating conditions from possible unit-specific problems."},"kind":"design","table":{"headers":{"ja":["状態","次工程へ渡す記録"],"en":["State","Record for the next stage"]},"rows":{"ja":[["冷却・点検待ち","戻り時刻／個体ID／確認待ち項目"],["充電中","充電器ID／開始時刻／異常表示"],["使用可","確認者／確認時刻／適用手順"],["隔離","理由／識別表示／再判定の担当"]],"en":[["Awaiting cooling or inspection","Return time / battery ID / pending checks"],["Charging","Charger ID / start time / fault indications"],["Released","Reviewer / time / applicable procedure"],["Isolated","Reason / identification / reassessment owner"]]}}},{"title":{"ja":"待ち列は、帰ってくる量と出せる量で見る","en":"Compare return demand with release capacity"},"body":{"ja":"電池が一時間に戻る個数をA、点検と充電を終えて使える状態へ出せる個数をBと置く設計例を考えよう。長い時間にわたりAがBを超えれば、予備を足しても待ち列は育つ。これは能力を見つけるための計算で、充電を急がせる指示ではないんよ。計測では、充電器の空き待ち、電源制約、確認者待ちを別の理由で記録する。給水、液剤準備、電池が同じ担当者を使うなら、人の時間も共有資源に入れる。機体を一機増やす前に、今の設備と手順で何を増やせるかを確かめ、増機後の最長待ち時間と一日全体の処理面積で効果を判断する。","en":"Consider a planning model in which A batteries return per hour and B complete inspection and charging for release. If A persistently exceeds B, extra spares only postpone a growing queue. This is a capacity diagnostic, not an instruction to accelerate charging. Record charger availability, power constraints and reviewer availability as separate waiting causes. If water supply, material preparation and batteries share one worker, include that person as a shared resource. Before adding an aircraft, identify what current equipment and procedures can support. Evaluate changes using maximum waits and whole-day accepted area."},"kind":"design"},{"title":{"ja":"一つの時計で、重なりと待機を見えるようにする","en":"Use one clock to distinguish overlap from waiting"},"body":{"ja":"架空の記録例は「10時00分着陸、10時02分電池引渡し、10時05分補給確認、10時07分出発可、10時10分離陸」のようにイベントを並べる。出発可から離陸までの3分も、待機理由を記録すれば改善対象になる。同時刻の二つの仕事を別々の作業時間として足し、経過時間を二重計上しない。一方、二人が働いた時間は人件費に両方入る。改善会議では平均だけでなく長い停止の原因を確認するんじゃ。飛行を速めた結果、確認漏れや再作業が増えたなら成功とはせず、安全に完了し検収された面積当たりの総時間と費用で見直す。","en":"An illustrative event log might show landing at 10:00, battery handover at 10:02, refill confirmation at 10:05, release at 10:07 and takeoff at 10:10. Recording the reason for the three-minute post-release wait makes it actionable. Do not add simultaneous activities twice when calculating elapsed time; both workers’ labor time still belongs in cost. Review causes of long stops as well as averages. Faster flying accompanied by missed checks or rework is not success. Assess total time and cost per safely completed, accepted area."},"kind":"design"}],"checklist":{"ja":["実測の地上時間を使う","薬液と電池の動線を分離","電源・給水の供給能力を確認","清掃・移動時間も予算化"],"en":["Use measured turnaround time","Separate chemicals and batteries","Check power and water capacity","Budget cleaning and travel"]},"sources":[{"title":"Purdue University — Operational Setup in the Field","url":"https://ag.purdue.edu/department/extension/ppp/resources/ppp-publications/mobile/ppp-154/7.operational-setup-in-the-field.html"},{"title":"Ufes — Pesquisa testa o uso de drones para reduzir custos e desperdício na agricultura","url":"https://www.ufes.br/conteudo/pesquisa-da-ufes-testa-o-uso-de-drones-para-reduzir-custos-e-desperdicio-na-agricultura"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"swarm","category":"operations","lenses":["field","platform"],"title":{"ja":"スウォームは、空間と時間の配車で考える","en":"Swarm operations as space-time scheduling"},"dek":{"ja":"面の分割、離着陸、補給待ち、通信断をまとめて設計する。","en":"Coordinate treatment zones, launch slots, service queues and link loss."},"guide":{"ja":"二機なら二倍、とはいかん。帰ってくる場所も同じじゃけえ。","en":"Two aircraft do not automatically double output. They may share the same bottleneck."},"sections":[{"title":{"ja":"編隊飛行と作業分担を混同しない","en":"Distinguish formation from coordination"},"body":{"ja":"本章は設計提案であり、実機の管制ソフトではない。農地を分割して複数機へ割り当てる方式と、互いの位置を見ながら協調制御する方式は要求が違う。地域の同時運航条件、操縦者数、監視、通信要件を先に確認する。","en":"This is a design proposal, not flight-control software. Partitioning work among aircraft differs from cooperative control using mutual state. Confirm local conditions for concurrent operation, staffing, observation and communications before choosing an architecture."},"kind":"design"},{"title":{"ja":"圃場の分割だけでは足りない","en":"Reserve more than treatment areas"},"body":{"ja":"セルごとに作業時間帯を予約し、移動経路、離着陸域、非常着陸先、補給設備も共有資源として扱う。隣接区画の散布が風下側に影響する可能性も考える。境界の重複処理を防ぐため、担当変更時には完了範囲と保留範囲を引き継ぐ。","en":"Reserve time windows for field cells, transit corridors, takeoff areas, contingency landing sites and service facilities. Consider downwind effects between adjacent jobs. A reassignment must transfer completed and pending treatment areas to avoid double application."},"kind":"design"},{"title":{"ja":"古い位置情報を安全と見なさない","en":"Treat stale telemetry explicitly"},"body":{"ja":"設計例では各機の状態に観測時刻と有効期限を付ける。通信断を検出したら割当済み空間をすぐ空きにせず、保留状態にする。緊急帰還が一つの着陸点へ集中しない設計と、操縦者の優先介入を実機・地域条件に合わせて検証する。","en":"Attach timestamps and expiry to each aircraft state. Do not release its reserved space immediately after link loss. Test contingencies that avoid simultaneous returns to one landing point, with pilot intervention appropriate to the aircraft and jurisdiction."},"kind":"design"},{"title":{"ja":"機体数より待ち行列","en":"Queues determine scale"},"body":{"ja":"増機判断には、処理能力だけでなく最長待ち時間、充電待ち、操縦者負荷、再作業率、通信の欠測を使う。デジタル試験、閉鎖環境、限定圃場の順で検証し、同時機数を増やすたびに運航条件と人員体制を見直す。","en":"Evaluate maximum waiting time, charging queues, operator workload, rework and missing telemetry alongside coverage. Progress through simulation, controlled tests and limited fields, revisiting operating conditions and staffing with each increase in concurrency."},"kind":"design"},{"title":{"ja":"群で撮る研究と、群で散布する能力を分ける","en":"Separate multi-drone sensing from spraying capability"},"body":{"ja":"Olds Collegeの石の地図づくりは、複数機の同時飛行と現地確認を組み合わせる計画として紹介されとる。掲載ページだけでは、散布機群の完成、増機による利益、別メーカー同士の協調まで確認できん。研究目的と確認済みの成果を分けることが大事じゃ。","en":"Olds College describes planned simultaneous drone flights and ground validation for rock mapping. That page does not establish a completed spraying swarm, profitable scaling or cross-vendor coordination. Project objectives must remain distinct from verified outcomes."},"kind":"evidence"},{"title":{"ja":"割り当ては、送信しただけでは確定せん","en":"Sending an assignment does not confirm it"},"body":{"ja":"以下は運航管理を考えるための設計例で、実機への制御手順ではないんよ。任務ID、計画版、対象区画、担当機、担当者、開始条件を一つの割当記録にする。管理側が予定を作った状態と、現場が受け入れた状態を区別し、受領確認がない仕事を別の機体へ重複発行しない。担当を替えるときは、旧担当の状態確認と実績の照合を終えてから新しい版を承認する。通信が戻った途端に古い予定が復活しないよう、版と連番を見て扱う。圃場の予約とは別に、離着陸設備、補給担当、周辺作業者の予定も対応させ、画面上の空き区画だけで実施可能とは判定せん。","en":"The following is a management design example, not aircraft-control instructions. An assignment record should include mission ID, plan version, field cell, aircraft, responsible person and start conditions. Separate a proposed assignment from field acceptance, avoiding duplicate assignment when acknowledgment is absent. Before reassignment, confirm the former operator’s state and reconcile completed work, then approve a new version. Use versions and sequence numbers to prevent old plans reviving after reconnection. Link field reservations to launch facilities, service staff and nearby workers’ schedules. An apparently vacant cell on a screen is insufficient evidence that work can begin."},"kind":"design"},{"title":{"ja":"障害試験では、復旧後の矛盾まで調べる","en":"Test inconsistencies after recovery"},"body":{"ja":"試験環境では、通信途絶だけでなく、遅れた位置情報、重複した完了通知、時刻のずれ、管理者交代をわざと入れ、保留からどう戻るかを確かめる提案じゃ。異常を検知した画面が赤くなるだけでは足りず、誰が現場状態を確認し、どの記録を根拠に再承認したかまで残す。機体自身の通信断時の挙動は承認された機種別手順に従い、この管理例で上書きしない。同じ人へ警報が一斉に届く場合も試し、確認を要する仕事が処理できず積み上がらんかを見る。通信が回復したことと、任務を再開できることを別の状態として扱うんじゃ。","en":"In a test environment, inject delayed positions, duplicate completion notices, clock discrepancies and operator handovers as well as link loss. Verify recovery from a hold, rather than merely displaying a red warning. Record who checked the actual field state and what evidence supported renewed authorization. Aircraft link-loss behavior remains governed by its approved procedures, not this management example. Also test simultaneous alerts to one person and whether required checks accumulate beyond their capacity. Treat restored connectivity and authorization to resume as different states."},"kind":"design","table":{"headers":{"ja":["試験事象","管理記録で確かめること"],"en":["Test event","Management-record check"]},"rows":{"ja":[["古い位置が後から到着","新しい状態を巻き戻さない"],["完了通知が重複","同じ面積を二重に数えない"],["担当者を交代","保留理由と未完了範囲を引継ぐ"],["通信が復旧","現地確認なしに保留を解除しない"]],"en":[["Old position arrives late","Do not roll back the newer state"],["Duplicate completion","Do not count the area twice"],["Operator handover","Transfer holds and unfinished coverage"],["Connectivity restored","Do not clear holds without field confirmation"]]}}},{"title":{"ja":"評価の単位を、延べ飛行面積から完了した仕事へ","en":"Evaluate accepted work rather than accumulated flight area"},"body":{"ja":"架空の例で二機が同じ区画を撮った場合、各機の面積を足して生産性が二倍になったとは言えん。目的を満たし検収された重複のない面積、欠測、再撮影、人の確認時間を並べる設計を勧める。散布なら面積の重複は品質上の問題にもなるため、撮影と同じ集計で済ませない。単機と複数機を比べる日は、圃場条件や作業内容をそろえ、違いがあれば記録する。機体を増やしても充電待ちが伸びたり、未確認の警報が増えたりするなら、その規模はまだ受け入れられん。一日の量だけでなく、作業期限内の完了率と記録を復元できるかも検収項目にするんじゃ。","en":"If two aircraft photograph the same cell, adding their covered areas does not demonstrate doubled productivity. We propose measuring unique accepted coverage, gaps, repeat capture and human review time. For application work, overlap can also be a treatment-quality problem and requires different accounting. Compare single- and multi-aircraft work under comparable field conditions and tasks, recording differences. A larger fleet is not ready for acceptance if charging queues or unreviewed alerts grow. Include completion within the agreed deadline and the ability to reconstruct the work history, alongside daily output."},"kind":"design"}],"checklist":{"ja":["同時運航条件を確認","空域・着陸・補給を予約","古い位置情報を保留扱い","人の介入と帰還集中を検証"],"en":["Check concurrent-operation conditions","Reserve airspace, landing and service resources","Hold stale reservations","Test intervention and return congestion"]},"sources":[{"title":"FAA — Dispensing Chemicals and Agricultural Products (Part 137)","url":"https://www.faa.gov/uas/advanced_operations/dispensing_chemicals"},{"title":"Purdue University — Operational Setup in the Field","url":"https://ag.purdue.edu/department/extension/ppp/resources/ppp-publications/mobile/ppp-154/7.operational-setup-in-the-field.html"},{"title":"Olds College — Threshold UAV Drone Rock Mapping","url":"https://www.oldscollege.ca/smart-farm-research/research-projects/smart-ag/completed/threshold-uav-drone-rock-mapping.html"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"farm-report","category":"data","lenses":["field","platform"],"title":{"ja":"農家に届く「一枚の答え」","en":"One clear page for the farmer"},"dek":{"ja":"解析の高度さを、確認・行動・結果へ翻訳する。","en":"Translate analytical complexity into checks, actions and outcomes."},"guide":{"ja":"指数を十個並べるより、今日どこを見るかが分かるほうがええ。","en":"Knowing where to look today can matter more than ten indices."},"sections":[{"title":{"ja":"先に表示する四つ","en":"Four things to show first"},"body":{"ja":"提案する画面は「どの畑のどこ」「何が起きた可能性」「次にすること」「いつまでに」の四つを主役にする。異常スコアを「病害確定」と言い換えない。写真、撮影日時、根拠、欠測、専門家の確認状態は一段下に置く。","en":"Lead with field and location, possible issue, next action and deadline. Never rename an anomaly score as a confirmed disease. Place imagery, timestamps, reasoning, missing data and expert-review status one level below."},"kind":"design"},{"title":{"ja":"色だけに頼らない","en":"Use more than color"},"body":{"ja":"赤・緑の区別だけで判断させず、番号、文字、形を添える。専門用語には短い説明を付ける。電波の弱い現場でも印刷やJSON出力を持ち出せるようにする。地図の凡例を固定し、欠測は灰色など独立した表現にする。","en":"Pair colors with labels, numbers and shapes. Explain technical terms briefly. Offer printable and machine-readable exports for weak-connectivity settings. Keep legends consistent and give missing data its own representation."},"kind":"design"},{"title":{"ja":"行動の閉ループをつくる","en":"Close the action loop"},"body":{"ja":"「確認した」「対応した」「様子を見る」「判断できない」を選べるようにし、写真と短いメモを残す。未対応件数より、期限内の確認率、誤検知率、手戻り時間を追う。分析モデルの改善と農家の実益を同じログで測る。","en":"Let users record checked, treated, observing or uncertain, with a photo and short note. Track timely verification, false alarms and rework rather than only unresolved counts. Use the same log to evaluate model performance and practical usefulness."},"kind":"design"},{"title":{"ja":"専門語を消すより、判断の順をそろえる","en":"Structure the decision before simplifying the vocabulary"},"body":{"ja":"WURは複雑なモデルを実用的な助言へつなぐ研究を紹介している。以下は納品画面の設計例じゃ。最初に「どの圃場のどこ」「何を確かめたいか」「いつまでに誰が確認するか」を置き、その下に撮影時刻、根拠、まだ分からないことを並べる。「北側の生育が弱い」は観測、「水路の詰まりかもしれない」は仮説、「明朝、水口を確認」は行動として分ける。専門語を全部消すと技術者へ引き継げなくなるため、元の指標名や解析条件は詳細に残す。農家が一枚を読んだ後、自分の言葉で次の作業を言えるかを試し、色が鮮やかかどうかで評価しない。","en":"WUR describes research translating complex models into practical decision support. Our proposed report starts with the field and location, the question to verify, and who should check by when. Follow with acquisition time, evidence and unresolved uncertainty. “Weaker growth in the north” is an observation; “a blocked channel may explain it” is a hypothesis; “inspect the inlet tomorrow morning” is an action. Removing all technical terms would hinder expert handover, so retain original indices and processing details beneath the summary. Test whether a farmer can explain the next action in their own words, rather than judge the report by visual appeal."},"kind":"design","table":{"headers":{"ja":["表示層","仮の記載例","意味"],"en":["Layer","Illustrative entry","Meaning"]},"rows":{"ja":[["観測","北側の一部で生育差","画像で見えたこと"],["仮説","給水不均一の可能性","原因は未確認"],["次の確認","明朝、水口と畝を確認","担当者へ渡す行動"],["未確認","根の状態・病害","地上で調べる項目"]],"en":[["Observation","Uneven growth in the north","What imagery indicates"],["Hypothesis","Possibly uneven water supply","Cause unconfirmed"],["Next check","Inspect inlet and rows tomorrow","Assigned action"],["Unknown","Roots and disease status","Ground investigation needed"]]}}},{"title":{"ja":"確認待ちを放置せず、引継ぎを閉じる","en":"Close the handover, not just the notification"},"body":{"ja":"通知を送っただけでは、誰も圃場へ行っていないかもしれん。報告ごとに確認担当、受領、期限、結果の記録欄を設け、受領されなければ地域の相談窓口へ回す。担当者が不在なら、勝手に処置を実施せず、代わりに誰が判断するかを契約で決めておく。解析の品質が足りない場合も「異常なし」にはせず、再撮影、地上確認、判断保留のどれへ渡すかを明記する。例えば雲影で北半分を評価できなかったなら、報告の完了率と圃場の確認率を分けるんじゃ。終了条件は画面を開いたことではなく、確認結果または確認できなかった理由が台帳へ戻ったことにする。","en":"Sending a notification does not mean anyone visited the field. Assign a reviewer, acknowledgement, deadline and result field to each report, escalating unacknowledged work to an agreed local contact. If the assigned person is absent, follow the agreed replacement decision process rather than applying treatment automatically. Inadequate analysis quality must trigger recapture, ground inspection or a held decision, not “no abnormality.” If cloud shadows invalidate the northern half, distinguish report delivery from field verification coverage. Close the item when a check result or a reason that checking was impossible returns to the record, not when someone merely opens the screen."},"kind":"design"},{"title":{"ja":"正解率より、誤りが生む作業を見る","en":"Evaluate the work caused by errors"},"body":{"ja":"モデルの正解率が高くても、農家へ大量の不要な見回りを頼めば使い続けてもらえん。試験では、実際に問題があった場所の見逃し、正常な場所への誤警報、確認一件に必要な移動時間を別々に測る。希少な病害では「ほぼ全部正常」と答えても正解率が高く見えるため、陽性候補のうち本当に確認された割合と、現地調査で見つかった問題をどれだけ拾えたかも見る。閾値は作物や被害の大きさ、確認できる人数で変わるが、変更理由と日付を残す。重大な問題を疑う場合は早く専門家へ渡し、軽微な差は次回観測とまとめるなど、検出の強さと作業の優先順位を混同しない。","en":"High classification accuracy can still create too many unnecessary inspections. Measure missed problems, false alarms and travel time per verification separately. For a rare disease, predicting normal almost everywhere can appear accurate. Also examine the proportion of flagged sites actually confirmed and the proportion of independently ground-detected problems captured. Thresholds may vary with crop, consequence and available inspection staff, but changes need reasons and dates. Escalate potentially serious cases to specialists while combining minor differences with a later observation when appropriate. Detection confidence and action priority are distinct: a moderately likely high-consequence issue may deserve attention before a highly certain trivial difference."},"kind":"design"},{"title":{"ja":"電波が弱い現場と、翌年の学習をつなぐ","en":"Connect low-connectivity work with next season’s learning"},"body":{"ja":"持ち歩く紙や端末には、圃場名だけでなく、目印、撮影日、確認期限、報告番号を載せる。電波が戻って写真やメモを送るときは、記録した時刻と送信時刻を分け、別の人が同じ場所を確認済みなら重複作業を避ける。図の色は印刷や色覚差でも意味が残る記号と文字で補い、単位と縮尺を消さない。シーズン終了時には「役立った報告」「遅すぎた報告」「確認できなかった報告」を農家と振り返るんじゃ。翌年の飛行回数をただ増やすのではなく、納期、観測時期、説明方法、担当者への渡し方のうち、どこを変えれば判断が良くなるかを決める。","en":"A printed sheet or field device needs landmarks, acquisition date, review deadline and report ID as well as the field name. When notes and photographs synchronize later, retain both capture and transmission times, checking whether someone else already inspected the same location. Pair map colors with symbols and text that survive printing and color-vision differences, retaining scale and units. At season end, review useful, late and unverifiable reports with the farmer. Do not simply increase next year’s flights. Identify whether better decisions require changes in delivery time, observation timing, explanation or handover responsibility."},"kind":"design"}],"checklist":{"ja":["場所・行動・期限を先頭に","不確実性を明記","印刷とデータ出力","現地確認の結果を回収"],"en":["Lead with location, action and deadline","State uncertainty","Support print and data export","Capture ground-check outcomes"]},"sources":[{"title":"FAO AgriTech Observer #2 — Drones for smallholders","url":"https://www.fao.org/digital-villages-initiative/europe/news-and-articles/news-and-articles-detail/agritech-observer--2--drones-for-smallholders---six-lessons-on-what-works-in-practice/"},{"title":"UN Handbook — UAV applications in agricultural statistics","url":"https://fao-eostat.github.io/UN-Handbook/uav_agriculture.html"},{"title":"WUR — AI, robotics and smart cultivation technologies","url":"https://www.wur.nl/en/research/plant/ai-robotics-and-smart-cultivation-technologies"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"field-workflow","category":"operations","lenses":["field"],"title":{"ja":"圃場で迷わない、作業の引き継ぎ","en":"A field workflow without lost handoffs"},"dek":{"ja":"依頼受付から現地下見、作業、農家への報告まで。","en":"From intake and survey to operation and farmer handover."},"guide":{"ja":"現場で決めんでええことは、前の日までに決めとこうや。","en":"Settle what you can before the crew reaches the field."},"sections":[{"title":{"ja":"依頼時に確定するもの","en":"Agree at intake"},"body":{"ja":"圃場の所有・利用関係、対象作物、目的、希望時期、成果物、費用、連絡担当を確認する。座標だけを送っても、境界、障害物、進入路、給水、隣接地の状況は伝わらない。依頼受付と実施承認を別状態にする。","en":"Confirm land access, crop, objective, timing, deliverables, price and contact. Coordinates alone do not describe boundaries, obstacles, access roads, water or neighbors. Keep request acceptance separate from authorization to operate."},"kind":"design"},{"title":{"ja":"下見を地図に戻す","en":"Return survey findings to the map"},"body":{"ja":"衛星地図や過去の画像を現地の確認で更新する。電線、樹木、人の通行、動物、水路、敏感な作物を記録する。操縦者・補助者・薬剤担当・農家の役割と、連絡がつかない場合の判断権限を合意する。","en":"Update maps with a site survey. Record wires, trees, movement of people and animals, watercourses and sensitive crops. Agree roles for pilot, observer, product handler and farmer, including who decides when someone cannot be reached."},"kind":"design"},{"title":{"ja":"完了は記録の照合まで","en":"Finish by reconciling records"},"body":{"ja":"作業後は実施面積、使用量、残量、未実施部分、異常、次の確認日を照合する。単なる飛行ログと農作業ログを関連付ける。農家へ渡す要約と詳細記録を分け、事故・苦情・再作業が発生したときに同じ作業IDからたどれるようにする。","en":"Reconcile treated area, quantities, residue, unfinished areas, anomalies and next review date. Link flight records with agricultural work records. Provide a concise handover and retain detail under the same job ID for incidents, complaints or rework."},"kind":"design"},{"title":{"ja":"飛行終了と、営農の完了を分ける","en":"Separate flight completion from agronomic completion"},"kind":"evidence","body":{"ja":"フィリピンTESDAの農業ドローン技能基準は、作業後の洗浄、電池保管、廃棄物管理、記録も技能に含めとる。一方、タイのサトウキビ研究では飛行計画の再利用で作業時間が短くなったが、調べた処理間の草丈には有意な差がなかった。前者は仕事の範囲、後者は時間と農学的結果を分ける必要を示す材料じゃ。この二つから、本ガイドでは「飛べた」「予定範囲を処理した」「農家へ引き渡した」「後日効果を確かめた」を別の状態として設計するんよ。","en":"The Philippine TESDA competency standard includes post-operation cleaning, battery storage, waste management and records. A Thai sugarcane study found time savings from reusing flight plans without significant plant-height differences between the tested treatments. These sources inform this guide's proposed separation of flight completion, area treatment, farmer handover and subsequent agronomic evaluation."}},{"title":{"ja":"診断を、実行できる作業指示へ渡す","en":"Turn a diagnosis into an executable work order"},"kind":"design","body":{"ja":"設計案として、異常を見つけた人、営農判断をする人、実行する人を作業票に残す。たとえば画像で薄い生育を見つけたら、地点と撮影日を添えて現地確認へ渡し、確認担当が観察・採取結果を返す。その後に営農担当と農家が「処置する・経過を見る・追加確認する」を決めるんじゃ。操縦者へ渡すのは色つき地図だけでなく、目的、対象区画、対象外部分、資材、承認された使用条件、適期、確認担当を含む版番号つきの指示にする。現場で作物段階や資材が変わったら、その場の口約束で上書きせず、判断担当へ差し戻す。承認者へ連絡できない場合の保留条件も先に決めとこう。","en":"Record who detected the issue, who makes the agronomic decision and who executes it. For example, a weak-growth image should become a location-specific inspection request with a capture date; the inspector returns observations or sampling results. The farmer and agronomic adviser then choose treatment, monitoring or further investigation. Give the pilot a versioned instruction covering objective, field, exclusions, material, approved conditions of use, timing and the review owner. A coloured map alone is insufficient. If crop stage or material changes, return the instruction for review rather than replacing it through an informal conversation. Agree beforehand when work remains on hold because the decision owner cannot be reached."}},{"title":{"ja":"農家に渡す一枚は、次の行動が読める形に","en":"Make the farmer's one-page handover actionable"},"kind":"design","body":{"ja":"納品画面は、農家が普段使う区画名、実施日、できた範囲、残った範囲、次の行動、連絡先を先に出す設計じゃ。専門的な指数や飛行ログは詳細へ置き、異常の理由が未確定なら「確認待ち」と書く。たとえば「北の田の水口側を担当者が確認、結果を電話で返す」と、場所・担当・行動を一文にするんよ。説明後には農家自身の言葉で次の予定を話してもらい、読み違いを直す。文字を大きくするだけでなく、紙・電話・音声でも同じ内容へ届くようにする。受領の返事は説明が届いた記録であって、防除効果や収量改善の証明にはせんことじゃ。","en":"Lead the handover with familiar field names, date, completed and outstanding areas, next action and a contact. Put technical indices and flight records in a detail view, and label unresolved causes as awaiting inspection. A sentence such as 'The assigned inspector will check the inlet side of the north field and call with the result' connects location, owner and action. Ask the farmer to explain the next step in their own words, then correct misunderstandings. Provide equivalent information through print, phone or audio as needed. Acknowledgement records delivery of the explanation; it does not demonstrate crop-protection efficacy or yield improvement."},"table":{"headers":{"ja":["引き継ぐ場面","渡す最小情報","受け手が返すもの"],"en":["Handoff","Minimum information","Recipient response"]},"rows":{"ja":[["画像から現地確認","区画・地点・日時・疑問","観察結果と確認不能な部分"],["営農判断から作業","版番号・対象・目的・使用条件","実施可否と変更点"],["作業から農家","実施範囲・未実施範囲・次の担当","次の行動の理解と連絡方法"]],"en":[["Imagery to inspection","Field, location, date and question","Observations and anything unverified"],["Agronomy to operation","Version, target, purpose and conditions","Feasibility and changes"],["Operation to farmer","Completed areas, gaps and next owner","Understood next action and contact route"]]}}},{"title":{"ja":"中断・再訪・苦情にも、担当を残す","en":"Assign ownership for interruptions, revisits and complaints"},"kind":"design","body":{"ja":"中断時は「何割終わったか」だけでなく、実際に処理した範囲と未処理範囲を区別して保存する設計にする。再訪時には最新の生育、既実施量、天候、隣接地の状況を見直し、単純に前回の経路を最初から流さんことじゃ。資材残量と実施記録が合わない場合も、帳尻を合わせる入力で消さず、差異として担当者へ渡す。請求の確定、再作業の判断、農家への連絡にはそれぞれ期限と担当を置く。苦情を受けた人が操縦者を探し回らんよう、同じ作業番号から指示の版、実績、連絡履歴をたどれるようにし、解決後に再発防止を更新するんよ。","en":"After interruption, preserve the actual treated and untreated areas rather than only a completion percentage. Before returning, review current crop conditions, previous application, weather and neighboring land; do not simply rerun the old route from the beginning. If material quantities do not reconcile with the work record, retain the discrepancy and assign investigation instead of entering a balancing adjustment. Give invoicing, rework decisions and farmer contact separate owners and deadlines. A common job identifier should connect instruction versions, actual work and communications so that complaints can be investigated without searching informally for the pilot. Update preventive measures after resolution."}}],"checklist":{"ja":["目的と成果物を合意","現地下見を反映","担当と中止権限を明確化","実績と残量を照合"],"en":["Agree purpose and deliverables","Incorporate the site survey","Assign roles and stop authority","Reconcile actuals and residue"]},"sources":[{"title":"Purdue University — Operational Setup in the Field","url":"https://ag.purdue.edu/department/extension/ppp/resources/ppp-publications/mobile/ppp-154/7.operational-setup-in-the-field.html"},{"title":"TESDA — Agricultural Drone Operation Level II competency standards","url":"https://tesda.gov.ph/Downloadables/CS/CS-Agricultural%20Drone%20Operation%20Level%20II%20ver2.pdf"},{"title":"Khon Kaen Agriculture Journal — Time and operational obstacles in sugarcane foliar spraying","url":"https://li01.tci-thaijo.org/index.php/agkasetkaj/article/view/251705"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"economics","category":"economics","lenses":["business","field"],"title":{"ja":"買う・頼む・共同で持つ。数字で比べる","en":"Own, hire or share: compare the whole cost"},"dek":{"ja":"機体価格ではなく、年間の延べ作業面積と総費用で判断する。","en":"Use annual treated area and total cost, not the aircraft price alone."},"guide":{"ja":"安い機体でも、年に数日しか働かんと高くつくことがあるんよ。","en":"An inexpensive aircraft can still be costly when it works only a few days."},"sections":[{"title":{"ja":"農地面積と延べ処理面積","en":"Land area is not treated area"},"body":{"ja":"Missouri大学の費用推計は、農家と受託事業者を分け、稼働面積、電池、労務、移動、所有費を扱っている。そこでの米国の仮定を日本の価格に移し替えることはできない。本サイトの計算機は独自の簡易モデルで、入力例は市場相場ではない。","en":"Missouri’s cost tools distinguish farmers and contractors and consider use, batteries, labor, travel and ownership. Their US assumptions cannot be transferred directly to another market. Our calculator is an independent simplified model; its defaults are illustrative, not market quotations."},"kind":"evidence"},{"title":{"ja":"一年の全費用を積む","en":"Build annual full cost"},"body":{"ja":"購入額から残存価値を引いて耐用年数で割り、年間固定費に加える。変動費には労務、電池消耗、電力、移動、洗浄、解析などを含める。農薬や種子を両方式で同額として除外するなら、その条件を明示する。","en":"Annualize purchase price less residual value over service life, then add fixed annual costs. Variable costs should include labor, batteries, energy, travel, cleaning and analysis. If product costs are excluded because they are equal across options, make that assumption explicit."},"kind":"design"},{"title":{"ja":"損益分岐の読み方","en":"Interpret the break-even point"},"body":{"ja":"外注単価から自社の変動単価を引いた差が正のとき、年間固定費と償却相当額をその差で割ると、単純な分岐面積になる。差がゼロ以下なら、このモデルでは面積を増やしても費用優位にならない。売上増と作業費節約は重複計上しない。","en":"When hire price exceeds owned variable cost, divide annual fixed plus annualized capital cost by the difference to obtain a simple break-even area. A nonpositive difference gives no cost break-even in this model. Avoid double-counting revenue gains and cost savings."},"kind":"design"},{"title":{"ja":"悪い年でも続けられるか","en":"Test a difficult year"},"body":{"ja":"雨による稼働減、故障、電池交換、受託失注を別々に試す。近隣農家を集めるほど移動効率は良くなるが、同じ日に依頼が集中する問題もある。共同所有では予約優先順位、保険、破損負担、離脱時の精算を契約で決める。","en":"Test weather loss, breakdown, battery replacement and fewer contracts separately. Local aggregation can reduce travel while concentrating demand in the same weather window. Shared ownership needs agreed booking priority, insurance, damage responsibility and exit terms."},"kind":"design"},{"title":{"ja":"三種類の面積を、同じ表に混ぜない","en":"Keep three area measures separate"},"body":{"ja":"以下の数字は計算説明用の仮定じゃ。80haの農場で年3回なら予定は240延べha。天候で最後の40haを実施できなければ、完了は200延べhaになる。さらに20haを無償でやり直した場合、作業資源を使った面積は220延べha、請求対象は200延べhaのままじゃ。予定面積で固定費を割ると、不稼働と手直しを隠してしまう。受託者は「販売可能な面積」、農家は「適期に品質を満たした面積」を分母に置き、同じ仕事を従来法へ頼んだ費用と比べる。圃場の実面積、延べ処理面積、品質確認済み面積を保存すれば、季節をまたいでも比較の意味が変わらん。","en":"These numbers are illustrative. An 80-hectare farm with three passes plans 240 treated hectares. If weather prevents the final 40 hectares, completion falls to 200. Repeating 20 hectares without charge consumes resources over 220 treated hectares but leaves only 200 billable. Dividing fixed cost by the original plan hides downtime and rework. Contractors should use saleable area; farmers should assess area completed on time to the agreed quality, against the actual ground or hired alternative. Preserve physical field area, total treatment area and quality-accepted area separately so comparisons retain their meaning across seasons."},"kind":"design","table":{"headers":{"ja":["指標","この仮定での値","用途"],"en":["Measure","Illustrative value","Use"]},"rows":{"ja":[["実圃場面積","80ha","土地規模"],["延べ作業面積","220ha","消耗・人件費"],["品質確認・請求対象","200ha","受託売上の分母"]],"en":[["Physical field area","80 ha","Land scale"],["Total treated area","220 ha","Wear and labor"],["Accepted and billable area","200 ha","Revenue denominator"]]}}},{"title":{"ja":"一件の採算に、移動と切替を戻す","en":"Put travel and changeovers back into job margins"},"body":{"ja":"UNRの2024年経済分析は、当時のアルゼンチンの仮定で読む資料じゃ。価格を輸入せず、以下の構造を地元の見積りで埋めよう。一件の限界利益は、受注額から、その依頼を追加したために増える移動、作業人件費、電池摩耗、電力、洗浄、解析、再訪の費用を引く。農薬を別請求するなら、その売上と仕入れも対にする。近い小区画をまとめても薬剤や作物が違えば洗浄が増えるため、面積だけの割引は危ない。最低出動料金と面積料金を分け、どちらが移動準備を回収するか明記する。既存社員の空き時間もゼロ円とはせず、繁忙日に他の仕事を断る機会費用を別欄で確認する。","en":"The 2024 UNR economic analysis belongs to its historical Argentine assumptions. Use local quotations to populate the following proposed structure instead of importing its prices. A job’s contribution is revenue minus costs caused by accepting it: travel, labor, battery wear, energy, cleaning, analysis and return visits. Match any separately billed chemicals with their procurement cost. Grouped small fields can still require cleaning between incompatible jobs, so area discounts may erase the expected savings. Separate a call-out charge from the area charge and identify which recovers mobilization. Existing employees’ time is not automatically free: record work displaced on a busy day as an opportunity cost."},"kind":"design"},{"title":{"ja":"会計上の黒字と、返済できる現金を分ける","en":"Separate accounting profit from available cash"},"body":{"ja":"購入判断では、損益表と現金表を並べるんよ。損益表の減価償却と、現金表の借入元本返済は同じものではない。機体購入額を初年度の支出に入れた投資評価へ、さらに減価償却を現金支出として足すと二重計上になる。簡易的な年額比較を超える場合は、同じ期間の受託費、運転資金、更新投資、残存価値をそろえ、資金調達費と資本の機会費用の扱いを明示する。通常年、悪天候年、故障年の月別残高を作り、売上入金より前に賃金や電池代が発生する谷を見る。補助金は対象外でも回るかを別シナリオで確認し、税務上の処理は当地の担当者と詰める。割引率に資本コストを含める事業評価と、借入・返済を含む出資者の現金表を混ぜないことも大切じゃ。","en":"Compare an income statement with a cash schedule. Depreciation is not the same as loan principal repayment. If an investment cash-flow model already records the purchase payment, adding depreciation as another cash outflow double-counts it. For decisions beyond simple annual cost comparisons, align the evaluation horizon, hired-service alternative, working capital, replacement investment and residual value. State how financing and the opportunity cost of capital are treated. Model monthly balances for ordinary, bad-weather and breakdown years to expose wage and battery payments that precede customer receipts. Test an unsubsidized scenario separately, and have local specialists determine applicable tax treatment. Keep project valuation using a cost-of-capital discount rate distinct from equity cash flows that include borrowing and repayment."},"kind":"design"},{"title":{"ja":"センシングの価値は、変えられる判断の数","en":"Value sensing through decisions that can change"},"body":{"ja":"撮影費が安くても、結果が届く頃には追肥や防除の適期を過ぎていれば価値は小さい。導入前に「異常が見つかったら、誰が何を変えるか」を書こう。仮に水路の詰まりを疑うなら、全面撮影、衛星で候補を絞る方法、歩いて確認する方法を同じ期限で比較する。価値の試算は、回避できる損失の期待額から撮影・解析・確認・対応の追加費用を引き、不確実な増収を確定売上にしない。確認しても何も変えない圃場は、次回の撮影頻度を下げる候補じゃ。一方、被害が少ない年でも重大な見逃しを避ける価値はあり、単年の検出件数だけで契約を評価せんようにする。","en":"Cheap imagery has little value if it arrives after the fertilizer or treatment window. Before buying sensing, name who will change which decision if a problem is found. For a suspected blocked water channel, compare full-field imaging, satellite screening followed by inspection, and walking the field against the same deadline. Estimate expected avoidable loss minus the additional capture, analysis, verification and response costs; do not treat uncertain yield gains as guaranteed revenue. Fields where findings never change action may need fewer flights. Conversely, avoiding a serious missed problem can matter even in a quiet season, so detection counts alone are a poor measure of contract value."},"kind":"design"}],"checklist":{"ja":["延べ処理面積で比較","労務・移動・電池を含める","自社利用と受託売上を区別","稼働減の感度分析"],"en":["Compare treated area","Include labor, travel and batteries","Separate internal savings from contract revenue","Test lower utilization"]},"sources":[{"title":"University of Missouri — Economics of Drone Ownership (2025)","url":"https://extension.missouri.edu/publications/g1274"},{"title":"UNR — Análisis económico de una alternativa de uso de drones (2024, pp.29–32)","url":"https://fcagr.unr.edu.ar/wp-content/uploads/2024/08/Agromensajes-Agosto-2024.pdf"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"investment","category":"economics","lenses":["business"],"title":{"ja":"投資判断は、機体の外側から","en":"Investment begins outside the aircraft"},"dek":{"ja":"継続率、季節性、運転資金、保守網から事業を見る。","en":"Assess retention, seasonality, working capital and service networks."},"guide":{"ja":"売れた台数より、次の年も使われる理由を見ようや。","en":"Look beyond units sold to the reasons customers return."},"sections":[{"title":{"ja":"顧客の成果と売上をつなぐ","en":"Link revenue to customer outcomes"},"body":{"ja":"設計提案として、農家の再依頼を「価格が安い」だけで説明しない。適期に作業できたか、負担が減ったか、報告が使えたかを確認する。面積ベース課金でも、結果の品質基準と再作業時の扱いを合意する。","en":"As an investment framework, assess whether repeat demand comes from timely work, lower workload and usable reporting. Area-based billing still needs quality criteria and agreed treatment of rework."},"kind":"design"},{"title":{"ja":"一件の粗利から季節の現金へ","en":"From job margin to seasonal cash"},"body":{"ja":"受注額から直接労務、移動、電池消耗、消耗品、外注解析を引く。さらに営業、保険、研修、修理待ち、予約管理の固定費を考える。売上が収穫後の入金なら、農繁期の給与や資材を支える資金が先に必要になる。","en":"Subtract direct labor, travel, battery wear, consumables and outsourced analysis from job revenue. Then include sales, insurance, training, downtime and scheduling overhead. Payment after harvest creates a cash gap before wages and materials are paid."},"kind":"design"},{"title":{"ja":"検証すべき投資仮説","en":"Make the thesis testable"},"body":{"ja":"「何機増やせば伸びるか」より、地域内の依頼密度、再依頼率、整備日数、作業窓の充足率を測る。補助金を除いた費用でも続くかを見る。メーカー由来の普及台数は市場全体の独立統計とは分け、調査範囲と定義を確認する。","en":"Measure job density, repeat usage, repair time and service within agronomic windows before expanding the fleet. Test economics without subsidies. Keep manufacturer adoption figures separate from independent market estimates and inspect their definitions."},"kind":"design"},{"title":{"ja":"投資の段階を、証拠で区切る","en":"Release investment against evidence"},"body":{"ja":"HohenheimのDiWenkLaは小規模農業のデジタル化を研究しているが、その存在だけで個別事業の採算は証明されん。ここからは投資審査の提案じゃ。最初は顧客課題と有償の試験契約、次は適期・品質・原価の実績、最後に継続契約と人材育成を確認して資金を増やす。問い合わせ件数、無償実演の参加者、購入機数を、売上が再現できる証拠へ置き換えない。新地域への進出は、既存地域で良かった平均値ではなく、その作物、分散度、修理拠点、許認可の条件で審査する。一度の成功に大きく投資するより、次の不確実性を検証できる額と期間を決め、停止条件も同時に残す。","en":"Hohenheim’s DiWenkLa researches digitalization for small farms; its existence does not establish the profitability of a particular business. Our proposed investment gates start with a customer problem and paid trial, then evidence of timeliness, quality and cost, followed by renewals and repeatable staff training. Enquiries, free-demo attendance and aircraft purchases are not substitutes for reproducible revenue. Review expansion against the new region’s crops, fragmentation, repair access and permissions rather than the existing territory’s average results. Fund a defined period and amount that resolves the next uncertainty, with stopping conditions agreed alongside the release of capital."},"kind":"design"},{"title":{"ja":"需要を年額から、使える一週間へ戻す","en":"Bring annual demand back to the workable week"},"body":{"ja":"年間の契約面積が大きくても、全顧客が同じ晴天日に作業を求めれば、売上計画は実行できん。契約ごとに作物の適期、所要時間、移動、準備、天候予備日をカレンダーへ置く。隣接する三農場は移動を減らすが、同じ雨雲に影響されるので需要リスクが三つに分散したとはいえない。機体追加の前に、充電・給水・操縦者・受入担当のどこが上限かを実測する。稼働率は飛行時間だけでなく、約束した期間内に受けられた有償仕事の割合で見る。断った仕事の理由も残せば、機体を買うべきか、予約条件や作目の組み合わせを変えるべきかが分かる。","en":"Large annual contracted acreage may be impossible to serve when everyone needs the same dry day. Place crop windows, work time, travel, preparation and weather reserves on a calendar for every contract. Three neighboring farms reduce travel but remain exposed to the same rain; they are not three independent demand risks. Before adding aircraft, measure whether charging, water, pilots or receiving staff constrain capacity. Assess the share of paid work deliverable inside promised windows alongside flight utilization. Record why work was declined. Those reasons distinguish a genuine need for another aircraft from a need to change booking terms or the mix of crops served."},"kind":"design"},{"title":{"ja":"同じ顧客群を追い、粗利の質を見る","en":"Follow customer cohorts and margin quality"},"body":{"ja":"開業初年度の新規売上と、翌年も戻る売上を分けて追う。前年顧客のうち、補助付き実演を除いて再契約した割合、値引き前後の粗利、説明や苦情対応に要した時間を同じ顧客群で比べるんじゃ。販売代理店が費用を肩代わりした仕事は、その支援がなくなった場合の原価も作る。面積は増えたが再訪が増えて粗利が減るなら、営業成功とは言い切れない。大口一社への依存は契約金額だけでなく、支払時期と予約優先権まで確認する。事業者が示す成功例を審査するときは、解約した顧客、未完了の仕事、返金を含む母集団と照合し、都合のよい一件だけを拡大しない。","en":"Separate first-year acquisition from customers who return. Track the same cohort’s paid renewals, margin before and after discounts, and time spent explaining results or handling complaints, excluding subsidized demonstrations where appropriate. If a distributor absorbs costs, also calculate the unsupported job cost. More acreage accompanied by more revisits and lower margins is not unambiguously commercial progress. For a dominant customer, inspect payment timing and booking priority as well as contract size. Compare a provider’s success stories against the complete cohort, including cancellations, unfinished jobs and refunds, rather than extrapolating from a selected success."},"kind":"design"},{"title":{"ja":"撤退・修理・乗り換えも、投資の出口","en":"Plan repair, switching and exit before buying"},"body":{"ja":"機体を使い切る計画だけでは、事業を守れん。主要部品の供給が止まったとき、誰が代替機を出し、保存した圃場や作業履歴を移せるかを購入前に試す。保守契約の応答時間と現場復旧時間を混同せず、部品待ちの営業日数を資金繰りへ入れる。売却価値は確約のない査定額を過信せず、売れない場合も計算する。投資判断の最後には、追加機体を買わない選択、繁忙期だけ外注する選択、解析に特化する選択を並べる。廃業時には顧客データの返却、未完了契約の引継ぎ、保険と記録の保持を担当者付きで決めておけば、撤退が顧客の営農停止へ直結しにくい。","en":"A plan that assumes uninterrupted use does not protect the business. Before purchase, test who supplies replacement aircraft and whether field data and job histories can move when key parts become unavailable. Distinguish a support response from restoration in the field, and include business days waiting for parts in cash planning. Treat unsupported resale estimates cautiously and model no resale. Compare buying another aircraft with peak-season subcontracting, specializing in analysis, or not expanding. Assign responsibility for returning customer data, handing over unfinished contracts and retaining required insurance and records if operations cease, reducing the chance that supplier failure interrupts farming."},"kind":"design"}],"checklist":{"ja":["一件粗利と季節資金を分離","再依頼の理由を確認","補助金なしの持続性を試算","導入台数と継続利用を区別"],"en":["Separate margin from seasonal cash","Investigate repeat demand","Test viability without subsidies","Distinguish sales from continued use"]},"sources":[{"title":"University of Missouri — Economics of Drone Ownership (2025)","url":"https://extension.missouri.edu/publications/g1274"},{"title":"FAO AgriTech Observer #2 — Drones for smallholders","url":"https://www.fao.org/digital-villages-initiative/europe/news-and-articles/news-and-articles-detail/agritech-observer--2--drones-for-smallholders---six-lessons-on-what-works-in-practice/"},{"title":"University of Hohenheim — Digital technology for smaller farms, DiWenkLa","url":"https://www.uni-hohenheim.de/pressemitteilung?cHash=9b0e769ad47d7f8c884308823130103d&tx_ttnews%5Btt_news%5D=59752"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"industry","category":"economics","lenses":["business","platform"],"title":{"ja":"産業構造を、農家に届くまでたどる","en":"Follow the industry all the way to the farm"},"dek":{"ja":"機体・資材・解析・販売店・受託者・農業指導をつなぐ。","en":"Connect aircraft, inputs, analytics, dealers, operators and agronomy."},"guide":{"ja":"機体が良くても、直す人と相談できる人がおらんと困るけえ。","en":"Good hardware still needs local repair and agronomic support."},"sections":[{"title":{"ja":"価値が生まれる連鎖","en":"Trace the delivery chain"},"body":{"ja":"分析の枠組みとして、部品・機体、資材、販売保守、操縦、農学、データ、金融保険を別の層にする。誰が顧客の課題を受け、誰が結果の責任を持つかを線でつなぐ。紹介手数料や解析料が積み重なるなら、最終価格への影響も見る。","en":"Map components and aircraft, inputs, sales and service, operation, agronomy, data, finance and insurance as distinct layers. Identify who receives the problem and who owns the outcome. Track how referral and processing charges accumulate in the final price."},"kind":"design"},{"title":{"ja":"普及の障害は購入費だけではない","en":"Adoption barriers extend beyond price"},"body":{"ja":"FAOの小規模農家向け事例整理は、サービス提供、地域の担い手、分かりやすい依頼窓口と成果物の重要性を示している。農家に機材と解析の複雑さを丸ごと渡すより、必要な作業単位で利用できる設計が論点になる。","en":"FAO’s smallholder case synthesis emphasizes service delivery, local capacity, accessible ordering and usable outputs. This points toward evaluating access to a useful service, rather than transferring every technical burden to the farmer."},"kind":"evidence"},{"title":{"ja":"競争力をどこに積むか","en":"Choose where to build capability"},"body":{"ja":"提案する強みは、地域の圃場知識、実測した品質、迅速な修理、異なる機体への移行性、農家との信頼じゃ。データを閉じ込めるだけでは乗り換え費用は作れても、現場の価値を増やせない。共通形式で出せることを調達条件にする。","en":"Build strength in field knowledge, measured quality, rapid repair, cross-aircraft portability and farmer trust. Locking data may create switching costs without improving field outcomes. Include exportable formats in procurement requirements."},"kind":"design"},{"title":{"ja":"同じ機体でも、販売できる仕事は違う","en":"The same aircraft can support different businesses"},"body":{"ja":"英国HSEはドローンによる商用農薬散布の未承認を説明し、フランスは2026年に限定条件の制度を整えた。両者を「欧州市場」と一括りにはできん。ここからは市場設計の提案じゃ。機体の販売可否、飛行条件、資材の適用、散布装置、作業者資格を別々の欄にし、見込み売上を実施可能な用途へ結び付ける。制度変更が検討中の用途は、実施済み案件と別の売上シナリオに置く。観測なら売れる地域でも散布が売れるとは限らず、同じセンサーでも助言を買う窓口が農家、協同組合、保険者で変わる。輸出台数を、その国の農業サービス市場の実需と同一視しないことが肝心じゃ。","en":"UK HSE describes commercial pesticide drone applications as unauthorized, while France established a conditional framework in 2026. These cannot be collapsed into one European market. Our market-design proposal separates aircraft sale, aviation conditions, product use, equipment and operator requirements, linking revenue to feasible uses. Put operations awaiting regulatory change in a separate scenario from delivered work. A territory that supports monitoring does not necessarily support spraying. Even for the same sensor, the paying customer may be a farmer, cooperative or insurer. Aircraft exports are not equivalent to demonstrated demand for agricultural services."},"kind":"design"},{"title":{"ja":"不具合の受け皿を、契約の境界に置く","en":"Assign an owner where responsibilities meet"},"body":{"ja":"散布むらが出たとき、機体会社は地図、解析会社は操縦、受託者は天候を理由にすると、農家だけが取り残される。提案する契約では、受付窓口を一つ決め、処方の誤り、機械故障、作業逸脱、判断に必要な情報不足を切り分ける。ただし原因が分かるまで受付を拒まない。窓口は必要なログを保全し、現地確認の担当と期限を伝え、作業再開を判断する責任者へ渡す。費用の最終負担は契約と当地の制度で決めるが、先に誰が動くかは決めておける。下請けが変わっても同じ仕事IDを保ち、農家へ同じ説明を何度も求めない構造を目指す。","en":"When coverage is uneven, an aircraft vendor may blame mapping, an analyst may blame piloting, and the contractor may blame weather. The farmer needs a responsible contact before causation is settled. Our proposed contract assigns one intake owner who preserves logs, distinguishes prescription errors, equipment faults, operational deviations and missing information, and names the field investigator and deadline. The case then passes to the person authorized to decide whether work resumes. Final cost allocation depends on contracts and local requirements, but immediate response ownership can be settled in advance. Preserve one job ID through subcontractor changes so the farmer need not repeat the same account."},"kind":"design","table":{"headers":{"ja":["問題","最初の担当","次へ渡す証拠"],"en":["Issue","First owner","Evidence for handover"]},"rows":{"ja":[["地図と圃場が違う","依頼窓口・地図管理者","境界の版、現地写真"],["散布むら・未処理","受託責任者","飛行・吐出・中断ログ"],["解析結果が届かない","解析サービス窓口","受領日時、品質判定、納期"]],"en":[["Map differs from field","Intake and map owner","Boundary version, site photos"],["Uneven or missing treatment","Contractor lead","Flight, flow and interruption records"],["Analysis is late","Analysis service contact","Receipt time, quality review, deadline"]]}}},{"title":{"ja":"価格競争の前に、誰の仕事を減らすか","en":"Identify whose work the service actually removes"},"body":{"ja":"機体価格が下がっても、販売店、操縦者、農学担当、解析会社の調整費が増えれば農家の負担は下がらん。価値連鎖の図には売上だけでなく、依頼の聞き直し、データ変換、説明、再訪の時間を書く。共同組織が日程と区画をまとめる場合は、その調整に対価があるかも確認する。事業者の強みは囲い込んだデータ量だけでなく、適期に修理できること、地域の作物を理解すること、引継ぎが途切れないこととして測る。無料解析を機体販売へ抱き合わせる方式も、契約終了後の閲覧・持ち出し・再解析費用を含めて比較するんじゃ。安い入口が、長く使える仕組みとは限らない。","en":"Lower aircraft prices may not lower the farmer’s total burden if coordination among dealers, pilots, agronomists and analysts grows. Map time spent repeating intake, converting data, explaining findings and revisiting sites as well as revenue. If a cooperative aggregates fields and schedules, check whether that coordination is funded. Assess competitive strength through timely repair, local crop knowledge and continuity of handovers, not only accumulated proprietary data. Bundled free analysis should be compared using post-contract access, export and reprocessing costs. A low entry price does not establish a durable service."},"kind":"design"},{"title":{"ja":"地域比較は、国名より制約の組み合わせ","en":"Compare combinations of local constraints"},"body":{"ja":"国別の市場規模から機体構成を決める前に、圃場の細かさ、地形、作物の高さ、水と電源、道路、農学的な適期をそろえて比べよう。分散した小区画なら依頼の集約と出動費回収、広い連続圃場なら補給の持続能力、急傾斜なら荷役と地上の移動が論点になる。どれも国全体の特徴と決め付けず、対象地区で確かめるんよ。同じ地域でも果樹と水田では必要な観測や作業が違う。地域拠点を増やす計画には、機体台数より先に、修理・相談・研修・資材補給の担当範囲を書き、忙しい日の連絡と代替手段まで定義する。","en":"Before deriving a fleet from national market size, compare fragmentation, terrain, canopy height, water and power access, roads and agronomic windows. Dispersed plots raise aggregation and mobilization questions; large continuous fields raise sustained resupply questions; slopes raise loading and ground-access questions. Verify these conditions in the intended district rather than treating them as national traits. Orchards and rice fields within the same region still need different observations and operations. Expansion plans should define repair, advice, training and input-supply coverage before aircraft numbers, including contacts and alternatives on the busiest days."},"kind":"design"}],"checklist":{"ja":["責任を持つ主体を特定","地域保守の到達時間を確認","農家の入口を簡潔に","データの出口を契約に"],"en":["Identify accountable parties","Check local repair response","Keep farmer intake simple","Contract for data export"]},"sources":[{"title":"FAO AgriTech Observer #2 — Drones for smallholders","url":"https://www.fao.org/digital-villages-initiative/europe/news-and-articles/news-and-articles-detail/agritech-observer--2--drones-for-smallholders---six-lessons-on-what-works-in-practice/"},{"title":"HSE — Aerial spraying","url":"https://www.hse.gov.uk/pesticides/using-pesticides/general/aerial-spraying.htm"},{"title":"French Agriculture Ministry — Drone application framework, 2026","url":"https://agriculture.gouv.fr/protection-des-cultures-publication-des-textes-autorisant-lutilisation-de-drones-pour-lapplication"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"platform","category":"data","lenses":["platform","business"],"title":{"ja":"空と農地のOSを設計する","en":"Design an operating layer for sky and field"},"dek":{"ja":"圃場、観測、処方、任務、実績を、別々に持って結びつける。","en":"Connect fields, observations, prescriptions, missions and actual work."},"guide":{"ja":"全部を一枚の地図に押し込まんでええ。つながる台帳が先じゃ。","en":"Start with linked records, not a map that tries to contain everything."},"sections":[{"title":{"ja":"共通IDを先に決める","en":"Start with shared identifiers"},"body":{"ja":"本章の設計案では、組織、農場、圃場、作期、作物、機体、担当者、観測、処方、作業、実績を独立させる。圃場境界が変わっても過去の実績を壊さないよう、境界の版と有効期間を持たせる。","en":"Our proposed model separates organization, farm, field, season, crop, aircraft, person, observation, prescription, job and actuals. Version field geometry and validity periods so boundary changes do not rewrite historical work."},"kind":"design"},{"title":{"ja":"画像の発見と作業の承認を分ける","en":"Separate data discovery from authorization"},"body":{"ja":"OGCのSTACは時空間データを記述するJSONの仕組みで、画像等を検索・参照しやすくする。だがカタログに画像があることは、処方や飛行が承認済みという意味ではない。作業の承認状態は別の業務データにする。","en":"OGC STAC describes spatiotemporal assets in JSON to support discovery and reference. An image in a catalog does not imply an approved prescription or flight. Keep operational authorization in a separate business record."},"kind":"evidence"},{"title":{"ja":"接続が切れても二重実行させない","en":"Prevent duplicate work after reconnection"},"body":{"ja":"依頼に一意のIDを付け、再送されても同じ作業を重複作成しない。現場端末の記録は同期時に競合を検出する。処方を更新したのに古い機体計画が残る場合は、実行前に版番号の一致を確認する。","en":"Use unique request IDs and idempotent processing. Detect conflicts when field devices reconnect. If a prescription changes while an old mission remains on a controller, compare versions before execution."},"kind":"design"},{"title":{"ja":"このサイトの実装境界","en":"What this website implements"},"body":{"ja":"このサイトは知識ガイドと計算ツールで、実機の操縦・農家データの管理サーバーは持たない。本文と調査データはJSON、生成物は静的HTMLじゃ。将来の業務APIに移行しても、特定AIの会話履歴を唯一の仕様書にしない。","en":"This website implements a guide and planning calculators, not live aircraft control or a farm-record server. Editorial and research content is JSON; output is static HTML. Future operational APIs should use explicit schemas, not an AI conversation as their only specification."},"kind":"design"},{"title":{"ja":"データ契約に、値の意味まで含める","en":"A data contract must preserve meaning"},"body":{"ja":"NaLamKIは公開インターフェースと分散学習を扱う研究例じゃ。以下はその性能を保証する話ではなく、本ガイドの設計提案。二つの会社が「散布量」を送れても、一方が原液、もう一方が希釈後の液なら接続は成立しない。各項目に意味、単位、座標系、時刻帯、欠測の表現、品質、作成者、版を持たせる。圃場境界はいつ有効だったかも必要じゃ。受信側は不明な単位を推測で補わず保留し、修正担当へ戻す。CSVで持ち出せるだけを互換性と呼ばず、別のソフトで同じ位置、量、対象日を再現できることを受入試験にする。","en":"NaLamKI is a research example involving open interfaces and distributed learning. The following is our design proposal, not a guarantee of its performance. Exchanging a field called “application quantity” fails semantically if one party means concentrate and another diluted liquid. Specify meaning, units, coordinate reference, time zone, missing values, quality, author and version. Field boundaries also need validity periods. Receivers should hold unknown units for correction rather than infer them. Exportable CSV alone is insufficient: acceptance testing should reproduce the same location, quantity and effective date in another system."},"kind":"design","table":{"headers":{"ja":["項目","必須の意味","曖昧なら"],"en":["Field","Required meaning","If ambiguous"]},"rows":{"ja":[["散布量","原液／希釈液、L/ha等","処方を保留"],["境界","座標系、有効期間、版","旧版と照合"],["観測時刻","取得時刻、時刻帯","鮮度を未確認表示"],["欠測","ゼロと区別した理由","未観測を正常にしない"]],"en":[["Quantity","Concentrate or mixture, units","Hold prescription"],["Boundary","Reference system, validity, version","Compare historical version"],["Observation time","Acquisition time and zone","Mark freshness unverified"],["Missingness","Reason distinct from zero","Do not infer normality"]]}}},{"title":{"ja":"依頼・指示・観測・承認を別イベントにする","en":"Separate requests, commands, observations and approval"},"body":{"ja":"「完了」という一語では、飛行終了、散布終了、品質確認、顧客への引渡しが混ざる。仕事を依頼受付、計画確定、開始、中断、部分実施、照合、品質確認、引渡しへ分け、各イベントに実行者と時刻を記録しよう。計画を書き換えても過去の実績を消さず、訂正は元の記録を指す追加イベントにする。例えば補給後に別機へ引き継ぐなら、未処理区画と実際の吐出量を確認してから再開指示を作る。通信が戻った際の同じ報告は同じイベントIDで重複排除するが、内容が違うなら自動上書きせず競合として扱う。これでAIが要約しても、責任ある人が元の根拠を追える。","en":"One “complete” flag confuses flight completion, treatment completion, quality acceptance and customer handover. Record intake, plan approval, start, interruption, partial execution, reconciliation, quality review and handover as distinct events with actors and timestamps. Editing a plan must not erase actuals; corrections should reference earlier events. When another aircraft takes over after replenishment, reconcile untreated cells and recorded discharge before issuing the restart. Deduplicate retransmissions by event ID, but treat changed content as a conflict instead of silently overwriting it. This preserves evidence for responsible human review even when an AI produces the summary."},"kind":"design"},{"title":{"ja":"空の予約と農地の処置を、同時に確定しない","en":"Separate airspace reservations from agronomic authorization"},"body":{"ja":"圃場の処方が承認されても、その時刻の空路が空いているとは限らん。逆に飛行枠が取れても、資材の条件や現地の準備は未確認かもしれない。提案する仕組みでは、農学的な実施条件と空域・人員・補給設備の予約を別管理し、開始直前に両方の有効性を照合する。天候で一機が帰還した際、全機を同じ補給点へ向かわせないよう、混雑と予備着陸場所を扱う。古い位置情報の機体を地図から消して空いたと判定せず、不明状態の予約を残して担当者へ渡す。ただし、このモデルは運航許可を与えるものでも、実機の安全機能を置き換えるものでもない。","en":"An approved prescription does not guarantee a free flight corridor at the intended time. A flight slot does not establish product eligibility or site readiness. Our proposed system manages agronomic conditions separately from reservations for airspace, staff and service facilities, checking both immediately before execution. Replanning after weather or a return should account for congestion and contingency landing sites rather than send every aircraft to one replenishment point. Stale telemetry must not make an aircraft disappear and release its reserved space; preserve an unknown state for responsible review. This architecture grants no operating permission and does not replace aircraft safety functions."},"kind":"design"},{"title":{"ja":"AIを替えても、仕事の台帳は残す","en":"Keep the operational record independent of the AI"},"body":{"ja":"Claude、Grok、その他のツールを替えるたびに圃場や履歴を作り直す構造にはせん。標準的なファイルと明示したAPIを正本へつなぎ、AIは検索・説明・下書きを担当するクライアントとして扱う。AIが提案した処方や予定は、人の承認状態と分け、会話だけを実行指示にしない。モデル更新後に同じ入力で結果が変わるため、使用モデル、入力資料の版、出力、承認者を結ぶ。停止時は最終承認済みの記録を閲覧でき、別の担当者へ引き継げる状態を保つ。将来APIを実装するなら、読み取りと変更の権限、監査、失効、データ持ち出しを最初の契約に含める。","en":"Changing between Claude, Grok or another tool should not require rebuilding field histories. Connect documented files and explicit APIs to the authoritative record; treat AI as a client for search, explanation and drafts. Keep AI-generated prescriptions and schedules distinct from human approval, and never treat conversation alone as an execution command. Model updates can change outputs for identical inputs, so link model identity, input versions, output and approver. During outages, retain access to the last approved records for handover. Any future API should define read and mutation permissions, audit, expiry and export from the outset."},"kind":"design"}],"checklist":{"ja":["圃場境界を版管理","観測と処方と実績を分離","再送・競合・古い計画に対応","任意のAIと通常Gitで編集"],"en":["Version field boundaries","Separate observations, prescriptions and actuals","Handle retries, conflicts and stale plans","Edit with any AI and standard Git"]},"sources":[{"title":"OGC — SpatioTemporal Asset Catalog Community Standard 1.1","url":"https://docs.ogc.org/cs/25-004/25-004.html"},{"title":"University of Hohenheim — NaLamKI project description","url":"https://humboldt-reloaded.uni-hohenheim.de/projekt?cHash=29d09814cb9f1aa9c33c7b082731bacd&no_cache=1&tx_uhohhrprojekte_projects%5Baction%5D=show&tx_uhohhrprojekte_projects%5Bcontroller%5D=Project&tx_uhohhrprojekte_projects%5Bproject%5D=2393"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"data-rights","category":"data","lenses":["platform","business"],"title":{"ja":"農業データを、持ち出せる資産にする","en":"Make farm data a portable asset"},"dek":{"ja":"権利、同意、保存期間、派生データ、退出時の扱いまで。","en":"Specify rights, consent, retention, derived data and exit procedures."},"guide":{"ja":"自分の畑の記録を、自分で持ち出せるようにしとこうや。","en":"Make sure the farmer can take their records with them."},"sections":[{"title":{"ja":"所有だけでは決まらない","en":"Ownership is not the whole agreement"},"body":{"ja":"本章は契約・システム設計上の論点整理じゃ。原画像、圃場境界、作業履歴、学習済みモデル、集計結果は別の対象として整理する。誰が利用できるか、第三者へ渡せるか、学習に使えるかを用途別に定義する。","en":"This chapter frames contractual and system questions. Treat imagery, field boundaries, operational history, trained models and aggregates as distinct assets. Define access, onward sharing and training use by purpose."},"kind":"design"},{"title":{"ja":"出口のテストを調達時に","en":"Test export during procurement"},"body":{"ja":"GeoJSONの境界、CSVの作業一覧、元画像、解析条件、単位、座標系、時刻をまとめて出せるか試す。ファイルが出ても意味が失われれば移行できない。削除、保存義務、契約終了後の取得期限は地域の法務担当と確認する。","en":"Test export of GeoJSON boundaries, CSV jobs, original imagery and metadata for processing, units, coordinates and time. A file is not portable if its meaning is lost. Review deletion, retention duties and post-contract access with local legal expertise."},"kind":"design"},{"title":{"ja":"最小権限と監査","en":"Use least privilege and audit"},"body":{"ja":"農家は自分の圃場、受託者は割り当てられた作業、解析者は必要な観測だけを扱う設計にする。共有リンクには期限を設け、書き込み履歴を残す。AIへ送る前に、圃場位置や個人情報を含む必要があるかを検討する。","en":"Limit farmers to their fields, contractors to assigned jobs and analysts to required observations. Expire shared links and audit changes. Before sending records to an AI service, assess whether precise locations or personal information are necessary."},"kind":"design"},{"title":{"ja":"標準形式は、利用許諾の代わりにはならない","en":"A standard file format does not grant permission"},"body":{"ja":"OGCのSTAC 1.1は、画像などの資産を参照し、用途や提供者、ライセンスを記述する仕組みを定める。データ本体とメタデータのライセンスが同じとは限らん。GeoJSONのRFC 7946も座標の解釈を定める規格であって、農地情報の第三者提供を許可する契約ではないんよ。本ガイドの提案は、読めること、使ってよいこと、他へ渡してよいことを別々に確認すること。公開されたカタログから画像の位置が分かっても、自由な再配布やAI学習への利用が認められたとは扱わない。形式の互換性と利用条件を一枚の点検票に並べると、移行時の思い違いを減らせる。","en":"STAC 1.1 describes assets, roles, providers and licensing; data and metadata need not share the same license. GeoJSON RFC 7946 specifies coordinate interpretation, not permission to share farm information. Our proposed review separates readability, permitted use and onward sharing. Discovering imagery through a public catalog does not establish redistribution or model-training rights. Record format compatibility and permitted uses on the same acceptance sheet to prevent migration misunderstandings."},"kind":"evidence"},{"title":{"ja":"一圃場を丸ごと引っ越す試験","en":"Test migration with one complete field history"},"body":{"ja":"退出テストには、境界だけの小さなファイルではなく、一圃場の一作分を使おう。境界の旧版と新版、作業、観測、処方、実施結果、修正理由を別の環境へ移し、同じ日付の状態を再現できるか見るんじゃ。提案する合格条件は、圃場IDの対応が残り、面積・単位・時刻が一致し、元画像から結果へたどれること。画面のPDFだけを渡されても、後から処方を再解析できるとは限らん。逆に生画像だけ大量に戻っても、校正や欠測の意味が失われれば実用上は移行不能じゃ。書き出し時間、費用、取得期限、読めなかった項目を契約前に具体的な結果として残しておこう。","en":"Test exit with a full crop cycle for one field, not merely a small boundary file. Move boundary versions, jobs, observations, prescriptions, execution results and correction reasons into another environment and reconstruct the state on a selected date. Proposed acceptance criteria include preserved field-ID mappings, matching area, units and times, and traceability from source imagery to results. A PDF of the screen may not support reanalysis; a large image dump without calibration or missing-data meanings may be equally unusable. Record export time, fees, retrieval deadlines and unreadable fields before contracting."},"kind":"design"},{"title":{"ja":"訂正と削除を、証拠の連鎖を壊さず扱う","en":"Handle correction and deletion without losing provenance"},"body":{"ja":"農家が「この境界は違う」と知らせた時、最新図だけを書き換えると、過去の散布がどの地図に基づいたか分からなくなる。設計案では、訂正理由と有効日を付けた新版を作り、過去の作業記録が参照した版を保持する。一方、不要な個人情報は何でも永久保存するのではなく、目的と保存期限を設定するんじゃ。削除要求、法令上の保存、保険や事故の調査に必要な保全がぶつかった時の担当窓口も先に決める。これは契約とシステムの検討枠組みで、全地域に同じ削除権や保存義務があるという説明ではない。どのデータに何が適用されるかは利用地域と契約に応じて確認する。","en":"Silently replacing a disputed boundary can erase the map basis for a historical application. A proposed design creates a new version with a reason and effective date while retaining the version referenced by prior jobs. This does not justify retaining every personal detail indefinitely: define purpose and retention periods. Agree who handles conflicts among deletion requests, legal retention and evidence preservation for insurance or incidents. This is a contractual and system-design framework, not a claim of identical deletion rights or retention duties everywhere. Determine the applicable requirements for each data category and jurisdiction."},"kind":"design"},{"title":{"ja":"学習への利用と、農家への納品を切り分ける","en":"Separate model-training use from the service delivered"},"body":{"ja":"解析サービスの提供に必要な利用と、他の顧客向けモデルを育てる利用は、同じチェック欄にまとめんほうがよい。設計案として、対象データ、目的、渡す相手、場所、期間、再委託、利用を止める時の扱いを用途別に記録する。匿名化したつもりでも、位置・日付・珍しい作物の組合せが農場の推測につながる可能性を検討したい。学習済みモデルから特定データの影響を除けるかは実装依存なので、削除ボタンだけで完全に戻せると約束せんことじゃ。農家が追加利用を断った場合の基本サービス、価格、出力取得への影響も明記すれば、便利さと引き換えに何を認めるのか判断しやすい。","en":"Do not combine use necessary to deliver analysis with reuse to train models for other customers in one consent box. Our proposed record specifies data, purpose, recipient, location, duration, subcontracting and cessation separately. Consider whether location, date and an unusual crop could reveal a farm despite removed names. Removing a contribution from a trained model depends on implementation; a delete button should not promise complete reversal without evidence. State how refusal of additional use affects the base service, price and access to outputs so farmers can assess the actual exchange."},"kind":"design"}],"checklist":{"ja":["資産ごとに利用条件を定義","実データで退出テスト","単位と座標系を保持","アクセス履歴を記録"],"en":["Define rights per asset","Test exit with real records","Preserve units and coordinate systems","Audit access"]},"sources":[{"title":"OGC — SpatioTemporal Asset Catalog Community Standard 1.1","url":"https://docs.ogc.org/cs/25-004/25-004.html"},{"title":"IETF RFC 7946 — The GeoJSON Format","url":"https://www.rfc-editor.org/rfc/rfc7946.html"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"flight-principles","category":"foundations","lenses":["field","platform"],"title":{"ja":"農業ドローンは、なぜそう動くのか","en":"Why agricultural drones move as they do"},"dek":{"ja":"揚力、積載、測位、地形追従、ダウンウォッシュをつなげる。","en":"Connect lift, payload, positioning, terrain following and downwash."},"guide":{"ja":"重くなれば、同じ飛び方でも必要な力は変わるんよ。","en":"A heavier aircraft changes the work its rotors must do."},"sections":[{"title":{"ja":"力の釣り合いから考える","en":"Begin with force balance"},"body":{"ja":"基礎モデルでは、静止ホバリング時の全推力が重量と釣り合う。加速や風への対処には余力が要る。電池と液剤を増やすと積載は増えるが、機体が必要とする推力も変わる。一定の航続時間を全積載状態へ当てはめない。","en":"In a basic model, total hover thrust balances weight; acceleration and disturbance rejection need margin. More battery or liquid also changes required thrust. A single endurance number should not be applied to every loading condition."},"kind":"design"},{"title":{"ja":"位置と作物上の高さは違う","en":"Position is not canopy clearance"},"body":{"ja":"GNSSやRTKによる位置、慣性センサーによる運動、地形センサーによる距離は役割が違う。圃場の標高と作物の上端を混同しない。設計時には補正情報の途絶、樹木や電線の検出限界、斜面での距離変化を試験条件にする。","en":"GNSS/RTK positioning, inertial motion sensing and ranging serve different roles. Terrain elevation is not canopy height. Test loss of corrections, obstacle-detection limits and changing clearance on slopes."},"kind":"design"},{"title":{"ja":"風が薬液を運ぶ","en":"Airflow also carries droplets"},"body":{"ja":"2026年のヘキサコプター研究は、ノズル配置とローター気流の関係が付着や均一性に影響すると報告している。ただし特定構成の結果を別機種へそのまま移せない。現場では液滴、気流、作物構造を組み合わせて評価する。 この研究はCFD解析と屋内での水による試験を含むもので、屋外の農薬散布効果を一般に証明するものではない。","en":"A 2026 hexacopter study reports that nozzle placement relative to rotor airflow affects deposition and uniformity. Results from one configuration cannot simply be transferred to another aircraft. Evaluate droplets, airflow and crop structure together. Its scope includes CFD and indoor water tests, not general proof of outdoor pesticide efficacy."},"kind":"evidence"},{"title":{"ja":"満載と帰還時を、別の飛行条件として見る","en":"Treat full-load departure and return as different conditions"},"body":{"ja":"機体選定では「最大積載量」だけを見ず、満載での離陸、作業途中、帰還時の三つを同じ試験票に並べるんじゃ。薬液が減る一方で電池残量も減るため、軽くなったから最後まで余裕があるとは限らん。平地の短い往復と、斜面の上側から下側へ長く進む作業では、補給地点までの戻り方も違う。提案する評価は、許容積載内での電流・電圧・温度・帰還残量を機体の記録から確認し、飛行中の値と着陸後に回復した表示を区別すること。公称航続時間の一つの数字から、散布面積や配送距離を直接決めんようにしたい。","en":"Evaluate full-load takeoff, mid-mission operation and return on one test sheet instead of comparing maximum payload alone. Liquid mass falls while battery charge also falls, so a lighter aircraft does not automatically retain sufficient margin. A short trip over level ground and a long pass down a slope have different return routes to the support point. Our proposed assessment checks current, voltage, temperature and return charge from aircraft logs within the permitted loading envelope. Separate in-flight readings from values that recover after landing. Do not directly convert a single advertised endurance figure into treatment area or delivery range."},"kind":"design"},{"title":{"ja":"流量・速さ・幅を、同じ単位で結ぶ","en":"Connect flow, speed and width in consistent units"},"body":{"ja":"説明用に、水だけを毎秒0.1リットル出し、毎秒5メートルで幅4メートルを均一に処理する理想条件を置く。毎秒の面積は20平方メートルなので、面積当たりの水量は50リットル／haとなる。これは農薬の推奨設定ではなく、重複・旋回・立上がりを除いた単位計算じゃ。流量が同じまま速度だけ半分になれば、面積当たり量は倍になる。自動流量制御があっても、加減速時の追従や噴霧の開始・停止は確認が要る。地図の線を正確に飛べたことと、線の両側へ同じ量を届けたことは別に検証しよう。","en":"Consider an illustrative water-only calculation: 0.1 liters per second applied uniformly across a four-meter width at five meters per second. Area coverage is 20 square meters per second, giving 50 liters per hectare. This is unit arithmetic, not a pesticide setting; it excludes overlap, turns and startup. Halving speed without changing flow doubles the amount per area. Even automatic flow control needs evaluation during acceleration, deceleration and spray start/stop. Accurate navigation along a line and uniform delivery on both sides of that line are separate outcomes."},"kind":"design"},{"title":{"ja":"下降気流は、強ければよいとは言えない","en":"Stronger downwash is not automatically better"},"body":{"ja":"韓国の2024年の飛散モデル研究では、風速、大気安定度、作物高、散布高が重要な要因だった。地上散布と異なる空間分布も報告されており、その抄録からは地上用モデルの単純流用に限界が読み取れる。これは対象試験条件での結果で、全機種に共通する安全距離の算定式ではないんよ。評価では「葉の上面に付いた」「葉の内側まで届いた」「圃場外へ出た」を分ける。同じ総液量でも付着場所が違えば農業上の意味が変わるため、下降気流を単独の優劣指標にせず、対象害虫の位置や作物構造と合わせて考えるんじゃ。","en":"A 2024 Korean drift-model study identifies wind speed, atmospheric stability, crop height and spraying height as influential. Its abstract reports spatial behavior different from ground spraying, limiting direct transfer of ground models. These findings do not supply a universal safety-distance formula. Our evaluation separates upper-leaf deposition, penetration into the canopy and off-field movement. The same liquid total can have different agronomic meaning depending on where it lands. Treat downwash together with pest location and canopy structure rather than as a standalone performance score."},"kind":"evidence"},{"title":{"ja":"測位が正しくても、作業が正しいとは限らない","en":"Correct positioning does not guarantee correct work"},"body":{"ja":"提案する受入試験では、位置の正しさ、作物までの距離、流量や投下の正しさを独立に記録する。RTKの状態が良好でも、古い圃場境界を読んでいれば作業場所を誤る。高さセンサーが地面を見ているのか葉の面を見ているのかも、作物や地形に応じて確認するんじゃ。故障を試す際は実農薬を使った強行飛行を避け、メーカーが認める安全な試験方法やログ再生で補正切れ・通信遅延への応答を評価する。停止・保留・帰還のどれになったかを残し、復旧後に未処理部分へ戻る位置まで検証すると、再作業の穴や重複を見つけやすい。","en":"Record positioning, canopy clearance and application delivery independently during acceptance testing. A good RTK status cannot correct an outdated field boundary. Confirm whether ranging represents the ground or foliage under the relevant crop and terrain conditions. Evaluate correction loss or communication delay using manufacturer-approved safe tests or log replay instead of forcing failures during pesticide operations. Record whether the system stops, holds or returns, and verify the restart location. This reveals untreated gaps and duplicated application that successful navigation alone would miss."},"kind":"design"}],"checklist":{"ja":["積載ごとの性能を確認","地形と作物高さを区別","センサーの限界を試験","機種別に付着を検証"],"en":["Check performance by load","Distinguish terrain and canopy","Test sensor limitations","Validate deposition per aircraft"]},"sources":[{"title":"Downwash–Spray Interactions in Agricultural Hexacopters (2026)","url":"https://www.mdpi.com/2504-446X/10/8/557"},{"title":"Virginia Tech — Spray Drones: Technology, Regulation and Field Operations","url":"https://www.pubs.ext.vt.edu/SPES/spes-819-spray-drones-in-agriculture-technology-regulation-and-field-operations.html"},{"title":"Korean Journal of Environmental Agriculture (2024) — Spray drift curve model; abstract reviewed","url":"https://www.kci.go.kr/kciportal/landing/article.kci?arti_id=ART003146836"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"history","category":"foundations","lenses":["field","business"],"title":{"ja":"農具から空の道具へ、変わらない問い","en":"From hand tools to aerial tools"},"dek":{"ja":"人力・畜力・機械化・精密農業を、現場の制約から見る。","en":"Read mechanization through the constraints it tries to solve."},"guide":{"ja":"新しい道具が勝つとは限らん。土地と仕事に合うかが肝心じゃ。","en":"The newest tool does not always win. It must fit the land and the work."},"sections":[{"title":{"ja":"置き換わる一本道ではない","en":"History is not a single replacement ladder"},"body":{"ja":"農業の道具を、人力から畜力、機械、デジタルへ全世界が同時に進む一本道として描かない。FAOの西アフリカの畜力研究は、道具の技術的完成と実際の採用が一致しない例を扱っている。土壌、資金、修理、家族労働、作物の違いを見る。","en":"Avoid a universal ladder from hand tools to animals, engines and digital systems. FAO’s West African animal-traction analysis discusses technically developed tools that were not widely adopted. Soil, finance, repair, household labor and crops shape suitability."},"kind":"evidence"},{"title":{"ja":"1987年の農業用無人ヘリ","en":"The 1987 agricultural helicopter milestone"},"body":{"ja":"ヤマハの社史では、R-50の最初のモデルが1987年に完成し、同年12月から20機を限定販売したと記録している。日本の農業用ドローンは、小型電動マルチコプターより前から続く無人航空散布の歴史を持つ。","en":"Yamaha records completion of the first R-50 model in 1987 and a limited sale of 20 aircraft starting that December. Japan’s agricultural unmanned aviation history therefore predates small electric multirotors."},"kind":"evidence"},{"title":{"ja":"次の道具を評価する物差し","en":"How to evaluate the next tool"},"body":{"ja":"本ガイドの評価軸は、重労働の軽減、適期作業、必要資材、整備可能性、品質、総費用じゃ。トラクターとドローンを競争だけで考えず、地上機が耕し、衛星が広域を見て、ドローンが局所を確認する組合せも比較する。","en":"Our evaluation framework asks about drudgery, timeliness, inputs, maintainability, quality and total cost. Compare complementary systems: ground machinery for soil work, satellites for broad screening and drones for targeted inspection."},"kind":"design"},{"title":{"ja":"農具の歴史を「何を省いたか」で読み直す","en":"Read tool history through the work removed"},"body":{"ja":"道具の変遷を並べるなら、発明年だけでなく、どの仕事を省き、どこへ負担を移したかを書き添えよう。手道具は人が位置と力を直接調整し、動力機械は広い面を繰り返し処理する。測位や画像解析は、さらに場所ごとに処理を変える判断を助ける。ただしこれは世界共通の発展段階ではなく、仕事を分解するための見方じゃ。力仕事が減っても給油・充電・整備・記録は増えうる。農具の優劣を一日当たり面積だけで判断せず、準備から片付けまでの担当者、必要な技能、地域内で直せる部品、繁忙期の代替手段を一緒に記録すると、導入が続く条件が見えてくる。","en":"Alongside invention dates, record which task a tool removes and where it moves the burden. Hand tools let people directly adjust position and force; powered machinery repeats work across larger areas; positioning and imagery support spatially differentiated decisions. This is a way to decompose work, not a universal sequence of development. Less physical labor can come with more fueling, charging, maintenance and record keeping. Compare staffing from setup through cleanup, required skills, locally repairable components and peak-season alternatives alongside daily area coverage. These reveal whether adoption can be sustained."},"kind":"design"},{"title":{"ja":"空から地上へ戻る判断も、技術の前進になる","en":"Returning a task to the ground can be progress"},"body":{"ja":"JA長野県の2024年報告には、前年にドローン直播を試した農業法人が、施肥・除草剤散布を同時に行うため田植機の直播装置を試験した例がある。ドローンで収量と省力化の成果を得た上で、工程全体を見直した事例じゃ。一方、韓国RDAの2023年資料は、雨で地上機が入りにくい水田で稲刈り前に飼料作物を播く用途を説明する。二つの資料は同じ条件の性能比較ではない。それでも、判断対象を「最新の機械」から「期限内に完了する栽培工程」へ変えると、地上機の同時作業と空からの接近性を公平に比較できる。","en":"A 2024 JA Nagano report describes a farm testing a transplanter seeding attachment after a successful drone-seeding trial, seeking simultaneous fertilizer and herbicide application. Korea's RDA describes aerial forage sowing before rice harvest when wet soil restricts ground access. These are not controlled comparisons under identical conditions. They illustrate an original decision frame: compare crop operations completed within the available window, weighing combined ground operations against aerial access rather than choosing the newest machine."},"kind":"evidence"},{"title":{"ja":"共同利用の歴史は、補給と修理の歴史でもある","en":"Shared machinery also depends on support and repair"},"body":{"ja":"共同利用や受託作業を評価する際は、所有者より先に「忙しい日の順番を誰が決めるか」を確かめるんじゃ。同じ地域で適期が重なる作物ばかりなら、台数を共有しても待ち行列は消えない。作期が違う圃場を組み合わせられるか、補給車をどこへ置くか、故障時に誰が代行するかで結果は変わる。提案する聞き取りでは、機械の購入時だけでなく、二年目の部品代、保険、訓練の引継ぎ、通信契約、担当者の離職まで扱う。過去の共同機械と新しいドローンサービスを同じ質問で調べれば、飛行技術以外に必要な地域の仕事が浮かび上がる。","en":"For shared ownership or contracting, ask who sets the order on the busiest days before asking who owns the aircraft. Sharing machines does not eliminate queues when neighboring crops need work simultaneously. Complementary crop calendars, support-vehicle locations and backup operators can change the outcome. Our interview framework includes second-year parts, insurance, training handover, connectivity contracts and staff turnover, not merely purchase arrangements. Asking the same questions of older shared machinery and new drone services exposes the local support work that flight technology still requires."},"kind":"design"},{"title":{"ja":"歴史事例を投資資料に変える時の確認順","en":"Check historical cases before using them in investment decisions"},"body":{"ja":"事例集には「当時の困りごと」「採用した手段」「比較相手」「継続した期間」「今も残る条件」を残したい。実証時だけ技術者や予備機が多く付いていたなら、それを通常運営へ持ち込む費用を計上する。失敗の記録がない場合も、失敗がなかったと解釈せんことじゃ。ある地域で修理網と訓練が育った機械は、購入価格が低いだけの別機種より継続しやすい可能性がある。この見方は歴史からの評価提案であり、特定ブランドの優劣を断定するものではない。再現条件をそろえられない事例は、収益予測の根拠より、次の実証で確かめる仮説として使おう。","en":"A useful case record preserves the original constraint, chosen method, comparator, duration and conditions still relevant today. If a demonstration received extra engineers or backup equipment, price that support into normal operations. Missing failure reports do not prove failure-free operation. A machine supported by local repair and training may be easier to sustain than a cheaper alternative. This is an evaluative framework, not a brand ranking. When the conditions behind a historical case cannot be reproduced, use it to frame the next pilot's hypothesis rather than as a direct earnings forecast."},"kind":"design"}],"checklist":{"ja":["地域の条件から歴史を読む","技術完成と普及を区別","メーカー史料の立場を明記","地上・衛星・空の分担を比較"],"en":["Read history in regional context","Separate technical maturity from adoption","Identify manufacturer perspectives","Compare ground, satellite and aerial roles"]},"sources":[{"title":"FAO — Animal traction in West Africa: impact and constraints","url":"https://www.fao.org/4/x5455b/x5455b0g.htm"},{"title":"Yamaha Motor History — Development of the R-50","url":"https://global.yamaha-motor.com/stories/history/stories/0028.html"},{"title":"JA Nagano (2024) — 直播を試験 面積拡大を目指す","url":"https://www.iijan.or.jp/topic/20240605-04"},{"title":"RDA (2023) — Italian ryegrass seeding by drone","url":"https://www.rda.go.kr/board/board.do?boardId=farmprmninfo&dataNo=100000790753&mode=updateCnt&prgId=day_farmprmninfoEntry"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"regional-data","category":"foundations","lenses":["business","platform"],"title":{"ja":"農業データの地域差をどう読むか","en":"How to read regional differences in farm data"},"dek":{"ja":"同じ解析技術でも、圃場・統計・通信・農業指導の歴史が違う。","en":"Field structures, statistics, connectivity and extension change what works."},"guide":{"ja":"他国の成功例は、そのまま移すより、前提をほどいて読もうや。","en":"Read the assumptions behind another country’s success before transferring it."},"sections":[{"title":{"ja":"四つの層で比較する","en":"Compare four layers"},"body":{"ja":"本ガイドでは農地台帳と統計、衛星・気象、農場内の機械ログ、現場の相談・意思決定を分けて比較する。国のDX政策があることと、小規模農家が記録を日々使えることは別じゃ。30カ国の調査ページに一次資料をまとめる。","en":"Compare land records and statistics, satellite and weather data, on-farm machine logs, and everyday advisory decisions. A national digital policy is not proof that smallholders can use records daily. Country pages collect primary evidence for these distinctions."},"kind":"design"},{"title":{"ja":"広域観測と局所の確認","en":"Connect broad observation with local checks"},"body":{"ja":"国連のリモートセンシング手引きは、衛星と現地調査の間をドローンが補い、圃場境界や生育、統計検証に使われる例を紹介している。高解像度だけでなく、雲、区画の小ささ、作物の混在が方式選択に関わる。","en":"The UN remote-sensing handbook describes drones bridging satellite observations and ground surveys for boundaries, crop monitoring and statistical validation. Cloud cover, small plots and mixed crops influence the choice alongside resolution."},"kind":"evidence"},{"title":{"ja":"比較の表に残す条件","en":"Preserve the comparison context"},"body":{"ja":"地域比較には作物、圃場規模、灌漑、通信、農業指導、データの利用権、調査年を並べる。普及率を比べるときは、農家数・面積・機体数のどれを分母にしたか確認する。対象国の一部地域の試験を全国の普及と呼ばない。","en":"Record crops, field scale, irrigation, connectivity, extension, data rights and study year. Adoption rates need an explicit denominator: farms, area or aircraft. A local pilot project is not evidence of national adoption."},"kind":"design"},{"title":{"ja":"台湾・韓国・インドでは、入口となる仕事が違った","en":"Different institutional entry points in Taiwan, Korea and India"},"body":{"ja":"台湾の2010年資料は、従来の航空写真による稲作面積調査を衛星・UAV・現地調査で補う構想を示す。韓国RDAの2021年成果報告は、作物別観測、画像合成、利用者向け解析基盤を扱う。インドの2021年政府発表は、作物保険の地域収量推定を支える100地区での観測について、当時の条件付き使用許可を記録している。現在の包括許可ではないんよ。この三例だけで国の先進度を順位づけることはできん。面積統計、栽培管理、保険という異なる出発点が、必要な粒度や納期、説明責任を変えることを読むための比較じゃ。","en":"Taiwan's 2010 account proposes supplementing aerial rice-area surveys with satellites, UAVs and field checks. Korea's 2021 RDA report describes crop-specific observation, image mosaicing and interpretation services. India's 2021 announcement records a then-conditional permission for observations supporting insurance yield estimation in 100 districts, not a present blanket authorization. These examples cannot rank national technological maturity. They show how area statistics, cultivation decisions and insurance create different requirements for spatial detail, delivery time and accountability."},"kind":"evidence"},{"title":{"ja":"「同じ一枚の地図」が答えない三つの質問","en":"One map does not answer every question"},"body":{"ja":"国全体の作付面積を知りたい統計担当、明日の追肥箇所を決めたい農家、台風後の損害を査定したい保険者では、正解の定義が違う。提案する比較表は、利用者、判断期限、空間単位、現地確認、誤りの負担者を一行にまとめることじゃ。例えば村の平均収量がよく推定できても、同じ村の一圃場の損害を公平に説明できるとは限らん。逆に一圃場を極めて細かく撮れても、全国の標本に偏りがあれば統計の目的を満たさない。データ量を増やす前に、何を誰へ説明できれば成功かをそろえると、国や地域をまたいだ比較のずれを減らせる。","en":"National crop-area statisticians, farmers choosing tomorrow's fertilizer locations and insurers assessing storm damage need different definitions of success. Our comparison template records user, decision deadline, spatial unit, ground checks and the party bearing errors. Accurate village-average yield does not necessarily explain an individual field's loss fairly. Conversely, exquisite detail in one field cannot correct an unrepresentative national sample. Agree what must be explained, and to whom, before collecting more data. This makes comparisons across regions more meaningful."},"kind":"design"},{"title":{"ja":"通信の弱い地域では、最後の一枚から逆算する","en":"Design backward from the final field instruction"},"body":{"ja":"仮に農家の端末で大きな画像を開けず、圃場の電波も弱いとする。この場合の設計案は、全画像の常時同期を前提にせず、圃場番号、確認する場所、期限、判断理由、担当者を軽い記録で届けることじゃ。元画像は回線のある場所で同期し、撮影と解析と農家への伝達の時刻を別々に残す。反例は、最新の衛星画像があっても助言が届くまで作業適期を過ぎる仕組み。地域比較では「クラウドがあるか」より、圃場から相談窓口まで情報を渡す人、紙とデジタルを照合する方法、同期できなかった記録の回復手順まで調べると実用性を判断しやすい。","en":"Suppose a farmer's device cannot open large imagery and field connectivity is weak. A proposed design delivers a lightweight field identifier, location to inspect, deadline, rationale and responsible person without requiring continuous image synchronization. Sync original imagery where connectivity exists, and record capture, analysis and farmer-notification times separately. A counterexample is a service with recent satellite imagery whose advice arrives after the agronomic window. Evaluate the people carrying information to advisory services, paper-to-digital reconciliation and recovery of unsynchronized records, not cloud availability alone."},"kind":"design"},{"title":{"ja":"他地域へ移す前に、小さな移植試験をする","en":"Run a transfer trial before scaling into another region"},"body":{"ja":"別地域で動いた解析を導入する時は、作物名が同じだけで互換と判断せんことじゃ。本ガイドの移植試験では、品種、生育段階、土の見え方、灌漑、センサー、日照、教師データの採り方を並べ、違う項目に印を付ける。少数の代表圃場を先に選び、既存モデルを変えずに試して、どの条件で誤るかを現地担当者と確かめる。誤りを見て調整した圃場と、最終確認に使う圃場は分けておく。全国平均の精度を一つ出すより、乾田・湿田、平地・斜面など導入先が判断できる条件別の結果と、対応できない範囲を提示するほうが次の投資判断に役立つ。","en":"A shared crop name does not establish transferability. Our transfer trial compares cultivar, growth stage, visible soil, irrigation, sensor, lighting and ground-truth collection, marking differences explicitly. Select representative fields and first test the unchanged model with local reviewers to identify failure conditions. Keep fields used to tune the model separate from those used for final evaluation. Instead of one national average accuracy, provide results for conditions meaningful to the customer, such as wet versus dry fields or level versus sloping land, together with the unsupported range."},"kind":"design"}],"checklist":{"ja":["比較単位と年を揃える","地域試験と全国統計を区別","通信と農業指導を確認","農家の実際の行動まで追う"],"en":["Align units and dates","Separate local pilots and national statistics","Assess connectivity and extension","Trace actual farmer decisions"]},"sources":[{"title":"UN Handbook — UAV applications in agricultural statistics","url":"https://fao-eostat.github.io/UN-Handbook/uav_agriculture.html"},{"title":"Taiwan MOA (2010) — Integrated remote-sensing rice-area survey","url":"https://www.moa.gov.tw/ws.php?id=22384"},{"title":"RDA — 2021 research outcomes: drone crop observations","url":"https://www.rda.go.kr/org/gud/gud_rsachoutcomeQuery_2021.do"},{"title":"Government of India (2021) — Conditional drone permission for crop-insurance observations","url":"https://www.pib.gov.in/PressReleasePage.aspx?PRID=1699360&lang=2&reg=3"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"quality","category":"operations","lenses":["field","business"],"title":{"ja":"実証実験を、導入判断につなげる","en":"Turn a pilot into an adoption decision"},"dek":{"ja":"成功動画より、比較条件と失敗の記録を残す。","en":"Preserve comparison conditions and failures, not only a successful demo."},"guide":{"ja":"うまくいった日だけ集めたら、次の年の計画を間違えるけえね。","en":"A collection of good days cannot plan the next season."},"sections":[{"title":{"ja":"比較する相手を決める","en":"Choose a real comparator"},"body":{"ja":"提案する実証計画では、地域で実際に使われる地上機、人力、委託散布を比較対象にする。地形、作物、生育、天候、資材の条件を記録し、可能なら対照区と反復を設ける。研究担当者と必要なサンプル数を事前に決める。","en":"Compare with the actual local alternative: ground equipment, manual work or hired application. Record terrain, crop stage, weather and materials, using controls and replication where feasible. Agree sample size with the research lead beforehand."},"kind":"design"},{"title":{"ja":"品質・負担・費用を一緒に測る","en":"Measure quality, workload and cost"},"body":{"ja":"処理面積だけでなく付着、効果、作物損傷、作業者の負担、段取り、移動、再作業を測る。病害虫や収量には時差があるため、飛行直後の映像だけで効果を言い切らない。どの結果なら採用を見送るかも決める。","en":"Measure deposition, efficacy, crop damage, workload, setup, travel and rework alongside coverage. Pest outcomes and yield take time; footage immediately after flight cannot establish them. Define results that would cause rejection before testing."},"kind":"design"},{"title":{"ja":"失敗も再利用できる記録へ","en":"Make failures reusable"},"body":{"ja":"機体、ソフト、処方、地図の版を残す。未実施、データ欠損、修理、操縦者変更を除外せず記録する。平均値だけでなく範囲と例外を示し、「どんな条件なら使えるか」を採否の結論にする。","en":"Record versions of aircraft software, prescription and map. Preserve uncompleted jobs, missing data, repairs and operator changes. Report ranges and exceptions, then state the conditions under which adoption is justified."},"kind":"design"},{"title":{"ja":"見たことのない年で、予測を試す","en":"Evaluate predictions on an unseen year"},"body":{"ja":"韓国の水稲研究は、2018〜2020年の多波長画像から収量・タンパク質を推定し、年をまたぐ予測で回帰手法を比較した。ここで確認したのは大学公開の抄録であり、別の作物や地域で同じ性能を保証するものではない。この研究を手がかりに、本ガイドは学習済みの圃場だけで精度を判断せず、次の年や未使用の圃場を残す評価を提案する。同じ撮影日の近接画素を無作為に分けただけでは、試験側が学習側によく似てしまうことがあるんじゃ。導入先で本当に新しい条件は何かを先に決め、その単位で評価用データを分けておくと、現場での期待値を合わせやすい。","en":"A Korean rice study compares regression approaches for yield and protein prediction using multispectral observations from 2018–2020 and cross-year evaluation. We reviewed the university-hosted abstract; it does not guarantee performance in other crops or regions. Our proposed evaluation reserves a new year or previously unused fields rather than relying on familiar training sites. Randomly dividing neighboring pixels from one flight can leave evaluation data too similar to training data. Define what will actually be new at deployment and split evaluation data at that level."},"kind":"evidence"},{"title":{"ja":"正解率の前に、見逃しと誤警報の損を決める","en":"Define the cost of missed problems and false alarms"},"body":{"ja":"説明用の仮定として、100区画中5区画だけに問題がある状況を考える。全部を「正常」と返しても正解率は95％になるが、問題の5区画を一つも救えておらん。提案する実証では、問題を見つける割合、問題とされた場所が実際に問題である割合、確認に要した人の時間を併記する。さらに、見逃しで失う作業機会と、誤警報で増える巡回や再撮影を農家と見積もるんじゃ。解析側が選んだ閾値で終わらず、見逃しを減らす設定と巡回を減らす設定の両方を比較する。最終的には、地図が当たった数ではなく、限られた人手で適切な確認と対処につながったかを問いたい。","en":"In an illustrative example, only five of 100 plots have a problem. Calling every plot normal gives 95% accuracy while missing every affected plot. Report the share of real problems detected, the share of flagged locations that truly have problems, and staff time spent checking. Estimate the missed treatment opportunities caused by false negatives and extra visits or flights caused by false positives. Compare settings favoring detection with settings reducing inspection workload instead of accepting an analyst-selected threshold without discussion. Ultimately evaluate whether limited staff can make useful checks and act appropriately."},"kind":"design"},{"title":{"ja":"機体の速さ、散布の品質、農業の結果を別々に判定","en":"Judge flight efficiency, application quality and crop outcomes separately"},"body":{"ja":"実証の三層を混ぜると、よく飛んだ日がそのまま農業上の成功に見えてしまう。第一層は予定区画をどれだけ完了し、どれだけ時間と人を使ったか。第二層は対象へ必要な処理が届き、むらや対象外への影響がどうだったか。第三層は病害虫、生育、収量、品質などの遅れて現れる結果じゃ。提案する試験票では各層の測定日と責任者を決め、未測定は未測定と表示する。例えば付着が改善しても病害の発生自体が少なかった年には、増収まで言い切れない。反対に同じ収量でも、作業者の負担や適期作業の確実性が改善していれば、その価値を別項目として評価できる。","en":"Keep three layers separate. First, operational completion: which fields were finished and how much time and labor were used. Second, application quality: delivery to the target, uniformity and off-target effects. Third, delayed agronomic outcomes such as pests, growth, yield and quality. Assign dates and accountable reviewers to each layer, and label unmeasured outcomes explicitly. Better deposition in a year with little disease does not establish a yield gain. Conversely, unchanged yield can coexist with lower operator workload or more reliable completion within the crop window; evaluate those benefits separately."},"kind":"design"},{"title":{"ja":"導入・条件付き継続・中止を、先に言葉にする","en":"Predefine adoption, conditional continuation and rejection"},"body":{"ja":"試験開始前に、採用に必要な品質、許容する作業負担、対応できる天候範囲、予算の上限を関係者で決めるんじゃ。平均だけを見ず、忙しい日の遅れ、最悪に近い補給時間、故障が続いた週をどこまで引き受けられるかも話し合う。小規模な実証で極端な条件を観測できなかった場合は「問題なし」ではなく「未評価」と残す。結果は一律の合否だけでなく、平地区画では採用、斜面は追加試験、特定用途は見送り、と条件別に書ける。費用計算には中止・再作業した日も含め、担当者やソフトの変更後に再確認する項目を定めれば、実証が終わった後も品質管理を続けやすい。","en":"Before testing, agree required quality, acceptable workload, operating conditions and budget limits. Discuss tolerable peak-day delays, long replenishment cycles and weeks with repeated faults instead of relying on averages alone. Conditions absent from a small pilot are unassessed, not proven safe or reliable. Decisions can be conditional: adopt on level fields, test slopes further and reject a particular task. Include abandoned jobs and rework in economics, and specify what must be rechecked after operator or software changes. This turns a completed pilot into an ongoing quality process."},"kind":"design"}],"checklist":{"ja":["実際の代替手段と比較","採否基準を先に合意","悪い日と欠測も記録","収量など遅れて出る結果を追跡"],"en":["Compare real alternatives","Agree acceptance criteria first","Keep bad days and missing data","Follow delayed outcomes"]},"sources":[{"title":"Virginia Tech — Spray Drones: Technology, Regulation and Field Operations","url":"https://www.pubs.ext.vt.edu/SPES/spes-819-spray-drones-in-agriculture-technology-regulation-and-field-operations.html"},{"title":"University of Missouri — Economics of Drone Ownership (2025)","url":"https://extension.missouri.edu/publications/g1274"},{"title":"Gyeongsang National University / Remote Sensing (2021) — Rice yield and protein cross-year modeling; abstract reviewed","url":"https://scholarworks.gnu.ac.kr/item/83b69b2a-34ce-482f-b026-a4b667f2867b"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"irrigation","category":"core","lenses":["field","platform"],"title":{"ja":"水を読む。熱画像から灌水判断へ","en":"Read water stress without over-reading the image"},"dek":{"ja":"温度の異常と、水不足の原因を切り分ける。","en":"Separate a temperature anomaly from the cause of water stress."},"guide":{"ja":"熱い場所を見つけても、すぐ水を増やすとは決めんのよ。","en":"A warm patch does not automatically mean more irrigation."},"sections":[{"title":{"ja":"画像は仮説をつくる","en":"Use imagery to form a hypothesis"},"body":{"ja":"設計提案として、熱画像の候補を土壌水分、気象、灌漑履歴、生育段階と重ねる。撮影時刻や日射が違えば温度の比較は難しくなる。反射、裸地、影を作物の温度として読まないよう品質確認を設ける。","en":"Combine thermal candidates with soil moisture, weather, irrigation history and crop stage. Different capture times and sunlight complicate temperature comparison. Check reflections, bare soil and shadow before interpreting crop temperature."},"kind":"design"},{"title":{"ja":"設備の問題も点検する","en":"Inspect the water system too"},"body":{"ja":"確認候補には、ポンプ、バルブ、配管、詰まり、圧力差、排水も含める。水不足らしい場所が見えても、施肥や病害、土壌条件が関わる場合を除外しない。灌水設定を変更する前に現地観察と担当者の判断を挟む。","en":"Inspect pumps, valves, lines, blockages, pressure and drainage. Do not rule out nutrient, disease or soil causes from an image alone. Require field checks and a responsible decision before changing irrigation settings."},"kind":"design"},{"title":{"ja":"水量と収量を両方見る","en":"Track both water and production"},"body":{"ja":"評価は使用水量の削減だけで終えず、収量、品質、電力、作業時間、ばらつきを追う。節水の効果を地域外へ移す際は、降雨、土壌、作物、灌漑方式の違いを記載する。","en":"Evaluate water use together with yield, quality, energy, labor and variability. When transferring results, preserve rainfall, soil, crop and irrigation-system context."},"kind":"design"},{"title":{"ja":"複合実証の成果を、ドローンだけの成果にせん","en":"Do not assign a package's results solely to drones"},"kind":"evidence","body":{"ja":"IRRIが紹介したベトナムCan Thoの低排出稲作では、施肥・防除用ドローンと水位センサーなどを組み合わせとる。これは複数の道具を営農へ組み込む事例として読めるが、ドローン画像による灌水判断だけの効果を切り出した比較ではないんよ。本ガイドの読み取りとして、節水や収益の変化を説明するときは、水管理、肥培管理、作業方式、天候のどれが変わったかを明記する。技術一式を導入した前後の違いだけで、特定の機体や解析の因果効果まで確定したとは言わんことじゃ。","en":"IRRI's account of low-emission rice in Can Tho combines fertilizer and pesticide drones with water-level sensors and other agronomic measures. It illustrates integration, rather than a comparison isolating irrigation decisions based on drone imagery. This guide therefore proposes identifying changes in water management, nutrient management, work methods and weather when interpreting outcomes. A before-and-after difference following a technology package does not establish the causal contribution of one aircraft or analytical method."}},{"title":{"ja":"水管理と、画像情報の効果を分けて試す","en":"Test water management separately from image information"},"kind":"design","body":{"ja":"検証案は、まず「画像を使うと、同じ水管理方針でも判断がよくなるか」という問いを一つに絞るんじゃ。条件をそろえた複数区画で、画像を使う組と、普段の観測だけで判断する組を比較する。水管理方式自体も変えるなら、その変更の有無と画像利用の有無を組み合わせて、何を比較したかを残す。区画の割り当ては可能な範囲で無作為にし、土壌や高低差は記録する。ただし同じ水路・水位操作の影響を受ける隣接地点を、独立した試験区として数えんことじゃ。十分な区画を設けられない実証は「探索的な観察」と示し、一回の好結果を普及効果へ拡大せず、複数時期で確かめる。","en":"Start with a focused question: does imagery improve decisions under the same water-management policy? Compare multiple reasonably matched units using imagery against units relying on the usual observations. If the water-management method also changes, distinguish the presence or absence of that change from the use of imagery and record the comparisons. Randomize allocation where feasible and document soil and elevation differences. Adjacent observation points influenced by the same waterway or water-level operation should not be counted as independent experimental units. Label small demonstrations without sufficient comparison units as exploratory observations, and seek confirmation across periods instead of extrapolating one favorable result."}},{"title":{"ja":"判断の記録を、後から検証できる形に","en":"Keep a decision trail that can be evaluated"},"kind":"design","body":{"ja":"設計上は、画像を取得した時刻と、現地を確認した時刻、実際に灌水・排水を変えた時刻を分けて残す。変更前に「どの区域の何を改善したいか」「何を見たら戻すか」を担当者と決め、判断後に都合のよい評価項目へ差し替えんのよ。取水量や運転時間は測った範囲を明記し、面積だけでなく降雨、収量、品質、電力、巡回時間も比較する。画像処理や確認のために増えた仕事も費用へ入れる。撮影できなかった日、センサー欠測、農家が提案を採用しなかった日も記録に残し、うまく撮れた日だけを集めて有用性を説明せんことじゃ。","en":"Record image acquisition, field inspection and actual irrigation or drainage changes as separate events. Before acting, agree which condition in which area should improve and what would trigger a reversal; do not replace evaluation measures afterward with more favorable ones. State the measurement boundary for water intake or equipment runtime, and compare rainfall, yield, quality, energy and inspection time alongside area. Include the added cost of processing and checking imagery. Retain days when flights were impossible, sensors failed or the farmer declined the recommendation, rather than evaluating usefulness only on successful capture days."},"table":{"headers":{"ja":["確かめたいこと","残す記録","言い過ぎを防ぐ点"],"en":["Evaluation question","Record","Interpretation boundary"]},"rows":{"ja":[["情報が判断を変えたか","提案前後の判断と担当","画像を見ただけを改善と数えない"],["水の使い方が変わったか","測定地点・水量・降雨・操作","ポンプ時間だけで圃場水量を断定しない"],["農家の結果がよくなったか","収量・品質・費用・作業時間","節水率だけを成功条件にしない"]],"en":[["Did information change a decision?","Decision before and after, with owner","Viewing an image is not itself an improvement"],["Did water use change?","Measurement boundary, volume, rain and actions","Pump runtime alone does not establish field water volume"],["Did farm outcomes improve?","Yield, quality, cost and work time","Do not define success only by water savings"]]}}},{"title":{"ja":"追加灌水を提案しない反例も用意する","en":"Include cases where more irrigation is not the answer"},"kind":"design","body":{"ja":"画面の設計例では、「温度の高い区域」へ即座に追加灌水のボタンを出さず、確認すべき仮説を短く並べる。配管や圧力の異常なら設備確認へ、排水や根の状態が気になるなら営農担当へ回し、原因未確定のまま全区画の水量を変えない流れにするんじゃ。比較用の写真や地上測定が古い場合は、判定を強くするのでなく保留へ戻す。農家には色の説明よりも「今日は何を確認するか」「誰へ連絡するか」「いつ見直すか」を渡す。担当者が不在でも自動変更に進まないよう、元の運用へ戻す条件と連絡経路を決め、提案を断った理由も改善材料にするんよ。","en":"An interface should present a short list of hypotheses for a warm area rather than immediately offering an 'add irrigation' action. Route possible pipe or pressure problems to equipment inspection, and concerns about drainage or roots to the agronomic adviser. Avoid changing water delivery across the whole field while the cause remains unresolved. Stale comparison photographs or ground measurements should weaken the decision and return it to review. Tell the farmer what to inspect today, whom to contact and when to reassess. Agree fallback conditions and a contact route so an absent decision owner does not lead to an automatic change, and retain reasons for rejected suggestions to improve the service."}}],"checklist":{"ja":["撮影条件を揃える","土壌・気象・履歴と照合","設備を現地確認","水と収量を同時評価"],"en":["Align capture conditions","Cross-check soil, weather and history","Inspect equipment on site","Evaluate water and yield together"]},"sources":[{"title":"UN Handbook — UAV applications in agricultural statistics","url":"https://fao-eostat.github.io/UN-Handbook/uav_agriculture.html"},{"title":"IRRI — Francophone Parliamentarians Explore Low-Emission Rice Farming in Vietnam","url":"https://news.irri.org/2025/02/francophone-parliamentarians-explore.html"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"adoption","category":"economics","lenses":["business","field"],"title":{"ja":"小さな農地に届く、サービスのつくり方","en":"Design services that reach small farms"},"dek":{"ja":"共同利用・受託・予約・移動を、農繁期の現実に合わせる。","en":"Fit shared access, contracting, booking and travel to the season."},"guide":{"ja":"使い方を覚える前に、頼み方で迷わせたらいけんのよ。","en":"Do not make ordering the service harder than using it."},"sections":[{"title":{"ja":"一つの依頼窓口","en":"One clear point of entry"},"body":{"ja":"提案する受付は、圃場、目的、希望時期、連絡先を必要最小限にする。農家にセンサーや解析モデルを選ばせるより、課題を聞いて事業者が適切な手段を提案する。電話や地域の窓口から来た依頼も同じ台帳に登録する。","en":"Keep intake to field, objective, timing and contact. Let providers translate the problem into a suitable technical approach instead of asking farmers to choose sensors or models. Bring phone and local-office requests into the same register."},"kind":"design"},{"title":{"ja":"小区画を束ねる条件","en":"Aggregate without hiding constraints"},"body":{"ja":"近隣の圃場をまとめるときは、作物、資材、適期、進入路、境界を揃えて確認する。単に面積を足すだけでは移動や洗浄の切替費用は減らない。天候延期時の順番と、キャンセル・再訪の費用を先に示す。","en":"Aggregation needs compatible crops, materials, timing, access and boundaries. Adding hectares does not automatically remove travel and cleaning costs. State weather-delay priority, cancellation terms and revisit charges in advance."},"kind":"design"},{"title":{"ja":"使い続けるための納品","en":"Deliver for continued use"},"body":{"ja":"報告は農家の言葉で、次に何をすればよいかまで説明する。解析だけ提供する場合は現地確認を誰が行うかを決める。翌年の予約につながるか、電話での説明時間が減るかを、利用継続の指標として追う。","en":"Explain next steps in the farmer’s language. If the service only supplies analysis, agree who performs ground checks. Track return bookings and support time as indicators of whether the service remains usable."},"kind":"design"},{"title":{"ja":"予約の入口と、実際の供給能力を分けて見る","en":"Distinguish easy booking from service capacity"},"kind":"evidence","body":{"ja":"タイのスパンブリーの農家調査では、知人の紹介や電話がサービス利用の接点として現れとる。別のIDE-JETRO調査は、受託者の電池・発電機などの費用に加え、順番待ちや修理待ちも記録しとるんよ。これらは地域と調査時点を持つ資料で、全国の普及率や現在の料金表ではない。本ガイドへの示唆は、立派な予約画面だけで供給問題は解けんということじゃ。受付件数、実行できる件数、適期内に完了した件数を分け、電話で頼む農家も同じ作業台帳につなぐ設計にする。","en":"A Suphan Buri farmer survey identifies referrals and telephone contact in service use. An IDE-JETRO study records batteries, generators, queues and repair delays. These are contextual studies, not national adoption rates or current price lists. They inform this guide's proposal to distinguish requests received, executable jobs and jobs completed within their agronomic windows, with phone requests entering the same register as online bookings."}},{"title":{"ja":"予約は、締切と地上作業を含む予定にする","en":"Schedule agronomic windows and ground work together"},"kind":"design","body":{"ja":"予約設計では、希望日をそのまま確約せず、農家と確認した作業可能期間、実施に必要な現地条件、判断の締切を別々に持つ。予定時間には現地移動、準備、補給、洗浄、片付けと報告を入れ、機体が空いていても人・水・充電場所が足りなければ追加受注しないんじゃ。天候で延期が重なったときは、作業の緊急性と適期を再確認し、先着順を黙って変えず、変更理由と見通しを農家へ返す。近所の区画をまとめる場合も、違う資材や作物で切替時間が増えるなら別便にする。急ぎの枠を確保する費用は誰が負担するかも明示して、平常日の稼働率だけを最大化せんことじゃ。","en":"Keep a requested date separate from a confirmed agronomic window, site prerequisites and the deadline for a decision. Schedule travel, setup, replenishment, cleaning, packing and reporting. Spare aircraft capacity is insufficient if staff, water or charging capacity are unavailable. After weather delays, review urgency and treatment windows, and explain changes rather than silently replacing an agreed queue. Nearby fields may still need separate visits when different crops or materials increase switching work. State who pays for reserved contingency capacity instead of maximizing utilization only on normal-weather days."}},{"title":{"ja":"安い面積単価でも、続かない受託を見抜く","en":"Identify services that cannot sustain a low hectare price"},"kind":"design","body":{"ja":"採算の設計例では、訪問ごとの売上から、移動・現地要員・資材取扱い・エネルギー・変動整備費を引いた残りをまず見る。その残りで年間の固定費や休業期間を支えられるかを、繁忙期と閑散期に分けて確かめるんよ。たとえば受注面積が同じでも、一か所にまとまる仕事と、遠く離れた小区画を何度も訪れる仕事では残る金額が違う。共同所有も無料にはならん。予約調整、点検、故障時の代替、担当者の手当を誰が担うかが曖昧なら、受託サービスを使う方が合理的な場合もある。反対に、急な需要が多く外部業者の待ちが長い農場では、自前の余裕を持つ価値も比較する。購入を結論に置かず、作業を適期に終える費用を比べるんじゃ。","en":"First examine revenue per visit after travel, field staffing, material handling, energy and variable maintenance costs. Then test whether the remaining contribution can support annual fixed costs and inactive periods, separately considering peak and quiet seasons. The same booked area can produce different margins when it is concentrated at one location or scattered across repeated distant visits. Shared ownership also requires paid coordination, inspection, backup arrangements and accountable staff. Contracting may be preferable when those responsibilities are unclear. Conversely, farms facing frequent urgent demand and long external queues may value spare internal capacity. Compare the cost of timely completion without making equipment purchase the predetermined answer."}},{"title":{"ja":"農家の理解と、断る理由まで確かめる","en":"Test understanding and learn from refusal"},"kind":"design","body":{"ja":"導入試験は、操作できた人数だけで終えん設計にする。初めて使う農家に、区画を選ぶ、料金に含まれる範囲を説明する、延期の連絡を見つける、結果から次の行動を話す、という短い課題を試してもらうんじゃ。つまずいた点は農家の能力不足と決めず、地域の呼び名、文字、通信、電話対応の流れを直す。利用継続を見るときも、再予約率だけでなく適期内完了、問い合わせのやり直し、苦情、再作業と、その理由を記録する。予約しなかった人や、途中でやめた人の声も聞く。補助や無料実演で集まった利用を、そのまま通常料金での需要と数えず、支払条件を明らかにして評価するんよ。","en":"Do not end an adoption trial by counting people who operated the interface. Ask first-time farmers to identify their field, explain what the price includes, find a postponement message and describe the next action after delivery. Treat difficulty as evidence for improving local field names, language, connectivity and phone support rather than automatically blaming ability. Alongside repeat bookings, record timely completion, repeated support contacts, complaints, rework and their causes. Include people who declined or stopped using the service. Demand generated through subsidies or free demonstrations should not be treated as willingness to purchase at normal prices; make payment conditions explicit."},"table":{"headers":{"ja":["観察する課題","使える状態の目安","失敗時に直す場所"],"en":["Observed task","Practical acceptance criterion","Where to improve"]},"rows":{"ja":[["自分の圃場を指定","担当者と同じ区画を指せる","区画名・地図・電話受付"],["依頼条件を確認","含む作業と追加費用を説明できる","見積りと説明"],["延期・結果を受け取る","次の担当と行動を言える","通知・納品・問い合わせ窓口"]],"en":[["Identify the field","Farmer and provider indicate the same plot","Field naming, maps and phone intake"],["Check service terms","Farmer can explain included work and extra charges","Quotation and explanation"],["Receive a delay or result","Farmer can name the next owner and action","Notifications, handover and support"]]}}}],"checklist":{"ja":["依頼フォームを短く","小区画の切替費用を見える化","延期と再訪の条件を提示","納品後の行動まで支援"],"en":["Keep intake short","Show switching costs","Explain delay and revisit terms","Support action after delivery"]},"sources":[{"title":"FAO AgriTech Observer #2 — Drones for smallholders","url":"https://www.fao.org/digital-villages-initiative/europe/news-and-articles/news-and-articles-detail/agritech-observer--2--drones-for-smallholders---six-lessons-on-what-works-in-practice/"},{"title":"Arts of Management Journal — Factors Influencing the Adoption of Drone Services for Rice Farming in Suphan Buri Province","url":"https://so02.tci-thaijo.org/index.php/jam/article/view/274034"},{"title":"IDE-JETRO — Effectiveness Analysis of Drone Use for Rice Production in Central Thailand","url":"https://www.ide.go.jp/library/English/Publish/Reports/Brc/pdf/27_05.pdf"}],"updated":"2026-10-30","readingMinutes":5},{"slug":"evidence","category":"foundations","lenses":["field","business","platform"],"title":{"ja":"このガイドの読み方と調査方針","en":"How to read this guide and its evidence"},"dek":{"ja":"事実、設計提案、仮定、未確認を分けて公開する。","en":"Separate verified statements, design proposals, assumptions and gaps."},"guide":{"ja":"親しみやすく話すけど、根拠をごまかすつもりはないけえね。","en":"A friendly guide still needs accountable evidence."},"sections":[{"title":{"ja":"30カ国×30件の意味","en":"What the 30 × 30 target means"},"body":{"ja":"各国30件、計900件の関連資料を調べる計画じゃ。「国内で最も読まれた30記事」を証明する共通の公開データは、今回の調査では確認できていない。検索順位や当サイトの並び順を閲覧順位と呼ばない。調査済み件数と不足を国別に表示する。","en":"The research target is 30 sources in each of 30 countries, or 900 records. We have not established a common public dataset proving each country’s 30 most-read articles. Search position and display order are not readership rankings. Country pages report reviewed counts and gaps."},"kind":"design"},{"title":{"ja":"読んだ資料と、候補を分ける","en":"Separate reading from discovery"},"body":{"ja":"本文・関連箇所・公開要旨を確認できた資料を「資料確認」、検索結果や書誌情報だけの段階を「検索候補」、取得できなかったものを「本文未取得」とする。確認した範囲も併記し、全文を精読したものとは区別する。読めても性能や政策効果を独立に実証したことにはならん。公開日が分からなければ推測で埋めない。","en":"Reviewed records include retrieved article content, relevant passages or public abstracts, with the scope stated. Search or bibliographic information alone remains a candidate; inaccessible material is unavailable. This is not a claim that every underlying paper was read in full. Reading does not independently validate performance or policy effects. Unknown publication dates remain unknown."},"kind":"design"},{"title":{"ja":"一次資料の立場も読む","en":"Read the source’s perspective"},"body":{"ja":"政府の制度、大学の試験、メーカーの製品紹介はそれぞれ立場が違う。試験の地域、作物、年、比較条件を残す。設計提案の章はAirffic独自の整理であり、実機の性能保証や運航承認ではない。","en":"Authorities, university trials and manufacturer descriptions have different roles. Preserve place, crop, year and comparison conditions. Design proposals are Airffic’s own synthesis, not equipment guarantees or operating approvals."},"kind":"design"},{"title":{"ja":"更新と翻訳","en":"Updates and language"},"body":{"ja":"本文は日本語と英語で提供する。Sir Airffic Goの日本語の案内は軽い広島弁にし、専門語・数値・条件を崩さない。原資料は各国語のまま参照できる。更新日と出典を残し、制度変更時は過去と現在を分けて修正する。","en":"Editorial content is available in Japanese and English. Sir Airffic Go uses light Hiroshima dialect in Japanese while preserving technical meaning. Original sources remain available in their languages. Retain update dates and distinguish historical rules from current changes."},"kind":"design"},{"title":{"ja":"今回の調査で、どこまで確かめたか","en":"What this research release actually checked"},"kind":"design","body":{"ja":"2026年10月30日時点で、30カ国・地域から各30件、計900件の重複しないURLを収集した。853件は本文・要旨・関連箇所を確認し、44件は検索候補、3件は本文未取得として残している。確認済みのうち244件は取得本文を読んだ記録があるが、精読範囲の細かな記録がないため、その限界を記した。900件には記事だけでなく制度資料、研究要旨、マニュアル、データ基盤の背景資料も含む。閲覧順位、全文精読、独立した効果検証は別の条件じゃ。数字をそろえることと、根拠がそろうことを混同せんようにしよう。","en":"As of 30 October 2026, this release contains 30 records for each of 30 countries or regions: 900 distinct URLs. It includes 853 reviewed records, 44 search candidates and three unavailable sources. Review may cover text, abstracts or relevant passages. For 244 reviewed records, retrieved text was inspected but the precise extent was not recorded; that limitation is explicit. The collection includes guidance, abstracts, manuals and data-platform context as well as articles. Readership ranking, full-text inspection and independent efficacy evidence are separate requirements."}}],"checklist":{"ja":["確認状況を読む","出典の立場を確認","地域と条件を照合","提案と実装を区別"],"en":["Check review status","Assess source perspective","Match region and conditions","Distinguish proposals from implementation"]},"sources":[{"title":"UN Handbook — UAV applications in agricultural statistics","url":"https://fao-eostat.github.io/UN-Handbook/uav_agriculture.html"},{"title":"OGC — SpatioTemporal Asset Catalog Community Standard 1.1","url":"https://docs.ogc.org/cs/25-004/25-004.html"}],"updated":"2026-10-30","readingMinutes":3}]