You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have massive points that almost fill the tile.
So the coordinate data takes the major size of tile.
Would the spec design new format for this situation?
For example, supposing the extent is 4096, it can use 4096 * 4096 bit matrix to store x and y.
if( bit(x, y) == 1), it has coordinate, else.....
And we can use array to store properties(number value?)., then compress them like being done in 3d tiles.
The text was updated successfully, but these errors were encountered:
I have massive points that almost fill the tile.
So the coordinate data takes the major size of tile.
Would the spec design new format for this situation?
For example, supposing the extent is 4096, it can use 4096 * 4096 bit matrix to store x and y.
if( bit(x, y) == 1), it has coordinate, else.....
And we can use array to store properties(number value?)., then compress them like being done in 3d tiles.
The text was updated successfully, but these errors were encountered: