Independent QGIS & RFC 7946 GeoJSON Evaluator — Paid GIS QA Pilot

We need one independent GIS practitioner for a paid, fixed-price technical pilot covering two separate workstreams:

LeafEngines Agricultural Intelligence v1.0.10: controlled QGIS Desktop plugin installation and workflow evaluation.
SoilCertify Phase 0: independent review of four frozen PDF/GeoJSON pairs covering U.S. and GB Summary and Detailed outputs, including field-level consistency and strict RFC 7946 review.
The products are independent. LeafEngines is not required to generate, reproduce, validate, or match SoilCertify reports, and SoilCertify users do not depend on LeafEngines. Optional complementary observations must not be presented as technical dependencies.

This is not unpaid testing, software development, remediation, implementation, or an endorsement. We need reproducible evidence from the named GIS professional who personally performs and signs the evaluation.

Controlled Environment
Plugin: LeafEngines Agricultural Intelligence v1.0.10
Frozen ZIP: qgis_leafengines-1.0.10.zip
SHA-256: ed0744ac690065c520821725835eeb7b08439464effbbbb086da952e7d70e676
OS: Windows 11 24H2, 64-bit
QGIS: official QGIS 4.0.0 Windows release
QGIS 4.0.0 is the exact base target—not the full 4.x compatibility range. macOS, Linux, other QGIS versions, additional builds, and post-fix retesting are outside the base scope unless separately authorized and funded.

LeafEngines v1.0.10 declares no external PIP packages. It uses the Python, Qt, GDAL/OGR, GEOS, PROJ, and network components bundled with QGIS; the evaluator must record their exact reported versions. No separate GDAL version is required beyond the approved QGIS package.

The plugin is not fully self-contained. Functional tests require internet connectivity and make HTTPS calls to LeafEngines services. Authenticated functions require an evaluator-specific temporary API key using the x-api-key header. The normal entry path is LeafEngines panel → Settings → API Key. The controlled configuration identifies no separate license activation beyond the temporary API key for this pilot.

LeafEngines is internationally used, but availability does not prove identical coverage or behavior in every jurisdiction. Record U.S. controlled behavior and GB exploratory behavior separately. Missing, unavailable, incomplete, access-limited, or jurisdiction-specific functions must remain explicit.

Workstream 1 — LeafEngines
Verify package identity; document installation, configuration, dependencies, permissions, and discoverability.
Capture first attempted use, first successful result, errors, warnings, blockers, and recovery steps.
Assess inputs, generated layers, attributes, CRS behavior, geometry roles, null handling, persistence, repeatability, and relevant exports.
Report installation success, execution, usable output, workflow fit, and format conformance separately.
Compare the tested workflow with the evaluator’s prior professional GIS workflow.
Workstream 2 — SoilCertify
Review a frozen eight-file package containing U.S. and GB Summary and Detailed PDF/GeoJSON pairs.

Compare matching PDF and GeoJSON fields.
Identify missing, null, inconsistent, or differently represented values.
Review data types, units, provenance, null meanings, jurisdiction applicability, geometry source, and coverage disclosures.
Distinguish raw, normalized, derived, estimated, and scored fields.
Validate each GeoJSON through a documented RFC 7946 method. Preserve the exact tool, version, command or menu path, settings, filename, hash, and actual output.
Opening successfully in QGIS does not establish RFC 7946 conformance.

ArcGIS Deferred
The ArcGIS browser comparison is not included in the base quotation because the controlled build is unavailable. Do not price or test the current public deployment. Future ArcGIS/QGIS comparison requires a frozen build and separate authorization and funding.

Required Work Products
Independent evaluation report covering the environment, prior workflow, installation, output behavior, PDF/GeoJSON comparison, RFC 7946 findings, strengths, defects, limitations, and unresolved items.
Reproducibility evidence bundle with relevant screenshots, redacted logs, validator methods and outputs, hashes, version records, and an evidence index.
Defect/acceptance matrix marking each authorized item Pass, Partial, Fail, Not Applicable, or Not Tested with a reason.
One real-world use case.
One workflow integration note.
One highest-priority improvement recommendation with its professional workflow consequence.
A negative finding can satisfy the milestone when specific, reproducible, evidenced, and in scope. Missing evidence must remain explicit. Use Not Tested—Access Not Available when access or documented regional coverage is unavailable, and Not Tested—Known Context for a supplied issue not independently encountered.

The detailed rubric, frozen manifest, evidence schema, and discrepancy classifications will be provided after shortlisting, award, and milestone funding.

Professional, Scope, and Security Boundaries
SoilCertify outputs are preliminary Phase 0 screening aids—not engineering certification, geotechnical investigation, foundation design, septic approval, cadastral survey, legal-boundary determination, permitting or lending decisions, or substitutes for authoritative data, field validation, and qualified professional review.

GeoJSON is an interoperable input used alongside authoritative cadastral, jurisdictional, project-controlled, and field-validated layers—not a replacement for them.

Without a separate funded milestone, do not modify code, fix defects, redesign or deploy interfaces, perform ongoing API debugging, build integrations or layers, procure datasets, conduct additional site studies, prepare endorsements, test other environments, or perform post-remediation retesting.

Never request, send, or expose credentials in proposals, normal Freelancer messages, documents, screenshots, logs, scripts, commands, recordings, or evidence bundles. Temporary evaluator access will be delivered securely only after award and funding and revoked after acceptance or suspected exposure. No production/admin, database, service-role, repository, payment, or personal-account credentials will be provided.

No project materials, credentials, or unpaid product tests will be provided before award and milestone funding.

Required Qualifications and Personal Performance
Hands-on experience with QGIS plugin QA, RFC 7946 validation, GDAL/OGR or another documented programmatic method, CRS and geometry validation, schema/provenance/null semantics, and reproducible GIS reporting. Development experience alone is insufficient.

The named bidder must personally perform and sign the evaluation. Agencies must identify the individual evaluator and confirm that no undisclosed substitute will perform the work.

Mandatory Proposal Format
Begin with GIS EVALUATION — PERSONALLY PERFORMED and answer using the same numbering:

Name, role, location/time zone, and confirmation you will personally perform and sign.
Confirm Windows 11 24H2, 64-bit, and official QGIS 4.0.0; state any setup limitation.
Describe one QGIS plugin you personally tested and its installation route.
Describe one GeoJSON conformance or data-quality review you personally performed.
Give exact RFC 7946 tools, versions, and command/script/settings/menu path. “Standard GIS tools” is insufficient.
Explain why “opens in QGIS” differs from “conforms to RFC 7946.”
Explain how you will preserve hashes, versions, timestamps, logs, screenshots, raw outputs, and an evidence index.
Describe a relevant parcel, site, environmental, land-use, or agricultural GIS workflow.
Provide or offer one redacted GIS QA report, defect log, or validation sample you personally prepared.
Quote LeafEngines and SoilCertify separately, plus any shared setup charge counted once; state combined price, earliest start, and realistic schedule.
List non-secret information needed after award.
Confirm the scope, security, evidence, and out-of-scope rules and that you will remain timely and engaged. Responsiveness is a selection factor.
Generic or incomplete proposals may not be considered. Written qualification comes before any call or award.

Paid Qualification and Terms
A shortlisted candidate may receive a small paid qualification milestone using redacted, non-production material, with its own scope, price, deliverable, and acceptance condition. It does not authorize the main work or provide production credentials or the full controlled package.

The two workstreams may be awarded together or independently. Substantive scope, acceptance, schedule, delivery, and payment communication must remain on Freelancer. No work starts until the applicable milestone is awarded and funded.