v0.10.6

• fix issue #46
• fix error: global is undefined

v0.10.5

patch release v0.10.5

resolves issue with geometry coordinate compare in different projections #40

v0.10.4

Fix issues in #40 and #43

v0.10.3

apply options merge in each component install function (#40)

v0.10.2

Patch that resolves issue with dataProjection plugin option #40

v0.10.1

There is a lot of error fixes, code improves and features in this release.

First of all note about upgrade from v0.9:

• ES6 version files moved to lib/_esm folder for easy setup tools like babel-plugin-transform-imports. If you use direct imports from vuelayers/lib/* directory and rely on ES6 version change them to vuelayers/lib/_esm/*
• core subpackage dropped out. All stuff from core now published as a small separate packages that you can use as before. Mixins now at lib/mixin/*/lib/_esm/mixin directory, ol-ext at lib/ol-ext/lib/_esm. ( #27 and #30 )
• bindToProj global option renamed to dataProjection

New features

• vl-interaction-draw and vl-interaction-modify - allow drawing and modifying vector features (documentation on the way)
• vl-geom-circle - circle geometry component
• vl-source-bing-maps - loads tiled data from Bing Maps (https://vuelayers.github.io/#/component/bing-maps-source?id=usage)

Other

• new documentation site based on docsify. Now writing documentation is less complicated and I finish it soon
• replace lodash dependency with own simplified mini lodash lib, ~150Kb reduced from final build
• reactive data-projection property on the map component
• Demo app upgraded to introduce new features
• fixed warning about $services injection
  and other minor changes

v0.9.1 Patch release

• resolve #32
• fix broken Travis build
• update license info

v0.9.0

The main change in this release concerns the projection of the coordinates. In previous releases coordinates, extents, GeoJSON Features were in hardcoded EPSG:4326 projection for simplicity, but because of this it was impossible to use VueLayers with custom projection.

From now all components by default accepts coordinates in projection of the map view like in OpenLayers. Projection of the view may be defined in vl-view component, EPSG:3857 used by default.

To return the old behavior there is global option was introduced:

import Vue from 'vue'
import VueLayers from 'vuelayers'
// all input/output coordinates, GeoJSON features in EPSG:4326 projection
// like in < 0.9 version
Vue.use(VueLayers, {
  bindToProj: 'EPSG:4326',
})
// Now all should work like before

With the new behavior coordinates should be provided in the map view projection (EPSG:3857 by default):

<template>
  <vl-map>
    <vl-view :center="center"></vl-view>

   <vl-feature>
    <vl-geom-polygon :coordinates="polygon"></vl-geom-polygon>
   </vl-feature>
  </vl-map>
</template>

<script>
  import { core as vlCore } from 'vuelayers'

  export default {
    data () {
      return {
        center: vlCore.projHelper.fromLonLat([5, 5]/*, 'EPSG:3857'*/),
        polygon: vlCore.projHelper.polygonFromLonLat([[[0, 0], [10, 10], [10, 0], [0, 0]]]/*, 'EPSG:3857'*/)
      }
    },
  }
</script>

Custom projections should be registered before use (they may be needed when working with static image layers, example will be added to documentation and demo):

// App.vue
// create custom projection
let x = 1024 * 10000
let y = 968 * 10000
let imageExtent = [-x / 2, -y / 2, x / 2, y / 2]
let customProj = vlCore.projHelper.create({
  code: 'xkcd-image',
  units: 'pixels',
  extent: imageExtent,
})
// add it to list of known projections
vlCore.projHelper.add(customProj)

v0.8.1

Fix issue with default value for crossOrigin prop in sources, changed to undefined by default

v0.8.0

• added vl-layer-image and vl-source-image-static
• vl-geom-*: added projection prop with default value EPSG:4326
• vl-layer-*: extent in map view projection
• vl-source-*: extent/coordinates in projection provided with projection prop

drop deprecated code