<blockquote>
<blockquote>
<p>Does anyone know of any other mechanism for loading an osm file into the database?</p>
</blockquote>
<p>This is definitely a part of the OSM ecosystem that I have struggled to understand. It seems there are a whole suite of tools for taking OSM data which <em>have already been extracted</em> from the database defined in this repository and importing into <em>other tools</em>, but I haven't come across anything but <code>osmium</code> for importing data directly into the database defined in this repository.</p>
</blockquote>
<p>This is because there is no real use case that would require this (and actually reloading original OSM data is not something you would want to try except in a dire emergency), you are far better of with normal backups.</p>
<blockquote>
<blockquote>
<p>I imagine it's a fairly common task for small deployments.</p>
</blockquote>
<p>Just to clarify, is there another tool you'd recommend for "large deployments" or am I reading too much into you comment?</p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/gravitystorm/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/gravitystorm">@gravitystorm</a> if getting <code>osmium</code> updated and re-deployed widely is unrealistic, what tool do you think would be a good starting point for building a successor for this use case? Maybe <a href="https://github.com/omniscale/imposm3">https://github.com/omniscale/imposm3</a>?</p>
</blockquote>
<p>imposm does something completely different.</p>
<p>Dropping osmosis is a policy decision, explicit or not, it would be a small thing to pay somebody for further maintenance of osmosis. osmium is likely going to be taking over some of the functionality, but in the end suffers from the same issues (bus factor one).</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/2449?email_source=notifications&email_token=AAK2OLJNK5EAN54W346O3P3QW76IJA5CNFSM4JVAZWAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF6FCXY#issuecomment-561795423">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLLTRKTSYKU4B6WJJSDQW76IJANCNFSM4JVAZWAA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AAK2OLOMJBZOPCYRKJPWATTQW76IJA5CNFSM4JVAZWAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF6FCXY.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/2449?email_source=notifications\u0026email_token=AAK2OLJNK5EAN54W346O3P3QW76IJA5CNFSM4JVAZWAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF6FCXY#issuecomment-561795423",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2449?email_source=notifications\u0026email_token=AAK2OLJNK5EAN54W346O3P3QW76IJA5CNFSM4JVAZWAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF6FCXY#issuecomment-561795423",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>