On 02/02/2020 16:39, Yuri Astrakhan wrote:
* Anyone working on an evolving project like OpenMapTiles would attest
that the import schema constantly changes.
Indeed, but ...
Every time schema changes, one needs to download newest planet, import
it based on the new schema, and run diffs from that point.
... that's why I said "... and there are ways of keeping a *.pbf* up to
date" in my message. - the idea is to avoid large downloads wherever
possible (emphasis new in this message; won't make it to plain text
archive).
For more info see:
https://docs.osmcode.org/pyosmium/latest/tools_uptodate.html
or if that's somehow not an option:
https://wiki.openstreetmap.org/wiki/User:EdLoach#Osmosis_to_keep_a_local_copy_of_a_.osm_file_updated
(from a few years back)
* Automation / easy adaptation. Providing an out-of-the box way to
set up your own server is much easier if you have a tool that
automatically downloads and validates the planet file or a portion of it,
Sure - an automated process is much easier to follow than a manual
do-it-yourself one, but the fact that a process is automated doesn't
mean that it has to be wasteful. Ultimately, someone's paying for the
bandwidth that downloads from each of the mirrors at
https://wiki.openstreetmap.org/wiki/Planet.osm#Planet.osm_mirrors use,
so it seems only fair to not be profligate with it.
Best Regards,
Andy
_______________________________________________
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
