Recent Posts

91

In-progress Highway Systems & Work / Re: mexf: Mexico federal routes

« Last post by neroute2 on July 23, 2025, 08:07:24 pm »

A new bypass around Mineral del Monte, Hidalgo, opened earlier this year. You can see at 18:15 in this video that the both the new bypass and the old alignment are signed as MEX 105 on brand new signs that weren't present in 2023 GMSV.

If I don't get to it in a week, please remind me.

92

In-progress Highway Systems & Work / Re: mexf: Mexico federal routes

« Last post by shiggins on July 23, 2025, 06:07:56 pm »

A new bypass around Mineral del Monte, Hidalgo, opened earlier this year. You can see at 18:15 in this video that the both the new bypass and the old alignment are signed as MEX 105 on brand new signs that weren't present in 2023 GMSV.

93

General Web Design Discussion / Re: dbname= functionality and archive databases

« Last post by Jim on July 23, 2025, 04:25:17 pm »

Thanks, @michih. I especially like the idea of a banner when an alternate DB is selected.

https://github.com/TravelMapping/Web/issues/843

94

General Web Design Discussion / Re: dbname= functionality and archive databases

« Last post by michih on July 23, 2025, 02:40:46 pm »

Just my 2ct on this...

I like the idea very much I think it could help to improve the update entries. https://travelmapping.net/devel/updates.php features the 'File Root' column. A new (automatically added by frontend) column could open showroute with dbname=TMxxxxxx where xxxxxx is the last stored alternate database before the date indicated in the 'Date' column. That means, with highway data and user data from the day (or week, or month or year) before the update was made.
If a routing was heavily changed, I usually check my travels on mapview. It would be great if I could directly switch to mapview with the current view.

I also love the idea of seeing stats and mapview at a previous point like before my last travels or at the end of last year

To be honest, dbname is not yet useful for me since it's not persistent. We could simply add a yellow banner - like the red 'update in progress' banner - that indicates 'You currently view historical data from xxxxxx'.

Having this in mind, I think that we should minimum have one historical database per year. Likely from Dec 31. A simple drop down menu could make the trick to select it on the front end. Could we also do this for 2015 to 2024 data? It's all on Github, but I assume it's hard to automate, isn't it?

If data space is not a big issue, I'd prefer having one historical database per month to better meet the use-case demands from above. Then, we would likely need a more sophisticated selection option.

I don't know what could be broken and how to test things on tmstage now. I cannot simply click around since the QS is not persistent. But all I quickly tried worked fine. Thanks for your work

95

In-progress Highway Systems & Work / Re: usaush: United States Historic US Routes

« Last post by Jim on July 23, 2025, 02:00:49 pm »

https://travelmapping.net/hb/showroute.php?r=il.us066hiscar exists.

Thanks.  Looks like I should have scrolled down in the CSV to all of the other alignments.  That makes it easier.

96

In-progress Highway Systems & Work / Re: usaush: United States Historic US Routes

« Last post by si404 on July 23, 2025, 01:34:54 pm »

https://travelmapping.net/hb/showroute.php?r=il.us066hiscar exists.

I renamed US66HisChi as US66His to match IA US20His as both go border to border.

97

Solved Highway data updates / Re: ME: I-395/Route 9 connector

« Last post by yakra on July 23, 2025, 10:38:45 am »

Dropping this here for future reference...

Code: [Select]

Route* ME9 = Route::pri_list_hash.at("ME ME9");
unsigned int i1 = ME9->pri_label_hash.at("US202_HAM");
unsigned int i2 = ME9->pri_label_hash.at("ME46");
cout << i1 << ' ' << i2 << endl;
TMBitset<TravelerList*, uint32_t> travelers(TravelerList::allusers.data, TravelerList::allusers.size);
for (unsigned int i=i1; i<i2; ++i)
travelers.fast_union(ME9->segments[i].clinched_by);
cout << "Travelers on ME ME9 US202_Ham ME46:";
for (TravelerList* t : travelers)
cout << ' ' << t->traveler_name << flush;
cout << endl;
return 0;
...because relocation.sh is unreadable & unmaintainable and has too many problems.

98

General Web Design Discussion / Re: Clinched Routes Highway Shields

« Last post by the_spui_ninja on July 23, 2025, 10:27:01 am »

Time for Batch 3:
  - CO NWPkwy: The same page on Wikimedia Commons that says it may be copyrighted also says, “This image of simple geometry is ineligible for copyright and therefore in the public domain, because it consists entirely of information that is common property and contains no original authorship.” I’m convinced. In it goes. Besides, the inclusion of the route on this site is likely to give them extra drivers and thus extra tolls…
https://github.com/TravelMapping/Web/pull/842

Thanks for pulling that in! Since you're doing batches, can you add one for the Badlands Loop Road (https://travelmapping.net/hb/showroute.php?units=miles&r=sd.badlprd)? DOT has green "BADLANDS LOOP" signs everywhere.

99

In-progress Highway Systems & Work / Re: usaush: United States Historic US Routes

« Last post by Jim on July 23, 2025, 08:01:50 am »

Looks like hwy_data/IL/usaush/il.us066hischi.wpt is now hwy_data/IL/usaush/il.us066his.wpt so I can apply those changes to that file, but I am not sure what to make of hwy_data/IL/usaush/il.us066hiscar.wpt.  New route?  Was that also supposed to be rolled into the single IL US66His?

100

In-progress Highway Systems & Work / Re: usaush: United States Historic US Routes

« Last post by Jim on July 23, 2025, 07:53:12 am »

I have an update by email from Highway63 that includes hwy_data/IL/usaush/il.us066hischi.wpt and hwy_data/IL/usaush/il.us066hiscar.wpt.  However, it looks like there is only a file il.us066his.wpt.  I'll see if I can get the changes where they need to go.  Those who are editing these files, please coordinate with each other on changes before submitting and make sure everyone's aware of  changes that are made.