[OSM-dev] Timestamp in PBF files

[Scott Crosby]

Idea, why not put the entire state.txt file into the OSMHeader block?

/* Contains the file header. */

message HeaderBlock {
  optional HeaderBBox bbox = 1;
  /* Additional tags to aid in parsing this dataset */
  repeated string required_features = 4;
  repeated string optional_features = 5;

  optional string writingprogram = 16;
  optional string source = 17; // From the bbox field.
  optional sint64 timestamp = 18; // Unix-Time encoded into varint.
  optional string osmosis_update_state = 19; // Encoding of the state.txt file.
}


One thing I don't like about it is that the state.txt file is not
self-contained:

#Tue Nov 20 19:02:18 UTC 2012
sequenceNumber=1668
timestamp=2012-11-20T19\:00\:00Z

It should have a planet URI (or a planet URI and a list of mirrors) of
what planet it corresponds to. That way a user merely needs to say
'update planet' and everything else can be automated.

Scott


On Tue, Nov 20, 2012 at 2:50 PM, Dennis Luxen <dennis.luxen at gmail.com>wrote:

> Hello,
>
>
>  Yes. Bascially "whatever was in Osmosis' state.txt file at the time this
>> file was created".
>>
>
> This is the use-case I had in mind when experimenting with time-stamps in
> PBF. Updating self-contained PBF files through Osmosis is a major advantage
> to using state.txt files. I, for one, plan to support such a time-stamp in
> OSRM from day one (or two).
>
> --Dennis
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20121120/5fe027bd/attachment.html>