Changelog
3.5.5
Changelog
3.5.4
mapnik-vector-tile
to 1.0.5
this solves a SEGFAULT that occurs in rare situations when encoding failssplit_multi_features
and lat_lon
to mapnik.VectorTile.reportGeometryValidity
and mapnik.VectorTile.reportGeometryValiditySync
that enables validity checks against the parts of multi geometries individually.Changelog
3.5.2
mapnik-inspect.js
around using old parse()
method on vector tiles, updated it to use mapnik.VectorTile.info
mapnik-vector-tile
to 1.0.3
fixing issues with non valid vector tiles being created and linking issue in mapnik-vector-tile with latest mapnik librarymapnik-vector-tile
Changelog
3.5.1
mapnik.VectorTile.info
command that returns an object that inspects buffers and provides information about vector tiles.mapnik-vector-tile
to 1.0.2
Changelog
3.5.0
This is a major update and reflects a large number of changes added into node-mapnik due to update of the Mapbox Vector Tile Specification. As part of this the mapnik-vector-tile library was updated to 1.0.0
. Therefore, a large number of interfaces changes have taken place around the mapnik.VectorTile
object.
It is important to know that the concept of width
and height
have been removed from mapnik.VectorTile
objects. This is replaced by the concept of tileSize
. While width
and height
were based on the concept of an Image size created from a vector tile, tileSize
is directly related to the extent
as defined in the Layer
of a vector tile. For understanding what the Layer
and extent
is please see the Vector Tile Specification. This also changed the buffer_size
arguments that were commonly used in many Vector Tile methods, which was also based on the Image size. The vector tile object now contains a bufferSize
which represents the buffer added to the layer extent in a tile.
Internally, all methods now depend on V2 tiles, however, any V1 tiles that are loaded into a mapnik.VectorTile
object will automatically be updated.
Summary of changes:
mapnik.VectorTile.addData
now verifies buffers validity and internally updates v1 tiles to v2mapnik.VectorTile.addDataSync
now verifies buffers validity and internally updates v1 tiles to v2mapnik.VectorTile.setData
now verifies buffers validity and internally updates v1 tiles to v2mapnik.VectorTile.setDataSync
now verifies buffers validity and internally updates v1 tiles to v2mapnik.VectorTile.addImage
now takes a mapnik.Image
object rather then a buffer, it also takes optional arguments image_scaling and image_format.mapnik.VectorTile.addImageBuffer
replaces the old functionality of of mapnik.VectorTile.addImage
mapnik.VectorTile.addImageSync
and made mapnik.VectorTile.addImage
accept a callback.mapnik.VectorTile.addImageBufferSync
and made mapnik.VectorTile.addImageBuffer
accept a callback.mapnik.VectorTile.height()
method is removedmapnik.VectorTile.width()
method is removedmapnik.VectorTile.parse()
method is removedmapnik.VectorTile.IsSolid()
method is removedmapnik.shutdown()
is removedmapnik.VectorTile
objects are no longer permitted.mapnik.VectorTile.extent()
method which returns the bounding box of a tile in EPSG:3857mapnik.VectorTile.bufferedExtent()
method which returns the bounding box including buffer of a tile in EPSG:3857mapnik.VectorTile.emptyLayers()
method which returns the name of layers which were not added to a tile during any tile rendering operation.mapnik.VectorTile.paintedLayers()
method which returns the name of layers which were considered painted during rendering or layers that contain data.mapnik.VetorTile.tileSize
property.mapnik.VetorTile.bufferSize
property.mapnik.VectorTile
class methodspath_multiplier
from the code entirely.tile_size
and buffer_size
to mapnik.VectorTile
constructor.Changelog
3.4.17
mapbox::variant
that was causing windows compiler crashNotable Changes in Mapnik v3.0.10 include:
Notable changes in the Mapnik SDK include:
Changelog
3.4.16
image.resize
behavior when scaling images with alpha (https://github.com/mapnik/node-mapnik/issues/585)Notable Changes in Mapnik v3.0.9-125-g5e30aee include:
dash-array
in SVGs(,)
between multiple command partspng
format stringmemory_datasource
now dynamically reports correct datasource type (vector or raster)mapbox::variant@272f91c
Notable changes in the Mapnik SDK include:
Changelog
3.4.15
vtile.query
now returns WGS84 x_hit
and y_hit
values of the nearest point/vertexChangelog
3.4.14
Notable Changes in Mapnik v3.0.9-57-g9494bc1 include:
PathElement
(https://github.com/mapnik/mapnik/issues/3225)Changelog
3.4.13
v3.0.9-48-gbb8cd10
(see Notable Changes in Mapnik
below for details).Notable Changes in Mapnik v3.0.9-48-gbb8cd10 include:
.index
files accompanying a .shp
must now be regenerated otherwise
an error will be throw like Error: invalid index file
. To avoid this error you can
either delete the existing .index
files, or ideally run shapeindex
(or mapnik-shapeindex.js) to recreate the .index
.
The trigger for this change was an optimization that required a new binary format for the shapefile indexes (https://github.com/mapnik/mapnik/pull/3217). It was a mistake of @springmeyer to bring this into node-mapnik minor release (I'm sorry).shapeindex
command now has a --index-parts
optiongeometry
Notable changes in the Mapnik SDK include: