README.md

OSMPubGuide-Backend

This repository is used to create an OSM based Pubguide, which deals with the aspects of an integration of temporal data. A customized API will be established, which will be used to provide additional, use case adapated information. On top of that, those temporal information should be stored within a database, which should be related to up-to-date OSM based information. A TileServer will serve Tiles, which focusses on specific entities.

How to start - Check the Wiki :)

To get started with the OHBPGIOSM Backend Part, please refer to this wiki. You will find a detailed setup and configuration guide as well as some information about the general idea and architecture.

1. System Overview (Idea, About, Architecture, Principles)
2. Webserver Setup and Configuration Guide
3. Database Setup and Configuration Guide
4. Tomcat 7 Installation and Configuration Guide
5. TileMill 2 Installation and Configuration
6. Vector Tiles via Docker Image
7. API-Documentation
8. Database Connection with JDBC and Netbeans.

---

Team Members:

• Andreas: aohrem
• Dominik: schlomm
• Fabian: froehr
• Ragnar: rw2013
• Stephanie: StephanieWalter
• Christopher: ChristopherStephan
• Ondrej: zvaraondrej
• Florian: flahn
• Tobias: TobiVanKenobi

Grouping

• Webservice / API
• Database
• Tile Server
• OSM & Overpass API Documentation and Review (will be skipped after the conceptual phase is done)
• Responsibilities: Check Sprint Backlog

Overall goals:

• Check Sprint Backlog for detailed Tasks, Task-Assignments and User Stories (click me)
• Deliverables:
  • System mockup
  • Documentation of decisions and components (Check Sprint Backlog)
  • Use Case adapted API to provide additional information (temporal information). The API will also be able to query OSM data using the Overpass API.
  • Use Case adapted database to store temporal information.
  • Use Case adapted Tile Services, which focusses on meaningful and useful entities.

Documents

• Github Backend (click me)
• Github Frontend (click me)
• Backlog: (click me)
• Sprint Backlog: (click me)
• OHBPGIOSM-API Concept: (click me)
• Tile Server Visualization Concept: (click me)
• OSM / Overpass API Documentation: (click me)

Architecture-Draft

Sprint Overview

• Sprint (1): 20.05.2014 - 10.06.2014
  • Conceptional work (Visualization concept, database schema, API)
  • Plans and detailed preparation
  • First rough prototypes (first implementation phase)
• Sprint (2): 10.06.204 - End of June
  • Actual start of implementation
  • Extend prototype
• Sprint (3): End of June - Mid of July
  • Actual implementation
  • More functionalities
• Sprint (4): Mid of June - End
  • Testing Finetuning Bugfixing

---

1. Sprint: 20.05.2014 - 10.06.2014

Organization:

• Scrum Master: Dominik
• Goals:
  • Conceptional work (Visualization concept, database schema, API concept)
  • Plans and detailed preparation
  • First rough prototypes (first implementation phase)
  • Server infrastructure

2. Sprint: 11.06.2014 - 01.07.2014

Organization:

• Scrum Master: Dominik
• Goals:
  • Implementation Phase (Extending API Prototype, Tile Server, Database)
  • API: Extending Prototype with more functionalities
  • Tile Server: Instance of an own Tile Server with own style.
  • Database: Function to handle operations on server side.