Author Topic: roudj: Romania Drumuri Județene  (Read 23172 times)

0 Members and 2 Guests are viewing this topic.

Offline panda80

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 264
  • Last Login:February 29, 2024, 07:57:27 am
Re: roudj: Romania Drumuri Județene
« Reply #45 on: December 27, 2019, 09:47:11 am »
Is the pace fine to you or should I try to accelerate and get the review done by January 6? I don't know how much time I'll have from week 2.
The pace is up to you. I am always a few posts behind your review, so if you will increase the pace , the difference will be higher.
If you decrease the pace after KW2, it's no problem, as my time will be also more limited afterwards.

I think it's better to keep the difference small.

After the next site update, I am 1 post behind. Just corrections from post 42 have to be implemented.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: roudj: Romania Drumuri Județene
« Reply #46 on: December 27, 2019, 10:38:24 am »
I think it's better to keep the difference small.

After the next site update, I am 1 post behind. Just corrections from post 42 have to be implemented.

It's fine. And do the Oradea stuff. I just think that it's better for me not be too much ahead in case you have a question. That's why I review some gbnb routes collateral.
If I'm too slow and you have time, you can also start with SCT, WLS or DEU-HE.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: roudj: Romania Drumuri Județene
« Reply #47 on: December 27, 2019, 03:31:38 pm »
DJ200:
DNCB must be positioned here: http://www.openstreetmap.org/?lat=44.515292&lon=26.190387


DJ200A:
DNCB must be positioned here: http://www.openstreetmap.org/?lat=44.539369&lon=26.142322


DJ201:
DJ306 is off


DJ201B:
StrIng -> StrEng, energy, not engineer ;)
DJ403 doesn't intersect in HB because the wp is missing on DJ403 route


DJ202:
DN23A/23B is off


DJ202A:
DN23 is off
Rac is off


DJ202B:
DN23 is off


DJ202E:
Exceeds limits b/n DC186 and DN2
DN2N is off


DJ202F:
I cannot see any route on WorldImagery between +X2 and +X3. Show me or split the route.


DJ203D:
DC34 -> DC24


DJ203G:
DN10 is off
Are you sure about the route at +X03? OSM and GM do both indicate the eastern road being DJ203G.
Merge DN1B_E and DN1B_W into one wp


DJ203J:
DJ203K should be moved to the next junction just a few meters to the west


DJ203K:
Move DJ204C to the traffic island
DN2_S is off, move it to the underpass of the GSJ
+X3 is off


DJ203R:
Exceeds limits b/n DJ203P and +X1

Offline panda80

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 264
  • Last Login:February 29, 2024, 07:57:27 am
Re: roudj: Romania Drumuri Județene
« Reply #48 on: December 28, 2019, 12:59:57 am »

DJ195Ard:
Rename file and route short name to DJ195 (keep Ardud in city field though), ask if procedure is not clear

I confess I don't understand what you mean. There is no DJ195Ard, just DJ195 and DJ195Pot. DJ195 has Ardud in the city field and it's the longest of the 2 roads. Should I rename the file rou.dj195.wpt to rou.dj195ard.wpt?

Quote
DJ196B:
DJ196C location looks odd. OSM and GM have a different route to the south
DN19_S is off
DN19_N is off
There is just one DN19 on DJ196B. Position was slightly off, corrected.


Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: roudj: Romania Drumuri Județene
« Reply #49 on: December 28, 2019, 03:13:49 am »
DJ195Ard:
Rename file and route short name to DJ195 (keep Ardud in city field though), ask if procedure is not clear

I confess I don't understand what you mean. There is no DJ195Ard, just DJ195 and DJ195Pot. DJ195 has Ardud in the city field and it's the longest of the 2 roads. Should I rename the file rou.dj195.wpt to rou.dj195ard.wpt?

Sorry, I assumed that the wpt name is wrong but I only checked the list name in HB:

Code: [Select]
.list name: ROU DJ195Ard
The error is in the roudj.csv file (_csv is fine):

Code: [Select]
roudj;ROU;DJ195;;Ard;Ardud;rou.dj195;
roudj;ROU;DJ195;;Pot;Potău;rou.dj195pot;

Ard is entered in the abbrev field which is not required / wrong. The longest route does not get an abbreviation.
I thought that the wpt file name contains ard too but it doesn't.

The manual doesn't mention it but there is an example (grc.a005):

