Skip to content

Commit

Permalink
Merge pull request #1128 from tilezen/tag-1.0.2
Browse files Browse the repository at this point in the history
Version bump -> 1.0.2
  • Loading branch information
rmarianski authored Nov 18, 2016
2 parents 0040c9c + c29ec59 commit 703430f
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 4 deletions.
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,10 @@
v1.0.2
------
* **Release date**: 2016-11-17.
* **Requires:** [tileserver v1.0.0](https://github.com/mapzen/tileserver/releases/tag/v1.0.0) and [tilequeue v1.0.1](https://github.com/mapzen/tilequeue/releases/tag/v1.0.1) and [mapbox-vector-tile v1.0.0](https://pypi.python.org/pypi/mapbox-vector-tile/v1.0.0).
* Merge water and earth polygons. See [#1106](https://github.com/tilezen/vector-datasource/issues/1106).
* Improve maritime_boundary tagging in Europe and globally by updating buffered_land shapefile. See [#294](https://github.com/tilezen/vector-datasource/issues/294).

v1.0.1
------
* **Release date**: 2016-11-04. _Live on prod 2016-11-04._
Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v1.0.1
v1.0.2
6 changes: 3 additions & 3 deletions docs/layers.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ Most Mapzen vector tile content is updated minutely from OpenStreetMap. Low and

#### Changelog

The current version of Mapzen vector tiles is **v1.0.0**.
The current version of Mapzen vector tiles is **v1.0.2**.

Our tiles are still in active development, but we promise to minimize backwards incompatable breaking changes. We list data model promises in the Tilezen [SEMANTIC VERSIONING](https://github.com/mapzen/vector-datasource/tree/v1.0.0/SEMANTIC-VERSIONING.md) statement.

Expand Down Expand Up @@ -155,7 +155,7 @@ Combination of OpenStreetMap administrative boundaries (zoom >= 8) and Natural E
* `id:right`: For the relation on the right side of the boundary line.
* `name:left`: See name section above, other variants like `old_name` also supported. _See planned bug fix in [#1102](https://github.com/tilezen/vector-datasource/issues/1102)._
* `name:right`: See name section above, other variants like `old_name` also supported. _See planned bug fix in [#1102](https://github.com/tilezen/vector-datasource/issues/1102)._
* `maritime_boundary`: a special Mapzen calculated value loosely coupled with OpenStreetMap's maritime tag, but with spatial buffer processing for lines falling in the ocean. _See planned data improvement in [#294](https://github.com/tilezen/vector-datasource/issues/294)._
* `maritime_boundary`: a special Mapzen calculated value loosely coupled with OpenStreetMap's maritime tag, but with spatial buffer processing for lines falling in the ocean.

#### Boundaries properties (optional):

Expand Down Expand Up @@ -1253,4 +1253,4 @@ Additionally, a `reservoir: true` or `alkaline: true` value can be present on th

* `lake` features with `alkaline: true` and `playa` features are sourced solely from Natural Earth. Zooming in, your feature may disappear (there is no equivalent in OpenStreetMap). Beware the desert around Great Salt Lake in Utah!
* `lake` features from Natural Earth sometimes change to `water` features on zoom into OpenStreetMap data. _See planned bug fix in [#984](https://github.com/tilezen/vector-datasource/issues/984)._
* Some of the minor kinds (like `bay`, `strait`, and `fjord`) are used for label_placement points only, as their area would duplicate water polygons already present from openstreetmapdata.com.
* Some of the minor kinds (like `bay`, `strait`, and `fjord`) are used for label_placement points only, as their area would duplicate water polygons already present from openstreetmapdata.com.

0 comments on commit 703430f

Please sign in to comment.