Plant detection dataset from Mapillary images in Martinique

This dataset contains automated plant identification results derived from onboard vehicle (wardriving) camera data in Martinique, using Mapillary imagery and the Pl@ntNet API for species recognition. This dataset contains results of automated queries to the Mapillary API for a large bounding box covering Martinique. The bounding box coordinates were set to [-61.3, 14.3, -60.8, 14.9], and the queries were performed on 2026-01-08. In comparison with the v1 of this dataset, more image metadata were retrieved from Mapillary service, as undocumented erroneous limitations of image retrieval number were in order at the time of the building of the v1 dataset. Each returned Mapillary image was then sent to the Pl@ntNet API using the whole Pl@ntNet flora to attempt automatic identification of the plant visible in that image. The produced v2 dataset, assembled_detection_results_Mtq_flora_all_v2.csv, possesses 182,493 lines and is stored as a CSV file with one row per image. Below is a description of each column. The dataset: image_id A unique identifier for the Mapillary image. Images can be accessed via the Mapillary web interface by accessing the URL https://www.mapillary.com/app/?pKey=XXXXXX&focus=photo where XXXXXX is the image_id. lon Longitude of the image (WGS84). lat Latitude of the image (WGS84). capture_date Unix timestamp (in milliseconds) corresponding to the date/time the image was captured. computed_compass_angle Compass angle after running Mapillary image processing. computed_rotation Corrected orientation of the image by Mapillary. creator The Mapillary username and user ID who owns and uploaded the image. best_match_scientific_name The top-ranked plant species name returned by Pl@ntNet. If the field is “Not Found,” it means the Pl@ntNet API did not return a valid species match (e.g., status code 404). best_match_probability Probability (score) associated with the best_match_scientific_name, as provided by Pl@ntNet. May be empty or zero when no valid species was found. plantnet_data A JSON string containing the full set of results from Pl@ntNet. Includes details such as predicted organs, alternative species suggestions, taxonomic information, and associated metadata. Data Collection Method The Mapillary API was queried systematically across the bounding box ([-61.3, 14.3, -60.8, 14.9]) on 2026-01-08 using a 0.01 x 0.01° sliding window approach to overpass Mapillary API limits, retrieving hypothetically all available images taken along roads or other traversable paths. For each image, the latitude, longitude, capture date and basic photo geometry parameters were extracted. Each image was then submitted to the Pl@ntNet API for plant identification. Only the best match (top-ranked species) and the associated probability are recorded in specific columns, while the entire Pl@ntNet response is stored under plantnet_data. Notes and Caveats Single-species assumption: Each image is mainly labeled with at most one best match species. In reality, scenes may contain multiple plant taxa, or the model would label the image with multiple putative classification results ; however, for simplicity, this dataset focuses on the top match returned by Pl@ntNet. Full Pl@ntNet API results are nevertheless stored in the plantnet_data column if needed. Spatial bias: Data covers only roads and areas with Mapillary coverage at the time of querying. Temporal mismatch: The capture_date of each image can vary widely; it is not uniform across all images. This can introduce seasonal or inter-annual discrepancies in plant appearance. Accuracy: Automated identification may yield false positives or imprecise probabilities, especially if the plant is partially obscured, out of focus, or not a common species in Pl@ntNet’s training set. Licenses and usage: Mapillary imagery is subject to CC-BY-SA licence (see this page). Pl@ntNet usage data follows Pl@ntNet’s license and usage policy. Acknowledgments The Mapillary platform for providing access to street-level imagery and enabling community-based data collection. The Pl@ntNet team for making plant identification services available via API. This dataset is released for research and educational purposes. Users are encouraged to cite this deposit if it contributes to any publications or projects.