You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change the default coordinate system to "Decimal, degrees" instead of UTM.
Ensure that all fields in the widget are automatically populated when a user clicks a location on the map.
Reduce the number of digits displayed for decimal degree coordinates to six after the decimal point (from 14)
As a user, I should be able to define the spill location by inputting coordinates in a variety of different coordinate types. These should be validated and should directly update the map and underlying Salesforce fields automatically.
Current implementation:
Supported Coordinate Systems:
Decimal Degrees (should be set as default)
Degrees, Minutes
Degrees, Minutes, Seconds
UTM
They no longer want to support TRS.
It’s confusing to the user that coordinates show up in both the map widget and the SF form.
I think that we need to keep the inputs in the map widget to support entering non-default coordinate types. However, maybe they can be hidden after typing them in and hitting a submit button. They should definitely be hidden or updated when the location is updated via map click.
Note
This is also a feature that needs to be built for PLSS.
Tasks
Build UI for selecting a coordinate type and inputting coordinate values
Update pin on map and zoom
Update coordinate fields in Salesforce (converting values, if needed)
Make sure that if the location is changed by clicking on the map that the coordinates in this UI are updated as well to eliminate confusion. Or create a better UI that does not create the same kind of confusion that the current one does.
Reduce number of digits after the decimal point from 14 down to six for the values that are stored in the database.
The text was updated successfully, but these errors were encountered:
As a user, I should be able to define the spill location by inputting coordinates in a variety of different coordinate types. These should be validated and should directly update the map and underlying Salesforce fields automatically.
Current implementation:
![Image](https://private-user-images.githubusercontent.com/1326248/376691582-8f8af107-e99b-4e38-a12e-0a831f0ffcce.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxMzIxNjgsIm5iZiI6MTczOTEzMTg2OCwicGF0aCI6Ii8xMzI2MjQ4LzM3NjY5MTU4Mi04ZjhhZjEwNy1lOTliLTRlMzgtYTEyZS0wYTgzMWYwZmZjY2UucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDlUMjAxMTA4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDVjY2QxN2E3NWQzMjg3ZWZlYzVkZTU0ZGZkZGUyZmM1OTI1ZDQ5ZTUwNTAyNmQyMDM1NGQ4ZjRhN2Y0NGRlNiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.v_lD3FsHF2ix0B5XjndxerE-A-neO2LSqcWsfrOYydE)
![Image](https://private-user-images.githubusercontent.com/1326248/376691689-bb6750bb-0d09-4eeb-941c-514b6975d140.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxMzIxNjgsIm5iZiI6MTczOTEzMTg2OCwicGF0aCI6Ii8xMzI2MjQ4LzM3NjY5MTY4OS1iYjY3NTBiYi0wZDA5LTRlZWItOTQxYy01MTRiNjk3NWQxNDAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDlUMjAxMTA4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZTRiMWMwNWIwOWFkNTFiNTRkMTMyYTE4ZjIxZTQwODEzNmEyMzYxYWQxNTJlYzBkMzI0YzFhYzgyNjljYjM5ZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.x89G8vzKkG92EmlRTVI12eMEWngB_1sa2CFAF2E-5jg)
Supported Coordinate Systems:
They no longer want to support TRS.
It’s confusing to the user that coordinates show up in both the map widget and the SF form.
![Image](https://private-user-images.githubusercontent.com/1326248/376791326-f2c7b359-1d84-4d8a-a088-cb2ae098017b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxMzIxNjgsIm5iZiI6MTczOTEzMTg2OCwicGF0aCI6Ii8xMzI2MjQ4LzM3Njc5MTMyNi1mMmM3YjM1OS0xZDg0LTRkOGEtYTA4OC1jYjJhZTA5ODAxN2IucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDlUMjAxMTA4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZDA0MTdmMmNmNDE0NjFhOWY3N2YyMGIwZjA2MGFkYjVhNjdiYjQxMTgzMzM2MWM1OTkwMmNhYjQwNjM5ZmZhOSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.jG1feFvwMXORRLoIi-fjWyb6rFOvf2Mm6ZHyqNaxUlI)
I think that we need to keep the inputs in the map widget to support entering non-default coordinate types. However, maybe they can be hidden after typing them in and hitting a submit button. They should definitely be hidden or updated when the location is updated via map click.
Note
This is also a feature that needs to be built for PLSS.
Tasks
The text was updated successfully, but these errors were encountered: