v0.5.0

Thanks to @nmccready and @mvl22, nested properties are now supported. See the tests for an example. Also, bad geometry will throw an error if doThrows.invalidGeometry is set to True. Example.

v0.4.1

This release updates the node version attribute ofpackage.json to be more permissive. Thanks to @gzurbach for the patch.

v0.4.0

This release is the result of work from @herkit, @eflowbeach, and @jkirsch. Thanks for the PRs.

Features:

• Passing a single object will return a GeoJSON feature, as opposed to passing an array with one feature, which returns a GeoJSON feature collection (#23).
• If you already have GeoJSON data, but you want to extend it with additional properties, you can now use the GeoJSON geometry type (see the README and tests for an example) (#25).

Fixes:

• Coordinates passed as strings are now correctly converted to numbers (#24).

v0.3.0

Linked and named CRS objects are now supported. Thanks @DemersM!

This package is now built on Travis CI.

v0.2.1

Objects with 0,0 as the coordinate pair no longer generate invalid/empty geometry. (#12). Thanks again to @missinglink.

v0.2.0

parse no longer throws an error if the objects parameter is an empty array. This sort of breaks backwards compatibility, but makes the library more flexible. Thanks to @missinglink for the PR.

v0.1.5

Added extraGlobal parameter to allow users to specify properties for the dataset. See README and tests for an example.

Thanks @jczaplew!