Code: [Select]
The route is a concatenation of 3-digit zero-padded number designation (e.g., a005, us042, pa343, la3132), the banner if applicable (bus, trk), and the 3-letter Abbrev. if applicable (e.g., cat, pit).
Examples:

    fra.a021.wpt = France A21.
    pa.pa042trkeag.wpt = Pennsylvania PA 42 Truck (Eagles Mere).
    grc.a005.wpt = Greece A5 (main piece).
    grc.a005art.wpt = Greece A5 Arta section.


Please fix it for other routes too. Always check in wpt editor or HB which route is the longest:
Code: [Select]
DJ105D
DJ159
DJ194B (3 routes)
DJ195
DJ208G
DJ222D (4 routes)
DJ255A
DJ562
DJ682E
DJ707L
DJ709A

Quote
DJ196B:
DJ196C location looks odd. OSM and GM have a different route to the south
DN19_S is off
DN19_N is off
There is just one DN19 on DJ196B. Position was slightly off, corrected.

DJ106C.

Sorry, I have a text file offline. I always add the issues at the end. Sometimes I forget to enter the line with the next route name and add the issue to the last route of the list by accident. That means, if you don't find it, it's often just the next route, or one of the next routes... ;)
« Last Edit: December 28, 2019, 03:16:29 am by michih »

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: roudj: Romania Drumuri Județene
« Reply #50 on: December 28, 2019, 03:17:50 am »
Please check routings through Tasnad (DN1F, DJ191, DJ109P, DJ108L). OSM, GM and GSV show different routings.

Was it correct?


Maybe I missed it but I don't see changes in Zalau in this pull requested: https://github.com/TravelMapping/HighwayData/pull/3463
Are the "post 42" issues not yet completely revised?

Please check routings through Tasnad (DN1F, DJ191, DJ109P, DJ108L). OSM, GM and GSV show different routings.


DJ191A:
How are DN1F and E81 routed through Zalau? 2018 GSV indicates E81 routed like it's on OSM and in HB. The sign didn't exist in 2012. E81 is also signed on the eastern route as you can see on a sign in the south (was already there in 2012). Thus I'd suggest:
- DN1F -> DN1F_N
- DN1F, E60 and DJ191A need a new wp @ http://www.openstreetmap.org/?lat=47.186457&lon=23.058921

But the signs do only indicate E81, not DN1F. I assume that E routes are always concurrent to DN routes but I don't know for sure. Maybe DN1F is on the western route through Zalau as it's indicated on OSM? What do official sources say?
« Last Edit: December 28, 2019, 03:21:03 am by michih »

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: wp is off
« Reply #51 on: December 28, 2019, 05:21:45 am »
Just a general note:

When I mention a wp being "off", I don't go with OSM only (like I did in pre-canmb-times) but always check the location on Esri WorldImagery too.
That means: I zoom-in to max with OSM Default layer, zoom-out twice. I click through the table and check the wp location and all non-TM-route label names (here, DC route names, street names, village names). When the wp looks off on OSM, I change to Esri WorldImagery layer. If it's also off here, I report the wp as being "off".

Note: Sometimes OSM is off compared to WorldImagery. Sometimes the junction is larger than it looks like on OSM. Sometimes the real situation and the best wp position is only clear - traffic island, road markings, slip roads,... - when checking on WorldImagery. I think that I don't report about 30...50% of the wps which look "off" on OSM. OTOH, I don't check wps on WorldImagery at all which look fine on OSM.

This should be considered when updating the location.

I recommend peer-reviewing other systems similarily.

Offline panda80

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 264
  • Last Login:February 29, 2024, 07:57:27 am
Re: roudj: Romania Drumuri Județene
« Reply #52 on: December 28, 2019, 06:27:12 am »
Was it correct?

Maybe I missed it but I don't see changes in Zalau in this pull requested: https://github.com/TravelMapping/HighwayData/pull/3463
Are the "post 42" issues not yet completely revised?

Tasnad was correct (I remember I spend some time there also while drafting), have to also check Zalau. That's the only missing point from Post 42.

Offline panda80

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 264
  • Last Login:February 29, 2024, 07:57:27 am
Re: roudj: Romania Drumuri Județene
« Reply #53 on: December 28, 2019, 07:13:56 am »
DJ202F:
I cannot see any route on WorldImagery between +X2 and +X3. Show me or split the route.

There is one, but different from initial draft. Modified.

Quote
DJ203J:
DJ203K should be moved to the next junction just a few meters to the west

No, as DJ203J becomes DJ203K at the border between Buzau and Braila counties.



Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: roudj: Romania Drumuri Județene
« Reply #54 on: December 28, 2019, 02:38:04 pm »
DJ204B:
DN23A is off


