ArticleScientific reports2026
SegFormer-based segmentation approach for landscape planning and overhead remote sensing image analysis.
Article in Scientific reports, 2026. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Not yet cited in PubMed.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
0 citing papers in PubMed.
No citing paper in PubMed yet.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
1 author.
Funding
No grant is acknowledged in the PubMed record.
Abstract
This study developed a semantic segmentation framework for landscape element analysis. The objective was to achieve high precision, structural stability, and computational efficiency in spatial information extraction. The framework was built on a Transformer architecture and adopted SegFormer as the core modeling paradigm. A Mix Transformer (MiT) encoder generated multi-scale spatial feature representations, while a Multi-Layer Perceptron (MLP) decoder performed cross-layer semantic fusion. At the architectural level, an Edge-aware Auxiliary Supervision mechanism was introduced to strengthen structural learning. Gradient information served as an explicit constraint, improving discrimination of boundary-sensitive elements such as roads and water bodies. At the training level, a Unified Label Mapping strategy and a Boundary Jitter Augmentation strategy were implemented. These strategies enhanced generalization stability across multi-source landscape datasets. To eliminate performance bias arising from distributional differences and inconsistent training settings, a Two-track Fair Comparison Protocol was designed. This protocol enforced unified training conditions while maintaining independent evaluation. Experiments were conducted on the Land-Cover in High-Resolution Visual Dataset (LoveDA) and a self-constructed landscape dataset. Under the unified LoveDA setting, the model achieved a Mean Intersection over Union (mIoU) of 76.5% across five key landscape categories. This result represents a 5.3% improvement over DeepLabV3+. For the Boundary F1-score, structurally sensitive categories showed clear advantages, confirming the effectiveness of structural supervision. During the inference stage, the edge auxiliary branch used in training was removed. Under a unified setting of a 512 × 512 input and a batch size of 1, the deployed model achieved 42.1 Frames Per Second (FPS), indicating that the structural gains were not obtained at the cost of a significant loss in inference efficiency. Overall, the performance improvements were primarily driven by the interaction between the structure-adaptive workflow and planning-oriented evaluation metrics. Network scaling alone did not account for the observed gains. The proposed framework offers a reproducible and engineering-feasible solution for structured spatial representation in landscape planning, remote sensing interpretation, and geospatial information analysis.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.