Clinched Highway Mapping

[Scott5114]

Servers are powerful these days. Using processor cycles on PHP is cheap, and the load would be distributed amongst all the other sites on that server anyway. All the PHP would have to do is look up the  If his host charges more for the more PHP he uses, then he's getting ripped off and should switch hosts. To be blunt, saying you can't do something like this for performance reasons is a total cop-out.

If you wanted to get really fancy with it you could have the JavaScript do *everything* but edit the list file after submission. That would be more difficult but then everything would happen on the user's browser and thus it wouldn't result in any more load to the server than when the list files are updated manually.

I'd much rather have a graphical data entry method than the rest of the state routes right now. The graphical data entry will benefit everyone in some way...which likely a lot more people than those who would find having Arkansas state routes in the system! (Not everybody has been on an Arkansas state route, but everyone who uses the site uses the site.)

[SSOWorld]

nevertheless - having a site like this is a privilege.  The guys working on it are using their spare time outside work to do so.  It would take lots of time that they likely don't have to do this.

[Scott5114]

Of course it is. Which is why I'm not saying it has to be some fancy dancy map-based click-and-drag production. If you set up something like I proposed, it would take about two days to set up. A lot of the code already on the site could be re-used for this. (Don't have to write a new list parser, don't have to write a way to pull up the point data...) The rest of it is just basic UI stuff.

Hell, if they actually took this suggestion I'd probably volunteer to do the Oklahoma highways for them.

[oscar]

Hell, if they actually took this suggestion I'd probably volunteer to do the Oklahoma highways for them.

Already in development, with the draft state routes up to the high 20s.  But not AR, LA, and TX, as far as I know.

[yakra]

I I don't see CPU cycles being a significant issue here. I envision adding an "Edit" or "Clinch" etc mode to the HB. It'd only even be active when a traveler choose to invoke it & do something with it. It'd probably have nothing on concurrent.php, or the HB's newish Show Intersecting Highways feature. Plus, as Scott noted, it could probably all be handled via JS client-side before sipping off a new .list to the server.

OTOH, getting the human(s) in charge of all this to agree on how it's to be implemented, and then find the tools knowledge & time to do it all -- that could be more of an issue. But nothing's gotta happen immediately...

Maybe start small, and explore methods of uploading a .list file from HD, or editing one with forms... and once that's down, branching out into snazzier interfaces.

O HAY! Look, I'm a... what comes after Viaduct, now?

[agentsteel53]

O HAY! Look, I'm a... what comes after Viaduct, now?

looks like you're a trafficway! 



(apparently, people in Kansas like traffic enough that they name a classification of road after it.)

[yakra]

I guess the solution for that is tons n tons n tons of gratuitous overposting.
Man, I kinda liked being a viaduct. But it'll never be back, though...

But seriously, folks...

Already in development, with the draft state routes up to the high 20s.  But not AR, LA, and TX, as far as I know.

I think an unofficial plan, when last discussed, (since TX is so bloody huge) was to have Andy be the ringleader & maintainer for TX, and delegate out routes in blocks of 50 to other interested collaborators, who then turn them over to him for a final check-over, submission & maintenance once completed.
Though for the time being, Andy is (and probably all the rest of us as well! ) holding off on the TX subsystems till his other states are done.

[agentsteel53]

I guess the solution for that is tons n tons n tons of gratuitous overposting.

are you attempting to get to 2,147,483,647 posts, so you can wrap around??? 

Man, I kinda liked being a viaduct. But it'll never be back, though...

I can change your post count.  What number would you like?

[rickmastfan67]

It may be a burden on a new user of the site to create a large list of highways clinched but the way I see it, it's easier to do a text file directly than to push the admins of the site to create an interface.

Tim's the only Admin for the site and does all the work on creating the interface for the site.

[SSOWorld]

I stand corrected.

[treichard]

Two new US state highway systems are ready for mapping travels:

- Illinois State Highways: compiled by Jeff Morrison.
- Maryland State Highways: compiled by me.

http://cmap.m-plex.com/index.php

==========================================

Regarding site features at the CHM site, I have far more ideas and plans for improvements than I have time to implement.  For now, we're focusing on improving quantity instead of quality, making use of about a dozen collaborators so kindly working in their spare time to add thousands more highways to the site.  Managing their constant output is actually time-consuming enough that I soon have to decide whether to accept or reluctantly reject having several more volunteers involved.

A plain text file is the second simplest solution for users, falling behind only having no file to mess with at all. 

[Alps]

Note for NJ, which you haven't yet implemented - you're missing some routes: 139 162 163 167 324.  Any questions about where those are, feel free to ask.

[yakra]

324 is out due to being unsigned.
139 is a headache...

