Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Update the project's roadmap.

  • Loading branch information...
commit d358b98384e50ee670644ef586dfdd47597e4e54 1 parent 5e5c38e
@jkoshy jkoshy authored
Showing with 22 additions and 15 deletions.
  1. +22 −15 doc/Roadmap.md
View
37 doc/Roadmap.md
@@ -1,35 +1,42 @@
## About
-This page lists the planned evolution of the server.
+This page lists the proposed evolution of the server.
-## Version 0.5
+## Current Status
-* The code is functional, but need not be fast.
+* The code is functional: [planet dumps][osmplanet] can be ingested and their data retrieved using the [API][osmapi].
+* Serving data via the API is quite fast (see [ProvisioningInformation][]), but ingesting a full planet is slow.
* Modules have unit tests.
-* External documentation is upto-date.
-* [Planet dumps][osmplanet] may be ingested and their data retrieved
- using the [API][osmapi].
-* Supported data store: [Membase][].
+* External documentation (i.e., the `doc/` directory) is upto-date.
+* The supported data store is: [Membase][].
-## Version 0.7
+## Future work
-* Performance bottlenecks have been identified and addressed.
-* Full [Planet dumps][fullosmplanet] dumps are supported, along with
- retrieval of history and previous versions of elements (tickets [#14][issue14] and [#4][issue4]).
-* The "front-end" is fully asynchronous ([#2][issue2]).
-* System tests have been added.
-* Wiki and internal documentation is complete and upto-date.
-* Supported data stores: [Membase][] and possibly [Riak][] ([#6][issue6]).
+* We need to support 'full' [Planet dumps][fullosmplanet] dumps, along with
+ retrieval of changesets, element history and prior versions of elements (tickets [#4][issue4] and [#14][issue14]).
+* Performance improvements that have been identified so far could be addressed:
+ * The `/map` API call could be further speeded up by grouping nodes and ways based on geographical proximity.
+ * The ingestion tool needs to be speeded up ([#13][issue13]) and possibly rewritten in a non-interpreted language.
+* Storage efficiency can be improved:
+ * A separate string table for frequently used strings could cut down storage needs.
+ * Slabs could be coded more efficiently ([#9][issue9]).
+* The "front-end" needs to be made fully asynchronous ([#2][issue2]).
+* System tests that verify end-to-end integrity of the ingestion process are needed.
+* More supported data stores: possibly [Riak][] ([#6][issue6]) for a scalable backend, or perhaps [BerkeleyDB][] for a single machine configuration.
<!-- References -->
+ [BerkeleyDB]: http://www.oracle.com/technetwork/database/berkeleydb/overview/index.html "Berkeley DB"
[fullosmplanet]: http://wiki.openstreetmap.org/wiki/Planet.osm/full "Full OSM Planet"
[issue2]: https://github.com/MapQuest/mapquest-osm-server/issues/2
[issue4]: https://github.com/MapQuest/mapquest-osm-server/issues/4
[issue6]: https://github.com/MapQuest/mapquest-osm-server/issues/6
+ [issue9]: https://github.com/MapQuest/mapquest-osm-server/issues/9
+ [issue13]: https://github.com/MapQuest/mapquest-osm-server/issues/13
[issue14]: https://github.com/MapQuest/mapquest-osm-server/issues/14
[membase]: http://www.membase.org/ "Membase"
[osmapi]: http://wiki.openstreetmap.org/wiki/API_v0.6 "OSM v0.6 API"
[osmplanet]: http://wiki.openstreetmap.org/wiki/Planet.osm "OSM Planet"
+ [ProvisioningInformation]: ProvisioningInformation.md
[riak]: http://www.basho.com/ "Riak"
[wiki]: https://github.com/MapQuest/mapquest-osm-server/wiki "Wiki"
Please sign in to comment.
Something went wrong with that request. Please try again.