Andreas Hocevar
c1af0de860
Merge pull request #6410 from rjackson64840/fix-toStringHDMS
...
fixed the degreesToStringHDMS_() function to promote a seconds value …
2017-02-08 11:36:25 +01:00
Andreas Hocevar
bff6a14a16
Merge pull request #6457 from tst-ppenev/add-circle-support
...
Add Circle Modification
2017-02-06 21:14:49 +01:00
Pavel Penev
8c6d15b877
Add an ol.coordinate.distance() helper method.
...
The method is a companion to {@link ol.coordinate.squaredDistance}.
The new method returns the Cartesian distance, instead of its square.
Conflicts:
src/ol/coordinate.js
2017-02-06 14:43:20 -05:00
Tim Schaub
f5aea97d3b
All @api annotations imply stability
2017-02-06 09:22:05 -07:00
alfred.jackson
eebcccab66
fixed the degreesToStringHDMS_() function to promote a seconds value of 60 up to the next minute; fixed calculation of components
2017-01-27 17:32:21 -06:00
alfred.jackson
2001244b88
fixed the degreesToStringHDMS_() function to promote a seconds value of 60 up to the next minute
2017-01-27 14:43:41 -06:00
Frederic Junod
97ececb470
Remove unused ol.coordinate.fromProjectedArray function
2016-09-15 10:39:46 +02:00
Peter Robins
535e8f5e35
Move top-level typedefs to typedefs.js
...
With one exception, those directly in the `ol` namespace can be moved without problem.
Some left-over goog.requires are also removed.
2016-05-11 17:18:05 +00:00
nicholas
c92223d792
Remove Goog.string
2016-04-08 18:09:57 +12:00
Nicholas Latham
2ee1969de7
Remove goog.math.modulo and goog.math.lerp
2016-04-04 09:43:24 +02:00
pfanguin
b584a9aeb5
Add precision parameter for HDMS coordinate
2016-02-11 09:15:41 +01:00
Marc Jansen
390153adc8
Remove goog.isDef from coordinate.js
2015-09-25 11:28:54 -06:00
Pierre GIRAUD
1cdfc709ae
Pad min. and sec. with leading zeros in DMS notation
...
FIxes 3776
2015-06-25 08:40:43 +02:00
Tim Schaub
d09c4afefb
Coordinate docs
2015-04-04 17:36:47 +02:00
Stefan Weil
e812f2435e
Fix typos found by codespell
...
Most of them are in comments, some in strings.
Signed-off-by: Stefan Weil <sw@weilnetz.de >
2015-02-12 16:39:55 +01:00
Éric Lemoine
546b42df07
Remove @api annotation from ol.coordinate.fromProjectedArray
2014-08-22 18:01:31 +02:00
Éric Lemoine
43bd2b740b
Add @api stable annotations for ol.coordinate
2014-08-21 13:24:57 +02:00
Frederic Junod
53be13a658
Remove unused ol.CoordinateArray typedef
2014-07-29 14:44:51 +02:00
Marc Jansen
64c03d0f9c
Add examples to ol.coordinate functions.
2014-07-23 09:15:50 +02:00
Tim Schaub
4cf5ab4620
Use @api annotation instead of @todo api
2014-07-05 15:41:14 -04:00
Peter Robins
2683f08bd2
Clarify that ol.Coordinate is for xy coordinates
...
Docs only; no logic change
2014-05-28 17:40:23 +01:00
Frederic Junod
8239a5c92a
Document ol.coordinate functions
2014-05-20 14:15:28 +02:00
Andreas Hocevar
e6dbb61d68
Document raw geometry types
2014-05-06 12:45:53 -05:00
Andreas Hocevar
fbdbbfb7a7
Get rid of stability annotations and document stability with api
...
This change adds a stability value to the api annotation, with
'experimental' as default value.
enum, typedef and event annotations are never exportable, but
api annotations are needed there to make them appear in the
docs.
Nested typedefs are no longer inlined recursively, because the
resulting tables get too wide with the current template.
2014-04-29 09:53:07 -06:00
Andreas Hocevar
c17ac0cae3
Greatly simplify and document the usage of JSDoc
...
This commit simplifies the exports.js plugin so it only relies
on the stability notes to generate the documentation, which
completely decouples it from the exportable API.
As a rule of thumb, whenever something has an 'api' annotation,
it should also have a 'stability' annotation. A more verbose
documentation of ol3 specific annotation usage is available in
the new 'apidoc/readme.md' file.
This commit also modifies all source files to implement these
usage suggestions.
2014-04-29 09:53:06 -06:00
Tim Schaub
fb497f5288
Annotations for exports
2014-04-29 09:53:05 -06:00
Éric Lemoine
00bc424098
Add ol.coordinate.sub
2014-04-10 12:40:47 +02:00
Tom Payne
35dea5e3a6
Always use === to compare with 0
2014-03-23 18:29:47 +01:00
Bart van den Eijnden
87d651af04
Add documentation for API typedef functions
2014-02-14 15:32:12 +01:00
ahocevar
06406d968f
Adding equals method for comparing coordinates
2013-11-13 00:44:38 +01:00
ahocevar
e9b934d041
Let closestOnSegment return nothing more than a coordinate
...
Since we do not use the 'along' property anywhere, and the
resulting array returned by closestOnSegment could cause trouble
when working with 3d coodinates, now only the closest point is
returned, and the squared distance to the segment is calculated
by squaredDistanceToSegment instead.
2013-11-04 20:54:07 +01:00
ahocevar
1670b31142
Moving squaredDistanceToSegment to the coordinate package
2013-11-04 19:19:54 +01:00
Frederic Junod
1217243f84
Better ol.coordinate.* documentation
2013-10-28 17:34:54 +01:00
Frederic Junod
9ca74200ed
Remove opt_precision check in ol.coordinate.format
...
Default is already 0, see http://www.ecma-international.org/ecma-262/5.1/#sec-15.7.4.5
2013-10-28 16:26:21 +01:00
Frederic Junod
cdf34b558a
Add ol.coordinate.format function
...
Return a formatted coordinate. Example usage:
> ol.coordinate.format([0.01 ,12.14], "{x}, {y}", 2)
"0.01, 12.14"
> ol.coordinate.format([0.01 ,12.14], "lat: {y} / lon: {x}", 1)
"lat: 12.1 / lon: 0.0"
2013-10-28 15:32:43 +01:00
Paul Spencer
bada596b45
Add default stability level to docs of exported things.
2013-10-24 18:20:24 -04:00
Frederic Junod
ef929e9a72
Fix jsdoc formating
2013-09-24 12:18:00 +02:00
Tim Schaub
58fe110419
Rename ol.geom.VertexArray to ol.CoordinateArray
2013-08-30 13:30:53 -06:00
Tom Payne
539529af59
Improve type checking in ol.coordinate
2013-04-30 21:29:56 +02:00
ahocevar
58c8b07ab5
Get hit candidates from RTree, then refine result
...
Now we get exact hits also for lines and polygons.
2013-04-30 13:34:12 +02:00
Tom Payne
58a512b52c
Remove unused constant
2013-04-05 12:30:38 +02:00
Tom Payne
02196c94b5
Redefine ol.Coordinate to be Array.<number>
2013-04-05 12:30:37 +02:00
Éric Lemoine
0b62c92cb3
Use @expose for Coordinate.z
...
By annotating the z property with @expose the compiler does not try to optimize that property in any way. See https://developers.google.com/closure/compiler/docs/js-for-compiler . The doc says that @expose should never be used in library code, but that's the only way I found for our case.
2013-03-26 17:05:54 +01:00
Tom Payne
7755555cc3
Use NaN as default value for Z
2013-03-20 12:02:40 +01:00
Tom Payne
d3ea5236ef
Optionally extend ol.Coordinate to the third dimension
...
We continue to inherit from goog.math.Vec2 instead of goog.math.Vec3
because goog.math.Vec2 better represents a position in space, with
appropriate functionality, whereas goog.math.Vec3 represents a direction
and magnitude.
2013-03-19 22:10:21 +01:00
Bart van den Eijnden
5e29830462
Add WMTS GetCapabilities parser
...
Implements WMTS GetCapabilities parser, which depends partly on
an OWSCommon parser.
Integration with the layer source will be done at a later stage.
2013-02-19 16:32:56 +01:00
augustus
f253c1bcf8
Some comments (no changes to code)
2012-11-09 16:26:59 +01:00
Tom Payne
ee1d1fa3e7
Fold ol.CoordinateFormat into ol.Coordinate
2012-10-18 14:22:23 +02:00
Tom Payne
424dbd7582
Remove problematic (and unused) clone methods, move contains out of ol.Rectangle
2012-09-25 00:04:45 +02:00
Tom Payne
f8c31ba45c
s/ol3/ol/
2012-09-24 14:21:41 +02:00