[OSM-talk] New API suggestion: Allowing contributors to easily track their OSM-objects over time

[pangoSE]

Hi Andy 😀

Andy Townsend <ajt1047 at gmail.com> skrev: (22 augusti 2020 13:03:56 CEST)
> > How/where was the notes addition proposed and implemented?
>
>If I remember correctly, it was done as a "Google Summer of Code" 
>project - effectively a sponsorship deal.  However, that project 
>requires a clone of the OSM website, which is a much harder job than 
>merely doing something with OSM data as it is updated.

Yeah. We should make it dead simple and easy to spin up a copy of our website and demo database for anyone to hack on on their pc or in the cloud. I'm going to contact the operations workgroup and start working on that because its crucial to making the much nedded improvements I'm interested in.

>
> >  I intended to write it myself it others find it useful.
>
>Great!
>
> > I would prefer that it is an official api so I don't have to cover 
>the hosting costs.
>
>Well if you start writing it locally and start initially with a small 
>extract of OSM data your hosting costs will be zero.  Even if you 
>absolutely need to go for a hosted server it needn't cost more than a 
>Northern European cup of coffee a month to start with (see e.g. 
>https://blog.jochentopf.com/2019-03-07-the-new-osmdata-service.html )

What a valuable writeup! Thats very cheap, interesting.
I just found http://fuga.cloud which is openstack based and also very cheap.

>
>>  Is there anywhere to post an issue to implement this and later pull 
>requests?
>
>I'd suggest creating such a place in a shared code repository such as 
>github (which is where lots of OSM-related stuff already is).  Don't 
>worry that it isn't "official" - very little in OSM is.  If it becomes 
>valuable it can easily be built on or incorporated into osm.org 
>centrally later.

All right, sounds reasonable 👍

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20200823/b1ea4db8/attachment.htm>