DJ204D:
Merge DJ205P_S and DJ205P_N into one wp


DJ204E:
DJ205I doesn't intersect in HB, there is no DJ205I in HB but on OSM and GM


DJ205B:
Move DN2M_E to the center of the roundabout
DJ205E is off


DJ205E:
DN2L is off
DN2D_E is off


DJ205H:
DN2L is off


DJ205J:
DioRed is off
DC41 is off


DJ205M:
PoduNAr -> PoduNar


DJ205N:
Exceeds limits b/n DC126 and +X1


DJ205P:
Exceeds limits b/n DC143 and DJ204D_E
StrIzv -> StrIzv_S


DJ205S:
DN2D/2M -> split off / new wp ?
DC142 -> DC142_N

Offline panda80

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 264
  • Last Login:February 29, 2024, 07:57:27 am
Re: roudj: Romania Drumuri Județene
« Reply #55 on: December 30, 2019, 07:19:17 am »

DJ205S:
DN2D/2M -> split off / new wp ?

See your comment in Post 9. It was originally separated, but you suggested to make one WP out of the 2.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: roudj: Romania Drumuri Județene
« Reply #56 on: December 30, 2019, 12:24:11 pm »
See your comment in Post 9. It was originally separated, but you suggested to make one WP out of the 2.

I guess that's why I had the "?" at the end :P

have to also check Zalau. That's the only missing point from Post 42.

Ok, I'll hold off.

Offline panda80

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 264
  • Last Login:February 29, 2024, 07:57:27 am
Re: roudj: Romania Drumuri Județene
« Reply #57 on: December 31, 2019, 08:40:57 am »

have to also check Zalau. That's the only missing point from Post 42.

Ok, I'll hold off.

Zalau is done.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: roudj: Romania Drumuri Județene
« Reply #58 on: December 31, 2019, 02:15:06 pm »
DJ207A:
StrCuc is off
DJ282E doesn't intersect here
DJ282D -> DJ282E

DJ207C:
DJ207D_N is off


DJ207E:
+X2 is off
Routing at south end: OSM indicates it being DN27, GM doesn't route DJ207E to the south but to the east, 2018 GSV indicates DJ207E, DN15D (must be a "To") and DN24. Funny. No action required :)


DJ207F:
DN2_S is off
DC6_N is off


DJ207G:
Move DN2_N to http://www.openstreetmap.org/?lat=46.574951&lon=26.930993 ?


DJ208:
DJ208G_W is off
DN28A_W is off
DJ281 is off
DJ208I is off
DJ208A is off
DJ208A -> DJ208A/208S
DJ208E is off
DC6 is off
DJ208C is off


DJ208A:
DJ208 -> DJ208/208S


DJ208B:
DN29A is off
DJ208D_W is off


DJ208C:
Exceeds limits b/n DJ207N and +X2


DJ208D:
DJ208U is off
DC57C is off
DN29A is off


DJ208E:
+X1 is off
DJ208F is off
DN2 is off


DJ208F:
Mov is off
DC134 is off


DJ208H:
DN28B_S is off


DJ208I:
+X2 is off


DJ208N:
East end: GM and both route it to Todiresti. Since both show the same, are you sure how you've drafted it?


DJ208S:
Move DC134 to the traffic island


DJ208T:
DC63 is off
DN29C is off


DJ209A:
DN2E is off
Hor is off


DJ209B:
Sab is off


DJ200C:
DN2E is off


DJ209D:
DC35 is off
DN17... off


DJ209J:
DN2E is off


DJ209K:
DN2H is off
DN2E/17A is off


DJ209M:
DC15 is off

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4555
  • Last Login:Yesterday at 04:04:16 pm
Re: roudj: Romania Drumuri Județene
« Reply #59 on: January 01, 2020, 10:42:34 am »
DJ211 + DJ211B:
Have a different routing through Tataru according to OSM and GM


DJ211:
DN2B is off


DJ211A:
DN21_S is off


DJ211D:
The route in HB (Calarasi) is confirmed by OSM but not GM nor GSV. There is another route in Braila b/n DJ211 (Rosiori) and DJ211C (Florica) according to OSM, GM and 2012 GSV.
The 2015 route list from the Ministry of Transport has only the one we have in HB. Fine.
DJ310 doesn't intersect in HB because the wp is missing on DJ310


DJ218:
OSM has the end more to the north. The HB route is 1.8km shorter than the 17.0km indicated on the official list and the route is not that winding as other routes


DJ219:
StrBer -> StrBer_W