District-Level Food Environment Indicators and Social Vulnerability in S\~ao Paulo

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.26299v1 Announce Type: cross Abstract: Urban food environments may reflect broader socioeconomic inequalities, but district-level evidence remains limited in Brazilian cities. This study examined whether indicators of food retail and street-market availability discriminate between levels of social vulnerability across the 96 districts of S\~ao Paulo. We conducted an exploratory cross-sectional ecological analysis integrating the S\~ao Paulo Social Vulnerability Index (IPVS), establishment records from the Rela\c{c}\~ao Anual de Informa\c{c}\~oes Sociais (RAIS), and street-market data from CAISAN. Census-sector information was aggregated at the district level. Twenty districts without an IPVS classification were excluded, resulting in 76 observations. The outcome distinguished districts classified as IPVS level 1 from those classified as levels 2--7. Predictors described the densities of healthy and unhealthy food establishments, the number of street markets, and the availability of establishments selling fresh or in natura food. Eight conventional machine-learning classifiers were evaluated using leave-one-out cross-validation. Reported mean F-scores ranged from 0.62 to 0.75, with XGBoost obtaining the highest value. In the Random Forest model, the densities of healthy and unhealthy food establishments jointly accounted for approximately 60% of the total impurity-based feature importance. These findings indicate that publicly available food-environment indicators contain information associated with the district-level distribution of social vulnerability. …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.26299
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.