What is range and zoom really doing? about mapbox-unity-sdk HOT 7 CLOSED

@Naphier Apologies, the documentation is sort of nested: https://www.mapbox.com/mapbox-unity-sdk/docs/03-examples.html#mesh-generation-basics (documentation is still WIP).

Range essentially describes how many tiles you would like to load in each direction from the center tile. 1 x 1 x 1 x 1 will load a 3 x 3 grid of tiles. We could name this better 😏.

Zoom describes which zoom level you would like to request for each tile. See:

• https://www.mapbox.com/api-documentation/#retrieve-tiles
• http://wiki.openstreetmap.org/wiki/Slippy_map_tilenames

Regarding the calculations and conversions, the world scale factor is recorded in MapController as WorldScaleFactor. This is also what the local scale of the root object is set to. Our conversions.cs class contains a bunch of methods that might help you.

Alternatively, you may want to write your own implementation of MapController that uses TileCover. This makes it easy to get all the tiles in a geographic bounds.

Can you share more about what sort of map you're trying to build?

from mapbox-unity-sdk.

That description of range helps it to make sense.

So if I have a tile size of say, 100 and range of 1,1,1,1 I would expect a 300m square. But that's also dependent on zoom level. According to documentation I can request zoom level of 0 - 22 (would be good if you guys limited this with a Range attribute in the Unity inspector). If I request less than 5 all I get are black textures (sometimes ? mark textures). If I request higher than 18 then the snap y to zero doesn't seem to work properly (tiles are maybe out of range of the raycast?). If I request higher than 19 then not only does the snap to y no longer work, but I also get ? mark textures. This is using mapbox://styles/mapbox/satellite-streets-v9.

.

It seems that a zoom level of 17 is close to 1:1 when I'm using:

• Tile size: 200
• Zoom 17
• Range 5,5,5,5

Ultimately, I think it would be more useful to Unity devs to be able to simply define a Unity world unit to map meters ratio, overall map size in Unity units (i.e. meters for most), and pixel density for images. I'm less concerned with entering a geographic bounds than just having control over the map unit to Unity world unit ratio. Does this make sense?

from mapbox-unity-sdk.

So if I have a tile size of say, 100 and range of 1,1,1,1 I would expect a 300m square. But that's also dependent on zoom level.

This is not quite true. 100 represents how many units in unity each tile is. Zoom level plays no factor in this.

If I request less than 5 all I get are black textures

Known issue: #42, apparently due to crazy scale values.

If I request higher than 19 then not only does the snap to y no longer work, but I also get ? mark textures.

@brnkhy can you look into this snapping issue? Please note that zoom > 19 is technically only supported in certain locations.

Ultimately, I think it would be more useful to Unity devs to be able to simply define a Unity world unit to map meters ratio, overall map size in Unity units (i.e. meters for most), and pixel density for images. I'm less concerned with entering a geographic bounds than just having control over the map unit to Unity world unit ratio. Does this make sense?

If you ensure the localScale of worldRoot is 1, you will have a 1:1 scale with the real world (and now TileSize is a non-factor. Using this as your basis, you should easily be able to decide your own relative scale.

That said, it might make sense to create another implementation of MapController to perform the conversions you mentioned above (or maybe a different editor implementation).

from mapbox-unity-sdk.

@Naphier develop now has an ITileProvider and AbstractMap (which is not quite abstract yet 😏 ). Using these abstractions, you should be able to create your own implementations much easier. Let me know if I can help clarify or point you in the right direction.

from mapbox-unity-sdk.

Is there any reason for specifying the size of tile? It can be quite easily computed based on zoom. Each zoom has some specific resolution in meters per pixel of heightmap. Since we know the size of tile, which is 256, then given latitude, it is easily computed as 156543.03 meters/pixel * cos(latitude) / (2 ^ zoom).
For further reference: http://wiki.openstreetmap.org/wiki/Slippy_map_tilenames#Resolution_and_Scale

from mapbox-unity-sdk.

@janovrom

Is there any reason for specifying the size of tile?

Yes. We figure some developers will want control over the "scale" of their world. Gigantic worlds can cause all sorts of bugs. However, this is just one implementation (which is why we're in the middle of abstracting maps and tile providers). Most of these are application specific, and many developers have different needs.

Also:

from mapbox-unity-sdk.

Since we have added ITileProvider (and AbstractTileProvider), you can now easily create your own system for requesting/disposing of tiles.

from mapbox-unity-sdk.