GeoTracing:Development:Todo

From GeoWiki

This section can be seen as a roadmap for development of the GeoTracing platform and its applications like GeoSkating.

Table of contents

Open Source

  • hosting by CodeHaus (done geotracing.codehaus.org) DONE
  • cleanup CVS DONE
  • migrate to SVN DONE
  • migrate Wiki to Confluence
  • Determine licensing type for code (LGPL?). DONE
  • Determine licensing type for content (Creative Commons?)
  • make real roadmap
  • make project organisation plan
  • release plan
  • documentation plan
  • Invite more developers (now 3)

Documentation

  • determine documentation technology (Wiki/DocBook/XBook)
  • write whitepaper
  • document architecture
  • document protocols
  • document JavaScript (JSDoc)

GeoSkating Features

These features specific to the GeoSkating application.

  • find/display routes in are (bounding box)
  • find/display route when clicking a GPS-dot (Jan de Schipper)
  • better algoritm to render trace-map
  • OpenStreetMap integration

General Features

Server

  • user registration DONE
  • map-making daemon (generates maps from all trackpoints) DONE
  • location-based triggers (user sets condition like area or point and is triggered through protocol)
  • introduce Event service (g_event table) to attach tracks to events (startdate/endate)
  • add tagging of anything DONE
  • GPX import protocol DONE
  • media handling (movie conversion quality, movie thumbnails, image w/h, investigate Scilla) DONE
  • support text media DONE
  • support configurable POI-types (possibly do away with POIs entirely and use text media + tagging) DONE
  • support configurable trackpoint rating (now numbers 1-5)
  • export to Google Earth KML
  • allow commenting on data items (tracks, media, POIs etc)
  • trackpoints should go into table (not in g_track file field) DONE

WebClient

  • user registration and login DONE
  • user resource management (tracks, media) DONE
  • more flexible layout (allow different layouts)
  • improve color schemes and all icons
  • use GeoExt framework (ExtJS+OpenLayers)
  • upload GPX tracks (DONE)
  • manage media (e.g. add/replace photo's to existing tracks) DONE
  • manage POIs DONE (POIs are text media with tags now)
  • evolve to GMap2 DONE
  • resolve collisions like multiple media at one point (see e.g. PanoramaExplorer)

MobiTracer

  • allow registration plus download DONE
  • use relative screen sizes DONE
  • improve GPS info (km/h, direction) DONE
  • filter bad GPS data DONE
  • show where you are on map DONE
  • obfuscate DONE
  • make signed ?
  • view trace map on map (DONE)
  • view other users on map
  • send GPS based on criteria: quality, time and movement (send on minimal distance or time) DONE

TraceBox

Making MobiTracer and applications for each possible phone/PDA is a dead end. Given all the issues around software platform, high-end requirements (need smartphone with Bluetooth) and per phone/provider GPRS hassle. The TraceBox is planned to be a GPS/GPRS embedded hardware device. Its main function is to connect to a GeoTracing server submit GPS ssamples and dependent on hardware allow a user to submit some parameters. The real application will then be executed on any other device (phone, PDA, laptop) through e.g. a webbrowser using the KeyWorx multi-channel session capabilities. The TraceBox will be a matchbox-size device with a few LEDs, buttons and possibly a one-line display. It should be easy reprogrammable/configurable.

  • determine hard/software platform (Siemens TC-series, Telin)
  • work out usage scenarios

GWorx

These are features of a more general nature for the GWorx base.

  • how to deal with time/timezones throughout framework (all UTC?)
  • internationalization throughout
  • generic query mechanism/protocol (backport GT query, deal with field naming, deal with security) DONE
  • general interceptor architecture for Handlers (use for e.g. LBS and notification)
  • improve AJAX client DONE
  • make GWAdmin AJAX app that is extensible (app can add own menu items/handlers)
  • introduce per-server automatic configuration of resource URLs (based on server name/address particular configuration settings are set like the base URL). DONE
  • improve security (no clear passwords in config)
  • KWAdmin session in DaemonContext DONE
  • adapt to standards: use XML schema for protocols
  • allow index-setting for fields in in Oase table config DONE
  • use JAI i.s.o. ImageMagick
  • investigate incorporating Scilla for media management
  • image JPEG photo upload should use time in photo as creation time if possible (DONE)
  • uniform backup/restore (now two mechanisms) through KWadmin

Research

This concerns researching technologies/approaches with the idea of supporting and/or using these.

  • using a geospatial database like PostGIS or MySQL spatial (DONE)
  • which/how to support OGC standards (WMS+WFS+WFS-T)
  • using KML and Google Earth
  • georss
  • Use GeoExt (ExtJS+OpenLayers) web client
  • tiling JS (OSM) openlayers (DONE)
  • using XHTML apps for mobile phones/PDAs (what can be done with AJAX here e.g. Opera Mobile/Platform)