Model

• User (osm user)
• User activity
• Area
  • user activity areas
• Feature
  • user activity features
• Issue
  • area
  • feature
  • user fixed

Working mechanism

• subscribe to diffs http://wiki.openstreetmap.org/wiki/Planet.osm/diffs
• check diff by each feature
• if feature find mistakes then create issue
• check diff by each open issue in feature
• if issue gone then mark feature closed by user

Aries hierarchy

• world divided to parts from biggest on top to small on bottom
• top level is country division
• middle levels is administrative division
• bottom level is computed small parts (small enough to manage any new use)

Features

• any user can see feature implementation
• feature have access to:
  • diff
  • osm api
  • osm postgis database with geometries
  • any another source

Stories

User subscription

• user login to app with osm account
• user select watching areas
• user select watching features
• user can see open issue in watching areas
• user can generate feed (rss) and now can see new issues in watching areas

Extend area or features

• user can extend watching area or features

Issues resolving

• user select issue and can select hinted resolution or fix it on external editor
• when user selected hinted resolution then issue will be changed via OSM API
• when new diff will come then issue will be marked as resolved by user

now not all views require user, but all processed by it, better replace it with explicit login_required view decorator

dockerize applications with docker compose:

• web
• validator schedule
• db
• redis

now validators running one after one, but it can be running in parallel:

• https://github.com/tbicr/osm-validator/blob/master/osm_validator/validators/base.py#L47
• https://github.com/tbicr/osm-validator/blob/master/osm_validator/validators/base.py#L41
• https://github.com/tbicr/osm-validator/blob/master/osm_validator/validators/base.py#L35

• remove requests from requirements.txt
• find and replace usage to asyncio analog

now issues closed one by one, but it can be improved with bulk update https://github.com/tbicr/osm-validator/blob/master/osm_validator/validators/processor.py#L206

• ui: user page with activities
• api: list of activities
• api: get one activity
• api: create activity (set name)
• api: update activity (change name)
• api: delete activity

now shell calls sync, but should be replaced with async analogs:

• https://github.com/tbicr/osm-validator/blob/master/osm_validator/validators/processor.py#L70
• https://github.com/tbicr/osm-validator/blob/master/osm_validator/validators/processor.py#L96

1. move from requirements.txt to https://docs.pipenv.org/
2. keep locked dependencies on Pipfile.lock
3. fix dependencies: aio-libs/aiohttp#2662

• periodically running
• avoid running in parallel