and when did he change that. i can't find anything

hi, where is the problem? and where did you see it?
regards
walter

Nice (and correct) edit :)

wouldn't you like to go to the neighbourhood and add some more street names?

regards
walter

hiemand wonht da und es wird auch keine Post hingeschickt.

Toiletten mit Postalischer Anschrift? was soll der Sch... ?

Yes. this project is running for some years.
see https://wambachers-osm.website/index.php/projekte/internationale-administrative-grenzen/missing-boundaries

and yes, it's my baby :)

JOSM performance: it is not easy to describe what i want to say.

a) i allways have all BOUNDARIES in the area loaded to josm. i do this by loading incomplete elements using the relation window or the relation manager.

b) i load all DATA in that area i'm working. i.e. editing a boundary which is part of a river or overlays a river can be dangerous if the river is not loaded.

c) i have a big pc with much memory, therefore i increased the java storage to 1 GB.

all together gives me security and performance.

walter

hi, was not aware that many districts are missing. Don't panic, no reason to hurry :)

btw: do you want to have the word "district" in the names? nearly all other districts in india don't.

i don't use overpass - never. i load those boundaries only in josm. including all other data. this will prevent such errors.

but: i have a display filter "admin_level=* or boundary=administrative or place=*" which shows only the relevant parts.

walter

Hi,
gujarat is getting better :)

some districts still are missing. it should be quite easy to add them, because the "big work" by adding the ways has been done.

see https://wambachers-osm.website/images/osm/snaps_2018/gujarat.png

thanks and greetings from germany
walter

btw: the data is about 8 hours old (03:00 german time), may be you added some missings yet.

hi, because you did not remove the old part of the riverbank from all involved boundaries, you "killed" Georgia, South Carolina and some other bondaries in that area.

see cs: changeset/58607191 and check source link

btw: Using iD for such kind of work, is not the best. iD is for "beginners" or for "quick shots". You should be using JOSM for that, because the validator will inform you about such errors before uploading.

regards
walter

ok, well known problem: partial load of the boundaries only.

sh.t happens :(

what i allways do when i'v done my work: loading all uncomplete boundaries using the relation window, selecting all boundaries and then "validate"

regards
walter

Hi again,

may be you are a litte bit confused about Mapbox and Jinal?

I asked Mapbox some days ago if they could fix the missing AL5 in India (because my contact to MBX is an Indian lady - Jinal - with good contacts to the Indian community).
And they comitted to do so.

So I assumed you were a member of the team. Good timing ;)

Thanks,
walter/germany

btw: do you know https://wambachers-osm.website/boundaries? it's my baby.

Hi, thanks for adding some missing districts in india. But you damaged the AL2 of India, because you did not re-add the new outer with AL2 back to the indian country border.

see: https://wambachers-osm.website/images/osm/snaps_2018/india_damaged.png

of course somebody (not me) fixed that asap.
changeset/58580790

working for mapbox? greetings to jinal :)

Regards
walter

Hi, die Straße ist nicht richtig. Obwohl es optisch an der Ohmstraße liegt, gehören diese Häuser zur Rheingauer Straße.

Das erkennt man daran, dass das Haus die selbe Hausnummer (43) hat und addr:street=Rheingauer Straße
Zudem fangen die "echten" Häuser der Ohmstraße erst weit oben am Hang im Westen an.

hi,

nicht ganz richtig:

Offensichtlich ist das Hotel "Grüner Wald" umbenannt worden - und das solltest du bitte auch machen. Einfach einen neuen Knoten hinzuzufügen, dem auch noch "amenity=hotel" fehlt, ist nicht toll. Das ist eben kein "Edit".

Bitte lösche den neuen Eintrag und BEARBEITE den "Grünen Wald".

Gruss
walter (aus wambach)

ps: ob Osmand das kann, weiss ich nicht. iD oder besser JOSM können das.

thanks, great link

checked my historic osm database.

May be, the borders are not exact, but before that "fix", both boudaries where damaged. Because the segment i readded was missing.

see in JOSM before: https://wambachers-osm.website/images/osm/snaps_2018/before.png

with historic boundaries:
https://wambachers-osm.website/images/osm/snaps_2018/before_historic.png

and now:
https://wambachers-osm.website/images/osm/snaps_2018/now.png

the blue lines a the historic boundaries, not the waterways, which are blue too.

as i wrote before: the "old" way may be not exact but before that, the way was missing.
If you got more local details, please fix it, but don't delete this way.

Regards
walter

Hi testas,

what is going on in Lithuania? 357 Admin Boundaries with AL8 have been corrupted.

see. https://wambachers-osm.website/index.php/projekte/internationale-administrative-grenzen/missing-boundaries/10-osm-reports/1210-countries-compare-2018-04-28

walter,
germany

Hi, did you not understand, what i was saying?
The new "boundaries" are *technically* not ok.

May be the ways describing the border are better than before, but there are no boundary relations at all. Therefore this "pseudo boundaries" are not availiable to all OSM software except the mapnik renderer, which is "painting little pink lines" on the map.

- if will be not found in the osm-map (please try a search for Darthmout)
- it is unknown to nominatim
- it is unknown to Josm
- it will not be found on other maps or application.

It does not exist to osm, that's all.

Please goto other areas in your country and see the differences: e.g. Québec(8) relation/2319206

regards
walter

Yes, that is what you tried - but you didn' manage it.

i see, that you don't know how Admin Boundaries will be added and tagged in OSM.

- Admin Boundarties are *relations* with type=boundary, boundary=administrative, admin_level=X, name=yyy + some less important tags.
without those 4 base tags, they are rubbish.

- members are the ways defining the outer and sometime inner shape.

see: osm.wiki/Relation:boundary

What you did:
- painting some ways
- tagging them as "boundary"
- not respecting existing borders
- not creating boundary relations
- overlap boundary ways
- using iD for boundary mapping
- ... tbc

never ever seen so much errors by an user, which is mapping for about 6 years and submitting ~4700 changesets :(

BUT: you are motivated, did a lot of good work, have access to good boundary data :)

therefore: if you like i may help you to do it right.

Regards
walter