Basic area analysis, PDF
Let us set up your workspace
This takes less than a minute. We will save your selected area and show the tools relevant to your needs.
1. How will you use the platform?
Large companies and public institutions arrange separate institutional access.
2. What would you like to do?
Select one or more tasks. You can change the modules in your workspace later.
3. Area of interest
Keep the area selected on the map, enter coordinates, search for a location, upload a boundary or draw a polygon. Supported formats: GeoJSON/JSON and KML boundaries, CSV coordinate tables and TXT text files.
4. Create an account
One shared workspace. Specialist modules can be added separately without registering again.
We will save your actual account and selected area, without demonstration or placeholder data.
Check an area
Specify your area and contact details. The map stays in the background; the report is calculated for your selected boundary.
Upload a GeoJSON/JSON Polygon or select “Draw polygon” and click on the map.
The price is fixed when the order is created. Payment is confirmed only by the provider’s server notification.
From a public map to an evidence-based report
Detailed indicators, scenarios and exports are available after payment or under contract.
Ongoing portfolio monitoring
Data exchange, team roles and service terms
Area-specific findings are generated only after calculation using available data layers and include the data date, limitations and evidence level. Synthetic answers and non-production events are not published.
The public map shows a 0.25° overview surface aggregated from H3 resolution 7. It is not exact H3 detail; parcel-level conclusions are available only in a report with sources and limitations.
A report for a specific decision
Choose the depth of analysis. Before payment, we confirm the area, deliverables, available sources and delivery time. Every report states its data date, limitations and clear next steps.
Basic report
For a rapid assessment of one area using available data.
- area map and profile;
- history of available indicators;
- observed risk signals;
- sources, limitations and recommended next steps.
Forest asset review
For a management decision, transaction, insurance review or project due diligence.
- everything in the basic report;
- extended analysis of risks and trends;
- analyst review;
- a list of missing data and a plan to resolve the gaps.
Scenario assessment
For comparing area-management options under an agreed brief.
- baseline and business-as-usual scenarios;
- intervention and monitoring options;
- ranges of assumptions and risks;
- review points and conditions for revisiting the decision.
Check an area and receive a report
Выберите участок на карте, введите координаты или нарисуйте полигон. Бесплатная сводка показывает агрегированные показатели; полный анализ, сценарии и рекомендации включаются в PDF после оплаты.
1. Area
If no area is selected, clicking the map fills in the coordinates. The free summary is limited to 10 000 ha. Area reports use detailed L1/L2 analysis, not just H3 resolution 7.
2. Report type
A basic report is emailed within 3–5 business days after payment and receipt of sufficient data. Delivery dates for other reports are agreed before payment.
Sign in to Forest OS
Individual customers receive a shared workspace after selecting an area and completing a short registration. Institutional access is provided under contract only.
Already have an account
Use your email and password. The system opens the individual or institutional workspace according to your verified access rights.
Large organisation
Corporate or institutional workspaces are created separately after agreeing the territory, modules, access rights and data sources.
Request institutional accessForest Os Global / Solutions for forest territories
From understanding forests —
to a plan of action.
Analytics, restoration and forest asset management. Choose a task and we will define the scope, data requirements and deliverables for your team.
A specific task.
A clear deliverable.
From a consultation on an existing report to a territory management strategy. Every package specifies the deliverables, analytical scope and delivery terms.
Loading current packages and prices…
From analysis
to implementation.
Field services and supplies are quoted individually. Availability, region and specialist provider are confirmed before contracting; there is no single rate for every territory.
Loading field services…
Special programmes
For tasks requiring a dedicated methodology, training programme or external specialists.
Your task first. Then a proposal.
Area and objective
Choose a service and specify the region, approximate area and the outcome your team needs.
Data, scope and price
We check data sufficiency and agree the providers, schedule and deliverables. Where necessary, we propose a preliminary survey.
Results with explanations
We deliver the agreed materials with sources, limitations and next steps. Fieldwork follows a separate agreed estimate.
Discuss your project?
Leave your contact details and a short description. We will clarify the input data and prepare a proposal.
Submitting an enquiry does not create an obligation to pay. Work begins after the terms are agreed.
Contact Forest OS ↗How does an analytics package differ from official project documentation?
Analytics packages help assess data and inform management decisions. They do not replace mandatory surveys, official project documentation, independent validation or certification. Model estimates and scenarios include limitations; the readiness of a particular method is checked when agreeing the brief.
What if my territory exceeds 1 000 ha?
Include the area and task in your enquiry. We will prepare a separate quote for large territories, portfolios, additional data sources or integrations. Prices do not increase automatically at a single per-hectare rate.
Are one-off reports and subscriptions included in service prices?
No, unless the proposal explicitly includes them. Services on this page cover project work and support. Terms for standalone reports and platform access are available under “Pricing”.
Your scale.
Your workspace.
One-off area analysis, regular monitoring or forest estate management. Choose your format and compare capabilities, area limits and pricing.
From a single area
to a forest portfolio.
Your plan sets the access limits: area, sites, number of reports and tools. Module availability and applicability are confirmed before contracting.
Personal
- Up to 500 ha / up to 3 areas
- Monthly monitoring and alerts
- 2 basic reports per year
Land Pro
- Up to 5 000 ha / up to 10 areas
- More frequent alerts under the agreed schedule
- Browser app, documents and 6 reports per year
Team
- Up to 50 000 ha / 10 users
- Basic forest inventory estimates, reporting and data export
- Notifications and 12 reports per year
Portfolio
- Up to 250 000 ha / 30 reports per year
- Scenarios and limited data exchange
- Organisation-wide single sign-on quoted separately
Enterprise
Agreed service levels, single sign-on, data exchange and dedicated support. Area, usage rights and modules are specified in the contract.
Annual contract. Additional large-portfolio rate: 1.74–4.35 ₽/ha
Initial recommendation based on area and number of sites.
What your subscription includes
Limits not specified in the base package are agreed during onboarding. On small screens, scroll the table horizontally.
| Capabilities | Personal | Land Pro | Team | Portfolio | Enterprise |
|---|---|---|---|---|---|
| Portfolio area, ha | Up to 500 | Up to 5 000 | Up to 50 000 | Up to 250 000 | Under contract |
| Number of areas | 3 | 10 | Under contract | Under contract | Under contract |
| Team | As agreed during onboarding | As agreed during onboarding | 10 users | Under contract | Under contract |
| Reports per year | 2 | 6 | 12 | 30 | Under contract |
| Monitoring frequency | Monthly | Higher frequency under an agreed schedule | Under the project schedule | Under the project schedule | Custom service schedule |
| Oracle option | Client access — subject to plan terms | Client access — subject to plan terms | Client access — subject to plan terms | Client access — subject to plan terms | Access level and capabilities — as agreed |
| Scenarios | Not included | Not included | Separate package | As specified | As agreed in the brief |
| Export | Included in reports | Reports and documents | Included as specified | Included as specified | Under contract |
| Data exchange with other systems | Not included | Not included | Separate package | Agreed datasets for external systems | Extended data exchange — separate module |
| Employee single sign-on | Not included | Not included | Under a separate brief | Optional | Under contract |
| Service and support | As agreed during onboarding | As agreed during onboarding | As agreed during onboarding | As agreed during onboarding | Custom service schedule / dedicated specialist |
The site is a separate area of analysis. The personal rate includes 2 basic reports per year. The composition of reports and the rules for using the annual limit are fixed when you connect. Subscription does not mean unlimited calculations, uploads or analyst work.
A report for a specific decision
The range takes into account the composition of raw data and analytical work. First, agree on the boundaries, applicability of methods, materials and final cost.
Basic area analysis
- Observation history and trends in key indices
- Condition, anomalies, fire history and moisture stress
- Area map, sources and limitations
Format, delivery time and larger areas
Print-ready document (PDF), area map (GeoJSON); tables (CSV/XLSX) if required
3–5 business days after sufficient data are received
Above the base area: a landmark of 4.35–8.70 ₽ /ha on an agreed scale. The final price depends on the data and amount of work of the analyst.
Forest asset review
- Everything in the basic report plus analyst input
- Model-based forest inventory estimates where accuracy is sufficient
- Review of risks and supporting evidence; comparison of available documents
Format, delivery time and larger areas
Analytical report and agreed exports
Schedule agreed after data review and approval of the brief
Above the base area: a landmark of 6.96–13.05 ₽ /ha on an agreed scale. The final price depends on the data and amount of work of the analyst.
Scenario assessment
- Four scenarios: baseline, stress, restoration and forest use
- Ranges for project net present value, revenue and costs
- Action plan and limitations of model-based findings
Format, delivery time and larger areas
Assessment, scenario comparison and intervention-zone map
Schedule and scenario applicability defined in the brief
Above the base area: a landmark of 13.05–26.10 ₽ /ha on an agreed scale. The final price depends on the data and amount of work of the analyst.
Operations centre
for your territory.
We will calculate the license, implementation and support for the tasks of the region. Before the contract, we fix the composition of modules, boundaries of responsibility, readiness of integrations and measurable terms of service.
Region: Core
- Operational map, priority zones and event register
- Roles, checks, reporting and exports
- Preparation for federal information system integration, subject to authorised access
- Business-hours support under the contract
Region: Extended
- Everything in the core regional package plus extended assessments
- Forest inventory, restoration and data exchange as specified
- Oracle recommendations and probabilistic hypotheses reviewed by a specialist
- Sensor integration and seasonal 24/7 support under contract
Paid pilot
The territory, deadline and criteria for the result are agreed in advance. Check the work on your task, then decide on a one-year contract.
of the annual price
50–100% of the pilot fee credited towards the annual contract, subject to agreed terms.Complex hardware integrations, cameras, exits and equipment - on a separate task. The composition of the expanded regional package and the calculations available for the territory are confirmed before connection.
Oracle: from explanation
to informed decisions.
Oracle helps interpret Forest Os Global data, compare evidence and explore courses of action. Its access level determines which data and tools it can use.
Public access
- Explanations of forest condition indicators
- Overview of published map data
- Sources and limitations
Open explanations on the public map
Open the public map ↗Client access
- Answers about your areas and observation history
- Explanations of risks, reports and available scenarios
- Work with client portfolios and materials
An option for individual or corporate workspaces
Operational access
- Review events and the evidence behind decisions
- Compare available documents and observations
- Decision log and action approval controls
Project-based onboarding for organisations
Strategic access
- Development scenarios for territories and forest assets
- Compare economic assumptions and risks
- Alternatives, limitations and testable hypotheses
Custom configuration based on your brief
| Capabilities | Public access | Client access | Operational access | Strategic access |
|---|---|---|---|---|
| Data | Public indicators and the general map | Only authorised client areas and documents | Agreed organisational data and documents | Isolated customer data and assumptions |
| Analysis | Explanations of indicators and their limitations | Observation history, changes and report explanations | Data quality checks and event comparison | Compare risks, objectives and economic assumptions |
| Scenarios | Not included | Available operational scenarios relevant to the task | Compare courses of action under the agreed brief | Long-term portfolio development scenarios |
| Workflow | Browse and ask about published data | Work with areas, reports and field observations | Decision log, specialist review and approval | Compare alternatives and supporting evidence |
| Access | Open explanations on the public map | An option for individual or corporate workspaces | Project-based onboarding for organisations | Custom configuration based on your brief |
What determines the option’s terms
- Selected access level and tasks
- Area and number of sites
- Number of users and calculation volume
- Connected sources, systems and support level
What we agree before onboarding
Sites, sources, available functions, number of users, settlement limits and maintenance procedure. Extended loops connect in a consistent configuration for the organization and do not allow access to other customers’ data or internal management of the platform.
Observations and scenarios differ. Conclusions are accompanied by sources and limitations; significant actions are confirmed by a specialist. Available settlements for your territory are checked before the contract.
API
with other systems
Annual agreement, agreed limits and separate payment of excess by area, calculations or forecast units. Derivative results are licensed.
Developer
- Sandbox
- Derived indices and low-risk features
- Quotas agreed during onboarding
For services and applications
- Higher throughput
- Automatic event notifications and available forecasting methods
- Limited commercial use
Enterprise data exchange
- Agreed service levels, batch calculations and dedicated quotas
- Private endpoints for an approved client
- Redistribution rights defined in the contract
In the tariffs "Personal" and "Land User" program data exchange is not included. The Portfolio tariff provides limited results for external systems; extended access is agreed separately. Raw unloading of the whole cube and internal models are not included in these tariffs.
Modules for your task
They are connected separately or included in a harmonized corporate specification. The same module is not charged twice if it is already included in the contract.
Fire safety
Priorities of territories, readiness and work with events. Composition of operational methods - after verification of applicability.
Additional rate: 1.74–6.96 ₽/ha per year.
Forest inventory and verification
Inventory estimates and monitoring. Detailed analysis is charged separately; field validation is not included.
Detailed analysis: 8.70–34.80 ₽/ha.
Forest restoration
Project and subsequent monitoring. Connection after checking the readiness of the module and agreeing on the field circuit.
Onboarding: 8.70–34.80 ₽/ha, one-off.
Forest risk analytics for insurance
Analysis of Portfolio Risk, Events and Implications for Insurance Teams It is not a substitute for an insurance decision.
Insurance pilot: on request.
Let us build your
workspace.
Specify the selected package and territory. We will prepare a proposal with the final cost, composition of the result and connection conditions.
An enquiry does not charge you or create a paid subscription.
Important terms
Aligning cost, expectations and results.
What is charged separately?
Commercial satellite imagery, ground surveys, laboratory work, equipment, complex integrations, travel and exceeding agreed quotas. These positions are highlighted in the proposal before work begins.
Can I pay monthly?
Tariffs “Personal”, “Land User”, “Team”, “Portfolio”, “Corporate” and data exchange packages are designed for a year. Schedule of payments, transfer between packages and revision of limits are agreed in the contract. There is no automatic monthly write-off on this page.
How do I change plans?
You report a new area, number of territories or module requirements. We will agree on new limits, date of transition and cost calculation. Access rights change after the terms and conditions are issued, not just when choosing a card.
Does Oracle make decisions on its own?
No. Oracle helps analyse data and possible decisions. Findings include sources and limitations, and significant actions require specialist approval. Event-cause classification remains a probabilistic hypothesis.
What determines the price and custom quote?
It depends on the area, refresh rate, data, volume of analytical work, level of service, connections and rights of use. Prior to the contract, these parameters and the total amount are fixed. The tax conditions are set out in the proposal.
Institutional access
Для крупных лесных портфелей, банков, страховых, государственных и научных команд: согласованный доступ к данным, API, роли, уровень обслуживания и настройка отчётов под задачи.
Enquiry
Your enquiry will be sent to the service provider. Scope, price and a delivery period of up to 30 calendar days are agreed in the specification or contract before payment.
What is included
Forest territory data.
A clear API.
Documentation for developers and integrators: available endpoints, parameters, responses, limits and pricing. From your first request to an agreed data integration.
API documentation 2.1.1 · 03 September 2026 · Validation statuses have their own dates
Get a time series by coordinates
The application programming interface (API) delivers Forest Os Global data to your system. The six available public read endpoints below require neither registration nor an API key. Private client endpoints, internal website requests and payments are outside this specification.
https://forestosglobal.comcurl --get "https://forestosglobal.com/api/public/h3-at-point" \
--header "Accept: application/json" \
--data-urlencode "lat=55.75" \
--data-urlencode "lon=37.62" \
--data-urlencode "var=ndvi" \
--data-urlencode "start=2026-06" \
--data-urlencode "end=2026-07"The line continuations above are for Bash. For PowerShell, use the single-line command below. Coordinates are latitude lat and longitude lon in WGS 84 degrees. Dates are explicit and both ends of the period are included. Start with one indicator and a short period.
Windows PowerShell · single-line command
curl.exe --header "Accept: application/json" "https://forestosglobal.com/api/public/h3-at-point?lat=55.75&lon=37.62&var=ndvi&start=2026-06&end=2026-07"What to request and what to send
/api/public/h3-at-pointTime series by coordinatesGET/api/public/h3-cellTime series by cell identifierGET/api/public/summaryOverview and indicator registryGET/api/public/validationDated validation snapshotGET/api/public/tariff-catalogPlan and option catalogueGET/api/public/pricing-settingsPrice labels for interfacesParameters are passed in the query string after ?. A GET request body is not required. Values of var are case-sensitive; use the names below without spaces. These endpoints do not support pagination or multi-cell selection.
/api/public/h3-at-pointTime series by coordinates
Resolves the coordinates to an H3 resolution 7 cell, then returns its monthly values. The result applies to the whole cell, not an individual tree or pixel.
| Parameter | Type / required | Rule | Example |
|---|---|---|---|
| lat | number / yes | WGS 84 latitude in decimal degrees, using a decimal point. | 55.75 |
| lon | number / yes | WGS 84 longitude in decimal degrees. Do not swap lat and lon. | 37.62 |
| var | array / no | Lowercase names, comma-separated, without spaces. If omitted, all currently allowed indicators are returned; explicit selection is recommended. Maximum 20 names; duplicates are unnecessary. Check availability at summary.spectral_indices.indices.<name>.public_ready. | ndvi,evi |
| start | string / no | First month, inclusive. Defaults to 11 months before end. The start must not follow the end; the maximum period is 12 calendar months, inclusive. Explicit dates are recommended. | 2026-06 |
| end | string / no | Last month, inclusive. Defaults to the server’s current UTC month, not the latest month with data. Explicit dates are recommended. | 2026-07 |
https://forestosglobal.com/api/public/h3-at-point?lat=55.75&lon=37.62&var=ndvi&start=2026-06&end=2026-07/api/public/h3-cellTime series by cell identifier
The same value format, without query_point. Use this if you already have the H3 identifier. One cell and up to 12 months per request; this endpoint does not support multiple cells or full-cube exports.
| Parameter | Type / required | Rule | Example |
|---|---|---|---|
| h3 | string / yes | One H3 resolution 7 cell present in the land cube. Use a lowercase hexadecimal identifier. The cell parameter remains a legacy alias; use h3. | 8711aa7aaffffff |
| var | array / no | Lowercase names, comma-separated, without spaces. If omitted, all currently allowed indicators are returned; explicit selection is recommended. Maximum 20 names; duplicates are unnecessary. Check availability at summary.spectral_indices.indices.<name>.public_ready. | ndvi,evi |
| start | string / no | First month, inclusive. Defaults to 11 months before end. The start must not follow the end; the maximum period is 12 calendar months, inclusive. Explicit dates are recommended. | 2026-06 |
| end | string / no | Last month, inclusive. Defaults to the server’s current UTC month, not the latest month with data. Explicit dates are recommended. | 2026-07 |
https://forestosglobal.com/api/public/h3-cell?h3=8711aa7aaffffff&var=ndvi&start=2026-06&end=2026-07/api/public/summaryOverview and indicator registry
Returns the platform overview and index availability. generated_at is the summary generation time, not the latest observation date. Select var using public_ready, not the total number of registered indices.
| Parameter | Type / required | Rule | Example |
|---|---|---|---|
| If-None-Match | string / no | ETag from a previous response at the same URL. If it matches, the server returns 304 without a body. Supported by summary and validation. | W/"etag-from-previous-response" |
https://forestosglobal.com/api/public/summary/api/public/validationDated validation snapshot
Aggregated validation results and limitations. HTTP 200 may contain ok=false when no snapshot is available. stale means the information is outdated; date_unconfirmed means the date is unverified. The number of checks is not a model accuracy percentage.
| Parameter | Type / required | Rule | Example |
|---|---|---|---|
| If-None-Match | string / no | ETag from a previous response at the same URL. If it matches, the server returns 304 without a body. Supported by summary and validation. | W/"etag-from-previous-response" |
https://forestosglobal.com/api/public/validation/api/public/tariff-catalogPlan and option catalogue
Public packages in rubles, including api and oracle_option. price_mode=quote indicates a custom quote: no numeric price is supplied. This catalogue does not create orders, charge payments or grant access rights.
No parameters required.
https://forestosglobal.com/api/public/tariff-catalog/api/public/pricing-settingsPrice labels for interfaces
A compatibility dictionary of price labels. Use tariff-catalog to select a package. If a key is in quote_required_keys, settings[key]=null: display labels[key], not a zero price.
No parameters required.
https://forestosglobal.com/api/public/pricing-settingsMonth first. Cell second.
Axis order matters: variables[name][month index][cell index]. The outer array corresponds to months; the inner array corresponds to h3. A public response contains one cell, so its index is always 0. The example below comes from a public endpoint; it illustrates the response format, not a forest condition benchmark.
{
"ok": true,
"h3": [
"8711aa7aaffffff"
],
"months": [
"2026-06",
"2026-07"
],
"variables": {
"ndvi": [
[
0.2637999951839447
],
[
0.19259999692440033
]
]
},
"encodings": {
"ndvi": {
"dtype": "int16",
"fill_value": -32768,
"scale": 0.0001,
"offset": 0.0,
"units": "1"
}
},
"encoded": false,
"resolution": "H3 r7",
"public_policy": "one_cell_max_12_months_no_raw_imagery",
"query_point": {
"lat": 55.75,
"lon": 37.62
}
}| Field | Meaning and handling |
|---|---|
| ok | Application-level success. Check this after the HTTP status. |
| h3[] | Cell IDs; there is exactly one in this contract. |
| months[] | Actual selected months in ascending order. Do not reconstruct months from your request. A period outside the available time axis may return 503 rather than a successful empty response. |
| variables.<name>[][] | A number or null. July NDVI in the example is variables.ndvi[1][0]. JSON field order does not determine time order. |
| encodings.<name> | dtype, fill_value, scale and offset describe the source encoding; units describes the returned units. |
| encoded | false: values have already been decoded into physical units. Do not multiply by scale again. |
| resolution / public_policy | Spatial resolution and public-response limitations. |
| query_point | The original lat/lon, present only in h3-at-point. These are not the cell-centre coordinates. |
Nine indices and four additional layers
| Name for the var parameter | Indicator | Units | How to interpret |
|---|---|---|---|
| ndvi | Vegetation index (NDVI) | Dimensionless | Greenness and vegetation activity. |
| evi | Enhanced Vegetation Index (EVI) | Dimensionless | An additional measure of vegetation condition. |
| nbr | Normalised Burn Ratio (NBR) | Dimensionless | Spectral response sensitive to vegetation cover condition and burning. |
| dnbr | Change in Normalised Burn Ratio (dNBR) | Dimensionless | In the global series: previous-month NBR minus current-month NBR. This does not prove that a fire occurred. |
| ndwi | Normalised Difference Water Index (NDWI) | Dimensionless | Spectral indicator of open water and moist surfaces. |
| ndmi | Normalised Difference Moisture Index (NDMI) | Dimensionless | A spectral measure of vegetation moisture. |
| lai | Leaf Area Index (LAI) | m²/m² | Leaf area per unit of ground area. |
| fapar | Fraction of absorbed light (fAPAR) | Dimensionless | Fraction of absorbed photosynthetically active radiation. |
| sipi | Structure Insensitive Pigment Index (SIPI) | Dimensionless | Pigment spectral index; not a diagnosis of tree condition. |
| lst_day | Surface temperature | Kelvins (K) | Daytime land surface temperature in kelvins, not air temperature. °C = K − 273.15. |
| soil_moisture | Soil moisture | m³/m³ | Volumetric soil moisture as defined by the source product; not a percentage unless converted. |
| disturbance | Land-cover disturbance | Bit flags | A bitmask, not a probability. Do not interpret bits without the agreed layer dictionary. |
| burn_date | Burn history | Day of year | Day of year from the historical product. Not a real-time alert; null does not mean no fire. |
units=1 means dimensionless. Do not transfer thresholds between indicators or territories without validation. Ranges and descriptions are available in spectral_indices.indices within the summary response. A layer’s presence in the cube does not guarantee an observation for every cell and month.
CCI and BAIS2 are used for detailed area analysis and are not included in this global public series. They may appear in the registry with public_ready=false. History and availability depend on the source; 319 months on the shared axis do not mean 319 measurements for every indicator.
Reading summaries and prices
| Endpoint / field | Content |
|---|---|
| summary · cube | Size and state of the overall data environment. READY and readiness percentages do not establish the accuracy of every value. |
| summary · spectral_indices | Version, groups, index specifications and availability flags. Querying an index requires public_ready=true. |
| summary · policy / map / l1_detail | Public-read limits, map overview and detail-level information. |
| summary · benchmark / external / heavy_layers | Additional technical context. Do not use it as stand-alone evidence of accuracy or an event. |
| summary · pricing_labels / pricing / payment | Interface reference information. Use tariff-catalog.api to select a data-exchange package. |
| validation · updated_at / snapshot_state | Source snapshot date and freshness: published, stale or date_unconfirmed. |
| validation · summary / components[] | Component counters and cards: id, name, status, decision, scope, limitation, checks_total, checks_passed, warnings, failures, blocked. |
| validation · controls / limitations / evidence_levels | What is checked, the applicable limitations and the different evidence levels. |
| validation · external_reference_* / disclosure_policy | Sources and disclosure boundaries; not a list of organisations that certified the platform. |
| tariff-catalog · version / currency / api[] | Catalogue version, RUB and API packages. Each package contains id, name, features and price_mode; published prices include min and sometimes max. |
| tariff-catalog · oracle_option | Oracle is an option within the main contract. Capabilities and pricing depend on the access level and agreed configuration. |
| tariff-catalog · portal / reports / institutional / modules | Other product groups do not automatically include API access. fx documents the conversion basis, not the current exchange rate. |
| pricing-settings · labels / quote_required_keys | Ready-to-display price labels and custom-quote keys. settings=null for a price does not mean free access. |
Component status codes retain their machine-readable spelling. validated: checks passed within the stated scope; limited_operational_use: limited use; research_only: research use; model_estimate_only: model estimates; draft_scenarios_only: preliminary scenarios; not_approved_for_production: not approved for operational use; validation_failed: validation failed; not_started: no confirmed status. A missing counter must not be treated as zero.
Additional fields may be introduced. Clients should ignore unknown fields, verify required value types and not treat operational summaries as an immutable measurement contract. Exact schemas for the main responses are provided in the OpenAPI file.
Errors, limits and retries
| HTTP / code | Meaning | Action |
|---|---|---|
| 200 / ok=true | Read operation completed | Check actual months, null values, dates and fitness for use. |
| 200 / ok=false | No validation snapshot available | Show that the snapshot is unavailable; do not claim that checks passed. |
| 304 | Snapshot unchanged under If-None-Match | Use the cached response body; 304 has no body. |
| 400 / invalid_coordinates | Coordinates missing, non-numeric or out of range | Check lat in −90 to 90 and lon in −180 to 180. |
| 400 / invalid_h3_r7 | Invalid identifier syntax | Supply one valid H3 resolution 7 identifier. |
| 400 / unsupported_public_variables | Unknown, private or too many indicators | Check var and public_ready. Do not request CCI/BAIS2 through this endpoint. |
| 400 / invalid_month | The date is not in YYYY-MM format or falls outside the supported range | Correct the calendar year and month. |
| 400 / invalid_month_range | The start of the period is later than the end | Swap the period boundaries or choose a new range. |
| 400 / public_range_exceeds_12_months | Period exceeds 12 months inclusive | Shorten the period; arrange commercial access for larger volumes. |
| 404 / not_available | Indicator excluded from public access | Change the selected indicators; retrying unchanged will not help. |
| 404 / not_found | Unknown route | Check the base URL and exact path spelling. |
| 503 / cube_read_unavailable | Source could not be read; a missing cell or period in the cube may produce the same result | Check parameters and coverage. Use bounded retries for temporary failures. |
| 503 / h3_lookup_unavailable | Cell lookup temporarily unavailable | Do not replace the response with zero; retry later or contact support. |
| Other 4xx / 5xx | Application, security or gateway error | Check HTTP and Content-Type first; the body is not necessarily JSON. |
{"ok":false,"error":"invalid_coordinates"}1 cell · up to 12 months
Up to 20 names in var; the currently available list is smaller. There is no public bulk export of the entire cube. Request-size limits are not requests-per-second quotas.
Agree limits before integration
Public access does not promise unlimited request rates, response times or service levels. For commercial projects, we agree frequency, concurrency, volume and overage charges.
Follow the HTTP headers
summary and validation support ETag / If-None-Match and 304. At this edition: Cache-Control: public, max-age=15, stale-while-revalidate=30. Series and pricing responses use no-store.
Client recommendation: use a bounded timeout and up to three retries for temporary network failures or 502/503/504 responses, with increasing randomised delays. This is guidance, not a guaranteed server response time. Never retry indefinitely. If 429 includes Retry-After, respect it; no universal numeric quota or header scheme is currently claimed.
Responses use application/json; charset=utf-8. Large summaries support gzip when Accept-Encoding: gzip is supplied. Do not depend on key order. For calls from another website, use your own server-side intermediary: actual GET responses currently lack an allowing CORS header. An OPTIONS response alone does not permit cross-origin reading.
This public specification includes no API key, Bearer token, OAuth login, callbacks to client URLs or guaranteed set of private endpoints. Commercial authentication, address restrictions, logging, retention and service levels are agreed separately. Never place secrets in request URLs or browser code.
Connect from Python and JavaScript
Minimal server-side read examples preserve missing values and the correct axis order. Add rate control, logging and bounded retries for a production application.
Python · standard library
import json
from urllib.parse import urlencode
from urllib.request import Request, urlopen
from urllib.error import HTTPError, URLError
params = {"lat": 55.75, "lon": 37.62, "var": "ndvi",
"start": "2026-06", "end": "2026-07"}
url = "https://forestosglobal.com/api/public/h3-at-point?" + urlencode(params)
try:
with urlopen(Request(url, headers={"Accept": "application/json"}), timeout=30) as r:
if r.headers.get_content_type() != "application/json":
raise RuntimeError("Expected JSON")
data = json.load(r)
except HTTPError as error:
raise RuntimeError(f"HTTP error: {error.code}") from error
except URLError as error:
raise RuntimeError("Connection error") from error
if not data.get("ok"):
raise RuntimeError(data.get("error", "Data unavailable"))
for index, month in enumerate(data["months"]):
value = data["variables"]["ndvi"][index][0]
print(month, "no data" if value is None else value)
# If months is empty, there are no observations in the requested interval.
# Values are already decoded; do not apply scale again.JavaScript · server-side Node.js
// Node.js 18+; server-side example; this does not bypass CORS restrictions.
const url = new URL("https://forestosglobal.com/api/public/h3-at-point");
url.search = new URLSearchParams({
lat: "55.75", lon: "37.62", var: "ndvi",
start: "2026-06", end: "2026-07"
}).toString();
const response = await fetch(url, {
headers: { Accept: "application/json" },
signal: AbortSignal.timeout(30000)
});
if (!response.ok) throw new Error(`HTTP error: ${response.status}`);
if (!(response.headers.get("content-type") || "").includes("application/json")) {
throw new Error("Expected JSON");
}
const data = await response.json();
if (!data.ok) throw new Error(data.error || "Data unavailable");
data.months.forEach((month, index) => {
const value = data.variables.ndvi[index][0];
console.log(month, value === null ? "no data" : value);
});From exploration to your scale
Explore the format
The six public GET endpoints above are available without payment or an API key. This is not a commercial licence for bulk export or data resale.
Developer
Derived indices and an agreed feature set for integration. Test access, quotas and usage terms are specified before onboarding.
For services and applications
Higher volumes and agreed commercial use. Event coverage, notifications and available forecast outputs are checked for each project.
Enterprise data exchange
Batch calculations, dedicated quotas and contractual service levels. Redistribution rights are agreed separately.
Prices come from the platform’s shared catalogue. The annual contract defines volumes, territories, outputs and usage rights. Implementation, overage and additional work are quoted separately unless included. The final amount and tax terms are confirmed in the proposal.
| Term | Public read access | Commercial access |
|---|---|---|
| Access | No key required; overview data contract | Agreed specification and authentication method |
| Volume | One cell, up to 12 months per request | Areas, periods, frequency and concurrency under contract |
| Outputs | Documented series and public reference data | Agreed set of derived outputs |
| Service | No numerical service-level commitment | Agreed targets, support and incident handling |
| Oracle | Public exploration through the platform interface | An option within the main contract; capabilities depend on access level |
| Source cube and models | Full export is not provided | Not included automatically; output rights are agreed separately |
Oracle is not sold here as a separate plan. Public, client, operational and strategic access differ in their data, tools and permissions. API access to the option is included only if explicitly agreed in the main contract; buying an API package does not automatically unlock every access level.
Agree the deliverables before work starts
Describe your task
Areas, periods, required indicators, your system’s format, expected request frequency and output rights.
Agree the contract
Endpoints, authentication, limits, acceptance criteria, service levels, pricing and change management.
Test the integration
Reference requests and responses, missing-value and error handling, followed by acceptance of the agreed configuration.
For support, include the endpoint, request time in UTC, HTTP status, error code and a minimal example without secrets. Send sensitive coordinates and client data only through an agreed secure channel. A universal request_id is not currently guaranteed in responses.
Technical terms explained
| Term | Meaning |
|---|---|
| API | Application programming interface: a way for another program to retrieve platform data. |
| HTTP / HTTPS | Network communication protocols; HTTPS uses an encrypted connection. |
| GET | A read method: a program requests data at a specified URL. The method name is not translated in requests. |
| JSON / UTF-8 | A structured data format and a text encoding supporting multiple languages, including Russian. |
| OpenAPI / JSON Schema | Standards for describing endpoints, parameters and response structures for automated validation. |
| URL / URI | A resource address or identifier. Copy it unchanged from the examples. |
| UTC | Coordinated Universal Time, not Moscow time or the browser’s local time. |
| H3 resolution 7 / WGS 84 | A spatial cell system and a geographic coordinate reference system. Grid resolution is not the accuracy of the original measurement. |
| null / true / false | In the data: a missing value, Boolean true and Boolean false. Their code spelling remains unchanged. |
| CORS | Browser rules for reading data from another origin. Server-side access does not imply browser access is allowed. |
| ETag / If-None-Match | A response version tag and a conditional request using that tag, allowing clients to detect changes. |
| Cache-Control / Retry-After / gzip | Instructions for caching a response, waiting before retries, and a data compression format. |
| Bearer / OAuth | An access-token scheme and an authorisation protocol. Neither is required for the documented public endpoints. |
| Webhook | An automatic notification sent to an agreed URL in another system. |
| MRV / SLA / AOI | Monitoring, reporting and verification; service-level agreement; area of interest. These concepts are explained in the interface. |
| P10—P90 | The range between the 10th and 90th percentiles of model estimates. It does not by itself guarantee that a future observation will fall within the range. |
| Validation / data provenance | Checks of result quality and applicability; information about where data came from and how they were obtained. |
The Forest Os Global name, URLs, commands, field names, scientific indices and format names retain their original spelling for compatibility. Their purpose is explained in this glossary.
A verifiable specification without private internals
API documentation edition 2.1.1, dated 03 September 2026: labels and the technical glossary were expanded without changing URLs, parameters or data structures. The document edition does not change a model version or its operational approval. Public endpoint URLs currently contain no version number.
The description uses OpenAPI 3.1.1 and JSON Schema 2020-12. HTTP methods and statuses are explained with reference to HTTP Semantics (RFC 9110). This is a machine-readable specification, not a claim of certification, software-register inclusion or compliance with every possible standard.
We publish purpose, parameters, formats, limits and access terms. We do not disclose keys, internal addresses, infrastructure diagrams, client data or private model parameters. Interface changes and migration for commercial projects are governed by their specifications. New capabilities are not included until the agreed delivery scope confirms them.
What has been validated.
Where limitations remain.
Dated validation results for Forest Os Global. Data integrity, model quality and permitted use are reported separately, without a single score that hides differences between components.
Edition 2.0 · 03 September 2026 · Validation statuses have their own dates
Published snapshot date (UTC): 2026-09-02T09:38:00Z. This is not the date of the latest forest event. Refresh the snapshot to confirm that the status is current.
Scope of engineering validation
These are validation counters, not a count of independent auditors or a forecast accuracy percentage. An external specification establishes the meaning of a source product; it does not by itself validate a Forest Os Global model.
| Dataset validation result | Count |
|---|---|
| No issues | 6 |
| With warnings | 19 |
| With errors | 0 |
Status of each component
Data and cube
Validated within the stated scopeThe stated checks passed; the conclusion applies only to the specified validation scope.
- Passed
- 13
- Total in summary
- 13
- Warnings
- 0
- Failures
- 0
- Unconfirmed
- 0
What was checked and what limitations apply
Integrity, spatial keys, dates and absence of duplicates.
Engineering data checks do not establish the accuracy of every analytical model.
F-12 · Active fire detection
Not approved for operational useQuality checks have not passed. No validated operational forecast is claimed for this model.
- Passed
- 20
- Total in summary
- 35
- Warnings
- 0
- Failures
- 15
- Unconfirmed
- 3
What was checked and what limitations apply
Detection timeliness, missed events and false alarms.
Operational release requires successful validation on a new independent period. Earlier detection is not guaranteed.
F-09 · Fire spread
Research use onlyThe result is not used as a validated operational forecast.
- Passed
- 15
- Total in summary
- 18
- Warnings
- 0
- Failures
- 0
- Unconfirmed
- 3
What was checked and what limitations apply
Comparison of forecasts saved in advance with actual fire perimeters.
Applicability to a territory requires independent time-stamped perimeters and reliable initial conditions.
Forest inventory and planning
Model estimates onlyOnly explicitly labelled model estimates are permitted; they do not replace field surveys.
- Passed
- 18
- Total in summary
- 25
- Warnings
- 3
- Failures
- 0
- Unconfirmed
- 4
What was checked and what limitations apply
Consistency of model estimates with available reference materials.
Regional aggregates do not replace a field inventory of a specific area.
Forest restoration
Preliminary scenarios onlyScenarios require specialist review and agreement on their initial assumptions.
- Passed
- 18
- Total in summary
- 26
- Warnings
- 2
- Failures
- 0
- Unconfirmed
- 6
What was checked and what limitations apply
Scenario justification, input data and specialist review.
Survival probabilities require observations of actual project outcomes.
Oracle · Four access levels
Limited useUse is permitted subject to the stated limitations and specialist review.
- Passed
- 39
- Total in summary
- 49
- Warnings
- 1
- Failures
- 0
- Unconfirmed
- 9
What was checked and what limitations apply
Approval handling, data separation and human review of significant decisions.
Testing software safeguards does not replace blind expert assessment of recommendations and observation of their consequences.
Core and data updates
Validated within the stated scopeThe stated checks passed; the conclusion applies only to the specified validation scope.
- Passed
- 12
- Total in summary
- 12
- Warnings
- 0
- Failures
- 0
- Unconfirmed
- 0
What was checked and what limitations apply
Reproducible updates, recovery and preservation of results.
Engineering resilience does not guarantee availability under any workload.
F-07 · Fire fuel index
Limited useUse is permitted subject to the stated limitations and specialist review.
- Passed
- 16
- Total in summary
- 19
- Warnings
- 1
- Failures
- 0
- Unconfirmed
- 2
What was checked and what limitations apply
Consistency of the analytical indicator and quality of input data.
The index is not a standalone fire probability; its relationship to field measurements requires separate validation.
F-14 · Event reports
Limited useUse is permitted subject to the stated limitations and specialist review.
- Passed
- 15
- Total in summary
- 18
- Warnings
- 1
- Failures
- 0
- Unconfirmed
- 2
What was checked and what limitations apply
Quality of permitted sources, duplicate reports and operator confirmation.
A report remains evidence to investigate, not an established fact.
F-13 · Fire type
Not approved for operational useQuality checks have not passed. No validated operational forecast is claimed for this model.
- Passed
- 15
- Total in summary
- 19
- Warnings
- 2
- Failures
- 1
- Unconfirmed
- 1
What was checked and what limitations apply
Classification quality and robustness across classes.
Fire type and ignition cause are different questions. Establishing the cause requires separate evidence.
F-15 · Fire risk forecast
Not approved for operational useQuality checks have not passed. No validated operational forecast is claimed for this model.
- Passed
- 17
- Total in summary
- 27
- Warnings
- 0
- Failures
- 7
- Unconfirmed
- 3
What was checked and what limitations apply
Accuracy, false alarms, calibration and transferability across territories.
A favourable result on an internal sample does not replace successful validation on new regions and periods.
Counters follow the source snapshot’s categories. Do not add them up to estimate the accuracy or readiness of the entire platform. A release decision requires new validation; redesigning the page does not change model approval.
External data and independent assessment
Does the process work correctly?
Data integrity, reproducibility, access controls and missing-value handling.
Is the result supported by observations?
Comparison with historical, satellite, event and field references under specified conditions.
Can the assessment be reproduced?
A separate protocol and conclusion from external experts. This cannot be claimed solely because NASA data or government aggregates were used.
Considerations for use
- The status applies to a dated snapshot, not every future version.
- The number of checks is not a forecast accuracy percentage. Source-summary categories should not be added without their methodological definitions.
- Validation against external data does not mean an independent organisation has certified the platform.
- A global grid and time axis do not guarantee complete coverage of every layer.
- Field accuracy and model transferability require separate field and cross-region validation.
- Recommendations do not replace the decisions of an authorised specialist.
Open to independent validation
We can agree areas, authorised field data, periods, metrics and a reproducible protocol with a research or specialist organisation. Access terms and any research quota are agreed separately; a positive result is not a condition of participation.
Share evidence. Protect confidential information.
Results and limitations
Sources, indicator definitions, dates, aggregated validation results and scope of use.
Project validation package
Specifications, methodology, anonymised examples and additional evidence within an agreed scope.
Intellectual property and data
Source code, trained weights, internal features and thresholds, infrastructure diagrams, keys and other customers’ materials.
Forest territories.
One digital environment.
Forest Os Global brings together satellite observations, analytics and tools for managing forest territories. For organisations that need to see what changed and understand the evidence behind each finding.
Edition 2.0 · 03 September 2026 · Validation statuses have their own dates
Global history. Local validation.
These figures describe the analytical infrastructure at the edition date, not a count of confirmed observations. Completeness depends on the layer, territory, season and satellite operating period.
From observations to informed decisions
Observe
Compare vegetation history, thermal anomalies, moisture and land-cover changes.
Validate
Distinguish observations, derived estimates and scenarios; see the source and limitations of each result.
Act
Prepare reports, prioritise survey areas and agree decisions with specialists.
One platform. Different tasks.
Territory condition
Maps and change histories for areas, portfolios and regions. Detail depends on available data.
Events and risk
Current satellite signals are separated from historical burned-area records. Forecast-model approval is shown on the validation page.
Assessment and planning
Model estimates, forest-use scenarios and portfolio analysis. These do not replace field forest inventories.
Restoration scenarios
Prepare and compare restoration options, with mandatory specialist review.
Assistance with data analysis
An option within the main plan: public, client, operational and strategic access, with different permissions and tools.
Comparison with observations
Work with field time series and satellite history under an agreed project. Independent validation is arranged separately.
Different roles. Shared data.
| User | Practical task | Deliverable |
|---|---|---|
| Forest operator | Monitor your territories and plan surveys | Report, change map and survey priorities |
| Public institution | Compare available information about a territory | Overview and analytical materials for domain specialists |
| Integrator | Embed analytics in your information system | Agreed data exchange and service terms |
| Research institution | Test hypotheses using field and satellite data | Reproducible comparison protocol and assessment of limitations |
Trust starts with clear boundaries of applicability
Software reliability, scientific model quality and independent assessment are different evidence levels. We report them separately and do not present the number of passed checks as forecast accuracy.
Forest Os Global public offer
Terms for analytical and information services. Edition dated 01 September 2026.
1. General provisions and acceptance
1.1. This document is a public offer within the meaning of Articles 435 and 437 of the Civil Code of the Russian Federation and contains the terms of the contract for the paid provision of analytical and information services Forest Os Global.
1.2. Service provider: FOREST OS Limited Liability Company (FOREST OS LLC), OGRN 1260400001619, INN 0400031243, KPP 040001001. Registered address: 11 Potanina Street, Gorno-Altaysk, Altai Republic, 649000, Russian Federation.
1.3. Full acceptance is the choice of the service and parameters of the Order, providing the necessary data, a separate confirmation of familiarization with the Offer and consent to the processing of personal data and payment for the Order.
1.4. The contract is considered concluded after confirmation of receipt of payment by the server notification of the payment provider. The return of the user to the Site after a payment form does not in itself confirm payment.
1.5. For a corporate or institutional workspace, a separate contract, technical brief or specification takes precedence within its relevant scope.
2. Services and results
2.1. The Contractor processes available satellite, geospatial, climatic and other data on the selected territory and transmits the result in electronic form.
2.2. A one-off Report is a PDF prepared for the selected area, together with CSV, GeoJSON or other materials if included in the product. Basic, Full and Scenario Reports are available with the scope and prices shown on the Website.
2.3. Corporate and institutional workspaces include only agreed roles, reporting, monitoring, API access and integrations. Scope, price, sources and service levels are confirmed in a specification, invoice or separate contract before payment.
2.4. The service is analytical and informational. It does not replace statutory, forest inventory, cadastral, valuation, insurance, investment, legal or other mandatory assessments.
3. Delivery times
3.1. A basic report is prepared within 3–5 business days after the later of full payment confirmation or receipt of sufficient input data. Delivery times for forest asset reviews and scenario assessments are agreed in the Order before payment. Previously agreed delivery times remain valid for existing orders.
3.2. A corporate or institutional workspace is prepared within up to 30 calendar days after the latest of receiving the agreed payment, approving the scope and obtaining sufficient data and access.
3.3. In case of insufficient, damaged or contradictory data, the Contractor sends a request for clarification; the period is suspended until a sufficient response is received.
3.4. The result is transmitted to e-mail from the Order, through a secure link and (or) in the client account. Re-sending to the confirmed address is carried out at no additional cost.
4. Price, payment and receipt
4.1. Current descriptions and prices are posted on the page “Pricing”. The price of each Order is fixed in rubles before payment.
4.2. One-off Reports require payment of 100% of the Order price. Payment terms for corporate or institutional workspaces are defined by the agreed specification or contract.
4.3. Payment is accepted through Robokassa or by other agreed non-cash method. Forest OS does not receive or store full credit card details.
4.4. The price includes taxes payable by the service provider under its applicable tax regime. VAT status and, where applicable, the VAT amount are stated in the Order, invoice and/or primary accounting document before payment. An electronic receipt is issued by the service provider, payment provider or authorised agent in accordance with the applicable procedure.
5. Rights and obligations of the parties
5.1. The customer has the right to receive the service in the agreed amount and term, request status, report shortcomings and use the methods of protection of rights provided for by law.
5.2. The customer provides reliable information, has legal grounds for data transfer, checks the selected product and territory and independently assesses the applicability of the analytical result to its task.
5.3. The Contractor uses the data available at the time of calculation, discloses significant restrictions and has the right to request clarification or propose a change in the volume if it is objectively impossible to fulfill the initial parameters.
5.4. The Contractor may engage infrastructure, data, communications and payment providers while remaining responsible for its contractual obligations within the limits of law.
6. Cancellation, refunds and claims
6.1. The customer-consumer has the right to withdraw from the Agreement at any time subject to payment of actually incurred and documented expenses of the Contractor in accordance with Article 32 of the Law of the Russian Federation "On Protection of Consumer Rights" and Article 782 of the Civil Code of the Russian Federation.
6.2. After the start of processing, the refund is calculated taking into account the confirmed costs and actually provided part of the Service. Claims for defects, non-conformity or violation of the term are dealt with under applicable law.
6.3. Send your request to Sibkub@yandex.ru with “Refund” in the subject line and the Order number. A substantiated claim is reviewed and a refund initiated within 10 calendar days after a sufficiently complete request is received, unless the law provides otherwise.
6.4. The detailed procedure is published under “Refunds and cancellation”.
7. Intellectual property
7.1. The rights to the software, interface, analytics structure, texts, visualizations and methodical materials of Forest OS belong to the Contractor or right holders.
7.2. After payment, the Customer receives a non-exclusive right to use the Report and exports for its own internal, management, research or contractual purposes, without the right to resell, distribute in bulk, extract private datasets or create a competing service.
7.3. The report may be forwarded to employees, consultants, auditors, a bank, insurer or government agency to the extent of a legitimate task while maintaining notifications about the source and limitations.
8. Limitations of Analytics
8.1. The results depend on the availability and resolution of sources, cloudiness, geometry of the territory, completeness of history and model assumptions.
8.2. Satellite signal, heat anomaly, risk index, correlation or causal loop candidate are not in themselves evidence of logging, fire, damage, culpability or cause-and-effect.
8.3. Predictions and scenarios are probabilistic estimates, not a guarantee of a future event, return, cost, carbon effect or managerial outcome.
8.4. Decisions requiring mandatory accuracy or legal confirmation should also be based on a field survey, official registries and appropriate independent expertise.
9. Personal data and confidentiality
9.1. Personal data is processed by separate consent according to Personal data processing policy. Refusal to provide mandatory data makes it impossible to execute, pay and transfer the result.
9.2. Payment data are processed by the payment provider. The service provider receives the information needed to identify payments, Order status and receipts and to perform the Agreement.
9.3. Confidential information is not disclosed, except as necessary to provide the Service, enforce the law, protect a right or engage a contractor with a duty of confidentiality.
10. Liability, duration and disputes
10.1. The parties are liable for breaches of their obligations under the Agreement and applicable law. Liability limitations do not apply where prohibited by law.
10.2. The offer is valid from publication to revocation or replacement. The new version shall apply to future Orders; the paid Order shall be subject to the revised version in force upon payment, unless a subsequent change improves the position of the Customer or is required by law.
10.3. The Agreement is governed by the law of the Russian Federation. Jurisdiction is determined by law and does not deprive consumers of statutory rights to choose a competent court.
10.4. Send enquiries to Sibkub@yandex.ru. The Contractor seeks to respond within 3 working days; a special deadline for the execution of the claim is determined by law or the Agreement.
11. Service provider details
Refunds and service cancellation
Procedure for one-off reports and individual client workspaces. Edition dated 01 September 2026.
At a glance
- The customer-consumer may refuse the service at any time with payment only of actually incurred and documented expenses of the Contractor.
- Basic reports take 3–5 business days; forest asset reviews and scenario assessments follow an agreed schedule. Workspaces are prepared within up to 30 calendar days after the start conditions are met. Existing agreed delivery times remain valid.
- If there is a lack of data, the period is suspended until clarification is received.
- Requirements for shortcomings and violation of the term are considered under the legislation of the Russian Federation.
How to submit a request
Send the letter to Sibkub@yandex.ru with “Refund” in the subject line.
Specify the name or name of the Customer, Order number, e-mail address from the Order, requirement and information sufficient to identify the payment. Do not send full credit card details, passwords or confirmation codes.
How the refund is calculated
Before the start of work, the paid amount is returned minus only those actual expenses that the Contractor is obliged to prove. After the start of work, documented expenses and actually provided part of the Service are taken into account.
After the delivery of the result, claims for defects, non-compliance with the Order or violation of the term are considered according to applicable law. The Contractor may gratuitously eliminate the confirmed defect or re-form the result, if this corresponds to the Customer's requirement and the law.
Timing and payment method
A substantiated claim is reviewed and a refund initiated within 10 calendar days after a sufficiently complete request is received, unless the law provides otherwise. The time until funds reach the account depends on Robokassa and the Customer’s bank.
Refunds are usually made by the same method of payment. If this is not technically possible, the Parties shall agree on a legitimate alternative method after identification of the recipient.
Corporate and institutional workspaces
Termination of work, calculations and return are determined by an individual contract or specification. Mandatory consumer rights apply if the Customer is a consumer by law.
Privacy policy
Applies to forestosglobal.com and its order and enquiry forms. Edition dated 01 September 2026.
1. Data controller
Data controller: FOREST OS Limited Liability Company (FOREST OS LLC), OGRN 1260400001619, INN 0400031243, KPP 040001001. Registered address: 11 Potanina Street, Gorno-Altaysk, Altai Republic, 649000, Russian Federation. Data protection contact: Sibkub@yandex.ru.
The policy is drawn up taking into account the Federal Law of 27.07.2006 No 152-FZ "On Personal Data" and applies to the processing of data of Forest Os Global users.
2. What data is processed
- e-mail address, phone number or messenger identifier, name and information about the company, if indicated;
- coordinates, polygon, name of the territory, country, region, settlement and files uploaded by the user;
- Order number, selected service, price, payment status, receipt information and support requests;
- technical information: IP address, date and time of request, page address, browser type, security logs and errors;
- other data that the user voluntarily provides in the application or correspondence.
Forest OS does not receive or store the full credit card number, CVC/CVV, bank password or payment confirmation code.
3. Purposes and legal bases
- Order execution, payment identification, formation and transfer of the result;
- preparing a proposal and workspace, providing support, performing contracts and processing refunds;
- issuing receipts and meeting accounting and tax obligations;
- protecting the Website, preventing abuse and maintaining technical logs;
- anonymised quality analysis and product improvement.
The grounds are the separate consent of the user, actions on his request before the conclusion of the contract, performance of the contract and obligations under the law, as well as a legitimate interest in ensuring security while respecting the rights of the user.
4. Actions, timelines and protection
The operator may collect, record, systematize, store, refine, use, transmit to the authorized processor, anonymize, block and delete data within the scope of the purpose of processing.
The data are stored no longer than is necessary for the execution of the Order, support, dispute resolution and mandatory tax or contractual deadlines, after which they are deleted or anonymized unless further storage is required by law.
Access delimitation, logging, secure connections, backups and other reasonable organizational and technical measures are applied.
5. Recipients and external services
To the extent necessary, data can be processed by hosting and communication providers, Robokassa and payment infrastructure participants, e-mail, mapping and geocoding services, as well as contractors bound by a duty of confidentiality.
Payment details are entered on the side of Robokassa. When using the territory search, the mapping or geocoding service receives only the request and technical information necessary for a response.
Cross-border transfer is allowed only if the requirements of the legislation of the Russian Federation are met. The Operator does not sell personal data and does not use them for advertising mailings without a separate consent.
6. User rights
The user has the right to request information about processing, clarification, blocking or deletion of data, withdraw consent and appeal against the actions of the Operator. The request is forwarded to Sibkub@yandex.ru and should allow reasonable identification of the applicant without transferring redundant data.
Withdrawal of consent does not affect the lawfulness of processing prior to withdrawal and does not terminate processing that is necessary for the performance of a law, contract or protection of a right. If the mandatory data are deleted before the execution of the Order, the provision of the Service may become impossible.
Contact Forest Os Global
Service provider details and support for orders, refunds and client workspaces.
Service provider
Support
For Order enquiries, include the Order number in the email subject. Use “Refund” for refund requests and “Personal data” for data protection enquiries.
The Contractor strives to respond to normal requests within 3 working days. The term of execution of a legal claim is determined by law or contract.
How to order, pay and receive a service
A single customer guide covering service scope, prices, ordering, delivery, cancellation and refunds.
1. Description of services, characteristics and prices
Analytics and access to Forest Os Global. Composition, area, term, limits and final cost are fixed before payment.
| Product | Scope | Pricing |
|---|---|---|
| Basic area analysis | Observation history and trends in key indices; condition, anomalies, fire history and moisture stress; area map, sources and limitations | 49 000–79 000 ₽ / report |
| Forest asset review | Everything in the basic report plus analyst input; model-based forest inventory estimates where accuracy is sufficient; review of risks, evidence and available documents | 180 000–350 000 ₽ / report |
| Scenario assessment | Four scenarios: baseline, stress, restoration and forest use; ranges for net present value, revenue and costs; action plan and model limitations | 450 000–900 000 ₽ / report |
| Personal | Up to 500 ha / up to 3 areas; monthly monitoring and alerts; 2 basic reports per year | 20 879 ₽ / year |
| Land Pro | Up to 5 000 ha / up to 10 areas; more frequent scheduled alerts; browser app, documents and 6 reports per year | 68 727 ₽ / year |
| Team | Up to 50 000 ha / 10 users; basic forest inventory estimates, reporting and data export; notifications and 12 reports per year | 400 000–800 000 ₽ / year |
| Portfolio | Up to 250 000 ha / 30 reports per year; scenarios and limited data exchange; organisation-wide single sign-on quoted separately | Custom quote |
| Enterprise | Agreed service levels, single sign-on and support; links to accounting systems and government services where available; additional large-portfolio rate: 1.74–4.35 ₽/ha per year | Custom quote |
A standard basic report for up to 1 000 ha using available data costs 49 000 ₽. Extended scope and larger territories are quoted separately. Forest asset reviews and scenario assessments require an agreed brief. Full plan comparison, implementation and additional modules: tariff. The term of the basic report is 3-5 working days after payment and receipt of sufficient data; for other packages - on assignment. For previously executed orders, the amounts and deadlines agreed upon during registration are valid.
2. How to place an order
- Select the territory on the map: country, coordinate, address, radius or drawn polygon.
- Select the report type and check the price before payment.
- Provide an email address to get the result.
- Confirm the familiarization with offerrules revocation and consent Policy of Personal Data Processing.
- After payment, the order falls into the queue of preparing a report. The order number is used for status, support and return.
3. Conditions and methods of payment
One-time report is paid in the amount of 100% of the order price. The subscription is paid for the selected settlement period - one calendar month, unless another period is agreed before payment. Payment is accepted through Robokassa or by other agreed non-cash method. Forest Os Global does not receive or store the full credit card number, CVC/CVV, bank password or payment confirmation code.
The contract is considered concluded and the order is considered paid only after receiving a server confirmation of payment from the payment provider. The return of the user from the payment page does not in itself confirm the payment.
Automatic renewal or recurrent write-offs apply only with a separate explicit confirmation of the buyer. If such confirmation is not issued, the renewal of the subscription is carried out after manual payment for the next period.
The price includes taxes that the Contractor is obliged to calculate under the applicable taxation regime. The VAT status and, where applicable, the amount of VAT shall be stated in the Order, invoice and/or initial document before payment.
4. Subscriptions: connection, period, cancellation
Subscription provides access to an agreed set of reports, preserved territories, monitoring and exports during the paid settlement period. The composition and limits of the subscription are indicated on the page “Pricing” And they're fixed before payment.
- Start of access - after confirmation of payment and creation of a client account or after fulfilling the necessary technical conditions.
- If there is not enough data for a particular area, the system shows the cause and does not replace the missing data with a calculated stub.
- Cancellation of the extension by letter to Sibkub@yandex.ru with the topic “Cancel Subscription” and the email address of the account.
- Cancellation of the extension does not deprive access to the already paid period, if the parties have not agreed on early termination and refund.
- The refund for the subscription is calculated according to the rules of refusal of service: the actually rendered part, used reports and documented expenses of the Contractor are taken into account.
5. Delivery of services and deadlines
A basic report is prepared within 3–5 business days after confirmation of payment and receipt of sufficient initial data on the territory; verification of the forest asset and scenario passport - in the period agreed before payment. For previously issued orders, their terms are retained. The result is transmitted to e-mail from the order, through a secure link and (or) in the client account.
The client account by subscription is created after confirmation of payment and sufficient registration data. If additional configuration of the territory, sources or roles is needed, the term and composition are specified before payment or in correspondence on the application.
A corporate or institutional workspace is prepared within up to 30 calendar days after agreeing on the composition, obtaining the necessary data and fulfilling the terms of payment, unless another period is specified in the contract or specification.
If the coordinates, polygon, sources or other data are insufficient, damaged or contradictory, the Contractor shall request clarification. The deadline shall be suspended until a sufficient response is received.
6. Refusal to purchase before receiving the service
The Buyer can refuse the service before receiving the result, as well as in the process of providing the service by sending an application to Sibkub@yandex.ru It's called "Return." In the letter you need to specify the name or name of the customer, order number, e-mail address from the order, requirement and information sufficient to identify the payment.
Before the start of work, the paid amount is returned minus only the actual costs of the Contractor, if such expenses are documented. After the start of work, the actually provided part of the service and documented expenses of the Contractor are taken into account. The commission of the payment service or bank is not withheld from the buyer as a separate basis for refund.
7. Step-by-step algorithm of refund
- The buyer submits the application to Sibkub@yandex.ru with “Refund” in the subject line.
- The Contractor checks the order number, e-mail address, payment status, execution stage, reports used or subscription period and sufficiency of information.
- If information is lacking, the Contractor requests clarification.
- Upon receipt of a sufficient application, the justified claim shall be considered and the refund shall be initiated within 10 calendar days, unless otherwise specified by law.
- Refunds are usually made by the same method of payment. If this is not technically possible, the parties will agree on a legitimate alternative method after identifying the recipient.
- The time until funds reach the account depends on Robokassa and the customer’s bank.
Detailed rules published on the page “Refunds and cancellation”.
8. Information, contacts and personal data
Everything for an informed
decision.
Documents for customers, integrators, research institutions and domain specialists. Service terms, methodology and verifiable information about the platform.
Edition 2.0 · 03 September 2026 · Validation statuses have their own dates
Documents for your task
How we reach our findings
Sources, spatial scale, indicators, validation and limitations. The browser version corresponds to the downloadable Russian document.
Validation status
Data and component checks, unresolved issues and permitted-use boundaries.
Public API
Query parameters, limits, formats and errors for the basic read endpoints. Private interfaces are not included in this file.
Order and terms of service
The composition, price, terms and procedure for obtaining the result are determined by the selected service and agreed conditions.
Commercial and legal documents
| Document | What to check |
|---|---|
| Offer | Procedure for concluding the contract, subject and conditions of service |
| Payment and provision of services | How the order is made and the result transmitted |
| Refunds and cancellation | How to request cancellation and a refund |
| Personal data | Contact data processing and applicant’s rights |
Integration under an agreed brief
Preparing materials for an external information system does not mean access to it has been authorised. FGIS LK requires coordination with its operator, granted access and verification of applicable official formats. Until then, Forest Os Global does not replace state forest register data.
Technical specifications and integration assessment materials are provided to identified recipients after the disclosure scope is agreed. Internal connection diagrams, addresses and operational instructions are not published on this page.
Technical assessment materials
Within the framework of the project, it is possible to agree on a demonstration, delivery description, results rights, service indicators and acceptance protocol. Official statuses and opinions are published only if there is appropriate confirmation. The presence of this documentation in itself does not mean inclusion in the register of Russian software or certification of the platform.
Open information and protected materials
Results and limitations
Sources, indicator definitions, dates, aggregated validation results and scope of use.
Project validation package
Specifications, methodology, anonymised examples and additional evidence within an agreed scope.
Intellectual property and data
Source code, trained weights, internal features and thresholds, infrastructure diagrams, keys and other customers’ materials.
Edition 2.0 aligns the time axis, nine public indices, two detailed-area indicators and four Oracle access levels. Validation is linked to a published snapshot; internal test results are not converted into marketing promises.
How data becomes
insight.
Forest Os Global public methodology: sources, scale, indicator definitions and rules for evidence-based validation. Applicability matters more than universal promises.
Edition 2.0 · 03 September 2026 · Validation statuses have their own dates
What this methodology explains
Forest Os Global links observations, derived indicators and analytical findings to a place and time. This methodology describes how results are produced and checked; it does not establish the accuracy of every model.
This edition describes the public and contractual analytical environment. Source code, trained parameters and infrastructure internals are not disclosed. Standard scientific definitions and source specifications are available through the links.
A global grid does not replace local detail
At the edition date, the global land grid contains 25 063 102 H3 resolution 7 cells. Its time axis contains 319 months, January 2000 – July 2026. This is a structure for storing and comparing data, not a guarantee of an observation for every indicator, cell and month.
The average area of an H3 resolution 7 hexagonal cell is about 5.16 km²; actual area varies across the Earth. Grid resolution does not improve the resolution of the satellite product. Small areas require detailed imagery and, where necessary, field measurements.
Some source time series start later. Clouds, snow and a lack of suitable scenes create missing values. Page date, validation snapshot date and observation date are different quantities.
Preserve data provenance
Sources include NASA MODIS, Copernicus Sentinel-2 and USGS Landsat satellite products, NASA FIRMS thermal anomalies, ERA5-Land climate reanalysis and available authorised field materials. Products differ in spatial and temporal resolution.
Source quality flags determine which observations are usable. Depending on the product, observations form a monthly series or retain an event date. Aggregation across sources and rescaling must be defined for each result.
Reproducing a result requires the area boundary, period, source product and version, units, aggregation method, completeness and limitations. The scope of supplied provenance documentation is agreed in the brief.
Nine public indices and detailed-area analysis
The public registry includes NDVI, EVI, NBR, dNBR, NDWI, NDMI, LAI, fAPAR and SIPI. CCI and BAIS2 support detailed analysis of a selected area where suitable Sentinel-2 data are available; they are not claimed as continuous global historical series.
NDVI and EVI describe vegetation spectral response; NDMI is moisture-sensitive; the selected NDWI definition measures water-related spectral contrast. LAI describes leaf area, and fAPAR describes absorption of photosynthetically active radiation. These indicators are not direct forest inventory measurements, disease diagnoses or carbon stock measurements.
NBR and dNBR support spectral change analysis. The difference between adjacent monthly values is not equivalent to the severity of a specific fire: that requires suitable before-and-after windows, seasonality checks and independent evidence.
Different sensors and approximated derived indicators are not assumed interchangeable without validation. The shortwave infrared band used for NBR is particularly important. An index name alone does not establish comparability between two series.
Observations, estimates and scenarios are different outputs
A missing observation remains missing, not zero. Zero is valid only as defined by the source product. Failure to detect a signal does not prove that a small or missed event did not occur.
A FIRMS hotspot is a satellite detection, not an established ignition cause. Burned-area archives, hotspot counts, fire area and the number of separate incidents are not interchangeable.
Fire type, degree of land-cover change and ignition cause are separate questions. Causal hypotheses require event, field and other independent evidence; the system does not make legal determinations.
Climate scenario context uses available NASA NEX-GDDP-CMIP6 regional data, including SSP2-4.5 and SSP5-8.5. These are pathways under specified assumptions, not site-level fire probabilities or a proprietary dynamic climate model from Forest Os Global.
Three levels of evidence
Engineering checks establish integrity, consistency and reproducibility of data and software processes. Backtesting compares a result with an observed outcome. External validation uses a reference not used for tuning; it is not equivalent to an independent organisation’s formal assessment.
A valid test specifies the task, forecast issue date, territory, horizon, observed-outcome source, metrics and acceptance criteria in advance. Samples are separated by time and, where appropriate, geography. Future information must not leak into input features.
Event evaluations measure detections, missed events and false alarms. Probability evaluations assess calibration and ranking; quantitative estimates assess error magnitude. Metrics are published with their validation scope, sample and limitations, not as a universal platform accuracy percentage.
If the actual outcome is not yet observed, a reference is missing or the sample is insufficient, the result remains unconfirmed. Technical readiness does not turn a failed test into a pass. Current component decisions appear in a separate dated validation summary.
Feedback without automatic release approval
Events from authorised sources and user reports can expand the reference dataset for forecast comparison. User reports first require verification, deduplication and confirmation of event time and location.
A new model version must be compared with its predecessor using independent data. Training or accumulating observations does not by itself authorise publication of a result. This section describes how improvements are verified, not a promise of automatic gains.
Oracle operates within its access level and permitted data. It helps explain results and compare options, but significant actions require specialist confirmation.
What must be agreed with the customer
Forest inventory characteristics remain model estimates until supported by appropriate field evidence. Restoration scenarios do not guarantee survival. Carbon and economic estimates require their own methodology, assumptions and validation.
Access to FGIS LK and other restricted sources requires lawful authorisation. The system does not replace official documents, state information or decisions by authorised persons.
Sources, definitions, validation scope, aggregated results and limitations are disclosed publicly. Additional materials for reproducing a study are supplied within an agreed scope, respecting data and intellectual property rights.
Official specifications
NASA MODIS
Vegetation history, land surface temperature and burned-area archives. Each product has its own dates, resolution and quality flags.
Open source documentationCopernicus Sentinel-2
Detailed area analysis using available optical scenes. Clouds and snow limit observations.
Open source documentationUSGS Landsat
Long observation series and detailed change analysis. Comparisons across sensors require validation.
Open source documentationNASA FIRMS
Current satellite thermal anomalies. A hotspot is not equivalent to a separate fire, its area or an established cause.
Open source documentationCopernicus ERA5-Land
Historical climate context: reanalysis, not an operational weather forecast.
Open source documentationNASA NEX-GDDP-CMIP6
Regional climate scenario context, not a forecast of an individual forest’s condition.
Open source documentationH3
A shared spatial grid for comparing data. Cell size does not equal the accuracy of the original image.
Open source documentationFor comparisons of fire-related indices, use the USGS definition of NBR, including the correct band mapping for the sensor.
USGS: definition of NBRChecking payment
Returning from the payment form does not confirm payment. Forest OS is waiting for a verified server notification from Robokassa.
Order status
Retrieving order status…
What happens next?
- Once payment is confirmed, a report-generation task is created in the operations centre.
- Analysis uses only actual available data layers for the selected area.
- The PDF and receipt details are sent to the email in the order.
Payment incomplete
Money should not be considered received without server confirmation. The order can be reopened after the status check.
The payment has been cancelled or the payment form has returned an error.
