Package: osmosis (0.49.2-2~bpo12+1)
Command line OpenStreetMap data processor
Other Packages Related to osmosis:
dep: [default-jre-headless]
Standard Java or Java compatible Runtime (headless)
dep: java17-runtime-headless
Package not available
dep: libcommons-logging-java
Package not available
dep: [libcommons-pool-java]
pooling implementation for Java objects
dep: [libplexus-classworlds-java]
Class loading utilities for the Plexus framework
dep: [libspring-beans-java]
modular Java/J2EE application framework - Beans
dep: [libspring-core-java]
modular Java/J2EE application framework - Core
dep: [libspring-transaction-java]
modular Java/J2EE application framework - transaction
dep: [libcommons-codec-java] (>= 1.15)
encoder and decoders such as Base64 and hexadecimal codec
dep: [libcommons-compress-java] (>= 1.22)
Java API for working with compression and archive formats
dep: [libcommons-csv-java] (>= 1.9.0)
Library for reading and writing CSV files
dep: [libcommons-dbcp-java] (>= 1.4)
Database Connection Pooling Services
dep: [libcommons-io-java] (>= 2.11.0)
Common useful IO related classes
dep: libguava-java
Package not available
dep: [libjpf-java]
Java Plugin Framework: plug-in infrastructure library for Java projects
dep: [libmariadb-java] (>= 2.7.6)
Java database driver for MariaDB and MySQL
dep: [libosmpbf-java]
Java access library for OpenStreetMap PBF file format
dep: [libpostgis-java]
Geographic objects support for PostgreSQL -- JDBC support
dep: [libpostgresql-jdbc-java] (>= 42.5.4)
Java database (JDBC) driver for PostgreSQL
dep: [libprotobuf-java]
Java bindings for protocol buffers
dep: [libspring-jdbc-java]
modular Java/J2EE application framework - JDBC tools
Download osmosis
| Architecture | Package size | Installed size | Files | Package |
|---|---|---|---|---|
| all | 919 KiB | 2.3 MiB | list of files | Download |
Percorsi file del pacchetto (0)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
No package-associated file paths were observed for the displayed build metadata.