Change Details

As a user, I want to add Statements using coordinate datatypes to Wikidata, and see them displayed on the main page. **Note: This ticket is not ready yet** {F71453567} [[ https://www.figma.com/design/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4--separated-because-file-was-too-heavy-?node-id=138-6172&t=bnULbyseexhrBWhV-1 | Figma File ]] - Once any property related to coordinates is selected, the input field for coordinates appears - once the input field is taped, the native keyboard comes `//discuss with the team if there is the possibility of having a keyboard with numbers and letters for coordinate input//` - When something is typed in the input field, the popover with the data rendering (will be displayed as) and the precision shows up - When the value inserted is not a valid coordinated, the data rendering is "Value malformed" - When the value typed in is a valid coordinate, the map appears displaying the pin on the location, and the publish option becomes active - The map and pin are //show only//, you cannot change the coordinates typed in by interacting with the map - In the map, you can zoom in and out `//- Discuss with team if there can/should be a full screen version of the map//` - The map includes links to the wikipedia maps and open street maps - these should open in a different tab if tapped - Under the map the user can see and change the precision - clicking change should bring out the native phone picker, with the available options inside

As a user, I want to add Statements using coordinate datatypes to Wikidata, and see them displayed on the main page. {F71469403} [[ https://www.figma.com/design/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4--separated-because-file-was-too-heavy-?node-id=138-6172&t=bnULbyseexhrBWhV-1 | Figma File ]] - Once any property related to coordinates is selected: the input field for coordinates appears - When the input field is active, the native keyboard is activated - we need letters numbers and punctuation ---- discuss with team how to make paste action easier, since this is probably what users do most and can be tricky {F71469410} **Once there is something in the input field:** - The popover for coordinates appears - The display for coordinate rendering and precision starts reflecting the changes - If the coordinate is not valid: display "Value malformed" - If the coordinate is valid, the map appears and the publish button becomes blue (default state) - The map is view only, moving around does change the coordinate input - Discuss with team if we should have a full view on mobile - The links to wikimedia maps and openstreet maps are to be open in new tabs **The precision button & drop-down:** {F71469415} - Are native components and will look different according to operating system. - These allows the user to override the automatic selection, and select their own. - The button itself should be big enough to display the word automatic in whatever is the display language, in a font size 12 - If the user selects something other than "automatic": ---- the location rendered and the precision value update accordingly ---- The selection reflects in the button, truncated to the same amount of letters that the word automatic has in the displayed language* OR if easier, lets say 10 values. This will make the value in the button hard to decifer, but the precision will be stated in front in the big display anyway. It is only important for the user to understand that it is not longer in automatic modus - the drop-down also allows the user to revert back into automatic selection: this is the first option in the menu *(in the case of english 9 - in the case of german "automatisch" 11, for example. Is it possible to have this rule or do we need to find a number and stick to it?)

As a user, I want to add Statements using coordinate datatypes to Wikidata, and see them displayed on the main page. **Note: This ticket is not ready yet** {F71453567}69403} [[ https://www.figma.com/design/9RwXYJxIYnuglDCwfBWi9H/MEX-Milestone-4--separated-because-file-was-too-heavy-?node-id=138-6172&t=bnULbyseexhrBWhV-1 | Figma File ]] - Once any property related to coordinates is selected: the input field for coordinates appears - When the input field is active, the native keyboard is activated - we need letters numbers and punctuation ---- discuss with team how to make paste action easier, the input fieldsince this is probably what users do most and can be tricky {F71469410} **Once there is something in the input field:** - The popover for coordinates appears - once the input field is taped, the native keyboard comes `//discuss with the team if there is the possibility of having a keyboard with numbers and letters for coordinate input//` - The display for coordinate rendering and precision starts reflecting the changes - When something is typed in the input field, the popover with the data rendering (will be displayed as) and the precision shows up - If the coordinate is not valid: display "Value malformed" - When - If the value inserted is not acoordinate is valid coordinatedid, the data rendering is "Vamap appears and the publish button becomes blue malformed"(default state) - When the value typed in is a valid coordinate, t - The map appears displaying the pin on the locationap is view only, and the publish option becomes activemoving around does change the coordinate input - The map and pin are //show only//, you cannot change the coordinates typed in by interacting with the map - Discuss with team if we should have a full view on mobile - The links to wikimedia maps and openstreet maps are to be open in new tabs **The precision button & drop-down:** {F71469415} - Are native components and will look different according to operating system. - In- These allows the user to override the mapautomatic selection, you can zoom in and outand select their own. `//- Discuss with team if- The button itself should be big enough to display there can/should be a full screen version of the map//` word automatic in whatever is the display language, in a font size 12 - The map includes links to the wikipedia maps and open street maps - these should open in a different tab if tapped- If the user selects something other than "automatic": - Under---- the map the user can see and change the precisionlocation rendered and the precision value update accordingly - clicking change should bring out the native phone picker,--- The selection reflects in the button, truncated to the same amount of letters that the word automatic has in the displayed language* OR if easier, lets say 10 values. This will make the value in the button hard to decifer, but the precision will be stated in front in the big display anyway. It is only important for the user to understand that it is not longer in automatic modus - the drop-down also allows the user to revert back into automatic selection: this is the first option in the menu *(in the case of english 9 - in the case of german "automatisch" 11, for example. with the available options insideIs it possible to have this rule or do we need to find a number and stick to it?)