SIGUA sometimes returns multiple "estancia" for a given latitude longitude.

It seems that the first is the one in wich the latitude longitude is contained but this must be more extensively checked.

If it fails in some cases, a client fuction should check with the GeoJSON geometries retrieved for the given latitude longitude looking for the one in wich it is contained.

Tasks

1. [DONE] Mark issue location on map with a click
   1. Enable option for pin-point accuracy with user aimed location on click
   2. Extract data from marker to populate new issue page when user confirm's location
2. [DONE] Show Issue create page once location in map is confirmed
3. [DONE] Assign SIGUA data to the issue based on the latitude/longitude.
   • "Estancia"
   • "Edificio"
   • "Planta"
   • "Sede"
   • "Actividad"
4. POST new issue including SIGUA identifier
   1. Include user feedback about the notify
   2. If success, update map with newly created issue.
5. NotifyIssue page - Fill term dropdown based on static JSON term list hosted on webapp
   1. Generate the JSON from the provisional material list given by http://datos.ua.es/
   2. Fetch and populate dropdown
6. NotifyIssue page - Fill action dropdown based on static JSON hosted on webapp with action's related to a given term.
   1. Generate the JSON for the materials from the provisional material list given by http://datos.ua.es/
   2. Fetch and populate dropdown
7. Enhancement - Predefined location via GPS or viewed map center as default location for new issue

Tasks

1. [DONE] Tiles from SIGUA on map
2. [DONE] With all building floor's information
3. [DONE] GUI to change floor's
4. [DONE] Enhance user feedback on map change floor controls

I did a "hack" to have the notify issue button outside the collapsible and right aligned.

It seems that broke the default collapsible behaviour.

Problem

Overlapping collapsible with brand on mobile screen

Todo

• Check in Android emulator. ✅ Works fine.
• Check in real phone (Android emulator behaving correctly)

The view refreshes multiple times for each change on the issue while fetching "SIGUAEstancia" "SIGUASede" "SIGUAEscenario".

If the user had some input, those are losed by the full view refresh.

Solution

Render once the view, and then do indiviuadial focused updates on the concrete part of the view that has changed, not the whole.

Tasks

1. Issue detail - Show state history
2. Map - Show latest issue state with date

The system aims to show friendly url's to the user and support back/forward in history.

1. [DONE] Page manager with transitions betwen pages
2. [DONE] Url asociated with page
3. [DONE] Browser history interaction
4. Controllers expose pages so App.js can subscribe them to Page manager
   • Nowadays App.js "manually" creates the states and subscribe them.
5. Page state - onLoad (to load state data) and onTransitionEnd (to be able to give visual feedback) callbacks asociated with a page state

Scenario

Once visited the issue detail view trought map "ver detalles" click of a certain issue
If that issue is updated with the DEBUG bulk state update
When visiting again the same issue trought map "ver detalles" click
Estancia is not available at the model.

If instead of "ver detalles" click u navigate to issue detail page with the main navigation, the information is there.

Also if you navigate issue detail trought "ver detalles" of any other issue, the estancia is correctly fetched

• Also triggering events like "change:idSIGUA", wich doesnt happen in the bug scenario.