Give us a file, get it back in the format you need

Applying schema "Roads and transport by the OSM model: baseline classification", pick one file, the schema decides the rest

The project's first scenario (scenarios/roads-osm.json), taken as a portable schema: classifies any drawing that has road-network layers and writes the result to GPKG. No paths and no one publisher's layer names live here, applies_to checks by model CLASSES, not by a specific dataset.

We read DWG, DXF, MapInfo TAB, Shapefile, GPKG, GeoJSON, and a ZIP that holds them: we take the file and its sidecars out ourselves, and say exactly what we took. Upload limit, 300 MB.

How much we take on at all is counted from the memory of the container that will READ the file: DWG up to 345 MB, DXF and tables up to 1035 MB. A bigger file is refused right away, with a number, not left to die of memory in half an hour.

And separately, a limit by the NUMBER of features: we take up to 434110 of them. It matters more than size: a 20 MB drawing with a hundred thousand features is heavier than a 200 MB drawing with a thousand. We find out how many you have in the first seconds of reading and, if we cannot take it on, say so as a number, before the work, not after half an hour.

On the left, your layers as they are, with their own names. On the right, a rebuild: we work out WHAT is in the layers and assemble only what is needed, under common names. Not sure, take “as is”: nothing will be lost.

A browser notification can fail silently: permission revoked, tab closed, a strict browser setting. Email is the fallback. The address is deleted together with the job, in the same deletion as the file.

We do not store your data. The file is deleted as soon as it is no longer needed for processing. What we read, our model of the file, is deleted once the processing period ends (24 h). The final file exists only with you: we assemble it from the model at the moment of download, and keep it available for download no longer than 24 h. What stays with us afterwards is anonymized data only, statistics and the outcome of processing, counters, the data's schema, tied neither to the source file nor to you. Neither the source nor anything derived from it is passed to anyone. Among that anonymized data we also keep a salted fingerprint of your dataset's layer names, used only to notice when unrelated files share the same schema.

The file is not read without consent: this is checked here, on our server, not by a checkbox in the browser.

work plan, stages, queues, jobs and a diagram. Drawn from a file in the repository, there is no other source for it.