Below is a summary of the major features that I am hoping to include, and you are invited to leave your feature requests as comments here too. (I may eventually get around to formalising this in a code repository.)
-  Editing of control locations, numbers and number positions for existing maps, via the web interface.
-  Saving of existing maps, via a short URL.
- Applying out of bounds points (e.g. gates), lines (e.g. major roads) and areas (e.g. closed parks) to the maps.
-  Addition of a new style – Street-O Enhanced, which builds on the Street-O style but adds parks, open areas and other useful features.
- Addition of a new style – Urban Adventure, which includes street names for the larger roads.
-  Automatic creation of the clue-sheet.
-  Assignment of points values to the controls. This will help with the clue-sheet creation and potential future route-analysis applications.
- Optional colouring of control circles based on points values.
- Better match of the look of the web preview and the final PDF.
- A basic how-to guide.
- Inclusion of a OpenStreetMap editing 101 guide.
- Output of a high-resolution raster (e.g. JPG) of completed maps and “blank” maps, for embellishment in Purple Pen etc.
-  Automatic daily refresh of the data from OpenStreetMap.
-  Increase contour widths and/or darken colours.
- More configuration options, e.g. railways on/off, contours on/off.
- Import/export of courses, probably via text config file.
- Allow separate start and end points.
- Creation and setup of an alternative tile rendering source.
-  Use source code management for the website and the stylesheets.
-  Better usage tracking and statistics.
- Use OS Open Data Vector Map District as alternative data source – misses out paths/parks, but complete coverage for roads.
-  Apply OpenOrienteeringMap logo and branding.
- Create point-to-point courses, with straight lines between each line.
- Use SVGs rather than raster graphics for points and complex lines.