NJ139 is the (mostly underground) portion of the Pulaski Skyway that connects US1/9 with I-78 in Jersey City, shown here). Except, it's also the surface street Hoboken Ave, which has interchanges the lower ("Skyway") portion does not. I have no idea how to handle this one. Two routes ("Upper" and "Lower")? One route with no intermediate intersections? One route with intersections (probably the two I have on the Hoboken Ave segment)?

...we have yet to figure out how to deal with.

As for the other routes, I know nothing about those; I'll forward your comment to the CHM forum.

[Alps]

324 is out due to being unsigned.

There are definitely unsigned routes in the database, like Quebec A-920.  So that's no excuse.  Three key points - western end, junction the one road that leads out somewhere, dead end.

139 is a headache...

139 itself starts at 1/9, next point would be merge with 139_U (Upper), next point would be junction I-78 at Jersey Ave., next point would be the state line probably.

As for the other routes, I know nothing about those; I'll forward your comment to the CHM forum.

The others are unsigned.  163 needs two ends (western and US46), 167_S would be US9 and end, 167_N would be end and US9.  162 also just needs two ends.  It looked like you had NJ 13 in there despite being unsigned - again, I'd argue to include any officially designated route.

[rickmastfan67]

324 is out due to being unsigned.

There are definitely unsigned routes in the database, like Quebec A-920.  So that's no excuse.  Three key points - western end, junction the one road that leads out somewhere, dead end.

FYI, Interstates don't count.  Hidden or un-hidden, Interstates will stay.

[oxlahun]

139 is a headache...

139 itself starts at 1/9, next point would be merge with 139_U (Upper), next point would be junction I-78 at Jersey Ave., next point would be the state line probably.

The lower route starts at 1/9 and has its other endpoint at I-78. It has no other interchanges. The upper route's western end is Kennedy Blvd, there are surface streets that may be of interest, and its eastern end is I-78 where it joins the lower route. Neither route continues into the tunnel.

It looked like you had NJ 13 in there despite being unsigned - again, I'd argue to include any officially designated route.

NJ 13 is more likely to get pulled than the others added, although there is at least some evidence that it exists as a separate designation (a 0 mile marker at its western end is visible in GMSV). The current policy for state routes is that unsigned routes are not intentionally included. I think many of us appreciate the ideal of completeness, but consider (for example) the hundreds of really short unsigned routes in Connecticut. There's a point of diminishing returns, at least for the first pass on the state routes, and whether the route is signed is a reasonable approximation of that point.

[vdeane]

Not to mention the high degree of difficulty in determining if you've been on a route in a state where you aren't familiar with the unsigned routes.

[froggie]

Regarding unsigned routes, Tim's preference for state/provincial routes (as noted before, this doesn't apply to Interstates and Autoroutes) is that unsigned routes be left out, though some have remained in (or placed in) the system if they provide a major connection.  It's looked at on a case-by-case basis.

[yakra]

though some have remained in (or placed in) the system if they provide a major connection.  It's looked at on a case-by-case basis.

I can just think of OR100 now... wat other examples are there?

[SSOWorld]

In WI - I don't see any that would need to be in.  I'm actually surprised that WIS 341 is included - it's not signed, but I guess it has a connection to Miller Park so that might be why.  There are two spurs, one (WIS 794) of which is listed.  The other is so short that it shouldn't even be mentioned in the state books.  These aren't signed.  - I just noticed that WIS 794 spur is on the wrong road too

[Bickendan]

though some have remained in (or placed in) the system if they provide a major connection.  It's looked at on a case-by-case basis.

I can just think of OR100 now... wat other examples are there?

Not that OR100 provides a major connection... but it is well signed (not by number), and most people going through the Gorge will take OR100 at one point or another. OR209, however...

[yakra]

I see it's not in the HB... another unsigned one that?

Oh yeah... and above, I wasn't asking for examples of major connection so much as just examples of unsifned routes in the HB

[Bickendan]

OR 209 got pulled; it got decommed in the late '50s and was a Google artifact when I drafted the route, and Google's corrected the error.
If we ever did a NP set, it'd go there.

[treichard]

Five more highway systems are now mappable at the Clinched Highway Mapping site. 

http://cmap.m-plex.com/index.php

Users can now track their cumulative travels on these systems:

- Massachusetts State Highways - compiled by Jim Teresco
- France Motorways (Autoroutes) - Si Hollett and me.
- Belgium Motorways (Autosnelwegen) - me.
- Martinique Motorways (Autoroutes) - me.
- Luxembourg Expressways (Schnellstrossen) - me.

[NWI_Irish96]

What exactly is required to "compile" a highway system?

I'm interested in getting Indiana State Highways on the site.