Travel Mapping
Highway Data Discussion => In-progress Highway Systems & Work => Topic started by: nezinscot on April 06, 2021, 12:34:55 pm
-
All of my driving in Japan has been on the national highway system and on prefectural roads, not the expressways. I wanted to add this mileage but did not find a highway system for the "common" national highways.
Is anyone working on a highway system for the 55000+ km of national highways? If no one is and you all feel the system is needed, I would be willing to help with the task.
I speak, read, and write intermediate level Japanese and would be willing to use this painfully acquired skill to dig through the ministry websites and GIS systems for original sources. I am also familiar with the problems related to Japanese street naming and addresses. The file creation and manipulation part of the task shouldn't be a problem because I spent years working in science and engineering-related IT.
The work would also help me improve my Japanese. I was definitely never taught highway-related vocabulary in class...
-
Great news :) si404 developed the existing systems. I think he will answer what he thinks about it.
General note:
The requirements for developing new systems are described here: https://travelmapping.net/participate.php?u=michih&#hwydatamanager
When you reach stage 5 (I guess you are currently at stage 3?), jpntk and jpne could be your candidates for the peer-review:
https://forum.travelmapping.net/index.php?topic=3004
https://forum.travelmapping.net/index.php?topic=3668
I started the jpne system peer-review last May but gave up quite soon and will not work on it again any time soon.
-
I'm at level 4. I read the developer manual before I volunteered so that I could have an idea of what the work might entail. I no doubt need to give it another close reading.
Japanese numbered highways have some interesting quirks --- most intersecting roads are nameless, roads can span multiple islands, mountain roads can use widely divergent paths for each direction, roads may have two options (one a new tunnel the other the old twisty mountain road), ridge roads often wind back and forth across prefectural borders, etc. At least the GSV coverage is good.
There are 47 prefectures, so a complete Japanese system would be a mini-US. And if we include the extensive train and metro systems, the task gets even bigger.
-
I have almost completed my review of the Japanese expressway systems and would like to work on the Japanese national highway system next.
There are 400+ national highways in Japan, plus hundreds of related bypasses and older routes that are still considered part of the national highways. In all there could be ~1000 separate entries in this new system. I believe we are trying to create smaller systems, so if I started this work, I would like to create separate systems for each prefecture (province). There are 47 prefectures.
Separate systems for each prefecture will also help deal with the abundant duplicate prefectural road names found on the longer national highways. For example N4, the longest national highway, intersects P8 and P25 in four separate prefectures.
There is information online about the newer parts of the national highway system, especially the bypasses around towns. GSV coverage is very good in urban areas and adequate in rural areas. Highways are usually well marked with route and mileage markers. Plus there are enthusiast websites in Japanese that cover the routes in detail, for example http://hgf03030.a.la9.jp/index.htm.
I would like to know if you all consider this a project worth doing.
-
I believe we are trying to create smaller systems, so if I started this work, I would like to create separate systems for each prefecture (province). There are 47 prefectures.
Separate systems for each prefecture will also help deal with the abundant duplicate prefectural road names found on the longer national highways.
I think that we can go with smaller systems through the development process as we did for gbna or deub but the systems should be merged on activation. However, we should not do it by prefectures since the routes (wpt files) would need to be changed. This would affect users.
For example N4, the longest national highway, intersects P8 and P25 in four separate prefectures.
There is a simple solution: https://travelmapping.net/devel/manual/wayptlabels.php#over2
I would like to know if you all consider this a project worth doing.
I think so! We have 7 users with travels in Japan so far. We have regions or systems with less travelers.
-
I'll follow your advice about using devel-only systems to split up the work.
I think jpnh should be the system name for the national highways.
Devel-only systems can be used for each island, or island section for Honshu. They can be swept into jpnh as they are completed.
jpnhky - Kyushu and Okinawa
jpnhsh - Shikoku
jpnhhk - Hokkaido
jpnhkt - Kanto (east Honshu / Tokyo)
jpnhks - Kansai (west Honshu / Osaka)
I was thinking that jpnh would be type 3, but I see that US national highways are type 2. Would type 3 be the better choice? Japan already has systems for type 1 and 2.
-
I was thinking that jpnh would be type 3, but I see that US national highways are type 2. Would type 3 be the better choice? Japan already has systems for type 1 and 2.
It should be tier 4 like the other national highway systems in Asia (and Europe) but the Indian one is tier 3 (https://travelmapping.net/hb/index.php?sys=indnh) - likely a mistake.
-
Just a note on N295:
https://travelmapping.net/hb/showroute.php?r=jpn.n295
https://travelmapping.net/hb/showroute.php?r=jpn.e065
- E51/E65 must be a one-point-per-interchange with E65's N295 wp
- E51/E65 might even be a one-point-per-interchange with E65's exit 10 + N295 wp
- E51/E65 does not (directly) connect to E51. Wp should be called E65_something
- NarApt must be a one-pont-per-interchange with E65! I tend to adding a wp to E65 at NarApt location.
-
N481
While deep into some shell scripting, I found E71(4)/P29 which led me here.
This would want to have either the E71(4) or the P29, but both isn't really something we do.
Avoid using two designations and a parenthetical suffix in the same label.
For the coordinates, I'd recommend moving the point in E71's file to match (https://forum.travelmapping.net/index.php?topic=3004.msg25501#msg25501).
Back to the label, what to do here... I guess I'd recommend E71(4), as this is where the multiplex would end anyway if Exit 3 weren't right up in the mix being all confusing. It fits in with with E71(5) and E71(3).
Reposition E71(3) to sync up with the point on E71 (https://travelmapping.net/hb/showroute.php?r=jpn.e071&lat=34.412327&lon=135.296888&zoom=17) and get concurrency detection working.
E71(5) is fine.
E71(2):
Wow. This is like some of the crazier parts of urban Texas. I don't envy you having to sort this out right when joining the project.
When plotting out points on these complex frontage road systems, I find it helps to ask where the points would fall if the frontage roads weren't in the picture, if the connections were made via traditional diamond ramps or equivalents.
On freeways/expressways, this usually results in point placement at a major central crossroad (often at another route in the HB if there is one) for diamond equivalents.
Half-diamond equivalents will usually be the first crossroad. The first one with a bridge, unless such is really far away. If there are multiple grade-separated crossroads close together where the ramps touch down, and a major route (also in the HB) isn't the very first one, I might still pick that sometimes, and get a graph connection.
Thus IMO JPN E71 2 (https://travelmapping.net/hb/showroute.php?units=miles&u=si404&r=jpn.e071) is placed appropriately, centered at N26.
So E71(2) and N26, we'd want to collapse into One Point Per Interchange. Putting it at the same coords as on E71 will give a graph connection with E71 now; I presume N26 will be drafted in the future. Right now N481's file has more precicse coordinates, so I'd recommend replacing the coords in E71's file with those.
As for whether to name this point E71(2) or N26, I'm agnostic; won't push for one over the other. This reminds me of TX US183 at TX21 (https://travelmapping.net/hb/showroute.php?r=tx.us183&lat=30.027758&lon=-97.687909&zoom=15), though I won't necessarily say what I did there is The Right Thing To Do.
-
Thank you both for the reviews.
I have mostly followed your advice and have modified both the national highways and the national expressways. Here are the changes I plan to submit. I'm not convinced what I did with E51(10) on N295 is right, but I wanted to include the connection to E51.
https://github.com/TravelMapping/HighwayData/compare/master...denishanson:master
Should I be the one to make the changes to the E65 and E71?
-
Is there an accepted process for promoting a system in multiple steps from devel to preview?
I have created jpnh plus five devel-only system for the Japanese national highways, splitting the country by islands. Should I push jpnh now to preview and sweep the other systems in individually once they are completed in devel?
-
Is there an accepted process for promoting a system in multiple steps from devel to preview?
Just check out systemupdates.csv (https://github.com/TravelMapping/HighwayData/blob/master/systemupdates.csv), e.g. here (https://github.com/TravelMapping/HighwayData/blob/master/systemupdates.csv#L289), here (https://github.com/TravelMapping/HighwayData/blob/master/systemupdates.csv#L447), here (https://github.com/TravelMapping/HighwayData/blob/master/systemupdates.csv#L543), here (https://github.com/TravelMapping/HighwayData/blob/master/systemupdates.csv#L563) or here (https://github.com/TravelMapping/HighwayData/blob/master/systemupdates.csv#L674).
-
I'm not convinced what I did with E51(10) on N295 is right, but I wanted to include the connection to E51.
https://github.com/TravelMapping/HighwayData/compare/master...denishanson:master
Oh man. Another screwy interchange. Looking at N295 alone, it seems to have a clear center. But getting a sensible graph connection at E65 seems to beg for a point right where you have it now.
E51(10) matches this sign (https://www.google.com/maps/@35.7835235,140.3542255,3a,15y,94.07h,99.99t/data=!3m9!1e1!3m7!1soCrh9uxv5fuXP4iY9ZKlKA!2e0!7i16384!8i8192!9m2!1b1!2i40), though there's no other E51 waypoint, so the exit number suffix should be dropped. ..."E51" offends my sensibilities, as it directly connects to E65. ;) Disambiguating multiple "E65" points? That could get messy too.
The more I look at this the more 1PPI (labeled E65) seems the way to go.
Then it becomes a matter of balancing the competing goals of a central point location vs. having a sensible graph connection point.
There's the "central ramp triangle" (http://www.openstreetmap.org/?lat=35.782559&lon=140.354963&zoom=19) approach the manual suggests (https://travelmapping.net/devel/manual/points.php#three_way) (which I'm not always a fan of); may be possible to weasel one's way out of it (like maybe even here (http://www.openstreetmap.org/?lat=35.782276&lon=140.355371&zoom=19)?) on "this ain't exactly a 3-way high-speed interchange" grounds?
Should I be the one to make the changes to the E65 and E71?
Check with si404; dunno whether he'd prefer to make the changes himself or be OK with you doing it.
-
Should I be the one to make the changes to the E65 and E71?
Check with si404; dunno whether he'd prefer to make the changes himself or be OK with you doing it.
I'm fine with this.
There's not much left of the jpntk review to do, once that's done, I'll activate my systems in Japan and hand over maintenance.
-
All routes for the islands of Kyushu and Shikoku have been added. Honshu is next.
What I've learned so far:
-- Routes are averaging about 2.5 entries per route number, so I anticipate the entire system will have 1000+ entries.
-- Japan is mountainous so roads curve a lot. Route lengths can be 20% less than the official route length.
-- To keep the waypoint count reasonable, I tend to only include expressways, national highways, and most but not all principal prefectural roads (主要地方道, usually they have numbers less than 100).
-- Routes are averaging a waypoint every 2 miles or so.
-- Determining whether a section of road is the main route, a bypass, or an old road (original route) can be difficult. Maps cannot be trusted. GSV can only be trusted if the data is very recent.
For Honshu, I've decided to do the worst first, so I have starting working on N1 - the Tokaido. It now bears no relationship to the Tokaido of woodblock prints. Its a 500km version of US1 through northern New Jersey, but with more trucks and stoplights.
I've found a lot of sections where N1 runs beneath an expressway, connecting with the overhead expressway at a series of ICs. How do I prevent concurrencies between N1 and the expressway? Add routing waypoints to N1 between the ICs? Nudge the N1 waypoints over a little, causing NMPs?
-
I've found a lot of sections where N1 runs beneath an expressway, connecting with the overhead expressway at a series of ICs. How do I prevent concurrencies between N1 and the expressway? Add routing waypoints to N1 between the ICs? Nudge the N1 waypoints over a little, causing NMPs?
Just add a visible (or hidden) wp to one of the routes to break the concurrency.
We often implemented another option in the past by moving one wp off for a route by 0.000001° to get a NMP. However, since we show intersecting routes in the HB, we should not implement this anymore.
-
I've found a lot of sections where N1 runs beneath an expressway, connecting with the overhead expressway at a series of ICs. How do I prevent concurrencies between N1 and the expressway? Add routing waypoints to N1 between the ICs? Nudge the N1 waypoints over a little, causing NMPs?
Either of those should work; I'm not sure what is the preferred method.
-
I've found a lot of sections where N1 runs beneath an expressway, connecting with the overhead expressway at a series of ICs. How do I prevent concurrencies between N1 and the expressway? Add routing waypoints to N1 between the ICs? Nudge the N1 waypoints over a little, causing NMPs?
Either of those should work; I'm not sure what is the preferred method.
Definitely adding shaping points between interchanges at this point for more graph connections. I think a past example of nudging waypoints over a little can still be seen on I-65/US 31 in Indiana just north of Louisville.
-
Thanks for the info. I have been using hidden waypoints, so I will continue to do so. I was concerned because in a few cases I have had to add hidden waypoints between every IC.
I have another complication with expressways over surface roads. Expressway E89 between Osaka and Kyoto is also a bypass of N1. E89 is a toll road and the surface road beneath it, also labeled N1 is free. The surface road has many additional waypoints. Should I make two separate N1 entries for the bypass.
And it gets more complicated. E88 is also an N1 bypass. The surface road beneath it, also marked N1, is only present at the ends of E88 (there is a long tunnel between). Plus the west end surface road marked N1 begins west of the west end of E88, and the east end N1 surface road continues past the east end of E88. Are there three N1 bypass entries here?
-
I've found a lot of sections where N1 runs beneath an expressway, connecting with the overhead expressway at a series of ICs. How do I prevent concurrencies between N1 and the expressway? Add routing waypoints to N1 between the ICs?
I'd recommend this.
-
yakra, how did you decide on what to do in regards to Toll 183 vs US 183? Are both truly part of US 183?
-
Not sure if you meant to post that in another thread.
Toll 183 is not included. None of the TX toll routes paralleling a same-numbered route in a mainline/frontage setup are.
-
Not sure if you meant to post that in another thread.
Toll 183 is not included. None of the TX toll routes paralleling a same-numbered route in a mainline/frontage setup are.
I was just wondering how related that could be to nezinscot's situation. It probably is not, but it sounds similar.
-
There are other cases. First that comes to mind is US183 & TX130.
I broke up the not-concurrencies with shaping points via a custom tool (https://github.com/yakra/tmtools/tree/master/autoshape).
That might be a bit rich for most people's blood; another option for keeping the divergences to a minimum is to double-click on the existing polyline in wptedit to center before adding a new point.
-
I'll follow your advice about using devel-only systems to split up the work.
I think jpnh should be the system name for the national highways.
Devel-only systems can be used for each island, or island section for Honshu. They can be swept into jpnh as they are completed.
jpnhky - Kyushu and Okinawa
jpnhsh - Shikoku
jpnhhk - Hokkaido
jpnhkt - Kanto (east Honshu / Tokyo)
jpnhks - Kansai (west Honshu / Osaka)
Why don't you bring your systems to preview status? I mean, the basic idea of splitting systems during development phase is that we can promote it earlier to preview and make it visible (stats, mapview) for users. If you think that "jpnhky" is complete (https://github.com/TravelMapping/HighwayData/pull/5423), it should go to preview (https://travelmapping.net/devel/manual/sysnew.php#preview)!
-
I was waiting for a second pass thru the systems but that is likely a long way in the future because doing Honshu is a big task. So, I will take your advice and promote the pieces that are done. Should I only promote jpnh to preview and fill it with what is done, or should I promote all the completed systems?
-
I was waiting for a second pass thru the systems but that is likely a long way in the future because doing Honshu is a big task. So, I will take your advice and promote the pieces that are done. Should I only promote jpnh to preview and fill it with what is done, or should I promote all the completed systems?
I don't understand why you already have a jpnh system in devel. I thought that you've split the future system into individual systems per island. The individual systems can be promoted to preview status when they are complete. Incomplete systems should stay in devel (except of special "select systems" we don't have in Japan). Once all individual systems are complete, you can merge the systems into one again.
-
jpnhky - national highways in Kyushu and Okinawa - is now in preview mode.
83 highways / 215 routes
4564 miles
If you were ever stationed at Sasebo or in Okinawa you probably have driven some of these roads.
-
N329BypHae
There's only one intersection with E58, so E58(A1) should become E58 or E58/N506.
WRT Byp as a banner, is this appropriate? The route may functionally be a bypass, but a banner should really only be included if it's an official part (usually signed) of the designation. If Japan does use (and sign?) such a designation, what's the JP word they use?
(Just watch it be English...)
-
I will update the E58(A1) waypoint name to E58.
As for bypasses, its complicated, like many things Japanese. Almost every expressway and many urban national highways in Japan are built from a set of connected "bypasses". A new section of road usually has its own bypass name. They actually use the katakana version of the word "Bypass". What we would consider a bypass in the US will also have bypass in its name. I spend a lot of time trying to figure out what the bypass name of a road segment is because most online info uses the bypass name and not the national highway designation.
I've done about 60% of the national highways so far, and have identified four types of road segments.
1) The current road (the main line). Originally the national highways went right through towns, but over time bypasses have been built to widen the road or avoid town centers and other obstacles, and the current road moved to the bypasses.
2) Old roads. When the original route is replaced by a bypass, usually the old route is transferred to the prefecture or city and given a local designation. (This transfer may take several years, so new bypasses are often associated with "temporary" old road sections.) But in some cases, the original route retains it national highway designation, so there are two routes with the same designation.
3) Bypasses. These are built usually to avoid town centers or other areas of heavy traffic. They are not old roads and they are not the current road. They often connect at both ends with the current road or another national highway. I believe "Byp" is the correct banner for these roads.
4) Spurs and connectors. They connect the current road, old road, or a bypass to another road, often an expressway.
There is some degree of ambiguity. Sometimes its tough to determine which is the current road and which is the bypass, or which is the current road and which is the old road. True bypasses and spurs are usually pretty obvious.
Japan does not sign its bypasses, old roads, or spurs any differently than it does current roads - they all get the blue rice ball sign with a number on it. Sometimes an overhead sign will indicate which route is the bypass, or the old road, but this is not prevalent.
There are also national highway bypass designations on many expressways, typically those that are free and were built with prefectural money. These bypasses usually do not have national highway signage because in general, Japan does not multi-sign concurrencies.
-
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. :D
-
バイパス (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.
-
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.
-
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 (https://github.com/TravelMapping/HighwayData/tree/master/rlwy_data).
-
btw: Are you interested in implementing a system shield (svg file) (https://travelmapping.net/devel/manual/sysnew.php#developshield)?
-
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.
-
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.)
-
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 :)
-
Here's a GitHub Issue that's probably relevant to the shields discussion (https://github.com/TravelMapping/Web/issues/614).
-
jpnhky_con.csv:
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.
-
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.)
-
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.
-
Working on some changes (https://github.com/TravelMapping/DataProcessing/issues/528) to the waypoint simplification routines for the graph generation process, some diffs in waypointsimplification.log (https://travelmapping.net/logs/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 (https://travelmapping.net/devel/manual/wayptlabels.php#bannerafternumber) of a waypoint label should generally match the route+banner of an intersecting route.
Beyond that, abbrevs (https://travelmapping.net/devel/manual/wayptlabels.php#abbrev) 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.
-
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?
-
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.
-
There are 564 pairs (https://travelmapping.net/logs/nmpbyregion/) of near-miss-points (https://travelmapping.net/devel/manual/syserr.php#nearmisspoint) to be checked if the wp coords need be synched (I had a quick look into it, and all I checked need to be synced) or marked FP: https://courses.teresco.org/metal/hdx/?load=jpn.nmp
I recommend synching the coords now but only mark the FPs on activation.
-
Regarding keeping intersection points aligned, I know everyone has their own methods. When I used to draft highway systems for CHM and during the early days of TM, I would always start the drafting of a new route by bringing in all of the points from existing routes that intersect (grep is your friend), line those up, then fill in the other needed points in the WPT editor. I found that it saved time while drafting and prevented nearly all non-FP NMPs.
-
Japan's datacheck errors can be seen at https://travelmapping.net/devel/datacheck.php?rg=JPN
VISIBLE_DISTANCE (https://travelmapping.net/devel/datacheck.php?rg=JPN&show=VISIBLE_DISTANCE) cases are handled a bit differently...
These are often false positives, and aren't reported once the relevant systems are promoted to active. So there's no need to mark them FP; just add intermediate points to fix the ones you can.
It may help to filter them out (https://travelmapping.net/devel/datacheck.php?rg=JPN&hide=VISIBLE_DISTANCE), address the other errors first, and then come back to these last.
N57BypKit needs a couple shaping points. Recommend:
N57 http://www.openstreetmap.org/?lat=32.921039&lon=131.000077
+X840372 http://www.openstreetmap.org/?lat=32.924118&lon=130.987541
P23 http://www.openstreetmap.org/?lat=32.915810&lon=130.981731
OtsHig http://www.openstreetmap.org/?lat=32.899815&lon=130.929381
+X767139 http://www.openstreetmap.org/?lat=32.896153&lon=130.896277
P339 http://www.openstreetmap.org/?lat=32.887664&lon=130.896727
-
It may help to filter them out (https://travelmapping.net/devel/datacheck.php?rg=JPN&hide=VISIBLE_DISTANCE), address the other errors first, and then come back to these last.
The errors highlighted in red are more important, especially Duplicate_Label (https://travelmapping.net/devel/manual/syserr.php#DUPLICATE_LABEL). Hidden_Junction (https://travelmapping.net/devel/manual/syserr.php#HIDDEN_JUNCTION) are usually in combination with NMPs. Dealing with NMPs (on HDX) is likely easier than trying to find the error with HB (opened with datacheck link).
-
Thanks for all the suggestions. I'm currently in the puckerbrush in rural Maine and have intermittent web access. I'll be home tomorrow and can start working on these issues then.
FYI all Japan national highways are now in jpnh. The system files for the temporary systems should be deleted by today's submission. I needed to use Github Desktop to do the bulk moves. Have you found it useful for other tasks?
-
I needed to use Github Desktop to do the bulk moves. Have you found it useful for other tasks?
I always use Github Desktop because I always open all (sometimes up to 1,000) relevant files to pick up wp coords to avoid NMPs.
-
Not sure if you're aware or if they might be of any use, but there are .wpt files generated by each site update that line up all NMPs. Unfortunately that would include (unmarked only? I'd have to check) FPs. They can be found on the server in /home/www/tm/nmp_merged or on the web under https://travelmapping.net/nmp_merged/
-
All the data errors and NMPs for Japan systems have been fixed or marked as FPs. I also have done a first pass at checking concurrencies.
I just uploaded an SVG file for the jpnh system. I have a few questions about how the shields directory is used.
-- How do these SVG files get chosen for use? Is it based on the file name, in this case template_jpnh.svg.
-- How can I add another font? The svg file should probably be using IPAGothic, a free Japanese sans-serif font.
-- The roads in the jpntk system have separate shields for each city network. I did see shields unique to one road, but is it possible to have a shield shared by some but not all of a system?
-- The jpne system could use a simple shared shield, or for each expressway have much more complicated separate shields that list the road name. Which would be the better choice?
Because of their shape, national highway shields are known colloquially as onigiri - meaning rice ball.
-
I just uploaded an SVG file for the jpnh system. I have a few questions about how the shields directory is used.
-- How do these SVG files get chosen for use? Is it based on the file name, in this case template_jpnh.svg.
Thanks :) If memory serves*, you need to call the svg file from https://github.com/TravelMapping/Web/blob/master/shields/shieldgen.php
@the-spui-ninja (or @rschen7754?) might help you if you need support.
*I dealt with it in 2016/17 but don't remember details. I think that the code was reworked meanwhile?!?
-
No, it is loaded automatically (https://github.com/TravelMapping/Web/blob/master/shields/shieldgen.php#L46) but most shields require a special treatment (https://github.com/TravelMapping/Web/blob/master/shields/shieldgen.php#L55).
-
I looked at shieldgen.php and it looks pretty easy to add a case for jpnh. All I need to do is strip out the N prefix.
case 'jpnh':
$routeNum = str_replace("N", "", $row['route']);
$svg = str_replace("***NUMBER***", $routeNum, $svg);
break;
I'm leery of adding it to the code for
case 'alakt':
case 'alavt':
case 'canmbw': .....
because I don't know if any of those cases have an N in prefixes.
Looking at shieldgen answered my question about the jpntk system having separate shields for each city network. It should be possible by adding a separate case for jpntk that determines the city network being processed.
-
Thanks for working on the Japan shields. Instead of pulling into the master branch of the repository, I've pulled your work so far into a branch named jpnshields. I've installed what's there on tmdevel, for example:
https://tmdevel.teresco.org/hb/showroute.php?units=miles&u=terescoj&r=jpn.n002
It looks like we're on the right track, but something's not quite right.
I might be able to take a look a little later today, but please feel free to investigate and submit another PR (to that branch, if you can) and I can put it on tmdevel to try it out.
-
The shields don't appear on https://tmdevel.teresco.org/shields/clinched.php?units=miles&u=nagamasa&cort=traveled (I've selected a traveler with jpnh travels)
chlinched.php might help to see more shields at the same time to validate if changes work.
I never had to do anything to make the shields visible there.
-
@nezinscot if you'd like to be able to experiment and are comfortable with working your way around the Unix command line and transferring files, I can set up a development server where you can try things out. Send me a direct message here or email me if you'd like to go in that direction.
-
Maybe starting in mid-July I can work with the development server.
Monday I'm heading to central Texas for two weeks. (My sister owes me bigtime for trading coastal Maine summer weather for Texas 100+ heat.)
-
The shields for jpnh is now displaying correctly working on the development server. The svg needed a viewport to be set.
The shield for jpne is also now available on the development server. Both shields are displaying on the clinched/traveled roads page
-
I'll merge those into the mainline and install on the production server if it's all looking good to go.
-
It looks good enough for now. I vote to promote it.
I eventually should tweak the font size, position, and possibly the kerning of the number text. That would be much easier on a development server because it'll require many iterations to get right.
-
The shields are now on the main site. Thanks!
-
Thank you! Work on the front end is always welcome :)
I've closed the Github issue for the jpne shield (https://github.com/TravelMapping/Web/issues/682).
-
hwy_data/JPN/jpntk/jpn.hie5.wpt is unprocessed (https://travelmapping.net/logs/unprocessedwpts.log). Please check if the route should be added to csv files or if the wpt file should be deleted.
-
hwy_data/JPN/jpntk/jpn.hie5.wpt is unprocessed (https://travelmapping.net/logs/unprocessedwpts.log). Add the route to csv files or delete the wpt file.
Why? What harm does its unprocessed existence do?
The route is under construction, and the file consists of the jpntk.csv entry, and an intersecting point, to make things easier for me when it opens. It's now not me who'll be dealing with it when it opens, and I'm not saying keep it, but nezinscot shouldn't have to delete it just because it appears in a log.
-
Thanks and sorrY! Text changed and
striked through since irrelevant now.
I thought that it might be unprocessed by accident.........
-
I have begun a second pass through the Japanese national highways, starting with the N300-N325 group.
As a result of the second pass, and doing recent updates because of new road openings, I've decided that I should change the way I designate the main road. Before, when there was a choice I followed the oldest existing route, typically the route through a congested urban area. The other option I designated as a bypass. I now believe I should put the main road on the through route, which is almost always the bypass.
Additionally I am removing the Byp designation from routes. There is no official designation marking a route as a Bypass, and routes are not signed as Bypass. I formerly based Byp on the route location and function. (An added complication is that almost all new road segments have their own unique name that contains Bypass, so everything new is a bypass in some way. Ambiguity is the norm in Japan and in Japanese.)
I now plan to use this route naming scheme:
1) The main road is the through road when there is a choice. The route name is Nxxx.
2) All other routes with the same number have an appended location abbreviation - e.g. N300Yam, N300Mat
3) No routes will use Byp in jpnh.cvs.
Some expressways are also designated as "motorway on general national highway". I will treat the concurrent national highway designation the same as any other route and not mark them as Byp.
-
I now plan to use this route naming scheme:
1) The main road is the through road when there is a choice. The route name is Nxxx.
2) All other routes with the same number have an appended location abbreviation - e.g. N300Yam, N300Mat
3) No routes will use Byp in jpnh.cvs.
Seconded!
-
- E9 (Nagato) wps do not match the N route wp coords
- N305/N365 concurrency is broken
I guess that the remaining NMPs might be intended: https://courses.teresco.org/metal/hdx/?load=jpn.nmp
-
Request: for all of N317, could we add some waypoints for where the cycling route joins and leaves the driving route? Well we are primarily expecting users to drive to cinch, I don't see why we can't add a few more points for this popular cycling destination.
Also the cycle route is also the moped (less than 125cc) route, so it is fair to actually drive on it.
-
I am 25% of the way through self-reviewing all of Japan. I have finished Kyushu and Shikoku and would greatly appreciate it if someone is able to review one or both of these islands. Errors in naming, waypoint location, waypoint density, etc. discovered there will likely be present for the rest of Japan.
I'd learn more from a review of Kyushu - it has urban areas similar to those on Honshu. A review of Shikoku would be a critique of my shaping points on winding mountain and coastal roads. Even a partial, quick review would be helpful.
Ok, I'll have a look into jpnh in the coming days or weeks. I'll go by road number. Not by islands. I'll "technically" check routes and wps but won't check GSV for every wp or route end.
btw, have you checked my April 2023 + nagamasa's 2024 comment above?
-
I did notice the last round of updates many routes were redrawn around Kyushu, and no longer had points for intersecting prefectural routes. I happened to have travelled onto those prefectural routes and noticed my cliches breaking. I think those points should be in?
-
I did notice the last round of updates many routes were redrawn around Kyushu, and no longer had points for intersecting prefectural routes. I happened to have travelled onto those prefectural routes and noticed my cliches breaking. I think those points should be in?
If they were points in use, nezinscot should kept them - and should add them again now if the routing has not changed.
@nezinscot, are you aware of this rule set: https://travelmapping.net/devel/manual/maintenance.php#break it's mandatory for active systems but whenever possible, we should obey it for preview systems too. ie keep points in use as alt labels. Just update entries are omitted for preview systems.
-
Request: for all of N317, could we add some waypoints for where the cycling route joins and leaves the driving route? Well we are primarily expecting users to drive to cinch, I don't see why we can't add a few more points for this popular cycling destination.
Also the cycle route is also the moped (less than 125cc) route, so it is fair to actually drive on it.
I'm assuming you are referring to the Shimanami cycling route. https://shimanami-cycle.or.jp/ (https://shimanami-cycle.or.jp/) Are you asking for waypoints to be added where the bike path joins and leaves the various bridges on E76/N317Set?
-
I usually check to see if a road has user entries, and if I need to change a waypoint name, I move the old name to an Alt Label. I must have failed to do this for some my recent Kyushu changes. I'll be more vigilant about this.
Also, during my recent reviews of Kyushu and Shikoku, I eliminated some waypoints to secondary prefectural roads that were only included because they prevented VISIBLE_DISTANCE warnings.
In urban areas, primary prefectural roads can be close together. I will skip some of them, choosing the ones that seem more important. Criteria include the presence of a stoplight, multiple lanes, leads somewhere locally important, length of the road, etc. The recent changes dropped some of these primary prefectural roads.
When choosing what to waypoint, my general rules are:
1) national expressways and urban expressway systems
2) national highways
3) primary prefectural roads - in most prefectures these are numbered < 100 (OSM green roads)
4) secondary prefectural roads that directly lead to expressway exits (OSM yellow roads)
5) secondary prefectural toads or local roads that lead directly to major tourist sites - these are rare
Even with restricting the inclusion of secondary roads, waypoint density is frequently less than 2 miles between points. In urban areas it is commonly less than a mile.
If a user wants a secondary or local road included in the waypoints, I'll likely add it. I just need to be told the road name or location.
-
When choosing what to waypoint, my general rules are:
Check this: https://travelmapping.net/devel/manual/includepts.php#intersections
I also recommend adding wps for intersecting roads heading to grade-separated roads.
-
Goodness, I didn't check the number of routes before I wrote that I'll review the system. And the first one is a very long one... :pan:
Please ask if you don't get why I suggest changes. Suggestions with ? are optional.
N1:
N4 -> N4/N6 since both are in Highway Browser
N15/P10 -> N15_Tok ?
N15 -> N15_Yok
P301/P319 -> P301 would be enough since P routes are not (yet?) in HB, I won't mention that for similar situations. It's up to you to change it.
P2_N -> P2_Shi ?
P2_S -> P2_Yok ?
N16Yok -> N16_E since the concurrent main route splits off
N16/P81 -> N16_W
N1Shi_E -> C4 since it's a route of higher tier
N1Shi_W -> E84
N129 -> N129/N412
E84/N1SSH_Iry -> E84_Kaz (preferred) or E84/N1SSH
N138 -> N138_W since it's concurrent from N255
N1SSH_W -> N1SSH_Hak ? (well, you don't have to change it, it's just a recommendation to better distinguish that the route is not concurrent, I won#t mention it for similar situations)
N136/P21 -> N136
N246/N414 misses the graph connection to N414 because N414's end point is off
N139/P76 -> N139
N1Fuj/P81 -> N1Fuj
N152/P65 -> N152
E1A/N23 -> E1A
N302_E -> C2(1)
N19/N247 -> N19/N22
N302_W -> C2(25)
N302_W needs to be synced to http://www.openstreetmap.org/?lat=35.126350&lon=136.818151
N365 -> N365/N477
N164 -> N164/N477
N164_End -> Suw since N164 does not intersect here, it's just the end of N164
E25 -> ToE25
Add a wp to E25 for that connector
E23/E25 -> E25 since there is no graph connection to E23
N478/N1Kei -> N1Kei/N478
N168/P20 -> N168
HE12/P2 -> E26 since it's highest tier
Add wp b/n N1Shi_W and N129 for a road heading to E84 at http://www.openstreetmap.org/?lat=35.332869&lon=139.377338
Add wp b/n P22_E and N136/P21 for a road heading to E70 at http://www.openstreetmap.org/?lat=35.114687&lon=138.927795
Add wp for GSJ west of N139FIS at http://www.openstreetmap.org/?lat=35.133391&lon=138.648394 (closer to the rules) OR http://www.openstreetmap.org/?lat=35.132167&lon=138.644575 (would also be fine)
Replace +X399258 by two visible wps for the nearby GSJ (or maybe just one wp?)
Add one or two wps b/n P54/P67 and P74
Add wp west of P84_Shi for a GSJ at http://www.openstreetmap.org/?lat=34.954254&lon=138.367800
Replace +X471047 by a visible wp
Add wp west of N1Sei_W for GSJ at http://www.openstreetmap.org/?lat=34.937017&lon=138.308194
Add wp for GSJ b/n N1Fuj/P81 and P32 at http://www.openstreetmap.org/?lat=34.889557&lon=138.256288
Add wps for GSJs west of P64 at http://www.openstreetmap.org/?lat=34.854207&lon=138.202847 and http://www.openstreetmap.org/?lat=34.848101&lon=138.182613 and http://www.openstreetmap.org/?lat=34.845772&lon=138.166959
Remove +X872523
Move P64 wp to the underpass at http://www.openstreetmap.org/?lat=34.843963&lon=138.150351
Add wp east of N1Nis_E for a GSJ at http://www.openstreetmap.org/?lat=34.820929&lon=138.106481
Add wps east of P39 for GSJs at http://www.openstreetmap.org/?lat=34.790149&lon=138.071258 and http://www.openstreetmap.org/?lat=34.786404&lon=138.050342 and http://www.openstreetmap.org/?lat=34.784475&lon=138.028139
Remove +X757522 and +X502773
Add wps east of P61_Fuk for a GSJs at http://www.openstreetmap.org/?lat=34.770481&lon=137.977987 and http://www.openstreetmap.org/?lat=34.757604&lon=137.936128 and http://www.openstreetmap.org/?lat=34.757260&lon=137.922235
Add wp west of P61_Fuk for a GSJ at http://www.openstreetmap.org/?lat=34.747003&lon=137.894243
Replace +X516279 by a visible wp for the nearby GSJ
Add wp b/n P44_Iwa and N152/P65 for a GSJ at http://www.openstreetmap.org/?lat=34.728387&lon=137.814297
Add wp north of N421 for a road heading to a GSJ of N258 at http://www.openstreetmap.org/?lat=35.076853&lon=136.684942
Remove +X864172 since it's no longer needed
Add wp for GSJ b/n N306 and E25 at http://www.openstreetmap.org/?lat=34.864217&lon=136.439799
Also add for concurrent N25
Replace +X845776 by a visible wp for the nearby GSJ
Add wp east of N307_N for a GSJ at http://www.openstreetmap.org/?lat=34.966353&lon=136.196217
Add wp b/n P13_E and P13_W for a GSJ at http://www.openstreetmap.org/?lat=34.989846&lon=136.116394
Add wp east of P32_Kyo for a GSJ at http://www.openstreetmap.org/?lat=34.994118&lon=135.775896
Also add for concurrent N8
Add wps b/n P17_Hir and P22_Yaw for intersecting roads heading to E1A/E93 at http://www.openstreetmap.org/?lat=34.857997&lon=135.712261 and http://www.openstreetmap.org/?lat=34.868244&lon=135.727496
Add wp b/n N170_N and N168/P20 for a GSJ at http://www.openstreetmap.org/?lat=34.806717&lon=135.652826
Add wp b/n P30_Osa and P8_Osa at http://www.openstreetmap.org/?lat=34.699288&lon=135.536394 (looks important)
Also add for concurrent N163
N258:
Add wp b/n E23 and N421_W for GSJ at http://www.openstreetmap.org/?lat=35.073876&lon=136.665126
-
There are >1200 roads. That's why I usually review by island or prefecture. N1 is probably the most complicated of them all. It connects every seaside city from Tokyo to Osaka, plus there are many bypass routes also considered part of N1.
I'm away for the next 10 days. I'll make these changes when I return at the end of the month.
-
Ok. Is the "missing wp for GSJs" a general issue of your system? Should I wait till you've added them, or should I go ahead and review the routes as I did for N1?
-
I think my personal preference is to just include all numbered prefectural roads as waypoints, it's significantly harder to add them in at a later time, and most other regions do have 2nd level secondary roads mapped too FWIW.
I also do wonder if JPN should be split by prefecture or region, it is a very dense region across our projects.
-
N1DNK:
The "city field" has "Daini Keihan Road" and the abbreviation "DNK". I'd call it DKR but not DNK. On the other hand, the rule (https://travelmapping.net/devel/manual/syshwylist.php#ccity) says "City: Used to distinguish between otherwise identically named routes of the same highway in the same region. Pittsburgh for Truck US 19 (Pittsburgh). Prefer using city names (if applicable) or other common geographical names to distinguish, e.g. island names."
Thus, I recommend calling it "Katano", the city in the middle of the route. The file name should be jpn.n001kat.
Add wp for GSJ b/n E89(1) and N1Kei.
Sync coords of E89(4) with E89's exit 4 coords. The latter look good.
Add wps for the two GSJ b/n P22_S and E89(5).
E89(5) is north of E89's exit 4-1. Are there ramps between E89 and N1? While the labels looks wrong, should we remove N1's E89(5) wp?
E89(5a) is at E89's exit 4-1. What's the right exit number? OSM + 2024 GSV (https://maps.app.goo.gl/UsJWtYNdXGd4UQTo8) suggest 5. No number southbound. The next exit to the south is also 5 (https://maps.app.goo.gl/jBxK71xtbh69v7fz5). Thus, I suggest:
- Remove E89(5) north of E1AYaw
- Rename E89(5a) -> E89(5) since it's the first exit 5, and the more important one.
- Add wp where E89 has it's exit 5, not sure if it should be E89(5) but it's also a GSJ with the surface roads
- Rename E89's exit numbers: 4-1 -> 5, 5 -> 5a
Replace +X140534 by a visible wp for the GSJ
Add wp for GSJ b/n +X140534 and E89(6)
Sync E89(7)'s coords with E89's exit 7 coords.
Sync E89(10)'s coords with E89's exit 10 coords.
Add N21 route, or rename the wp
Move N163 between the main lines of both routes
Sync E89(12)'s coords with E89's exit 12 coords.
N1Fuj:
Add wps for both GSJs
N1/P81 -> N1, no need to add the number of a lower category road.
N1Hok:
Extend route from 'End' to N477Yok.
End -> Sak or Yam or ToP622
N136Izu:
OSM indicates N136(!) extending at north end onto the surface road of N1Izu up to P141. Please check.
N1Kum:
N1DNK -> N1Kat ? see above
N1Ots:
N1 -> N1/N8 because it's a number for a route of the same system
Add wps for four GSJs b/n P43 and E1/E89
E1/E89 -> E1/E88
N1Rit:
Add wp for GSJ b/n P22 and N1/P4
N1/P4 -> N1
Add wp for GSJ b/n N1/P4 and E1
Move E1 to http://www.openstreetmap.org/?lat=35.017485&lon=136.022801
N1Sei:
ToN52 -> N52 and extend N52 ?
Add wp for the partial exit (GSJ) b/n ToN52 and ShiMarRd
Add wp for GSJ b/n P67_E and P67_W
Add wp for GSJ b/n P27 and N362 (P205)
Add wp for GSJ b/n P27 and N362, west of the river
Add wp for GSJ b/n N362 and N1_W
N1SSH:
Rename to Odawara, file name jpn.n001oda but with alt route name N1SSH because the route has a traveler (Cw9)
N1_Yam -> N1/N138
N1Yok:
N1_Tok -> E83_N
-
Thanks for the responses. I'm back from my trip and finally finished my taxes, so I'm working on these roads again.
I would hold off on reviewing other roads while I work through your review of N1.
I do have a question about removing roads. The Tokyo Expressway (TE) was decommissioned on April 5th and will be torn down. Also, the nearby Yaesu Expressway (SEY) was closed on the same day and will be rebuilt over a multi-year span. I plan to remove both roads. Latest OSM doesn't show them.
One user has driven TE. Would I need to notify users that TE is deleted?
-
I think my personal preference is to just include all numbered prefectural roads as waypoints, it's significantly harder to add them in at a later time, and most other regions do have 2nd level secondary roads mapped too FWIW.
I also do wonder if JPN should be split by prefecture or region, it is a very dense region across our projects.
Currently, primary prefectural roads are mostly included. Most exceptions are where the prefectural road network is dense, such as in urban areas. Secondary prefectural roads are mostly not included. Hokkaido is an exception because of the scarcity of primary roads there.
I'm wary of trying to include prefectural road mapping for a number of reasons.
1) There are 129000 km of prefectural roads.
2) It is difficult to trace the paths of prefectural roads when they are concurrent with other numbered roads.
Concurrencies are usually not shown on OSM.
3) I have found lists and routes of roads on a few prefectural websites. The quality of prefectural sites is widely variable. I doubt my ability to find the data for every prefecture. (Or to be able to read it if I find it.)
4) Prefectural roads change frequently. Keeping up with changes will be difficult.
As for splitting Japan's national highway system into 47 prefectural pieces:
a) Are many smaller systems preferred over one huge system?
b) Would jpne and jpntk also be split?
c) If it is likely that this split will eventually need to be made, should we do it prior to getting promoted to active?
-
I would hold off on reviewing other roads while I work through your review of N1.
Yep, that's why I didn't start with N2. I'd like to know if you understand my feedback for N1. If it's helpful as I documented it.
I do have a question about removing roads. The Tokyo Expressway (TE) was decommissioned on April 5th and will be torn down. Also, the nearby Yaesu Expressway (SEY) was closed on the same day and will be rebuilt over a multi-year span. I plan to remove both roads. Latest OSM doesn't show them.
One user has driven TE. Would I need to notify users that TE is deleted?
You should remove TE. You need an update entry because it belongs to an active system: https://travelmapping.net/devel/manual/maintenance.php#delroute
Keep SEY.
-
I think my personal preference is to just include all numbered prefectural roads as waypoints, it's significantly harder to add them in at a later time, and most other regions do have 2nd level secondary roads mapped too FWIW.
I also do wonder if JPN should be split by prefecture or region, it is a very dense region across our projects.
Currently, primary prefectural roads are mostly included. Most exceptions are where the prefectural road network is dense, such as in urban areas. Secondary prefectural roads are mostly not included. Hokkaido is an exception because of the scarcity of primary roads there.
Fine.
I'm wary of trying to include prefectural road mapping for a number of reasons.
1) There are 129000 km of prefectural roads.
2) It is difficult to trace the paths of prefectural roads when they are concurrent with other numbered roads.
Concurrencies are usually not shown on OSM.
3) I have found lists and routes of roads on a few prefectural websites. The quality of prefectural sites is widely variable. I doubt my ability to find the data for every prefecture. (Or to be able to read it if I find it.)
4) Prefectural roads change frequently. Keeping up with changes will be difficult.
I think it's similar to France. I drafted the D route systems in France :D I recommend to not add the Japanese prefectural road systems. First, because what you wrote 1-4. Second, because we only have 18 travelers so far.
As for splitting Japan's national highway system into 47 prefectural pieces:
a) Are many smaller systems preferred over one huge system?
I don't think that we have a preference about the system size. 47 instead of 1 system for prefectural roads would only make sense if each prefecture has it's own numbering e.g. if there would be more than one P1 etc i.e. each (or many) prefecture would have a P1.
b) Would jpne and jpntk also be split?
The wpt files had to be split at the prefecture borders. The systems would remain as-is.
c) If it is likely that this split will eventually need to be made, should we do it prior to getting promoted to active?
There was a proposal for hidden systems (https://forum.travelmapping.net/index.php?topic=4781), i.e. would not have to update their list files if we'd split a region. The code is quite advanced but @yakra is currently kinda out of order :(
-
Thanks for the responses. I'm back from my trip and finally finished my taxes, so I'm working on these roads again.
I would hold off on reviewing other roads while I work through your review of N1.
@nezinscot I've seen two pull requests since your last post:
https://github.com/TravelMapping/HighwayData/pull/8300
https://github.com/TravelMapping/HighwayData/pull/8309
I didn't check them in detail but guess that you are not yet done with processing my comments on N1?
Please check this too: https://forum.travelmapping.net/index.php?topic=6794.msg37727#msg37727
-
Some issues I've found (not a full review):
New N145 branch at Gobara?
New N353 branch (https://www.google.com/maps/@36.5467294,138.9242292,3a,15.8y,128.1h,101.89t/data=!3m7!1e1!3m5!1s6KOmaMZLATJF9ROD0IxSAQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-11.893738843377207%26panoid%3D6KOmaMZLATJF9ROD0IxSAQ%26yaw%3D128.1042969678432!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUxMy4xIKXMDSoASAFQAw%3D%3D) at Shibukawa
E29 and N373 don't intersect properly
E35Kar and N202Ima don't intersect properly
KE2 and N199 don't intersect properly
New piece of E55/N493 east of E55Tan?
N1 interchange between N139 and N139FIS, KanBarE and KanBarW, P208 and P81/P381, N1Nis_E and N1Nis_W, P44_Iwa and P262 (two), P262 and N152, N152 and N150
N1: N23Mei -> N23, N23/N259 -> N151/N259, N1Kei/N478 -> N1Kum/N478
N1: what is the E23 point supposed to be?
N1 missing point for E1(33-1)
N1DKR interchange between P188 and E89(1), E89(5) and NagHig, N170 and E89(11)
N1DKR: N1Kei -> N1Kum
N1Hok interchange between P66_E and P66_W
N2 and N28 should not overlap HE3
N2 interchange between HE3(3-23) and N28_W, N29 and N179_W, N179_W and P29_B (three), P29_B and P44/P715 (five?), E2(11) and N250/N374, P37 and P397 (three?), P397 and P45 (three), P40 and N30 (two?), N30 and P21_B, P21_C and P73, P22_B and N429_N (three), N429_N and P54, P54 and ToN429 (two), P54_E and N2Ono_E (three), N2Ono_W and P55, P25_Hir and P50/P362 (three), N375 and P67_B (four), N2EH_W and P86 (three)
N2Ono interchange between N2_E and P48, E76(1) and N184, N184 and N2_Fuk (two), P71 and P41_Hir (two), P41_Hir and N2WH_W, N188_W and E2(37) (two?), P58 and P24 (two?), N9_E and N190_E, N190_E and E2/P6, E2(45) and N190_W (two)
N2: P90_W relocated
N2WH interchange between N2 and P71, P71 and P41 (four), E2 and N2_W
N2 has a branch from P335 to E2 (https://www.google.com/maps/@34.0802816,131.4533083,3a,15y,231.96h,97.75t/data=!3m7!1e1!3m5!1srAjHWjhsxaQzZyHTkK0JIQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-7.75130071006015%26panoid%3DrAjHWjhsxaQzZyHTkK0JIQ%26yaw%3D231.9585922533239!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUxMy4xIKXMDSoASAFQAw%3D%3D)
Is N2Kan signed?
N3Kur: End -> KE5 (and it seems that logically it should use the ramps back to N3)
N3 interchange between N199 and P73, P27 and P87 (four?), P87 and P69 (three), P75 and P92, P92 and P97, P97 and P30, KE2(209) and P35_S (two), P31 and N200_S (two), N200_S and P17, P17 and N34
N3Hak interchange between N3_N and N201
N3Kum interchange between N3 and N387, N387 and P49, P49 and N57
N3Kag interchange between E3_Kag and P24
N4 interchange between MeiDor and SEC2/P308, SEC2/P308 and P318, P49 and P34, P34_Nas and P17 (two), P17_Kor and P47 (two), P47 and P6, P6 and N49, N49 and N288 (four), P30_Ota and N459_W, N459_E and P62_Nih, P62_Nih and P39/P129 (two), P51 and N115_W (four?), P23/P137 and N45, N45 and P8, P56_N and N347/P1 (two), P1_N and E4(32), P48_Kur and N284/N457, N4Miz and E4(36), N281_End and N282/P16 (two), E4(43) and P157, P6_Nin and P24_Nin, N454_W and N45/N102
N4Uts interchanges between C4 and N354 (two), N354 and P56, P56 and N125, N125 and P54, P54 and N50, N50 and P44 (four), P44 and N352/P47 (four), P35 and E50, P46 and N123
N4 should have a point between P126/P127 and P54_Sen for the connection to E48
N6 interchange between N298 and N464, N16 and P7_A, P8 and P11, P19 and N6UsS (three), N354/N125Ami and P24 (two), P24 and N125 (two), N125 and P64, P43_S and P43_N, P38_A and P31_N, N289 and P10_N, Ona and P66 (three?), N49 and P26, P26 and N399 (three), P36_B and N288, P266 and N115/P74, N115/P74 and P38_B (two)
N7 interchange between P46 and P556, P53 and N113?, P38_N and N47/P40, N345_D and N345_E, E7(12NTE) and P32 (two), N341_E and P44_Iwa, P65_S and P65, E7(15) and P3_Fut, P3_Hir and P41, N7Aom and N280Uch, N280Uch and N280
N7Aom interchange between N7 and E4 (two), E4 and P44_N
N8 interchange between P20 and E8(38), E8(38) and P8, P8 and N17/N351, P53 and P52, P68 and N41 (two), P1 and P41_Toy, P41_Toy and N472 (two), P11_Imi and P24 (two), P32 and N471, P16_Oya and P59 (five), N159_N and N159_S (eight), N8Ima and E8(17), E8(17) and P60 (two), P58 and N305_N (six), P54 and N360, N416/P22 and P11_Kom (three), P11_Kom and N305, N305/N364 and P61_Kag, N416 and N158 (two?), N158 and P32_Fuk
N8: N8BypOts -> N1Ots
N9 interchanges between E27 and N175/P55 (three), P8 and N429, N429 and N175_N, P6_B and E72, P43 and N53, N53 and N29/P41 (two), N29/P41 and P264, P264 and P233, N9Aoy and P51, N431_E and N181, N184 and P28_E (two)
N9 realigned west of P89?
N9Got interchange between N261 and P330
N10 interchanges between P25_B and N10Shi/P28 (two), P10_N and N219Hir (three), P9_S and E10(29), P13 and P28 (two), P28 and N268, E10(3) and N221
N10Tot interchange between N10 and P49
N10Miy extended north
N11 interchange between P15 and E32, P29 and N28/P14, P21/P46 and N319_S
N13 interchange between P102 and E13/N458, E48 and P24, P36 and P28, P62_S and E7, E7 and P41
N14 interchanges between P306 and N14Kei/P308 (two), E14 and P57, N357_N and N357_S
N16 interchange between N16Hod_S and E1, P7_N and P5, E14/P20 and E14(12) (two), P13_Ich and P87, P23 and N127
N16Hod interchange between P17 and P40
N16Hac interchanges between N16 and P160 (two), P160 and N20, N20 and E20, E20 and N16_N
N16Yok should have a point at the connection to E16 between P23 and P17
N17 interchange between P311 and P68, P13_S and P71, N17Job/N291 and N291/P26 (two), N351_N and P23, N8/N351 and P8
N17Kum interchange between N17_S and P66, P66 and N125
N17Job interchange between N17Fuk and P69, P4 and N17/N291
N17Omi interchanges between N254/P311 and P68_W (two)
N18 interchange between P10 and P48_N, P33_E and P33_W, N117_S and P34, N405/P38 and P13, E8 and N8/N350
N18Kar interchange between P43 and N18_W
N18Ued interchange between N143 and WEnd
N19 interchanges between N155 and P49 (four), P49 and P16 (two), P15 and P382 (two), P382 and P19_S, P352/N21_End and P47?, N418 and P66, P68 and E19(27), P6_S and P7 (two?), P7 and N256_W, N256_E and P473 (two), P25_Shi and P27 (two)
N20 interchange between P319 and P305, P38 and E20(12), P302/P311 and N140_N, P22 and P29, E19 and P63
-
N21 interchange between C3(8) and N21Mit_W?, N248/P84 and N41 (two), P63 and N248_W, N248_W and P207 (two), P93 and E41, E41 and N22/N156 (two), N22/N156 and P14, P1/P77 and P23, P23 and P50 (two)
N417 has been realigned near N21 (https://www.google.com/maps/@35.3850405,136.5995487,3a,29.9y,117.42h,103.79t/data=!3m7!1e1!3m5!1sKNkzmxNn7mkArJOoyo8hMA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-13.79214039758969%26panoid%3DKNkzmxNn7mkArJOoyo8hMA%26yaw%3D117.41823001196734!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D)
N22 interchange between E41 and N21/N156
N23 interchanges between P59_W and N302/C2 (two?), P71 and P7, P64 and N164, N164 and N25?, N25 and N23Chu/P8 (two), N23Chu/N166 and N42_W (three?), P59 and P60 (two?), P511 and P748
N24 interchange between P7/P188 and P69_N?, E24(1) and P69_S?, N163/N163Kiz and E24(7), E24(7) and P44, P44 and N369/P1, N308/P1 and P41, P64_S and N24Wak/P14
N24Kas interchange between E24_Miy and P14
N23Chu interchange between N23/P8 and P41, P41 and P54 (two), P54 and N306 (two), P10 and P55_N, N165 and N23/N166 (three)
N25: N125BypNan -> N25Nan
N26 interchanges between N480 and P40_N (three?), P39 and P40_S, E71/N481 and P63_N, P63_N and P63_S, P63_S and P752_N (five), P752_N and P752_S, P752_S and Nak, P7 and N24_E
N27 interchanges between N8 and P225 (four), P225 and E27(14), E27(14) and E27(13) (two)
N29 interchanges between N2 and P5 (two), E2 and P80
N30 interchange between N2 and P74
N32 interchange between N439_W and P33?, N440Mis_S and N440Mis_N, P23 and N33Mat, N33Mat and N11_E?
N34 interchange between N207_E and N207, N207 and P24, P37_N and N57_W
N36 interchange between P46 and P45?, P45 and P46_S?, P46_S and N337/P16
N37 interchange between P107_W and N37Hak
N38Kus interchange between N240 and P53
N41 interchanges between P49 and P84 (five), N21 and N418_W, N418_W and P80, N418_E and P64_S?, P98_N and N158
N42Kii interchanges between N167_S and P37_E (two), P59_S and P13, P38_W and P37, P31_N and P29 (three), P29 and E42(34), E42(34) and N424_S, P20_W and N480
N42 new spur on Arida Sun Bridge?
N43 interchange between HE17(17-02) and HE17(17-03), HE17(17-03) and HE17/N172, HE3(3-06) and P57_N, HE3(3-07) and HE3(3-08), HE3(3-08) and E1
N43 branch (https://www.google.com/maps/@34.701526,135.4389303,3a,16.4y,133.05h,97.63t/data=!3m7!1e1!3m5!1so8Jr0J24AavX4jC5luRfOw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-7.6267131241503705%26panoid%3Do8Jr0J24AavX4jC5luRfOw%26yaw%3D133.05313305265483!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D) on old Yodo River bridge
N45 interchanges between N4 and E6 (two), E45(39) and N283, N283 and P242 (two), N104 and E4A(7) (two?)
N45San does not properly overlap E45 between 15 and 17
N46 interchange between P266 and N341_A
N47 interchange between E13/P34 and N47SKE, P38 and E7, E7 and N7
N47SKE and N47SKW should be combined
N48 interchanges between N286_E and E4 (two?), P31 and N457_N (two)
N49 interchange between N6 and Iwa, E8 and N7/N8 (two)
N49 has been realigned to use N49Sui? (https://www.google.com/maps/@37.8227209,139.2267053,3a,28.6y,358.49h,100.12t/data=!3m7!1e1!3m5!1su3SVXFUw43A4dvxRwYzkQA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-10.115912273774825%26panoid%3Du3SVXFUw43A4dvxRwYzkQA%26yaw%3D358.4896931920866!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D)
N50 interchange between P69_E and P78, N122_N and P39, P8 and P7, P9 and E4, P11 and P33_W (two), P15_E and N294 (two)
N50Mit interchange between P50 and N6/N6HMR
N51 interchange between P70 and N356
N51 branch at Kashima (https://www.google.com/maps/@35.9655018,140.6138945,3a,18.6y,133.47h,103.33t/data=!3m7!1e1!3m5!1seoC2pCOf2aN-rP-8Mt3hMQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-13.328457845603054%26panoid%3DeoC2pCOf2aN-rP-8Mt3hMQ%26yaw%3D133.47361213183316!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D)
N53 interchanges between P72 and P81 (four), E29(8) and N29
N53Tsu interchange between N53 and P338
N54: add point for Higashihiroshima Takada Road (Mukaihara Yoshida Road) (https://www.google.com/maps/@34.6562855,132.6914176,3a,16.4y,166.18h,91.5t/data=!3m7!1e1!3m5!1ssqVzzJLNkv0mnSQtgGLc2A!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-1.5029923498110804%26panoid%3DsqVzzJLNkv0mnSQtgGLc2A%26yaw%3D166.18388701405235!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D) between P5_N and P29
N54 needs shaping points between N184_N and P38_Kak
N55 interchange between P27 and P23
N56 interchange between N32_N and P34, P36_E and P37 (two), P36_W and P39_E, P23 and N33Mat/N56Mat, N33Mat/N56Mat and P16
N57 interchanges between N10_S and P57_Inu (two)
N57Kit interchange between OtsHig and P339
N58Oki interchange between N58Nag_S and E58(10)
-
N101 interchanges between P56_N and E7/N7 (two)
N105: move P30?
N108 interchange between N457_N and N108Nar_S
N108 should get a point for P248 (https://www.google.com/maps/@38.8116695,140.6462234,3a,15.1y,126.22h,99.83t/data=!3m7!1e1!3m5!1sSBLib1b7fgvWAar6LndYNQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-9.8329172246832%26panoid%3DSBLib1b7fgvWAar6LndYNQ%26yaw%3D126.21746931144146!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D), which is signed as a bypass to N108
N108 realigned at Shimokogawa (not sure what the old route is)
N108Fur interchange between N108 and P32
N112Gas interchange between Yud and E48(10)
N113 interchange between P17 and P17_E
N115 interchange between N6/P74 and P34, N4_S and N13FWR
N116 interchange between P192 and P22, P22 and P18 (two), P2 and P44, P44 and E8
N117 interchange between N18_S and P34
N118 new branch (https://www.google.com/maps/@37.319064,139.9081986,3a,23.2y,195.33h,106.14t/data=!3m7!1e1!3m5!1sRww7sTOMwX6rDfOv9tShPw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-16.136480811796062%26panoid%3DRww7sTOMwX6rDfOv9tShPw%26yaw%3D195.32646444961844!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D) at Yunokami Onsen
N119Nik has been partly closed and realigned (https://www.google.com/maps/@36.7128873,139.7335178,3a,15y,102.01h,87.88t/data=!3m7!1e1!3m5!1sBcqv-g90vL4DWeyNEtuG6Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.12347692439765%26panoid%3DBcqv-g90vL4DWeyNEtuG6Q%26yaw%3D102.00822927756747!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D); it's not clear if it exists east of here (is any of it signed?)
N119Uts interchange between N119 and N119Utc, P63 and N4/N4Uts
N121 interchange between N287Yon and P3_A, P333 and P16, N4Uts and P46_N
I wonder what's under the blue...has N121 been realigned? (https://www.google.com/maps/@37.204693,139.7661621,3a,15y,259.92h,96.01t/data=!3m7!1e1!3m5!1siNIKqsvIyXcZ3Np3FW1z-g!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-6.011791192022841%26panoid%3DiNIKqsvIyXcZ3Np3FW1z-g%26yaw%3D259.9195959411237!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D)
N121Nik has been partly closed (https://www.google.com/maps/@36.684495,139.7186605,3a,43y,172.17h,79.91t/data=!3m7!1e1!3m5!1sVJ8LTwIJZEcAqPWJZwQetQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D10.086076960120423%26panoid%3DVJ8LTwIJZEcAqPWJZwQetQ%26yaw%3D172.17053531759663!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyNy4wIKXMDSoASAFQAw%3D%3D)
N122 interchange between N122Iwa_N and N122Iwa/P2, N16 and E4/N463Kos (at least one, maybe more), E4(2) and N298 (three?)
N123 interchange between N294/P69 and P51
N124 interchange between N126/N356 and P117
N125 interchange between N125Ami and P68, P48 and N354_W, N354_W and P24, P32 and P7
N125 and N354 don't overlap properly at P125, and N354 needs N125_E -> P125
N126 interchange between P49 and N126Sam
N126Sam has been extended east?
N128 interchange between N297_N and N465_W
N129 interchange between P63 and N246_W, N246_W and N412/P60, P65 and C4(33) (two), P54 and N16/P63
N135 interchange between N135Ito_S and N135Ito_N
N135Man interchanges between N135_S and N135_N (two)
N137 interchange between N137Mis_S and N137Mis_N, E20 and N20_E
N138 interchanges between E68_End and N138Got (two)
N138Fuj interchange between 3 and 4
N139 interchange between E1 and E1A, P71 and E68 (two), E68 and N138
N140Han interchange between P47 and P69
N140Min interchanges between N140_N and P82 (two), P44 and N299
N140NKR interchanges between N140Man and N140/P6 (four)
N141 no access at P17 (move to connector?)
N142 and N142Shi need to be separated (they shouldn't overlap)
N145 interchange between P375 and P237
New N145 branch at Iwashima?
N150 interchange between P30 and N150Yai
N150Nan interchange between P239 and N150
N152Yuk has a point on N152 but no file
N152 interchange between N152Yuk and YatEchLin
N153 interchange between C2/N302 and P58_W, P57 and P54_W?, P54_E and N155_S, P227 and P59_Mat
N153Toy interchange between N153 and C3; extend to meet C3?
N153Min has been extended south
N155 interchange between P265 and N155Chi_S?, P56_N and E1/P76, P67 and P79, P45 and N158_E?
N155Chi interchange between N155_S and P46, P46 and N247Chi_N (two)
N155: N419_S does not connect to N419Tak
N159 interchanges between P56_E and N8_E (three), N8_W and P215, E8/N304 and P210
N160 interchange between N415 and P76
N161 interchanges between P54 and N303/P54 (five), N303/P54 and P38 (three), P38 and P23, P23 and P345 (six), P345 and N477, P315 and P47 (two), P47 and P30, P30 and N1 (three)
N163 interchanges between P20 and N168 (four)
N165 interchange between N166_E and P38
The E91/N24/N165/N166/N166MHR overlap is messy; N24 needs to be aligned to the others and then probably everything removed from E91 to the frontage roads east of UnaRmp. N166MHR has a weird hanging east end.
N168 interchange between N165 and N168Kas
N170 interchange between P8 and N308, N308 and P24, N170Shi and P12?, N371 and N170Izu_A (two), P39 and P40_W?, N170Kai_W and P30
N171 interchange between P13 and P42, P42 and N2_E (three?)
N175 interchanges between N175Kan_N and ToP20 (two), P23_S and P23_N (two?), P23_N and P81, N372 and P17, P294 and N427_N
N176 interchange between N176Naj_E and P51
N176Tak interchange between P42 and E2A(3), E2A(3) and P13
N176Tak: N176BypMei -> N171
N180 interchanges between P8 and E2A/P8 (two?)
N180Soj now continued west from the turn (https://www.google.com/maps/@34.6857989,133.7703661,3a,15y,260.8h,108.61t/data=!3m7!1e1!3m5!1snlNR5z-Zi0SwJif5FVIm9w!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-18.609113860835095%26panoid%3DnlNR5z-Zi0SwJif5FVIm9w%26yaw%3D260.8034453060434!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D); the north-south part has become N429 (https://www.google.com/maps/@34.6795579,133.7707164,3a,15y,348.96h,102.03t/data=!3m7!1e1!3m5!1sXbQUH9XD3rRlWCN1a5CDCg!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-12.031797064638312%26panoid%3DXbQUH9XD3rRlWCN1a5CDCg%26yaw%3D348.9559625028433!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D)
N183 interchange between N432_S and P26, P8 and N180_N
N188 interchange between P8 and P63
N190 interchange between P6_E and P29, P6_W and P71 (two?)
N191 interchanges between N9_W and P40 (four)
N192ToE interchange between N438 and N55/P29
N195Koc interchanges between P44 and N32 (two)
N196 interchanges between N317 and P38 (two)
N197OHB interchange between End and P38_E, P610 and N10Oit
N199 interchanges between KE2(203) and KE2/N199Kit (two)
N199 has points for H199Hig, but there's no such file
-
N200 interchange between P53 and N3_S
N200Nog interchanges between E3 and P28 (three), P28 and P22 (three), P22 and P62, P62 and N200_S (three)
N200Hiy interchanges between N200_C and P77 (two?)
N201Yuk interchange between N201/P25 and P28
N201Yak interchanges between N201_E and N211 (four), N200 and P60, P60 and N201_W
N201 interchange between N201Yak_W and P92, E3 and FE4(404)
N201 should not overlap FE4
N202 interchange between E35_Jur and E35_Ima, N204 and N203
N202 should not overlap E35
N202Ima interchange between P49_W and Yos, E35(24) and N202/N323 (two)
N202Asa interchange between N202_E and N202_W
N202Fuk should not overlap FEC
N205 interchanges between E35 and N202 (two), N202 and P213 (two)
N212Nak: N213 -> 2
N213 interchange between N212 and N212Nak
N219 interchanges between E10 and P44 (three)
N219Hir interchange between N219/P14 and N10
N220 interchanges between E10/E98 and P52 (two), P377 and N222 (three)
N229 interchange between P820 and P956
N238 interchange between P204 and P1151
N246 interchange between ShiKurRd and P13, SEK7 and ToP18, ToP18 and N16, N467_S and P42 (three), P51 and N129_N, N412/P60 and N129_S, P71 and P62, P76_W and P150 (two), P24 and E70
N247 interchange between N1/N19 and Tok, N419/P50 and P45
N247 and N23 should probably not overlap
N247Chi interchange between N155Chi_E and P249
N248 interchange between N23/N247 and N23_W, P83 and P84 (three), N21_W and P17 (three)
N248: N23/N247 -> N247, N23_W -> something else, N23BypOka -> ToN23, N363Kam -> N363Set
N250 interchanges between N2/P21 and P208 (three?), P208 and P19 (six?), P19 and P79
N251Shi interchange between N251_S and N251_N
N253 interchange between N403_N and P49_S?
N253Ura: N43 -> P43
N254Fuj interchanges between N463 and P56 (five)
N254 interchange between P27 and N407, P66 and P41?, P23_W and P40_Fuj
N258 interchange between P23 and P26, P142 and N421_W?
N274 interchange between E5(30) and P3_W
N288 interchange between N4 and P296
N288Mih interchange between P73 and E49, E49 and P54
Does N289 continue past End to where OSM shows a gate?
Is N289Taj now mainline N289? (see discussion under N121)
N292 interchanges between P66 and N403_N (four)
N293 interchange between P8 and P40_S?
N294 interchange between P47 and P46, P3 and N354Ban, N289_E and P11_Shi?
N298 interchange between C3(71) and C3(72), C3/P67 and C3(81), C3(81) and C3/P54 (three?), C3(85) and N14?
N299 and N462 have been realigned (https://www.google.com/maps/@36.091243,138.8246961,3a,31.3y,93.42h,97.81t/data=!3m7!1e1!3m5!1sBXtTuutlANhryEUeWt07ng!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-7.810122657115301%26panoid%3DBXtTuutlANhryEUeWt07ng%26yaw%3D93.42018977973312!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D) near their eastern split
N299 interchange between N299Han_W and P30?
N299Iru interchange between N299/N299Han and N16/N463Tok
-
N302 interchange between P30 and P15, C2(9) and P59_B?, C2/N1_E and N23
N308 should not overlap HE13
N309 interchange between N170Sot and N170, N170 and P36 (two)
N313 interchanges between N482_W and P50 (three)
N313 has a bad shaping point between 7 and 6
N320 interchange between N56/N320Uwa and P57?
N322Yam is a bypass (https://www.google.com/maps/@33.5722014,130.7753491,3a,19.9y,214.31h,114.88t/data=!3m7!1e1!3m5!1sChQqzLWGkNijLTURgQd92g!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-24.883015880823066%26panoid%3DChQqzLWGkNijLTURgQd92g%26yaw%3D214.31170671345345!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D), not the old road
N322 interchange between P81 and N210
N325 interchange between P30 and N57/N443
Which way does N327 go at the Oicho Tunnel (https://www.google.com/maps/@32.48638,131.2412145,3a,47.6y,63.09h,90.22t/data=!3m7!1e1!3m5!1sl7MC1CePrPpao_cvji8-ag!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-0.22010399063115926%26panoid%3Dl7MC1CePrPpao_cvji8-ag%26yaw%3D63.08532664846454!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D)? If this sign (https://www.google.com/maps/@32.5031048,131.2662879,3a,15.4y,285.4h,91.91t/data=!3m7!1e1!3m5!1sVH124OTGrXQ2vnjMvgxJJg!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-1.9132897851959%26panoid%3DVH124OTGrXQ2vnjMvgxJJg%26yaw%3D285.4007828400515!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D) is correct, points should be added at either end of the detour.
N330 interchanges between E58 and P153 (two), P153 and P38, P82 and P29
N331 interchanges between N331Oro and P77 (three)
N337Doo interchange between P1149 and N337_Shu
N337 interchange between N12 and P139
N279Aom's route in Oma has always been how OSM shows (https://www.google.com/maps/@41.5232035,140.906388,3a,24y,219.78h,104.45t/data=!3m7!1e1!3m5!1sqooSQ2IBREhSFhllC0Z13w!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-14.447978196612212%26panoid%3DqooSQ2IBREhSFhllC0Z13w%26yaw%3D219.77717875716155!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D), and N338 was removed from the other alignment (where we have both) after 2021 (https://www.google.com/maps/@41.5231563,140.9064098,3a,75y,219.78h,104.45t/data=!3m8!1e1!3m6!1sRyAgvORis9hzzz-WzUHT3A!2e0!5s20210801T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-14.447978196612212%26panoid%3DRyAgvORis9hzzz-WzUHT3A%26yaw%3D219.77717875716155!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D). So N279 needs to be moved, and N338 either gets moved with it or truncated to the junction.
N349Bai interchange between P50 and N349
N349 interchange between P37 and P36_E
N352Toc and N352Nik should not overlap; also see notes for N121Nik
N352Toc and N293Kan don't intersect properly
N354 interchange between P69_N and N407, P58 and N294/N354Ban (three?)
N357 interchange between N14_W and E51(4), E51/P8 and E51(2), N298 and SEB(B32), SEB(B32) and P242, SEB(B31) and SEB(B30), P308 and SEB(B24), SEB(B24) and P304_E, SEB(B23) and P484, P484 and SEB(B22) (two), SEB(C18) and SEB(B18), P316 and HanAir_N
N357 should not overlap SEB between B19 and B21
N357Kaw interchange between SEB(B11) and SEB(B10)
N357Shi interchange between N357 and P316
N357Yok interchanges between NEnd and SEB(B07B) (two), SEB(B07B) and SEB(B06), SEB(B06) and P82, P82 and SEB/P17
N358 interchange between N139 and P36_E
N359 interchange between P68_N and P59_N
N366 interchange between N366Han/P50 and N155_W
N367 interchange between P181_E and P105
N371Kaw interchanges between N170 and N371 (three)
N371Sek has been extended south
Do N371 and N371Tan now connect?
N372 should not overlap E9
N373Kom and E29 should overlap
N373Sak and E29Oha should overlap
N378 interchange between P43 and N197_W
N385: N385Hig* -> N385Sak*
N387 and E10 don't connect properly
N399: P12_W realigned
N399Iza interchange between P5 and N399
-
N400 may have been realigned at Minamiaizu (see N121 discussion)
N404Nag interchange between P499 and P86
N408 interchange between P19_N and P56?
N408Mok interchange between E50 and P193
N409 should overlap CA between SEB and Umi
N409 interchange between P87 and CA(3)/N16
N414Shi interchange between P139 and N414
N415 interchange between P57 and P11
N416 interchange between N8 and N416Eih_W
N418Kis probably doesn't need to be its own section; just keep the point on each end of the closure
N418Nag: P1_S realigned
N419 interchange between N153_W and ToP76
Why doesn't N419Tak extend north to N155?
N419Tak interchange between N1 and N23, N23 and P48
N421 interchanges between N258_N and E23 (two), E23 and P26_S?
N423 interchange between P135 and P2_S?; split ComArtHill in two
N431 interchange between P2 and P47
N431Hay interchange between N431_W and N431_E
N442: N442Oka point has no corresponding file
N443Mit interchange between N208Ari and P83?
N453 interchange between P82 and P341
N456: remove P25_E, P25_W -> P25
N458 realigned at P30_S, P26_S (https://www.google.com/maps/@38.3558668,140.2581643,3a,28.8y,138.97h,105.39t/data=!3m7!1e1!3m5!1sa17bzEy1VY0KLt_VNmX7oA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-15.387426223367612%26panoid%3Da17bzEy1VY0KLt_VNmX7oA%26yaw%3D138.96535461607363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D)
N458 interchange between P51 and E13/N13
N459Sui: see N49Sui
N460 needs a point at N49Sui
N463 interchange between E4/N122 and P1_E?
N464 interchange between N16 and P61?, P4 and P64_N?, P65 and P12
N246 and N467 should not overlap
N473Sag needs a point at E1
N473Sag interchange between N473_N and N473Hag, N473Hag and N150Nan (two)
N477Yok interchange between N477_W and P14
N477 interchange between P11/P26 and N161
N478: N1/N1Kei -> N1/N1Kum
N479 interchanges between P8 and N308/ChuDor (two?), P173 and N25?
N479 should not overlap HE14
N480 interchange between N26 and P30_W
N481 interchange between P64 and P30
N181, N183, and N482 now use N181Kis (https://www.google.com/maps/@35.3724773,133.4163186,3a,15y,291.56h,99.96t/data=!3m7!1e1!3m5!1sww1see1-x_jRPUHcn3mejA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-9.958867174097023%26panoid%3Dww1see1-x_jRPUHcn3mejA%26yaw%3D291.55988692437097!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDUyOC4wIKXMDSoASAFQAw%3D%3D)
N485Mat interchange between N431_W and N9
Should N9Mat be removed from the E9Mat overlap between 21 and 23?
N507Tsu interchange between N507_S and P48, P48 and E58/P82, E58/P82 and N329_W
-
That should be it for my notes, which are not a full review.
-
One question: what does the h stand for in jpnh?
-
One question: what does the h stand for in jpnh?
National Highway I presume...
-
One question: what does the h stand for in jpnh?
National Highway I presume...
How does H stand for national? JPN is the country code.
-
One question: what does the h stand for in jpnh?
National Highway I presume...
How does H stand for national? JPN is the country code.
Highway
-
The wp label prefix is N. Thus, I think the system abbreviation should be jpnn. It can simply be changed since it doesn't affect users.
btw, should the system name be "Japan Ippan Kokudō"? https://en.wikipedia.org/wiki/National_highways_of_Japan