subject:"\[OSM\-talk\-be\] intersection looks very wrong"

Re: [OSM-talk-be] intersection looks very wrong -> use PICC with JOSM

2017-11-13 Thread Jakka

Thx for the reply,
Was working on it this WE several houres allready and saved it offline.
Will checked again 'with after an good night sleep) and hopefully I can
uploaded all changes at once.
The PT relation will all be destroyed, could not keep the highway with
them on it.

Op 13/11/2017 om 0:58 schreef André Pirard:

On 2017-11-11 13:49, Jakka wrote:

The middle intersection looks very wrong. Want to redesign it. There
for need to know if the aerial image on "Wallononmap" are still
corresponding with what is out there ? Or are there other images ?
The same with intersection north and south of it I need to connect
directly good on those also.
Check this in editor:
1)
https://www.openstreetmap.org/#map=19/50.543085562147645/5.4872411965277195
Check a routeplanner
2)
https://www.mapcat.com/directions/car#map=18.9/50.54324/5.48770&route=50.54312,5.48745;50.54332,5.48772
check aerial image I want to work with. No Mapillary image yet.
3)
http://geoportail.wallonie.be/walonmap#SHARE=5DB543FAA0BC7C61E053D0AFA49DE388#CTX=DDB

The problems are:

* That the roads are drawn too wide and one cannot see the turns they
make to enter or leave the main road; "we should not tag for the
renderer" they say but report the problem to them. But maybe
changing the road types as soon as they start turning and not when
they enter the side road would help.
* That the mappers did not use JOSM+PICC (rarely needing the
orthophotos because PICC is rarely wrong), they used Potlatch and
ID; but in this case the photos are necessary; using BE SPW(allonie)
2012-2013 aerial imagery is clearer that 2015 which is clearer that
2016.

*PLEASE USE JOSM + PICC*: I have spent much time getting them working. I
have been repeatedly laughed at when I was requesting the SPW to correct
their projection bug and I kept hearing "we cannot copy yet" which is
not what we are doing.
If I had been heard, we would have been able to map Wallonia correctly
since 2010.
I am doing *a lot* of corrections (Jakka seems too), often moving houses
and other elements by 2, 3, ... 5m or more, adding numbers, using
Improve Way Accuracy mode to straighten roads, etc.
With JOSM a house is drawn, including increasing number, in a single
click. Correcting a badly mapped one takes much longer and one feels
like erasing it.

I doesn't look like this intersection changed over the years nor lately
(latest OSM topology around 2013).

Here is how you see that intersection with JOSM and PICC:

route du Condroz PICC

route du Condroz aérienne

You can see that PICC is right.
The OSM two lower main lanes are offset north by more than 2m in the
middle and to the right.
The upper one makes a bump that it shouldn't do, it should go straight on.
The turns going diagonally make no sense. They should go straight and
then make a sharper turn.
Like the one coming from the left: it should be passing somewhere over
the stopped car.
They should certainly not connect (on a dot in common) with the other
ways they cross !!!
==> beware not to destroy relations when changing those dots erroneously
belonging to 2 ways:
JOSM will warn you but I'm not sure about the others: they destroyed my
relations.
The yellow, north-south roads are not precisely in the right place either.

Hoping this and the PICC can help,
Cheers
Cordialement,

André.

___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] intersection looks very wrong

2017-11-11 Thread Gerard Vanderveken

In Streetview it looks the same.
I see this of a typical case of willing to map too much.
By that I mean every turn (or shortcut) from one lane to all possible
others.

The crossing should look in its basic form like a #.
Is it needed to represent every lane as separate roads?
I don't think so.
Only when there is a real division in the form of a physical separation,
other then a simple white line, such as a sideway, traffic island,
arched surface, ..., additional trunks should be mapped.
For all other things tagging Lanes
and Turning indications
per lane

should be sufficient to map this crossing.

A lot of cleanup is needed here, starting with the 2 trunks 214506429
and 115952062

Regards,
Gerard.

Jakka wrote:

Check this in editor:
1)
https://www.openstreetmap.org/#map=19/50.543085562147645/5.4872411965277195

Check a routeplanner
2)
https://www.mapcat.com/directions/car#map=18.9/50.54324/5.48770&route=50.54312,5.48745;50.54332,5.48772

check aerial image I want to work with. No Mapillary image yet.
3)
http://geoportail.wallonie.be/walonmap#SHARE=5DB543FAA0BC7C61E053D0AFA49DE388#CTX=DDB

___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

[OSM-talk-be] intersection looks very wrong

2017-11-11 Thread Jakka




The middle intersection looks very wrong. Want to redesign it. There for 
need to know if the aerial image on "Wallononmap" are still 
corresponding with what is out there ? Or are there other images ?
The same with intersection north and south of it I need to connect 
directly good on those also.

Check this in editor:
1) 
https://www.openstreetmap.org/#map=19/50.543085562147645/5.4872411965277195

Check a routeplanner
2) 
https://www.mapcat.com/directions/car#map=18.9/50.54324/5.48770&route=50.54312,5.48745;50.54332,5.48772

check aerial image I want to work with. No Mapillary image yet.
3) 
http://geoportail.wallonie.be/walonmap#SHARE=5DB543FAA0BC7C61E053D0AFA49DE388#CTX=DDB



___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] intersection looks very wrong -> use PICC with JOSM

Re: [OSM-talk-be] intersection looks very wrong

[OSM-talk-be] intersection looks very wrong

3 matches

Site Navigation

Mail list logo

Footer information