Michael Bechtold - 3 days ago

Hi Robert,
coming back to your ask, here are my comments (assuming that you kept the zip file with the java patches as well as the .md):
1) original MOBAC 2.3.x and betas fail at the border areas between two or more layers with mapsforge maps: one of the pair "wins" and can leave part of bordering tile blank. The fix patch merges the "overlapping" tiles taking all relevant data from both. This also includes a "debug" feature by which you can specify x/y/z and a target directory to dump each layer contributions as well as the final tile as files in that directory (heavily used in the fix development for this issue).
2) hillshading you already incorporated from my earlier delivery in July
3) overcoming the partially emotional discussion from earlier years, this patch leaves MBtiles strict rules as a default, but allows earlier MOBAC behaviour via an optional setting
4) in the original MOBAC log file it was nearly impossible to tell which entry came from which job. This patch attributes the log entries with the job identifier (profile).

Does this make sense?
Cheers
Michael

 

Last edit: r_x 3 days ago
OAM-patches-for-Robert-handover.zip