Create tasks ready to use in PyBossa.
- you may use test_geometry.kml for this
- your results should look like aoi.png, grid.png, tiles_grid.png for zoomlevel=18, width=480, height=640
- Define the area of interest and get a .shp, .geojson, .kml file of it. Infile projection: EPSG 4326 (WGS84)! (e.g. here: https://osm.wno-edv-service.de/boundaries/)
- result: aoi.shp
- Find all tiles that intersect with your area of interest. Specify a zoomlevel. Use the script create_tiles_grid.py.
- input file: aoi.shp
- result: aoi_tiles_grid.shp
- Download all tiles. Specify an output directory. Use the script get_tiles.py.
- input file: aoi_tiles_grid.shp
- result: many .png files in the output directory you specified
Use script create_tiles_grid.py
- Takes two arguments:
- An input file containing an Areo of Interest polygon
- A tile zoom level
For example, you might create a polygon in Google Earth surrounding the area you want to get volunteers to look at, export that polygon as a KML called myArea.kml. Then navigate to the create_pybossa_tasks folder and type the command:
python create_tiles_grid.py /path/to/myArea.kml 18
A CSV file will be created, containing the fields:
- WKT (Well Known Text): a set of 5 points in lat/long defining the area of each tile
- TileX (integer): the x-coordinate of the tile, not in lat/long but the ordinal number of the tile column (i.e. 4324 meaning the 4324th column of tiles from the left)
- TileY (integer): the y-coordinate of the tile (as above)
- TileZ (integer): the zoom level of the tile (which will be the same as you specified as an input argument)
- URL: the individual URL of each tile
- internal-id (integer): a simple counter to help keep track of the tiles in the particular set you've generated (placed at the end and named internal-id to avoid conflicts with unique task IDs in the app's tasking system)
A KML file will also be created showing the tile squares.
The CSV and KML will be created in the same folder as the input AOI file, with "_tiles.csv" and "_tiles.kml" appended to original filename.
- Define the area of interest and get a .shp, .geojson, .kml file of it. Infile projection: EPSG 4326 (WGS84)! (e.g. here: https://osm.wno-edv-service.de/boundaries/)
- result: aoi.shp
- Create grids that have your custom resolution and intersect with the area of interest. Specifiy width, height and zoomlevel. Use the script create_custom_grid.py.
- input file: aoi.shp
- result: aoi_grid.shp
- Find all tiles that intersect with your grids. Specify a zoomlevel. Use the script create_tiles_grid.py.
- input file: aoi_grid.shp
- result: aoi_grid_tiles_grid.shp
- Download all tiles. Specify an output directory. Use the script get_tiles.py.
- input file: aoi_grid_tiles_grid.shp
- result: many .jpeg files in the output directory you specified
- Stitch the tiles together and clip to your grid extent. Specify a directory with the png files of the tiles, an output directory and an compression modus. Use the script stitch_tiles.py.
- input file: aoi_grid.shp
- result: beautiful .jpeg files that fit to your needs in the output directory you specified
- calculate grid polygons from given input file, area of interest (.shp, .geojson, .kml)
- grid polygon size adjusted to specific resolution (e.g. 480x640 pixel)
- grid polygon size adjusted to specific zoomlevel
- two output files: e.g. polygon_grid.shp (for use in your GIS) and polygon_grid.csv (to upload in PyBossa)
- polygon_grid.csv contains: id;wkt_geometry;zoomlevel;width;height
- polygon_grid.shp and polygon_tiles_grid.geojson contain fields 'width', 'height', 'zoom'
- polygon_grid.kml contains field 'description' with 'width_height_zoom' as value
How to use the script create_custom_grid.py:
- example run: python create_custom_grid.py test_geometry.shp 480 640 18
- four arguments mandatory:
- input file: e.g. polygon.shp, polygon.geojson, polygon.kml
- device width in pixel: e.g. 480
- device height in pixel: e.g. 640
- zoomlevel: 1- 20
Constraints:
- requires python packages ogr, osr
- supported input file formats: .shp, .kml, .geojson
- input file projection: EPGS 4326 (WGS 84)
- get geometry of all tiles that intersect with input file, area of interest
- two output files: e.g. polygon_tiles_grid.shp (for use in your GIS) and polygon_tiles_grid.csv
- polygon_tiles_grid.csv contains: id;wkt_geometry;TileX;TileY;TileZ
- polygon_tiles_grid.shp and polygon_tiles_grid.geojson contain fields 'TileX', 'TileY', 'TileZ'
- polygon_tiles_grid.kml contains field 'description' with 'TileX_TileY_TileZ' as value
How to use the script create_tiles_grid.py:
- example run: python create_tiles_grid.py test_geometry.shp 18
- two arguments mandatory:
- input file: e.g. polygon.shp, polygon.geojson, polygon.kml
- zoomlevel: 1- 20
Constraints:
- requires python packages ogr, osr
- supported input file formats: .shp, .kml, .geojson
- input file projection: EPGS 4326 (WGS 84)
- download all tiles as .jpeg file for given tiles grid polygon
- save files to specified output directory
- check if files are already stored in output directory and will only download tiles that do not exist in the directory (when script exits, e.g. due to connection error, it will start from where it failed and will not download all the tiles again)
- requires file 'api_key.txt' with (BingMaps) api key in the same directory!
How to use the script create_tiles_grid.py:
- example run: python get_tiles.py test_geometry_tiles.shp tiles_directory
- two arguments mandatory:
- input file: e.g. polygon_tiles_grid.shp, polygon_tiles_grid.geojson, polygon_tiles_grid.kml, polygon_tiles_grid.csv
- output directory: e.g. directory_path
Constraints:
- requires python packages ogr, osr, urllib, numpy
- input file must be in a format according to the result of the script create_tiles_grid.py
- supported input file formats: .shp, .kml, .geojson, .csv
- input file projection: EPGS 4326 (WGS 84)
- requires file 'api_key.txt' with (BingMaps) api key in the same directory
- creates custom JPEG-files that fit to input grid
- find all tiles within one input grid geometry
- stitch all tiles together
- extract pixels that intersect with input grid geometry
- resulting JPEG-file has the same size as specified in the input grid (e.g. 360x480 pixels)
How to use the script stitch_tiles.py:
- example run: python stitch_tiles.py test_geometry_grid.shp tiles_directory stitch_directory JPEG
- four arguments mandatory:
- input file: e.g. polygon_grid.shp, test_grid.geojson, polygon_grid.kml
- tiles directory: e.g. tiles_directory
- stitch directory: e.g. stitch_directory
- compression: e.g. JPEG or None (for more information see: http://www.gdal.org/frmt_gtiff.html)
Constraints:
- ...
- adjust the file "simple_map.html"
- change the geometry in line 12, e.g. copy and paste a single geometry from your output .csv file
- (adjust the height and width of the map in line 46, so that they fit to the height and width you specified before)
- open the file in your webbrowser
Get a cloud server running Ubuntu 14.04 64-bit. Go through the usual securing, updating, and create a user.
Now you need to install GDAL. First add the UbuntuGIS repository. You need the 'unstable' repo as the stable one is not updated for Ubuntu 14.04:
sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable
sudo apt-get update
Then install the gdal libraries themselves:
sudo apt-get install gdal-bin libgdal-dev python-gdal
Now install Git so that you can clone this repo
sudo apt-get install git
Now grab the repo and change directory into it
git clone https://github.com/mapswipe/create-pybossa-tasks.git
cd create-pybossa-tasks/
You'll need an API key to generate useable URLs for some tile servers. The API key needs to be copied into an otherwise empty text file that the script can read (we're not including API keys in the code because you should get your own, not use ours, which could get us in trouble if you use it in contravention of the tems of service of the tile server)! For Bing Maps, for example, follow the instructions on https://msdn.microsoft.com/en-us/library/ff428642.aspx to get a key. Copy the text your api key, and place it in am otherwise empty text file called api_key.txt in the create-pybossa-tasks directory.