3D Tiles Viewer & Georeferencer (move + save tileset.json)
View a 3D Tiles model (tileset.json + b3dm), move it to the right WGS84 coordinates, two-point align it and save the new tileset.json. Free, in your browser.
Open a 3D Tiles model, place it on Korean satellite imagery at the right coordinates, and save the updated tileset.json — 100% in your browser.
No tileset loaded yet.
🔒 Your model is rendered locally; only basemap tiles are fetched.
View and georeference 3D Tiles locally
Select a folder containing a tileset.json and its .b3dm tiles (or pick the files directly).
The model renders in your browser with CesiumJS on a Korean VWorld satellite (or OpenStreetMap) basemap. If the tileset has a
root.transform, its current geographic origin is read; if not, you place it by entering an origin.
Move it to the right coordinates
Type a longitude, latitude and height (표고, orthometric — the geoid height is added automatically), or use two-point
alignment: click a point on the model, then click where it belongs. The model repositions live using an East-North-Up frame
with meridian-convergence correction for grid-authored Korean tilesets. Click any point to read its lon/lat, EPSG:5186 grid
E/N and orthometric height. Download the updated tileset.json with the new root.transform.
Is anything uploaded?
No. The model is read, rendered and repositioned entirely in your browser. Only the map basemap loads tiles over the network; your model and coordinates never leave your device.
Frequently asked questions
What files do I need?
A 3D Tiles set — a tileset.json plus the .b3dm tiles it references, including any nested tileset.json a large dataset is split across. Choosing the whole folder lets the viewer resolve the relative tile paths, and anything referenced but missing from your selection is named on the page instead of quietly leaving a hole in the model.
How does moving the model work?
It rebuilds the tileset root.transform from your chosen longitude/latitude/height (with geoid and, for grid-authored tilesets, meridian-convergence correction), or from a two-point alignment, then writes it back into a downloadable tileset.json. Only root.transform is rewritten, so a tileset that instead carries its placement in a child tile transform, or whose footprint is a region bounding volume (which the 3D Tiles spec does not transform), is flagged on the page rather than saved as a file that will not land where you put it.
Is my model uploaded anywhere?
No. Everything runs locally in your browser; only the map basemap (VWorld satellite or OpenStreetMap) is fetched over the network.