[OSM-dev] Multiple temporary API instances

Ian Dees ian.dees at gmail.com
Wed Aug 24 13:27:32 BST 2011


On Wed, Aug 24, 2011 at 6:53 AM, Josh Doe <josh at joshdoe.com> wrote:

> I'm interested in providing a facility whereby users can create and
> edit copies of OSM data for a small region, say 16 sq miles (~40 sq
> km). This is for a project [0] that I'm working on which would allow
> for users to experiment with adding/removing walking and bicycling
> infrastructure around a school to see how the changes impact
> accessibility (i.e. how many more kids can walk or bike to school
> given a specific change). While I'm quite a ways from implementing a
> full web app for all of this, I'd like to understand the challenges
> I'd be facing.
>
> I'd like to allow all of this to be done via a web interface, and I
> think Potlatch2 would be a good editor to provide. For that I'd need
> to set up a server side API, for which I believe the "rails port" is
> the only option. For a given school, it's possible that there could be
> dozens of users making changes to the same area, and each user may
> want to try out different combinations of changes. Therefore it makes
> sense to introduce the concept of "scenarios", where each scenario
> consists of a copy of the main OSM data. Users should be able to
> create, copy, and destroy these scenarios on demand.


 Josh, I've thought about implementing something like this for a couple
reasons:

- There have been several people interested in making maps of historical
areas or events. These certainly don't belong in the main API but using the
existing editors and tools would be nice.
- Give people somewhere to test their tools that is maybe a bit faster than
the dev API?
- Allow "offline" or "proxied" mapping at mapping parties that have crummy
network connections.

I'd be happy to work with you on this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20110824/aca7e2ce/attachment.html>


More information about the dev mailing list