Mobile App
Area search, map layers, pasture profile, analytics, favourites, user-defined areas and a PDF report.
Digital pasture monitoring powered by GIS, satellite data and mobile fieldwork.


Pasture boundaries, water resources, satellite trends, soil and climate data were scattered across different sources. Specialists needed fast mobile access to territory information, while administrators needed a safe way to update GIS data without releasing a new application version.
KazPasture brought the mobile application, satellite analytics and a separate web administration panel into one connected system: from selecting a territory on the map to viewing its analytical profile, receiving recommendations and publishing updated geospatial data.
Area search, map layers, pasture profile, analytics, favourites, user-defined areas and a PDF report.
NDVI, precipitation, soil, elevation, temperature, tiles, time series, recommendations and a two-tier cache.
Editing water sources and zones, drafts, versions, publishing, rollback, users and system settings.
The map displays pasture boundaries, administrative districts, water sources and watering zones. Users enable thematic layers, locate their position and select the territory they need.


For each selected pasture, the system compiles a complete profile and presents indicators in cards, charts and tables.
The values shown on the analytics screen are illustrative; the interface and implemented indicator set are real.

MapLibre GL displays pastures, water sources and watering zones in the browser. Administrators can add, edit and remove water sources, draw circular zones and filter features by the current map extent.

Geodata changes do not appear in the mobile application immediately. An administrator prepares a draft, publishes a new version and can restore the previous state when necessary.

The dashboard shows the status of Google Earth Engine, memory/file cache, active MapIDs, users and pre-caching completeness. TTL is configured separately for different types of resource-intensive data.


The base map and boundaries are available without having to load all geometry from the server.
The API returns geospatial objects for the visible area, reducing data transfer and rendering overhead.
Frequently requested satellite analytics results are served quickly from process memory.
The second layer retains heavy data between separate requests.
Pre-caching prepares pasture data before users request it.
Cache lifetimes are configured separately for NDVI, soil, precipitation, tiles and recommendations.
The two backend services can scale independently: database operations do not compete within the same process with NDVI, tile and time-series calculations.
Material/Cupertino UI, Provider, Secure Storage and SharedPreferences.
latlong2, proj4dart, geolocation and device permissions.
TypeScript, Tailwind, Zustand, Axios, Radix UI and MapLibre GL 4.
Pydantic, SQLAlchemy Async, asyncpg, GeoAlchemy2 and Shapely.
Alembic, GiST indexes, BBOX and spatial functions.
NDVI, imagery, tiles, climate indicators and time series.
fl_chart, printing, share_plus and OpenAI-compatible API.
Docker Compose, reverse proxy, health endpoints and Render Blueprint.
Short and long sessions; refresh tokens are rotated and can be revoked.
Passwords are never stored in plain text and are verified against a secure hash.
Administrators can edit and publish content and manage users.
The backend validates the structure and types of incoming API data.
Sensitive routes are protected by rate limiting.
API access is restricted to approved frontend origins.


Users can view the map as guests and synchronise favourites after signing in. Settings include language, data source, administrative boundaries and local cache.



Vite warns that the map editor's GIS chunk exceeds 500 kB. This does not prevent the build, but identifies the next optimization step: further code splitting. The supplied materials do not include load tests or verified production KPIs.
KazPasture combines mobile fieldwork, a spatial database, satellite analytics and controlled data management. Specialists gain clear territory profiles, managers receive a consistent assessment format, and administrators can safely publish and roll back GIS changes.
The architecture can support a regional monitoring system, an agricultural analytics product or another platform that combines field data with intensive computation and mapping.
We will analyse the data and field processes, design the architecture and build a manageable solution.
Discuss the Project ↗Back to Case Studies