Japan: National Highways 一般国道 system

[yakra]

They actually use the katakana version of the word "Bypass".

LOL figures. Works for me!
バイパス!
(...or would that be バイパツス?)
グーグル翻訳  seems to like the ichiban one.

[nezinscot]

バイパス (baipasu) is the word used.

I updated N329BypHae to use E58. 

FYI - On March 6th the entire Yonabaru bypass will open and N329BypHae and N329BypYon will then connect.

[nezinscot]

I'm thinking of splitting the national highways into three systems because of the size of a single system containing everything.

jpnh     - current roads, spurs, and connections
jpnhby - bypasses
jpnhor  - old roads

If compared to the US systems, jpnhby are the Alt routes and jpnhor are the Bus routes.  jpnh and jpnhby would each have ~550 entries.  jpnhor might reach 75 entries.

Do you think this division would be preferable to having a single system of 1200 entries?

And I would like to eventually add the very extensive railway system.  Most of my and other visitors' travelling in Japan uses the railroads.

[michih]

I'm thinking of splitting the national highways into three systems because of the size of a single system containing everything.

jpnh     - current roads, spurs, and connections
jpnhby - bypasses
jpnhor  - old roads

If compared to the US systems, jpnhby are the Alt routes and jpnhor are the Bus routes.  jpnh and jpnhby would each have ~550 entries.  jpnhor might reach 75 entries.

Do you think this division would be preferable to having a single system of 1200 entries?

Do your "systems" have different signs? How can one distinguish them?
The number of routes is not a relevant argument.

And I would like to eventually add the very extensive railway system.  Most of my and other visitors' travelling in Japan uses the railroads.

You can draft it but we need a new (or enhanced) database and front end before getting them live. I highly doubt that anyone would code it anytime soon. There are already prepared US railway systems.

[michih]

btw: Are you interested in implementing a system shield (svg file)?

[yakra]

A single system of 1200 routes would be better -- usaus & usausb are, tmk, the only instance of bannered routes split off into their own system. Everything else has bannered & mainline together in the same system. They were the first two systems developed for the old Clinched Highway Mapping project after Interstates (both regular & business), before how these things are done got nailed down. If US Highways were to be drafted today, they're surely be as a single system, including bannered routes.

[nezinscot]

Thanks for all the feedback.  One system - jpnh - will contain everything.

I plan on creating system shields for jpne and jpnh.  There is no one shield that works for jpntk. Each regional system may need its own shield.  Is it easy to associate a shield with some but not all routes in a system?

I'll revisit the railroad system later.  (By the way, I used to develop Javascript-based web GUIs that allowed users to design their own UIs using DnD.  I know SQL but only enough to sort of follow yakra's musings.)

[michih]

Is it easy to associate a shield with some but not all routes in a system?

It's doable but not easy - not as simple as we deal for other systems.

btw, if we have different jpntk shields per region, why don't we have one system per region?

I'll revisit the railroad system later.  (By the way, I used to develop Javascript-based web GUIs that allowed users to design their own UIs using DnD.  I know SQL but only enough to sort of follow yakra's musings.)

You might want to check the dedicated thread for railway systems

[Jim]

Here's a GitHub Issue that's probably relevant to the shields discussion.

[yakra]

jpnhky_con.csv:

Code: [Select]

jpnhky;N497;;Nishi Kyūshū Expwy Sasebo section (E35);jpn.n497
jpnhky;N497;;Nishi Kyūshū Expwy Sasebo section (E35);jpn.n497fuk
These two routes have the same GroupName data, and should be named differently.
Also, recommend removing the "(35)". Looks like that just refers to a concurrent route, something that's not done elsewhere.

[nezinscot]

Cut-n-paste error.  n497fuk should be Fukuoka section.

The fix will be submitted later today. 
I will also remove "(Exx)" from group names.  (Kyushu only, I'll do the others the next time I access them.)

[michih]

I will also remove "(Exx)" from group names.  (Kyushu only, I'll do the others the next time I access them.)

Neither "section" nor "Expwy" etc. should be used.

https://travelmapping.net/devel/manual/syshwylist.php#conncname

Use geographical names, e.g. city names, island names or country names.

[yakra]

Working on some changes to the waypoint simplification routines for the graph generation process, some diffs in waypointsimplification.log (20 MB file -- you probably don't actually want to click the link! ) led me here.
The banners and/or abbrevs in some waypoint files mismatch the .list names of the files they connect to:

in file(s)	point label sans suffix	corresponds to
N49, N459	N49OldMik	N49Mik
N49, N459	N49OldTsu	N49Tsu
N121	N121OldIka	N121Ika
N121	N121OldOku	N121Oku
N121	N121SprKin	N121Kin
N16	N17BypSom/N17BypAge	N17BypAge, N17BypOmi
N126	N126OldIna	N126Ina
N55, N195, N438, N439	N192BypTok	N192BypToE
N192, N318	N192BypTok	N192BypToW
N492	N439BypSug	N439, N439Yas
N32	N32SprKoc	N32Koc
N56	N56OldMas	N56Mas

This is probably not an exhaustive list. Only locations with 3+ waypoints were captured.
The route+banner of a waypoint label should generally match the route+banner of an intersecting route.
Beyond that, abbrevs are generally only needed to disambiguate; say, if a given file refers to more than one flavor of N121 or of N192Byp,etc.
I haven't been following closely enough to know whether "Old" should be added as a banner to the system CSVs, or removed from the waypoint labels. Same for that one "Spr" on the list.

Long labels like N299BypHan/N463BypTok:
Not wrong per se but the manual suggests avoiding them:

If one of the two highways is already long as a label (e.g., a bannered route like US42BusKin), consider skipping the city abbrev. or even skipping the whole second route.

So for N17BypSom/N17BypAge, if that were to otherwise become N17Byp/N17Byp, that might be a good candidate for "skipping the whole second route".
N299BypHan/N463BypTok OTOH could be shortened to N299Byp/N463Byp -- or another option that the manual is quiet on but that people have been doing for years is to just list the banner once, implying that it applies to both route numbers: N299/N463Byp.

[nezinscot]

With the promotion of jpnhks (Kansai) to preview last night, all Japanese national highways are now at preview level.

   459 highways
   1200 entries
   30000 miles

Next few tasks include:
1) Remove all the Old and Spr abbreviations from waypoint and file names. 
2) Make a second pass through the roads, in numeric sequence, to make sure I was consistent in waypoint selection and naming.
3) Now that I can see all the routes on one map, I can better determine if I need to remove or add shaping points.  (The road network is rather dense on Honshu so I tended to use more shaping points there.)

I have had the highways colored red so that color-blind me could easily see them during development.  What color should I change this to?  Salmon?

[michih]

You should use the same color what's used for other national highway systems in Asia.

You could also go ahead now and:

Once all individual systems are complete, you can merge the systems into one again.