xivk
commented
10 years ago Thanks again for testing! :+1:
1) Probably a bug in how the objects are stored or how the zoom-offsets are calculated. 2) I would not add anything below 15, maybe 16 for some devices. The cost of reading the data at that level is bigger than the advantage of storing it a bit more efficiently for viewing at 18-16. Not sure about the lower levels (lower meaning lower zoom-numbers), would need to test, but usually I leave out every other level:
ex: 15,14,12,10,8,6,4,2
I'm writing a new performance test to check this stuff for the higher zoom levels.
I created a map with the command: ..\output\odp --read-pbf namibia.osm.pbf --write-scene scene=Namibia_Osm.vec.qmz css=default.mapcss cutoffs=18,17,16,15,14,13,12,11,10,9,8,7,6,5,4,3,2 (odp runs very fast now :) ) the map is only displayed from 7 to 18, from 2 to 6 _serializer.Search(_stream, box, results); returns 0 results. btw: is it neccessary to add all the levels to the cutoffs for best performance?