Merge pull request #1076 from OpenGeoscience/v1.0.0

Version 1.0.0

CHANGELOG.md

@@ -1,9 +1,10 @@
 # Change Log
 
-## Unreleased
+## Version 1.0.0
 
 ### Improvements
 - Screenshots now handle mix-blend-mode settings on top level divs (#1074)
+- More flexible default position accessors (#1066)
 
 ### Bug Fixes
 - Fixed an issue with affine transforms and polygons (#1073)
@@ -586,7 +587,7 @@ Migrating from the plane feature to the new quad feature provides major performa
 - @jbeezley
 - @manthey
 
-Huge thanks to all of the contributers, and the many others who tested, created issues, and gave feedback during the development of this release.
+Huge thanks to all of the contributors, and the many others who tested, created issues, and gave feedback during the development of this release.
 
 
 ## Version 0.5.0

README.md

@@ -1,6 +1,6 @@
 ![GeoJS](https://opengeoscience.github.io/geojs/images/logo_256.png)
 
-[![Build Status](https://travis-ci.org/OpenGeoscience/geojs.svg?branch=master)](https://travis-ci.org/OpenGeoscience/geojs)
+[![Build Status](https://travis-ci.com/OpenGeoscience/geojs.svg?branch=master)](https://travis-ci.com/OpenGeoscience/geojs)
 [![codecov.io](https://codecov.io/github/OpenGeoscience/geojs/coverage.svg?branch=master)](https://codecov.io/github/OpenGeoscience/geojs?branch=master)
 [![DOI](https://zenodo.org/badge/doi/10.5281/zenodo.15459.svg)](https://dx.doi.org/10.5281/zenodo.15459)
 [![Gitter](https://badges.gitter.im/OpenGeoscience/geojs.svg)](https://gitter.im/OpenGeoscience/geojs?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)

docs/developers.rst

@@ -127,4 +127,4 @@ To make a new GeoJS release:
 - Tag the commit on GitHub with a tag of the form vX.Y.Z (e.g., v0.17.0).
 - After the release appears on GitHub, update the release notes with the changes since the last release.
 
-Tagging a commit on the master branch will trigger a build on travis-ci.org, at the end of which the new version will be published to npm and the build artifacts will be pushed to the tagged version on GitHub.
+Tagging a commit on the master branch will trigger a build on travis-ci.com, at the end of which the new version will be published to npm and the build artifacts will be pushed to the tagged version on GitHub.

docs/index.rst

@@ -1,14 +1,14 @@
-=================================
-Welcome to GeoJS's documentation!
-=================================
+================================
+Welcome to GeoJS's documentation
+================================
 
-GeoJS is a flexible library for all kinds of geospatial visualizations
+GeoJS is a flexible library for all kinds of geospatial and 2-D visualizations
 from traditional point markers to 3D climatological simulations.  It is
-designed for displaying large datasets (over 100,000 points) leveraging
+designed for displaying large datasets (over 1,000,000 points) leveraging
 the power of WebGL.  The programming interface was inspired by the widely
 used `d3 <https://d3js.org/>`_ and allows the user to generate features from
 arbitrary data objects with custom accessors.  The API also provides
-custom mouse events that mimick browser level events, but work with
+custom mouse events that mimic browser level events, but work with
 WebGL features and even through active layers.
 
 See the growing list of `examples <https://opengeoscience.github.io/geojs/examples/index.html>`_

docs/quickstart.rst

@@ -14,7 +14,7 @@ The following software is required to build geojs from source:
 
 For testing and development, the following additional software is required:
 
-* `Python 2.7 <https://www.python.org/>`_
+* `Python 3 <https://www.python.org/>`_
 * `CMake <https://www.cmake.org/>`_
 
 In addition, the following python modules are recommended for development

docs/users.rst

@@ -23,9 +23,9 @@ under its standard name in global scope.
 Software conventions
 --------------------
 
-At it's core, GeoJS is an object oriented framework designed to be extended
+At its core, GeoJS is an object oriented framework designed to be extended
 and customized.  The inheritance mechanism used provides an isolated closure
-inside the constructor to maintain private methods and variables.  Prototypal
+inside the constructor to maintain private methods and variables.  Prototypical
 inheritance is performed by a helper method called ``geo.inherit``.  This
 method copies public methods declared on the parent class's prototype.  In general,
 classes inside GeoJS do not declare methods on the class prototype.  Instead,
@@ -189,7 +189,7 @@ Coordinate systems
 
 A major component of GeoJS's core library involves managing several coordinate systems that
 are used to keep layers aligned on the screen.  The following conventions are used in GeoJS's
-documentation and codebase when refering to coordinates:
+documentation and codebase when referring to coordinates:
 
 Latitude/longitude coordinates
     Expressed in degrees relative to the WGS84 datum as objects using keys ``x`` for longitude and ``y``
@@ -212,7 +212,7 @@ World coordinates
     These are the coordinates used internally as coordinates of the 3D scene in much the sense as defined
     in 3D graphics.  The world coordinates are a rescaled and translated version of the GCS coordinates so
     that the world coordinates of the current viewport is near ``1`` in each axis.  This is done to
-    provide well conditioned transformation matrices that can be used acurately in contexts of limited precision
+    provide well conditioned transformation matrices that can be used accurately in contexts of limited precision
     such as WebGL or CSS.  In order to achieve this, the world coordinate system is dynamic at run time
     and will change as the user pans and zooms the map.  By convention, the world coordinates are given
     relative to a dynamic "scale" and "origin".  Changes to these values trigger events on the map that
@@ -232,14 +232,14 @@ Feature coordinates
 Coordinate transformation methods
 ---------------------------------
 
-To facilitate uniform tranformation between the many coordinate systems used inside a map object,
+To facilitate uniform transformation between the many coordinate systems used inside a map object,
 there are many available transformation methods provided in the core API.  These methods vary
 from being useful to all users of the library to methods that are only relevant to developers
 interacting with low level renderers or wishing to optimize performance.  The following is a list
 of transform methods present in the library as well as example uses for them.
 
 ``geo.map.gcsToDisplay/displayToGcs(c, gcs)``
-    This is the most common tranformation method that converts from a geographic coordinate system into
+    This is the most common transformation method that converts from a geographic coordinate system into
     pixel coordinates on the map.  If no GCS is given, the method will assume the coordinate system of
     the map.  For example, to get the lat/lon of the point under the mouse you would get the pixel
     coordinates relative to the map's container and pass them to this method as ``c`` in
@@ -258,7 +258,7 @@ of transform methods present in the library as well as example uses for them.
 
 ``geo.camera.worldToDisplay/displayToWorld(c, width, height)``
     This converts between world space coordinates and display pixel coordinates given a viewport
-    size.  In addition to thse methods, the camera class provides access to the raw transformation
+    size.  In addition to these methods, the camera class provides access to the raw transformation
     matrices for layers that can make use of them directly.  For layers supporting CSS
     there is also a ``camera.css`` property that returns a CSS transform representing the current
     camera state.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "geojs",
-  "version": "0.20.0",
+  "version": "1.0.0",
   "description": "JavaScript Geo Visualization and Analysis Library",
   "homepage": "https://github.com/OpenGeoscience/geojs",
   "license": "Apache-2.0",