I downloaded the latest pbf file(dated 27-Aug-2020 23:37) from a mirror and read its header using a python wrapper to osmium (v3.0.1)
The sequence number was missing. Is this expected behaviour? In the documentation, all the replication fields in OSMHeader seem to be set as optional. What pbf files are expected to have these values set? asked 04 Sep '20, 09:37 M_T_ |
The sequence field in the headers are currently set only on extracts from Geofabrik. pyosmium-up-to-date also sets them when you update a PBF file. There is a good reason that the sequence number is not set on the official planet file: there is no exact sequence number that corresponds to the state of a planet file. Planet files are created independently of the change files. So the content of the planet might correspond to something like sequence number "4164164 3/4". When you want to use updates with a downloaded planet file, the usual way is to look at the creation time and find a change sequence number that is far enough in the past that you get all new changes that are not yet contained in the planet. You don't have to do the math yourself, pyosmium-get-changes, which is included in the python osmium package, can do that for you. Just run
and it prints a single number. This is the recommended sequence number where you should start with the updates. See the section on updating OSM data in the pyosmium manual for more information. answered 05 Sep '20, 20:25 lonvia AFAIU the sequence number you get from a call to
(07 Sep '20, 10:15)
M_T_
1
You can't directly translate to hourly/daily sequence ID. You need to compute the appropriate ID in the same way as for the minutely replication. Use the parameter
(12 Sep '20, 15:35)
lonvia
|