Commit Graph

20 Commits

Author SHA1 Message Date
Vladimir Agafonkin
d145b1fdba fix a bunch of eslint warnings in the spec suite 2015-01-28 19:32:27 +02:00
John Firebaugh
2ee1aa2c23 jshint 2015-01-12 11:03:42 -08:00
Sergey Kruk
c8e5d7c61b L.latLng factory not to throw error on empty array parameter 2014-12-05 20:36:35 +03:00
Sergey Kruk
c5ebd534b2 Factory L.latLng to accept altitude as third parameter or an object's 'alt' property 2014-12-01 16:02:43 +03:00
Vladimir Agafonkin
760c730f92 fix LatLng.distanceTo race condition, close #2705 2014-05-28 17:26:41 +03:00
Vladimir Agafonkin
dd313e6930 better CRS test coverage 2013-12-02 19:18:07 +02:00
Vladimir Agafonkin
7e20997e40 remove LatLng wrap and fix wrap tests 2013-12-02 19:16:01 +02:00
Vladimir Agafonkin
91c039b7aa jshinting and major clean up of specs code, ref #2151 2013-11-07 23:54:33 +02:00
Hans Kristian Flaatten
8e98e52b88 Renames L.LatLng property .altitude to .alt 2013-07-03 15:44:57 +02:00
Hans Kristian Flaatten
46885de00d Adds support for altitude and 3D GeoJSON
This commit adds a third parameter to the L.LatLon class for specifying
altitude. This is in turn stored in the `.latitude` property for the LatLng
instance. Latitude property will only be set if the latitude parameter is not
undefined, this is done in order to ensure backwards compability.

```javascript
var latlng = new L.LatLng(10, 20, 30);
console.log(latlng.altitude); // prints '30' to the console
```

Similar functionality has been added to L.GeoJSON coordsToLatLng() and
latLngToCoords() methods in order to handle import and export of 3D GeoJSON.

```javascript
var geoJSON = {
  type: 'Feature'
  ,properties: {}
  ,geometry: {
    type: 'Point'
    ,coordinates: [20, 10, 30]
  }
}
var layer = new L.GeoJSON();
layer.addData(geoJSON);
console.log(layer.getLayers()[0].getLatLng().altitude);
```

`NB` It is important to notice that no logic has been added in order to prevent
latitude and longitude to change without appropirate change in altitude – this
must be handled by the application.
2013-07-03 10:13:00 +02:00
Tom MacWright
a2f7d7e834 Use mocha 2013-04-03 14:50:09 -07:00
John Firebaugh
01332ebead Omit "should" in spec descriptions
The rationale is this: the spec string describes the expected
behavior unconditionally. The code examples, on the other hand,
set up an expectation that is tested with the call to the expect
method. The code examples can violate the expectation, but the
spec string does not. The value of the spec string is as clearly
as possible describing the behavior. Including “should” in that
description adds no value. (From http://rubyspec.org/style_guide/)
2013-02-19 12:41:48 -08:00
Tom MacWright
0a2000166a Fix semicolons, breaking, whitespace, duplicate var statements. 2013-02-19 11:18:15 -05:00
Vladimir Agafonkin
a0dd4a60e9 accept coordinates in form of simple objects, close #1412 2013-02-19 18:01:53 +02:00
Vladimir Agafonkin
5e05068478 complete LatLng and LatLngBounds tests, #1347 2013-02-05 15:21:40 +02:00
Vladimir Agafonkin
8350bb1e08 update LatLng specs after removing default clamping/wrapping 2012-12-12 12:04:54 +02:00
Pascal Borreli
9546599520 Fixed typos 2012-11-09 23:15:48 +00:00
Alex Graul
57f44bc423 fix issue with 180 longs being clamped to -180 2011-12-21 13:22:07 +00:00
mourner
4854e0f9f7 minor renaming 2010-09-06 19:14:04 +03:00
mourner
0b5cc9c455 LatLng + specs 2010-09-06 19:06:38 +03:00