|
From: James T. <zak...@ma...> - 2017-01-26 12:28:26
|
> On 26 Jan 2017, at 08:18, Torsten Dreyer <To...@t3...> wrote: > > That looks like terrasync is trying to fetch osm data for e000n50 which does not (yet) exist on the server. > It should be a perfectly legal case and I think the terrasync client should know beforehand that the data is not there as the .dirindex did say so: > http://dream.t3r.de/fgscenery/Buildings/.dirindex > > Rebecca, does the terrasync process proceed and ignores the error? > James and/or Stuart, I think we could use the .dirindex entries and not try to load that osm data for a nonexistant path. Missing files should be ignored and we carry on. Unfortunately terraSync currently starts syncing below the level of the layer directories - it never actually syncs 'http://dream.t3r.de/fgscenery/Buildings/.dirindex’, but rather looks for a sub-dir beneath that. The same thing would happen for an Objects or Terrain dir, there is nothing special about the new layers here, I believe. (Stuart, unless you have changed that?) (This is also why terrasync makes rather too many .dirIndex poll requests on startup, since it doesn't just check the top level indices) I have local patches to improve this, but I have not been able to test them out to my satisfaction, but I can share the change if people are interested. Kind regards, James |