Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Feb 19, 2015
  1. gdal.py: Properly deal with Web Mercator equivalent projections

    Maxime Dupuis authored
    There are a whole bunch of equivalent projection to EPSG:3857. Let OSR deal
    with them.
  2. Bumped version to 1.2.0

    Maxime Dupuis authored
Commits on Dec 16, 2014
  1. gdal.py: VRT.render() now uses BIGTIFF=IF_SAFER.

    Maxime Dupuis authored
    If the uncompressed size of the GeoTIFF is bigger than 2GB, GDAL will create
    a BigTIFF.
  2. Style fixes all around.

    Maxime Dupuis authored
Commits on Jan 29, 2014
  1. gdal.py: Datasets deal with ESRI Web Mercator projections properly.

    Maxime Dupuis authored
    If the Dataset's projection isn't recognisable by OSR, try to determine its
    EPSG code, try to identify an equivalent ESRI code instead. If it succeeds,
    the SpatialReference returned will be based on a EPSG one.
Commits on Jan 13, 2014
  1. gdal.py: Deal with ESRI Web Mercator projections properly.

    Maxime Dupuis authored
    Added two ESRI WKID in the constants file along with their equivalent EPSG
    code.
Commits on Jan 8, 2014
  1. gdal.py: Fix a tile alignment problem.

    Maxime Dupuis authored
    Some times, when upscaling and slicing a partial world, the bottom TMS extents,
    which is used to determine the Y position of tiles, would be wrongfully
    rounded down, thus rendering the tiles exactly 1 tile downward from where
    they should be on the map.
    
    Rounding the calculations of the TMS extents before converting the floating
    point values into integers fixes the problem.
Commits on Nov 26, 2013
  1. Change default projection from EPSG:3785 to EPSG:3857.

    Maxime Dupuis authored
    EPSG:3857 is understood by Proj4 and thus understood by GDAL. It is also the
    projection that is used in most web apps, such as Google Maps or Microsoft
    Bing. Having the default to EPSG:3785 is not good.
Commits on May 29, 2013
  1. @sfllaw

    Version 1.1.0

    sfllaw authored
Commits on Apr 9, 2013
  1. vips.py: Verifying width and height of the upsampled image against an…

    Maxime Dupuis authored
    … epsilon
    
    We might have to deal with floating point errors when computing the new
    width and height of the upsampled image. Using an epsilon makes sure that we're
    within an acceptable integer range.
    
    After verifying that, we round the resulting width and height, and int() them
    before continuing normally.
  2. renderers.py: Encode the output file names.

    Maxime Dupuis authored
    Vips doesn't like to receive unicode strings, so we encode the temporary file
    names when rendering the tiles.
Commits on Mar 26, 2013
  1. @sfllaw

    test_scripts.py: Use gdal2mbtiles/main.py for testing script execution

    sfllaw authored
    Since we removed scripts/gdal2mbtiles, we need something to run
    against before we install the console entry point.
Commits on Jan 10, 2013
  1. Remove scripts/gdal2mbtiles as the entry point is defined by setup.py

    Maxime Dupuis authored
    Also, configure logging by default.
Commits on Dec 20, 2012
  1. vips.py: Proper band sizes, copy buffers in ReadAsArray to prevent co…

    Maxime Dupuis authored
    …rruption
    
    The band's X and Y size was not referring to the dataset, so if you got a
    handle on the band and then scaled the dataset, the X and Y sizes were not
    changed and were thus wrong. Always report the X and Y sizes from the dataset.
    
    There was a bug in the band and dataset ReadAsArray methods where if you tried
    to read from the buffer, the values could be modified because the ndarray
    returned was referring to the direct buffer in memory. Copying the buffer
    before returning the ndarray is the correct thing to do.
Commits on Dec 14, 2012
  1. @sfllaw

    Package gdal2mbtiles

    sfllaw authored
  2. @sfllaw
  3. @sfllaw
Commits on Dec 12, 2012
  1. Adjusted the number of pixels when upsampling to not lose any data.

    Maxime Dupuis authored
    When upsampling, if the scaling ratios cause the number of pixels of the
    output image to be a fraction of a pixel, we round up so we don't lose any
    data.
    
    Before, we were rounding the number of pixel to the closest integer, but that
    means that we could lose up to half a pixel worth of data.
    
    This shouldn't have much of an impact on the output image, especially when
    using nearest neighbour.
Commits on Nov 28, 2012
  1. vips.py: Fix typos.

    Maxime Dupuis authored
  2. Rename GetTileScalingRatios to GetScalingRatios.

    Maxime Dupuis authored
Commits on Nov 23, 2012
  1. @sfllaw

    mbtiles.py: Use an in-memory journal by default.

    sfllaw authored
    We don't use large transactions anyway, so we can save time writing to
    disk, at the cost of safety.
  2. @sfllaw

    Move zoom_level offset handling to MbtilesStorage.

    sfllaw authored
    The old implementation, where we had the tiles view compute the
    offset, was architecturally cleaner but slower because SQLite had to
    scan the entire map table before it could locate a single tile.
    
    Instead, there are only two lookups now, directly from the index,
    because the zoom_level for the map table is already offset when we
    write the file.
  3. @sfllaw

    helpers.py: x-minzoom and x-maxzoom metadata extensions

    sfllaw authored
    Because TileJSON offers minzoom and maxzoom metadata, we add this to
    the MBTiles metadata to make serving this information
    quicker. Otherwise, the TileJSON server would have to query the tiles
    table for this information.
Commits on Nov 22, 2012
  1. @sfllaw
  2. @sfllaw
  3. vips.py: Support for VipsBand in VipsDataset and ReadAsArray.

    Maxime Dupuis authored
    A VipsBand is a band that belongs to a VipsDataset which you can read from
    using ReadAsArray, just like a normal GDAL band.
    
    Other reading methods, such as ReadRaster and ReadRaster1, are now disabled in
    both VipsBand and VipsDataset to prevent you from shooting yourself in the
    foot.
Commits on Nov 21, 2012
  1. Remove upsample and align from TmsPyramid.

    Maxime Dupuis authored
    vips.py: Remove all traces of upsample and align from TmsPyramid
    helpers.py: Make the callback call upsample and align on the VipsDataset
    test_vips.py: Fix the tests for those changes and remove TestTmsPyramid
Something went wrong with that request. Please try again.