Scott,
Scott Crosby wrote:
message HeaderBlock {
required HeaderBBox bbox = 1;
// Author, name, and version number of the dataset in this file. (to permit
// patches/updates to be incrementally applied)
optional string datasetauthor = 16; // TODO: WANT THIS?
optional string datasetname = 17; // TODO: WANT THIS?
optional int64 version = 18; // TODO: WANT THIS?
// Program generating this data
optional string writingprogram = 19; // TODO: WANT THIS?
}
To start regular updates after importing a full planet file, one
typicalle needs to find out which state.txt file on
planet.openstreetmap.org to copy. The current alogrithm for this is:
* decide whether you want daily, hourly, or minutely updates;
* find out the latest timestamp in your data set, or alternatively use
the time of dataset creation
* find the latest state.txt file from the appropriate directory that was
created before your own latest timestamp
* copy that to your Osmosis working directory
In order to make this really easy, a data file should (in order of
preference) either
* contain the information required to synthesize a state.txt file for
daily/hourly/minutely updates - then one would just have to extract that
information, save it to a state.txt file and start running Osmosis for
updates, or
* contain the URLs of the daily/hourly/minutely change files that would
have to be loaded to start regular updates, or
* contain the timestamp of dataset creation or time of most recent
object to allow manually looking up the proper state.txt file.
Bye
Frederik
--
Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33"
_______________________________________________
dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/dev
