Bug 2747 - Add a constructor to GeoPoint that takes lat/lon as degrees
Summary: Add a constructor to GeoPoint that takes lat/lon as degrees
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Bindings ()
Version: 4.0
Hardware: All All
: Normal enhancement
Target Milestone: ---
Assignee: Atsushi Eno
URL:
Depends on:
Blocks:
 
Reported: 2012-01-05 10:52 UTC by Mike Bluestein
Modified: 2017-06-23 15:35 UTC (History)
4 users (show)

Tags: XATriaged
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Mike Bluestein 2012-01-05 10:52:25 UTC
The Android GeoPoint class uses latitude and longitude as integers of microdegrees. It would be useful to have an additional constructor that takes lat/lon as degrees and handles the conversion internally.
Comment 1 Marek Habersack 2016-09-01 19:22:03 UTC
@Mike, there's no GeoPoint class in Android API - can you clarify? Not sure if this issue is still valid after 4+ years :)
Comment 2 Cody Beyer (MSFT) 2017-06-23 15:35:43 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!