Based on a custom route, a user should be able to downlaod a standard GPX file

Technical notes:

• This is a backend REST endpoint feature

AC:

• One endpoint should be defined
• TBD
• ...

As writing up a hike can be no easy task on a JSON file, I would rather like an automatic way to import such hike to system.

• User should be able to add N POIs
• User should be able to add waypoints to connected trails
• User should be able to customize:
  • Name
  • Description
  • Difficulty rating

Tech notes

• Makes use of already adopted technologies
• Could be RESTful too, secured by local requests allowed only (DMZ).
• Allows to upload a GPX file to generate the GEOJson one

AC:
-Determine what data should be
-Join the postcode and other
-Write a script that periodically imports the POI to DB

The following should contain a set of data for functional and informative use.
Define that and implement it in the codebase.

• POI
• Trail
• Waypoint
• Route

AC:

• Add all needed to quickstart developing
• Test the configuration

REST

• Should match data structure expectation as defined in #7
• Update the Swagger file
• Add controller endpoints
• Update the init_db.js

AC:

• Create a paper/mockup template
• Draw also a few interactions about:
  ** Getting a trail data
  ** Plan a hike
  ** Show some POI data
• Gather the icons needed for it to go live

AC:

• Choose the categories format
• Determine what data should be imported
• Join the postcode and other fields
• Write a procedure to import the POI in a compatible format

AC:

• Update Swagger file
• Add a controller
• Eventually update the init_db.js file

AC:

• Add a controller endpoint
• Add reference to trail

AC:

• As specified in Swagger as for #7
• Implement also all performance improvements from on DB side
• Support to geo based searches

AC:

• Add a rest endpoint
• Add a proper response type

This enables:

• Checking for close hikes to any point
• Provides much faster hiking import (waypoints can be suggested on import)

Given the user coordinates and a final destination, if the latter is a Poi, a destination or a trail start, system should investigate and find a route to destination.

REST

• All
• Request by
• Destination position

Further options:

• All
  • Y/N Should check all close trails for available routes?
• coords:
  • Y/N should specify for radial distance from point

Business logic

• Response should include trails, waypoints, poi references
• Shortest paths are rated higher

AC:

• Create a test set

• Run Parallel executions

• Check DB performance (are indexed all used by all queries?)

• Note down all average times

Code coverage does not make a project of any greater quality but helps into understanding what it is not cover by tests. Does awareness make me responsible?

AC:

• Investigate most common code coverage frameworks
• setup a ci code coverage tool
• integrate it with Travis CI
• Only REST service shall be covered

• Research and add a stub UI with frameworks of choice
  • A graphic template shall be choosen
  • The framework shall be choosen on the base of:
    • speed of dev
    • maintainability
    • adoption

• Add the basic components and libraries needed for the UI development