Download Pullara map in Cloud-Optimized GeoTIFF format
A map built from OpenStreetMap data, ready to download
Customize the map
Open this place's area in the constructor and adjust everything to your needs
Open in constructor →Map passport
What this map contains by default
This is how the map is built as-is — every setting can be changed in the constructor.
.tif
About Cloud-Optimized GeoTIFF
Map of Pullara in Cloud-Optimized GeoTIFF: 410 buildings, 49 km of roads, 33 points of interest — in the WGS 84 coordinate system, units are meters.
Which layers are in the file
This file for the selected area contains:
- Roads
- Buildings
- Water
- Points of interest
Geometry by layer
- Roads — drawn as lines in pixels, no separate features
- Buildings — drawn as filled pixels, no separate features
- Water — drawn as filled pixels
- Points of interest — drawn as icons in pixels
What the file carries
The Cloud-Optimized GeoTIFF file for Pullara: layers are flattened into one picture: objects become pixels and cannot be selected separately, OpenStreetMap tags are not kept — geometry and styling remain.
File size
The expected size of the Cloud-Optimized GeoTIFF file for Pullara is about 1.8 MB; the exact size depends on the chosen layers and area.
Coordinate systems
WGS 84 (EPSG:4326), selectable in the wizard
Units
Meters (projected in the chosen coordinate system)
| Category | Raster |
| File extension | .tif |
| Tier | Open Beta |
How to use Cloud-Optimized GeoTIFF for Pullara
- QGIS — Layer → Add Raster Layer; the file lands by its coordinates, and the overview levels make redrawing on zoom fast.
- Checking whether this is a real COG — the command rio cogeo validate map.tif, or gdalinfo, which will show the internal tiles and the list of overview levels.
- Cloud storage — upload the file to S3, Google Cloud Storage or Azure Blob and serve it over HTTPS: clients will read it in parts through range requests.
Programs that open Cloud-Optimized GeoTIFF
FAQ: Cloud-Optimized GeoTIFF for Pullara
How is COG different from regular GeoTIFF?
COG contains internal tiles and overviews, allowing reading only needed parts via HTTP range requests.
Where to host COG files?
On any cloud storage with range request support: AWS S3, Google Cloud Storage, Azure Blob.
Are there OSM objects and attributes in the file?
No, this is a raster: the map is baked into pixels. You cannot click a building and see its tags — for working with objects take GeoJSON, GeoPackage or Shapefile.
How do I make sure the file really is cloud-optimized?
Run rio cogeo validate map.tif — the utility will say outright whether the file conforms to the specification. The same is shown by gdalinfo: a correct COG has visible internal tiles and overview levels.
What compression and projection are used?
DEFLATE by default — lossless compression, safe for maps with text and thin lines; LZW, ZSTD, JPEG and WebP are also available. Georeferencing is done in WGS84.
