List view

• Import/Export

  In order to integrate the results obtained through the platform with other platforms it'll be implemented exporting mechanisms to format the obtained data to some standard format (i.e. GeoJson). Importing data should be considered for some popular formats such as GeoJson and Shapefiles too.

  No due date
  0% complete0 open0 closed

• Offline support and request/session recovery for lost connections

  Create mechanisms to provide automatic session and request recovery in case of lost connections.

  No due date
  0% complete0 open0 closed

• Security and access control

  The server should implement the HTTPS protocol and access control to some resources.

  No due date
  0% complete0 open0 closed

• User requests' progress

  The user should be able to request several resources at a time. In order to allow the user to verify which requests are done and how much others have progressed a mechanism to check and report the progress of current requests will be created. This mechanism is related to the "User's requests handler" milestone.

  No due date
  0% complete0 open0 closed

• User's requests handler

  Some user's requests are more demanding than others and can take more time to be processed. To avoid an overload at the server a mechanism to handle, enqueue and segment big requests will be created.

  No due date
  0% complete0 open0 closed

• Administrator dashboard

  The administrator's dashboard will inform about the different modules state (i.e. online/offline), total storage memory available, and the server's load in a given period.

  No due date
  0% complete0 open0 closed

• User panel

  The user panel should display to the user all saved sessions previously saved and allow the user to reload those saved sessions.

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• System's database/User's account

  The system's database will store data provided by the miners (image, map and GIS) and user's data. User's accounts will contain user's login information and sections information, that is, the user should be able to save the current marks done over the map and currently collected data in order to load the section afterwards and continue from the save point.

  No due date

  •2/2 issues closed
  100% complete0 open2 closed

• Marking tools/concepts

  The user interface (UI), the administrator's interface of the system (another UI) and the marking tools will be based upon common tools for GISes like ArcGIS, QGIS, OpenStreetMap or others. Some examples of common marking tools are, lines, circles and polygons and text. The common user (not an administrator) should be able to define an region of interest over the map and make some annotations using the marking tools.

  No due date

  •1/8 issues closed
  12% complete7 open1 closed