https://github.com/krithin/tileguide
Visualize slippy tile bounds over a mapbox map.
https://github.com/krithin/tileguide
Last synced: about 1 year ago
JSON representation
Visualize slippy tile bounds over a mapbox map.
- Host: GitHub
- URL: https://github.com/krithin/tileguide
- Owner: krithin
- License: gpl-3.0
- Created: 2019-12-22T03:28:04.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2023-01-24T19:24:08.000Z (over 3 years ago)
- Last Synced: 2024-10-29T07:02:49.422Z (over 1 year ago)
- Language: Go
- Size: 25.4 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# tileguide
Visualize slippy tile bounds over a mapbox map.
This supports XYZ tiles in the format used by [OpenStreetMap](https://wiki.openstreetmap.org/wiki/Slippy_map_tilenames) and [Google Maps](https://developers.google.com/maps/documentation/javascript/coordinates#tile-coordinates), which is notably different from the [TMS scheme](https://gist.github.com/tmcw/4954720) used by some other services.
See it in action: https://onetwotwo.sg/tileguide
## Motivation
I often work with tiled geospatial datasets (whether that's raster satellite imagery or vector tiles containing information about a road network). Getting tile references right when working with external datasets is occasionally challenging, so I created this tool to help visualize standard [OSM](https://wiki.openstreetmap.org/wiki/Slippy_Map) / [Mapbox](https://docs.mapbox.com/vector-tiles/reference/)-compatible [slippy tile](https://en.wikipedia.org/wiki/Tiled_web_map) numbers to make it easier to compare them to the tile identifiers used in an dataset.
## Usage
You can use an existing, deployed instance of this tool at https://onetwotwo.sg/tileguide.
Alternatively, deploy it for yourself with Docker.
### Deploy with docker
1. Set up the tileguide server:
```
docker build -t krithin/tileguide .
docker run --rm -p 8080:8080 krithin/tileguide:latest
```
Optionally, instead of using 'docker run' you can set up a systemd service to run this container on startup, using the included tileguide.service file.
1. Move `index.html` somewhere where your HTTP server can read from it.
1. Modify `index.html`:
1. Set `mapboxgl.accessToken` to your [Mapbox access token](https://docs.mapbox.com/help/how-mapbox-works/access-tokens/)
1. Set `tileguide_server_url` to point to your tileguide server from step 1.
That's it!
### Manual deploy
As an alternative to the docker build you can also clone this repository into your `$GOPATH` and use standard golang tooling (`go install && go build`) to build the server.