Re: [OSM-dev] Javascript library for the editing-API (not overpass)

[Viet Nguyen]

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, 2017 at 10:27 AM, Simon Poole  wrote:

>
>
> Am 24.04.2017 um 18:36 schrieb Viet Nguyen:
>
> 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 empty relations?
>
> I was referring to crag and other relevant data already being present in
> OSM (note that your proposed app will lead to such situations even if you
> believe that it currently can't happen).
>
> Simon
>
> Before writing to OSM my app would have to convert Geojson polygons (its
> native format) to OSM list of nodes similar to areas in iD.
>
>
>
>
>
> On Mon, Apr 24, 2017 at 1:29 AM, Simon Poole  wrote:
>
>> 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
>> will add complications that you likely don't want to deal with (or if you
>> ignore them you will not want to deal with being publicly roasted because
>> your app starts breaking things).
>>
>> I would really suggest building on existing code except if you want to
>> write the equivalent of a full blown editor all on your own (which is a
>> couple of man years of work).
>>
>> Simon
>>
>> Am 23.04.2017 um 18:46 schrieb Viet Nguyen:
>>
>> Hello,
>>
>> I'm a new subscriber.  I have looked on Github, iD repo, and npm but
>> haven't found a Javascript that can be used with the editing API.  Before
>> rolling my own library (JS is not my strong suit) I thought I should check
>> with members of the dev list.
>>
>> TLDR;
>> I want to experiment with creating polygons describing rock climbing
>> areas and submit them to OSM.
>>
>> https://lists.openstreetmap.org/pipermail/talk/2017-April/077879.html
>>
>> Viet
>>
>>
>> ___
>> dev mailing 
>> listdev@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/dev
>>
>>
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Javascript library for the editing-API (not overpass)

[Viet Nguyen]

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 empty relations?

Before writing to OSM my app would have to convert Geojson polygons (its
native format) to OSM list of nodes similar to areas in iD.





On Mon, Apr 24, 2017 at 1:29 AM, Simon Poole  wrote:

> 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
> will add complications that you likely don't want to deal with (or if you
> ignore them you will not want to deal with being publicly roasted because
> your app starts breaking things).
>
> I would really suggest building on existing code except if you want to
> write the equivalent of a full blown editor all on your own (which is a
> couple of man years of work).
>
> Simon
>
> Am 23.04.2017 um 18:46 schrieb Viet Nguyen:
>
> Hello,
>
> I'm a new subscriber.  I have looked on Github, iD repo, and npm but
> haven't found a Javascript that can be used with the editing API.  Before
> rolling my own library (JS is not my strong suit) I thought I should check
> with members of the dev list.
>
> TLDR;
> I want to experiment with creating polygons describing rock climbing areas
> and submit them to OSM.
>
> https://lists.openstreetmap.org/pipermail/talk/2017-April/077879.html
>
> Viet
>
>
> ___
> dev mailing 
> listdev@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/dev
>
>
>
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Javascript library for the editing-API (not overpass)

[Simon Poole]

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 will add complications that you likely don't want
to deal with (or if you ignore them you will not want to deal with being
publicly roasted because your app starts breaking things).

I would really suggest building on existing code except if you want to
write the equivalent of a full blown editor all on your own (which is a
couple of man years of work).

Simon


Am 23.04.2017 um 18:46 schrieb Viet Nguyen:
> Hello,
>
> I'm a new subscriber.  I have looked on Github, iD repo, and npm but
> haven't found a Javascript that can be used with the editing API. 
> Before rolling my own library (JS is not my strong suit) I thought I
> should check with members of the dev list.
>
> TLDR;
> I want to experiment with creating polygons describing rock climbing
> areas and submit them to OSM. 
>
> https://lists.openstreetmap.org/pipermail/talk/2017-April/077879.html
>
> Viet
>
>
> ___
> dev mailing list
> dev@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev



signature.asc
Description: OpenPGP digital signature
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Javascript library for the editing-API (not overpass)

[Martin Raifer]

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:

  https://github.com/openstreetmap/iD/blob/master/modules/services/osm.js

Best,
Martin


On Sun, Apr 23, 2017 at 6:46 PM, Viet Nguyen  wrote:
> Hello,
>
> I'm a new subscriber.  I have looked on Github, iD repo, and npm but haven't
> found a Javascript that can be used with the editing API.  Before rolling my
> own library (JS is not my strong suit) I thought I should check with members
> of the dev list.
>
> TLDR;
> I want to experiment with creating polygons describing rock climbing areas
> and submit them to OSM.
>
> https://lists.openstreetmap.org/pipermail/talk/2017-April/077879.html
>
> Viet
>
> ___
> dev mailing list
> dev@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev
>

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] XML xPath or trick to get way bounds

[François Lacombe]

Hi all,

With osm xml format (overpass, josm), is there any technique to get the
bounds of a given way ?

I want to get min lat/lng and max lat/lng without processing the whole
document (which can be pretty big)

This would be useful to list all nodes from my db contained into that
bounds prior to process ways.
I want to prevent numerous queries to check if each individual node exists
or not while importing ways, assuming that some nodes already exist and
some other don't.

The question can be extended to relations if possible

Thanks in advance for any hint

All the best
Francois
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev