My workflow in the last few days was to select/process series of way id's from
Frederik list with closed iterations that look to come from the same changeset.
Using the JOSM Overpass query function with instructions I provided earlier, it
is easy to download such a block of data, validate and
Hello,
Le 17.03.23 à 13:36, Harrison Scofield a écrit :
you can be overwhelmed by the shear number of "errors"
it's true, i think however the validator will only detect a douublon
only if you have touched or created a duplicate, so it seems to me
necessary to delete this duplicate before
I sure hope I am replying correctly to your reply! To clarify two
points: Yes, the JOSM "validator" detected the duplicate Ways, both
pipelines, highways and buildings which is how I discovered the issue.
Unfortunately, when you "upload", you can be overwhelmed by the shear
number of "errors".
Mar 16, 2023, 14:54 by sainokawara.sisyp...@gmail.com:
> By the way, it was extremely difficult to detect & delete these "extra" Ways
> manually using JOSM.
>
Have you tried https://josm.openstreetmap.de/wiki/Help/Dialog/Validator ?
Have you disabled validator warnings about duplicated ways?
Le 16.03.23 à 14:51, Harrison Scofield a écrit :
it was extremely difficult to detect & delete these "extra" Ways
manually using JOSM
https://www.openstreetmap.org/#map=19/5.85176/6.82890
clic edit with josm
in josm, open the validator pannel and run it
validator output several "duplicate way"
I don't know the "cause/effect" but several months ago, I noticed that
Ways were being "duplicated" multiple times when I used JOSM and they
weren't buildings! I could not determine whether it was at fault or
when it was only for specific types of ways but I did "report" a
potential problem to
From the OSM-id list of Frederik, it is possible to query with Overpass. For
the following list:
id1,id2,id3,id4
-15538065,-15538064,-15538063,1137657546
I isolate negative values and query as relation, others as way.
[out:xml][date:'2023-03-05T00:00:00Z'];
(
way(id: 1137657546
);
Le 14.03.23 à 21:35, Pierre Béland a écrit :
Hi Marc,
I created a csv file available on wetranser for 7 days.
in fact I was thinking about the overpass turbo query :)
to test it in my area
the 4 dates of edit.
a fast lookup show a lot of similar timestamp
but also some very old object...
Hi Marc,
I created a csv file available on wetranser for 7 days. It contains
901 quadruplets. For each line, the 4 OSM id's (similar to Frederik list) +
the 4 dates of edit.
See https://we.tl/t-rt9KSsZXBD
The osm-id list below refers to 77 buildings (ways) with level, layer or
building:part
Marc, I will revise and share data.
First, below are the instructions to extract relations metadata with
[out:csv(::changeset, ::timestamp,::user, ::type, ::id, building, highway,
level, layer, 'building:part', 'building:roof')];
relation(id:
3240506, 3240507, 3240508, 3240509, 3240510,
Le 14.03.23 à 13:45, Pierre Béland via talk a écrit :
I imported the osm metadata using overpass
can youu share it to avoid having to make it again :)
Simple Building duplicates from the same contributor are the easy ones to
correct.
yes, on the condition that you can easily detect when
Using id's from the Frederick quadruplicate list, I imported the osm metadata
using overpass. Note thate the negative values in the list represent relations.
The table below shows that the majority of quadruplicate cases implicate only
one contributor. Simple Building duplicates from the same
Le 11.03.23 à 13:35, Frederik Ramm a écrit :
it would be a good idea to try and find out what the root cause of the
problem is - bad software, bad imports, bad instructions?
I have already encountered 3 cases:
- as Warin says: create something in josm, save it as faile, send to
osm, don't
Many thanks for putting some numbers on this.
Warin's comment would suggest it may also be more than just buildings that
are involved.
For buildings the total number as a percentage is small unfortunately they
tend to cluster so are more of a problem than if they were more spread out.
John
On
On 11/3/23 23:35, Frederik Ramm wrote:
Hi,
I think an automatic fix of the problem is possible, however it would
be a good idea to try and find out what the root cause of the problem
is - bad software, bad imports, bad instructions?
I have duplicated an entry the following way in JOSM;
Hi,
I think an automatic fix of the problem is possible, however it would be
a good idea to try and find out what the root cause of the problem is -
bad software, bad imports, bad instructions?
To get an idea of how big the issue is, I did this on a standard
rendering database:
create
There are many and I have tools that can pick them out in a particular
area. However to use them I inspect the building visually before deleting
one or the other. Sometimes if the mapper has less than ten edits to their
name I may even skip adding a change set comment first.
However I do see
It might be better to check for building features which have a very large
percentage of their area overlapping with another, rather than an exact
duplicate, just in case there are a few kicking around that are identical
except for one vertex
Isaac
On Sun, Mar 5, 2023 at 7:05 PM John Whelan
Occasionally I come across a building that has been mapped twice. A
number of them look as if they have been uploaded twice.
Could some nice bot expert build one to run through the map and delete
any ways that are an exact duplicate even as far as the tags are concerned?
The problem comes
19 matches
Mail list logo
