[email protected] writes: > Hi all, > > as the API 0.6 is on the air now I'd like to bring up t...@h migration to 0.6: > As far as I can see t...@h with 0.5 is still working, but has some > disadvantages: > - the only leftover 0.5 data source is XAPI with > http://www.informationfreeway.org/api/0.5/*[bbox=<BBOX>] > - the data is outdated (i.e. no new 0.6 changes get there) > > The migration would maily be just to set "OSMVersion" to "0.6" in > "general.conf": I've already tried this and it worked properly. Running > the client in 0.6 version there's only a warning from area-center > "Expected version 0.5 but received 0.6.", but that can be ignored > momentarily. > The disadvantage of a migration to 0.6 _now_ would be in my point of > view that at the moment the main API server would be the only > (realtively slow) data source, because as far as I can see XAPI and ROMA > are _not_ migrated to 0.6 yet (mainly because the minute planet diffs > are not yet available and bretth is sleeping right now). > So I'd opt for staying at 0.5 for at least another day.
Do ROMA and TRAPI need to be migrated to API 0.6 in order to be able to read 0.6 diffs? If so t...@h can not use them anyway after the main API switch because they would not be able to update themselves. Otherwise, OSMVersion is substituted into the download URLs for a placeholder (%v I believe). This placeholder could just be replaced by the API version in the config file to make the client download from different API versions from different servers. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
