Would it be reasonable to create an issue to request nautical miles ("nm"
as the abbreviation) for the DistanceUnit enumeration?
This would make it much more natural to adapt Elasticsearch for aircraft
planning / charting applications. Everything in that world is in nautical
miles and knots (nautical miles per hour).
Would it be reasonable to create an issue to request nautical miles ("nm"
as the abbreviation) for the DistanceUnit enumeration?
This would make it much more natural to adapt Elasticsearch for aircraft
planning / charting applications. Everything in that world is in nautical
miles and knots (nautical miles per hour).
One nautical mile is one minute of arc along the meridian line (one degree
of longitude), that makes it very easy to calculate distance on a chart
(independent on the vehicle used
On Mon, Feb 10, 2014 at 3:27 PM, Ivan Brusic ivan@brusic.com wrote:
Aircraft use nautical miles? You learn something new every day!
Would it be reasonable to create an issue to request nautical miles ("nm"
as the abbreviation) for the DistanceUnit enumeration?
This would make it much more natural to adapt Elasticsearch for aircraft
planning / charting applications. Everything in that world is in nautical
miles and knots (nautical miles per hour).
never thought about such a use-case, but it sounds useful. Feel free to
create an issue, and even better, a pull request to add that functionality
to DistanceUnit
--Alex
On Tue, Feb 11, 2014 at 12:54 AM, Raffaele Sena raff367@gmail.com wrote:
One nautical mile is one minute of arc along the meridian line (one degree
of longitude), that makes it very easy to calculate distance on a chart
(independent on the vehicle used
Would it be reasonable to create an issue to request nautical miles
("nm" as the abbreviation) for the DistanceUnit enumeration?
This would make it much more natural to adapt Elasticsearch for aircraft
planning / charting applications. Everything in that world is in nautical
miles and knots (nautical miles per hour).
I don't use GitHub that much, and I kinda muffed the issue, so I'll let
someone else add the one enumeration to wherever it should best go:
NAUTICALMILES(1852.0, "nm", "nmi"),
Thanks!
Brian
Brian
On Tuesday, February 11, 2014 8:25:03 AM UTC-5, Alexander Reelsen wrote:
Hey,
never thought about such a use-case, but it sounds useful. Feel free to
create an issue, and even better, a pull request to add that functionality
to DistanceUnit
--Alex
On Tue, Feb 11, 2014 at 12:54 AM, Raffaele Sena <raf...@gmail.com<javascript:>
wrote:
One nautical mile is one minute of arc along the meridian line (one
degree of longitude), that makes it very easy to calculate distance on a
chart (independent on the vehicle used
On Mon, Feb 10, 2014 at 3:27 PM, Ivan Brusic <iv...@brusic.com<javascript:>
wrote:
Aircraft use nautical miles? You learn something new every day!
--
Ivan
On Mon, Feb 10, 2014 at 3:21 PM, InquiringMind <brian....@gmail.com<javascript:>
wrote:
Would it be reasonable to create an issue to request nautical miles
("nm" as the abbreviation) for the DistanceUnit enumeration?
This would make it much more natural to adapt Elasticsearch for
aircraft planning / charting applications. Everything in that world is in
nautical miles and knots (nautical miles per hour).
Create a branch for your changes. Submit a PR from the branch and not
master. Make sure to update DistanceUnitTests.java as well. The trickiest
part is getting the Elasticsearch team to notice your PR. They must be
super busy with the 1.0 release.
Thanks so much for the advice. I created the nm-branch (nautical miles
branch) off of master, then cloned it to my laptop. Found the two files
(DistanceUnit, and DistanceUnitTests). Made the (very simple) changes. Then
built ES and ran only the tests in DistanceUnitTests. The build was
surprisingly quick; the tests ran and succeeded:
$ mvn test -Dtests.class=org.elasticsearch.common.unit.DistanceUnitTests
[INFO] Your default console's encoding may not display certain unicode
glyphs: MacRoman
Executing 1 suite with 1 JVM.
Started J0 PID(9572@).
Suite: org.elasticsearch.common.unit.DistanceUnitTests
Completed in 0.54s, 2 tests
[INFO] Total time: 8.507s
[INFO] Finished at: Tue Feb 11 15:57:37 EST 2014
[INFO] Final Memory: 10M/123M
[INFO]
Here is the pull request:
Please let me know if anything is amiss. This is my first actual use of
GitHub. A local git expert offered his advice as well, but any errors are
mine and no one else's.
Thanks! Also, note the range (that is, maximum distance traveled with
appropriate fuel minimums) of the following aircraft. All are in nm(nautical miles):
On Monday, February 10, 2014 6:54:44 PM UTC-5, Raffaele Sena wrote:
One nautical mile is one minute of arc along the meridian line (one
degree of longitude), that makes it very easy to calculate distance on a
chart (independent on the vehicle used
I'm glad I was able to steer you in the right direction. I flubbed a PR
recently since I have not used git consistently in the past few years, so I
am glad someone else can learn from my mistakes. Your PR seemed to have
gained some attention!
Thanks so much for the advice. I created the nm-branch (nautical miles
branch) off of master, then cloned it to my laptop. Found the two files
(DistanceUnit, and DistanceUnitTests). Made the (very simple) changes. Then
built ES and ran only the tests in DistanceUnitTests. The build was
surprisingly quick; the tests ran and succeeded:
$ mvn test -Dtests.class=org.elasticsearch.common.unit.DistanceUnitTests
[INFO] Your default console's encoding may not display certain unicode
glyphs: MacRoman
Executing 1 suite with 1 JVM.
Started J0 PID(9572@).
Suite: org.elasticsearch.common.unit.DistanceUnitTests
Completed in 0.54s, 2 tests
Please let me know if anything is amiss. This is my first actual use of
GitHub. A local git expert offered his advice as well, but any errors are
mine and no one else's.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.