For climbing areas that haven't been mapped/tagged in OSM (a lot of them in
the US for example) I don't see it's being the problem. For existing areas
I would have to convince OSM community to convert nodes to areas, either
using iD, JOSM or my app. Am I seeing this right?
On Mon, Apr 24,
Thanks Martin and Simon.
It was my intention to reach out for suggestions before writing anything to
OSM db (and of course not without some testing with the dev instance).
Simon, can you please clarify what you meant by 'there is no other data
there'? Are you referring to the risk of creating
Martin has already pointed to the iD repo. But some further comments
from my side: simply creating objects and writing them to the OSM DB is
fairly easy, however there is an unspoken assumption in your concept:
that there is no other data there. In reality that will not be
universally true and
Hi,
you may want to take a look at iD's source code. Depending on what you
actually need, some of its code might be reusable (in form of
ES6-modules). For example, the code handling the interaction with
OSM's editing API is found here:
4 matches
Mail list logo
