Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-23 Thread mmd
On 2/11/19 11:41 AM, wambac...@posteo.de wrote: > Hi, > > there is a relation https://openstreetmap.org/relation/2632934, which > currently has *42698 members*. Processing this rel with osm2pgsql fails, > because this value is bigger than 32737 (small int). > FYI: As a follow up to this

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread Roland Olbricht
There must have happened something ugly at versions 99 and 106: https://overpass-turbo.eu/s/FYm Thanks for that - yet again something useful in overpass-turbo ("make stat") that I had no idea existed.  Is there any documentation about it anywhere?  There is

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread wambacher
it's an old problem: https://github.com/openstreetmap/osm2pgsql/pull/716 need to check my osm2pgsql  (is 0.93 and should be ok, but it is not) walter -- My projects: Admin Boundaries of the World Missing Boundaries

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread ajt1...@gmail.com
On 11/02/2019 10:59, Roland Olbricht wrote: There must have happened something ugly at versions 99 and 106: https://overpass-turbo.eu/s/FYm Thanks for that - yet again something useful in overpass-turbo ("make stat") that I had no idea existed.  Is there any documentation about it anywhere? 

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread Jo
I split the route relation in 2. Didn't fix the erroneous use of route_master though. Polyglot On Mon, Feb 11, 2019 at 12:30 PM Jo wrote: > I'm looking into it, but someone completely misunderstood the use of > route_master relations and all those relations should be split in at least > 2, for

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread Jo
I'm looking into it, but someone completely misunderstood the use of route_master relations and all those relations should be split in at least 2, for each direction of travel / variation in itinerary. Jo On Mon, Feb 11, 2019 at 12:27 PM Maarten Deen wrote: > On 2019-02-11 12:14, Roland

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread Maarten Deen
On 2019-02-11 12:14, Roland Olbricht wrote: Hi, the relevant changesets are 65448087 (for version 99, created_by "upload.py v. 1") and 67093992 (for version 106, created_by "Vespucci 12.1.2.0"). I cite the user agents because the data looks like unintentionally changed that way. I have left a

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread Roland Olbricht
Hi, the relevant changesets are 65448087 (for version 99, created_by "upload.py v. 1") and 67093992 (for version 106, created_by "Vespucci 12.1.2.0"). I cite the user agents because the data looks like unintentionally changed that way. I have left a bug report on Vespucci, see

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread wambacher
Hi > this is an Osmosis problem. oops, osmosis. running osmosis 0.45. has this problem (int2 -> int4) solved in any other version? > Nonetheless, the relation does not make sense. It is an ordinary bus route in > Manhattan, but members hundreds of times repeated. > > There must have happened

Re: [OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread Roland Olbricht
Hi, > there is a relation https://openstreetmap.org/relation/2632934, which > currently has 42698 members. Processing this rel with osm2pgsql fails, > because this value is bigger than 32737 (small int). this is an Osmosis problem. Nonetheless, the relation does not make sense. It is an

[OSM-talk] Relation #2632934 is "killing" differential update

2019-02-11 Thread wambacher
Hi, there is a relation https://openstreetmap.org/relation/2632934, which currently has *42698 members*. Processing this rel with osm2pgsql fails, because this value is bigger than 32737 (small int). Reading in file: /osm/db/planet3/diffs/2019/02/11/2019-02-11T10:33:01.osc Using XML parser. node