GeoForms Flow WithAudio

Field data shouldn't live on paper, in three spreadsheets, and a folder of dropped pins. This is GeoForms. One platform to design the form, map the territory, send the work to the field — and ship clean, georeferenced data straight to your master database. In the next ten minutes, watch one project go from a blank screen to a closed loop — designed in the office, captured in the field on QField, validated by the team, and promoted to production. One tool, every step. Every workflow starts with the right hands. Our project designer signs in first — this is the role that builds the survey, sets the rules, and dispatches the work. Notice the operations dashboard the moment they land: active projects, captured records, published forms, field surveyors, geographic layers, registered organizations — the pulse of every program, in real time. Trends versus the previous period are right there next to each number, so anomalies surface before they become incidents. Now we sign out and switch to a second user — a field technician — with a completely different profile, a different home screen, and a tightly scoped view of what's theirs to capture. They never see another team's projects, and they can never touch data outside their assigned area. One platform. Multiple roles. Separated permissions. Full audit trail of who did what and when. But the data flows through one source of truth — and that changes everything downstream. Back as the designer, one click — Crear Proyecto — and we name our work. We set the projection: WGS 84, UTM zone 17 South. We pick the area of interest — the encuadre — that this project will operate inside. We lock the campaign window. Now the canvas. Every GeoForms project is a tree of groups and layers — the same way QGIS organizes a project, the same way your team already thinks. No new mental model to teach. No translation layer between what the office knows and what the field sees. We'll build two groups. The first, Base Map, is the visual ground truth that our surveyor will see on the tablet — imagery they can trust. The second, Field Data, is where every captured polygon and every typed value will land. Two groups, one mental model, ready in seconds. Inside Base Map, we drop in an Esri raster service. One URL — WMS, WMTS, or an XYZ tile feed — and the imagery streams in, georeferenced and aligned with our project's projection. No conversion. No GeoTIFF wrangling. No special license server to babysit. The same Esri imagery your office runs on, now mirrored in every surveyor's tablet. And because it's tile-based, it's fast even on a marginal connection. Now to the second group: Field Data. Two layers go inside. The first, Plots, captures geometry — every parcel the surveyor draws becomes a polygon record with its own attributes. Points, lines, polygons — every geometry type your work needs. The second, Owners, has no geometry. Pure data, joined to the parcels through a relation — one plot, many owners; one owner, many plots. Whatever the real world looks like, the schema mirrors it. No flattening, no shoehorning. For each layer, we open the field designer. Text, number, date, image attachment, catalog dropdown, boolean, file, coordinates, range, time — every field type you already use in QGIS and QField is right here, with the same data semantics and the same widget behavior. Whatever your team builds today, GeoForms can carry it tomorrow, with zero translation cost between desktop and field. Now the real power. Each field gets the controls a serious form needs. We rename labels so the surveyor sees plain language, not a database column name. We write helper descriptions for the moments when a fresh hire is staring at a question for the first time. We mark fields required so a record can't be submitted half-done. We set minimum and maximum to keep numbers honest. We write a default expression that auto-fills from another field — the same formula syntax QField evaluates out in the field, so what you preview here is what your surveyor sees there. We control visualization. Show this question only when this checkbox is on. Hide that whole section unless the plot type equals coffee. Make the form react to the answers, instead of overwhelming the user with everything at once. And we wire up dependencies. Pick a country, and the city dropdown filters itself — only that country's catalog appears. Pick a crop, and the variety list narrows. No code. No reload. The kind of cascade that used to mean a developer ticket and a week of waiting — now built right here, by the form designer, in seconds. Before we send anything out, we say who can touch it. We assign two field technicians to this project, each scoped to their own Encuadre — their own area of interest on the map. They get exactly the right layers, in exactly the right region. No accidental edits outside their assignment, no curiosity-clicks on someone else's data.