Input and output data (images + boulder labels, model setup, model weights and more) for the manuscript "Automatic characterization of boulders on planetary surfaces from high-resolution satellite images"

Open data API in a single place

Provided by Zenodo

Get early access to Input and output data (images + boulder labels, model setup, model weights and more) for the manuscript "Automatic characterization of boulders on planetary surfaces from high-resolution satellite images" API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2023.07.23 00:00
Created
2023.07.21
Available languages
English
Keywords
GIS, digitized boulder outlines
Quality scoring

Dataset description

File 1: raw_data_BOULDERING.zip Size: 8.8 GB Summary: It contains all of the rasters (planetary images) and labeled boulders (raw data): a boulder-mapping file, which is the manually digitized outline of boulders. a ROM file (stands for Region of Mapping), which depicts the image patches on which the boulder mapping has been conducted. a global-tiles file, which shows all of the image patches within a raster. There are multiple locations/images per planetary body. Structure: . └── raw_data/ ├── earth/ │ └── image_name/ │   ├── shp/ │   │ ├── <image_name>-ROM.shp │   │ ├── <image_name>-boulder-mapping.shp │   │ └── <image_name>-global-tiles.shp │   └── raster/ │     └── <image_name>.tif ├── mars/ │ └── image_name/ │   ├── shp/ │   │ ├── <image_name>-ROM.shp │   │ ├── <image_name>-boulder-mapping.shp │   │ └── <image_name>-global-tiles.shp │   └── raster/ │     └── <image_name>.tif └── moon/   └── image_name/     ├── shp/     │ ├── <image_name>-ROM.shp     │ ├── <image_name>-boulder-mapping.shp     │ └── <image_name>-global-tiles.shp     └── raster/       └── <image_name>.tif   File 2: best_model.zip Size: 624.7 MB Summary: This zip file contains all of the inputs and outputs required/obtained from the training of the BoulderNet Mask R-CNN model (model setup, augmentation pipeline, model weights, log during training, logged metrics): augmentation_pipeline.json (required as inputs for the training of the algorithm to apply augmentations). See https://github.com/astroNils and the MLtools repository for more information. Base-RCNN-FPN.yaml (base model setup file). config.yaml (complete model setup file, merge of the base and Mars-Moon-Earth setup file). Mars-MoonEarth-v050...yaml (model setup file). log.txt (log during training of the algorithm). model_0055999.pth (model weights at second last saving step) model_0063999.pth (model weights at last saving step) We advice the use of model weights model_0055999.pth (to avoid slight overfitting). File 3: Apr2023-Mars-Moon-Earth-mask-5px.zip (pre-processed input images) Size: 252.8 MB Summary: This zip files contains the input data (images and boulder outlines) for the train, validation and test datasets. See https://github.com/astroNils and the MLtools repository for more information in how-to-use the different files. The json folder contains json files that can be given as input (as a custom dataset) to the Detectron2 platform. The only differences between the two files is how the bounding boxes around masks have been generated. We advised to use "Apr2023-Mars-Moon-Earth-mask-5px.json". The pkl folder and pickle file includes some informations about the 950 image patches in our boulder dataset. The pre-processing folder contains all of the training, validation and test image patches and corresponding shapefiles. The shapefile folder is actually empty (it should not be there!). Structure: . └── preprocessed_inputs/   ├── json   ├── pkl   ├── preprocessing/   │   ├── train/   │   │   ├── images   │   │   └── labels   │   ├── validation/   │   │   ├── images   │   │   └── labels   │   └── test/   │       ├── images   │       └── labels   └── shp  
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks