-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Maps] Support UTM and MGRS in Maps #76144
Comments
Pinging @elastic/kibana-gis (Team:Geo) |
How often do users switch between decimal degrees, UTM, and MGRS? Would it make sense to move this setting to a map wide setting that would also effect the coordinates displayed in the lower right corner? |
@nreese I'll have to ask the users; my experience is that it changes based somewhat arbitrarily based off the source of the coordinates. In other words, I have a map that I use for analysis, and sometimes I get a UTM coordinate to look at and sometimes I get a Degrees Decimal, and sometimes I get MGRS. That said, I think that if would be fine for the coordinate setting in the "Go To" to also affect the display in the lower right corner. I just wouldn't want the coordinate setting to be a global setting across all users or be buried somewhere that makes it annoying for the user to change. |
@maihde I see from your code that What about supporting other projections like |
The fuzziness of the license of the |
I like the idea of using coordinate inputs for navigation and to display coordinates on the map per user preference. The existing Go To UI is OK. I think an improvement to this experience would be to use a single-search bar to navigate/search a map. User can easily copy/paste coordinates into the search bar and hit enter/return/go. No configuration required. i.e. In the future, the search would expand to allow for navigate to documents on the map; or common places via a simple forward geocoder. |
After further review, I recommend we use https://github.com/codice/usng.js instead of the mgrs library. The license of usng.js is more definite and it supports conversion to UTM and MGRS. |
@nickpeihl would it help to get this into the baseline sooner if I submit a PR of this using the @kmartastic I like the concept you propose a lot! My only concern is that such a large change would mean that it will take longer for UTM/MGRS support to be available in the map. It's a relatively simple change to use the existing UI paradigm now. @jsanz my users only really care about WGS84. |
Hi @maihde. I don't believe anyone is currently working on this feature, so I think it may help if you submit a PR. I agree with you on making small changes first and supporting additional features later. |
* implemention of usng support fixing #76144 * linting fixes * lint fixes * pr code edits * fixed utm zone and added error proofing * removing any data types and replacing with explicit ones * avoiding render of unused components * fixing linting issues Co-authored-by: Michael Ihde <mihde@spectric.com>
) * implemention of usng support fixing elastic#76144 * linting fixes * lint fixes * pr code edits * fixed utm zone and added error proofing * removing any data types and replacing with explicit ones * avoiding render of unused components * fixing linting issues Co-authored-by: Michael Ihde <mihde@spectric.com>
Fixed by #107835 |
* implemention of usng support fixing #76144 * linting fixes * lint fixes * pr code edits * fixed utm zone and added error proofing * removing any data types and replacing with explicit ones * avoiding render of unused components * fixing linting issues Co-authored-by: Michael Ihde <mihde@spectric.com> Co-authored-by: Michael Kellogg <mkellogg91@gmail.com> Co-authored-by: Michael Ihde <mihde@spectric.com>
Describe the feature: Currently the Maps "Go To" button only supports Degrees Decimal format. For many users it would be convenient to be able to also use UTM or MGRS coordinates.
Describe a specific use case for the feature: Users who use MGRS or UTM to perform geospatial analysis.
I have implemented a prototype:
spectriclabs@9fb93d8
The text was updated successfully, but these errors were encountered: