Hi,
On 11/21/2012 04:27 AM, Scott Crosby wrote:
Idea, why not put the entire state.txt file into the OSMHeader block?
I tend to view the structure of state.txt as an Osmosis implementation
detail and I'm not sure if it would be a good idea to require that PBF
parsers not only decipher the PBF, but also have knowledge about how
Osmosis builds its state.txt files.
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.
To be self-contained, it should be sufficient to include the "baseURL"
from configuration.txt, no?
So maybe:
optional string writingprogram = 16;
optional string source = 17;
optional sint64 timestamp = 18;
optional sint64 replication_timestamp = 19;
optional string replication_url = 20;
I don't know if the sequenceNumber from state.txt adds any value, if it
does then one could throw that in as well.
Bye
Frederik
--
Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33"
_______________________________________________
dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/dev
