Travel Mapping

User Discussions => Other Discussion => Topic started by: Jim on February 14, 2016, 12:31:46 am

Title: Project Statistics
Post by: Jim on February 14, 2016, 12:31:46 am
I haven't posted anything like this since we moved to this forum, so I thought it was time.

Our highway and user data now results in a database that gets constructed from 3,727,950 lines of SQL.  Over 20,000 .wpt files now get processed, along with 113 .list files.

A site update now takes about a half hour from start to finish.  When I get a chance over the summer to unify the regular database and the one that includes preview routes for mapping and stats, I expect we'll cut that nearly in half.  If I run it on my FreeBSD desktop instead of my Mac Book Pro, it also seems to be 25% faster, at least.  I'm sure other efficiency improvements will also present themselves the next time I can get my hands deep into the site update code.

Load on the server to serve maps and stats pages (including running the cgi scripts and DB queries) seems nearly negligible.
Title: Re: Project Statistics
Post by: michih on February 14, 2016, 03:23:29 am
How many users do mapping their travels / how many list files of real travelers do we have now?
I think CHM had about 350.
Title: Re: Project Statistics
Post by: Jim on February 14, 2016, 08:46:52 am
How many users do mapping their travels / how many list files of real travelers do we have now?
I think CHM had about 350.

It's right around 100.  We have a bunch of dummy files that are used to help find errors, etc. The next time I work on getting more statistics computation and reporting set up, I'd like to do something to flag those so that aren't listed in rankings, included in averages, etc.
Title: Re: Project Statistics
Post by: yakra on February 14, 2016, 12:16:34 pm
It's right around 100.  We have a bunch of dummy files that are used to help find errors, etc. The next time I work on getting more statistics computation and reporting set up, I'd like to do something to flag those so that aren't listed in rankings, included in averages, etc.
On a related note, there are still some vestigial log files (yaxtest-ma138.log, yaxtest-ma79.log, yaxtest-us6.log) for dummy lists that I deleted. They're in the /logs directory but not /devlogs. (Maybe they predate the creation of devlogs...) Might be a good idea to clean up that directory / those directories, and/or automate a cleanup / rebuild-from-scratch as part of the site update process.
Title: Re: Project Statistics
Post by: michih on February 14, 2016, 12:27:12 pm
^^ These log files must be deleted manually (by Jim). There are also michih2.log files ;).
Title: Re: Project Statistics
Post by: Jim on February 14, 2016, 03:28:11 pm
It's right around 100.  We have a bunch of dummy files that are used to help find errors, etc. The next time I work on getting more statistics computation and reporting set up, I'd like to do something to flag those so that aren't listed in rankings, included in averages, etc.
On a related note, there are still some vestigial log files (yaxtest-ma138.log, yaxtest-ma79.log, yaxtest-us6.log) for dummy lists that I deleted. They're in the /logs directory but not /devlogs. (Maybe they predate the creation of devlogs...) Might be a good idea to clean up that directory / those directories, and/or automate a cleanup / rebuild-from-scratch as part of the site update process.

For now, I've done a quick cleanup.
Title: Re: Project Statistics
Post by: Thing342 on February 15, 2016, 11:08:14 am
Furthermore, the website now contains 40956 lines of code, with 2,488 being standard HTML/PHP stuff. Most of the other stuff is split among the SVG shield definitions and styling files.
Title: Re: Project Statistics
Post by: yakra on February 15, 2016, 01:06:07 pm
Furthermore, the website now contains 40956 lines of code, with 2,488 being standard HTML/PHP stuff. Most of it is split among the SVG shield definitions and styling files.
What are the other 38,468?
Title: Re: Project Statistics
Post by: Thing342 on February 15, 2016, 01:51:58 pm
Furthermore, the website now contains 40956 lines of code, with 2,488 being standard HTML/PHP stuff. Most of it is split among the SVG shield definitions and styling files.
What are the other 38,468?
Mistyped my post. Most of the rest of the code is in SVG shield definitions, CSS files, and the WPT editor (which is written in JS)
Title: Re: Project Statistics
Post by: Jim on February 20, 2016, 06:15:22 pm
There are currently 404 .wpt files that do not have entries in .csv files.  Nothing wrong with that, as its perfectly reasonable to commit partial work on wpt files before they're ready for a csv file that will put them into the system in devel mode. 

But the fact that "404" were "not found" grabbed my attention.
Title: Re: Project Statistics
Post by: mapcat on February 20, 2016, 07:27:00 pm
There are currently 404 .wpt files that do not have entries in .csv files.  Nothing wrong with that, as its perfectly reasonable to commit partial work on wpt files before they're ready for a csv file that will put them into the system in devel mode.

Where can we see a list of those? I'll check to see if I forgot any.

Quote
But the fact that "404" were "not found" grabbed my attention.
;D
Title: Re: Project Statistics
Post by: Jim on February 20, 2016, 11:09:20 pm
There are currently 404 .wpt files that do not have entries in .csv files.  Nothing wrong with that, as its perfectly reasonable to commit partial work on wpt files before they're ready for a csv file that will put them into the system in devel mode.

Where can we see a list of those? I'll check to see if I forgot any.

http://tm.teresco.org/logs/unprocessedwpts.log (http://tm.teresco.org/logs/unprocessedwpts.log)

Some of these belong, as they are part of not-yet-in-devel systems or (like some usava) are copies for routes that will later be moved in from other systems.  But there are quite a few that don't need to stay.  I'd consider it a low priority cleanup, but one worth doing when time permits.
Title: Re: Project Statistics
Post by: froggie on February 21, 2016, 07:21:12 am
The following WPTs can be deleted.  They have been "turned back" (MnDOT-speak for decommissioned):

hwy_data/MN/usamn/mn.mn290.wpt
hwy_data/MN/usamn/mn.mn293.wpt
hwy_data/MN/usamn/mn.mn294.wpt
hwy_data/MN/usamn/mn.mn295.wpt
hwy_data/MN/usamn/mn.mn297.wpt
hwy_data/MN/usamn/mn.mn333.wpt
hwy_data/MN/usamn/mn.mn361.wpt
hwy_data/MN/usamn/mn.mn801.wpt
hwy_data/MN/usamn/mn.mn860.wpt


I'll have to look back and see why Tim deactivated MN 309.  Will also have to see why the leg of MN 23 through Wisconsin is on the "unprocessed list".
Title: Re: Project Statistics
Post by: si404 on February 21, 2016, 08:34:55 am
Will also have to see why the leg of MN 23 through Wisconsin is on the "unprocessed list".
It's in the wrong folder (there's one in the right folder that is processed) - MN/usamn rather than WI/usamn.

I've made a pull request deleting the ones you listed, some in my regions that are there for no reason, and a handful of wrong folder files (checking that there were right folder equivalents)
Title: Re: Project Statistics
Post by: Bickendan on February 21, 2016, 03:57:05 pm
The yt.bc097s need to be checked -- I think they're appearing correctly in the BC directory, so the ones in the YT directory might be superfluous.
That said, I know that bc.bc097con isn't showing on the map.
Title: Re: Project Statistics
Post by: si404 on February 21, 2016, 04:23:35 pm
The yt.bc097s need to be checked -- I think they're appearing correctly in the BC directory, so the ones in the YT directory might be superfluous.
Other way around. And dealt with.
Quote
That said, I know that bc.bc097con isn't showing on the map.
It is for me.
Title: Re: Project Statistics
Post by: oscar on February 21, 2016, 11:41:34 pm
The Alaska Highway zigzags along the YT/BC border. It's YT 1 for the part YT maintains, which includes one segment in BC and two in YT, and BC 97 for the part that province maintains, which includes three segments in YT and four in BC.

See http://cmap.m-plex.com/hb/selecthwys.php?sys=cansph&rg=all&gr=p#r and http://cmap.m-plex.com/hb/selecthwys.php?sys=canyt&rg=all&gr=p#r to confirm what belongs where (I edited some files from what was in CHM, but didn't move or rename any).

All the BC 97 segments in YT, and YT 1 segment in BC, seem to be where they belong in TM.
Title: Re: Project Statistics
Post by: rickmastfan67 on February 24, 2016, 03:12:47 am
These files can be axed:
hwy_data/SC/usaib/sc.i073futmyr.wpt
hwy_data/SC/usaib/sc.i074futmyr.wpt
hwy_data/SC/usaib/sc.i526futcha.wpt

Seems they somehow got duplicated into the wrong folder as they are already in the 'hwy_data/SC/usaif/' folder, which is the correct folder for them.

As for the following file, it can be safely deleted since the route was decommissioned a few years ago.  No idea why Tim didn't delete the file, and thus, got erroneously uploaded to TM.
hwy_data/SC/usausb/sc.us021busroc.wpt
Quote
June 2014
(USA) South Carolina US 21 Business (Rock Hill): Deleted route.

https://github.com/TravelMapping/HighwayData/pull/448
Title: Re: Project Statistics
Post by: Bickendan on February 25, 2016, 10:49:55 pm
The Alaska Highway zigzags along the YT/BC border. It's YT 1 for the part YT maintains, which includes one segment in BC and two in YT, and BC 97 for the part that province maintains, which includes three segments in YT and four in BC.

See http://cmap.m-plex.com/hb/selecthwys.php?sys=cansph&rg=all&gr=p#r and http://cmap.m-plex.com/hb/selecthwys.php?sys=canyt&rg=all&gr=p#r to confirm what belongs where (I edited some files from what was in CHM, but didn't move or rename any).

All the BC 97 segments in YT, and YT 1 segment in BC, seem to be where they belong in TM.
NT 5 also border skips between NWT and Alberta, if memory serves.
Title: Re: Project Statistics
Post by: Jim on March 28, 2016, 11:24:03 pm
With Oscar's updates today, we are not showing any more locations where 8 or more points are colocated that have points from placeholder files anymore.  So that's good.  Our new (and I expect valid) current record for most routes at a given point is now 10, which happens in 3 places: Public Square in Cleveland, the Mississippi River bridge at Memphis that carries 5 routes across the AR/TN border, and what appears to be a similar situation to that where 5 routes cross concurrently between Kazakhstan and Uzbekistan.

Here are the complete colocation counts from tonight's site update:

Waypoint colocation counts:
220105 are each occupied by  1 waypoints.
 82534 are each occupied by  2 waypoints.
 17524 are each occupied by  3 waypoints.
  3873 are each occupied by  4 waypoints.
  1013 are each occupied by  5 waypoints.
   211 are each occupied by  6 waypoints.
    55 are each occupied by  7 waypoints.
    12 are each occupied by  8 waypoints.
     7 are each occupied by  9 waypoints.
     3 are each occupied by 10 waypoints.
Title: Re: Project Statistics
Post by: si404 on March 29, 2016, 10:00:30 am
and what appears to be a similar situation to that where 5 routes cross concurrently between Kazakhstan and Uzbekistan.
Actually, as Kazakhstan renumbered it, it's 4 concurrent routes (AH5, AH62, E40 and E123), the old Soviet M39 (Uzbekistan only) and the Kazakh A2.

Public Square in Cleveland has: US6, US20, US42, US322, US422, OH3, OH8, OH14, OH43 and OH87 (all but the first two terminating), giving an average of 3 concurrent routes on each of the four routes we map.

And the Mississippi River Bridge is: I-55, US61, US64, US70 and US79
Title: Re: Project Statistics
Post by: si404 on April 03, 2016, 03:57:56 am
With last nights update you can now map travels from the Atlantic to the Pacific across Eurasia in preview systems, as well as travel across the two most populated countries in the world. http://tm.teresco.org/user/system.php?u=si404&sys=asiah
Title: Re: Project Statistics
Post by: Jim on April 17, 2016, 09:00:10 pm
From the update currently in progress:

Code: [Select]
Processed 192 highway systems.
Processed 21738 routes with a total of 480738 points and 459000 segments.
Title: Re: Project Statistics
Post by: Markkos1992 on May 07, 2016, 10:43:38 am
I would not say this is a huge issue but looking at my stats (http://tm.teresco.org/user/?u=markkos1992) I saw this:

Stats by Region
Pennsylvania-Percent Clinched 11.3% (only showing one decimal place)

Stats by System (always showing two decimal places, even showing 0.00%)
US Interstate Highways-Percent Clinched 10.70%
US Future Interstate Highways 7.60%

Basically, do we want the statistics to be consistent to two decimal places, 3 significant figures, etc. or is this such a non-issue to where I am making an issue out of nothing?
I also snipped a copy of it for myself in case I send in another update.

-Mark
Title: Re: Project Statistics
Post by: Jim on May 29, 2016, 04:02:11 pm
I would not say this is a huge issue but looking at my stats (http://tm.teresco.org/user/?u=markkos1992) I saw this:

Stats by Region
Pennsylvania-Percent Clinched 11.3% (only showing one decimal place)

Stats by System (always showing two decimal places, even showing 0.00%)
US Interstate Highways-Percent Clinched 10.70%
US Future Interstate Highways 7.60%

Basically, do we want the statistics to be consistent to two decimal places, 3 significant figures, etc. or is this such a non-issue to where I am making an issue out of nothing?
I also snipped a copy of it for myself in case I send in another update.

-Mark

Am I reading correctly that the issue here is that there's a trailing 0 on the percentages in systems but not in regions? If so, I just fixed it.
Title: Re: Project Statistics
Post by: Jim on May 29, 2016, 04:05:54 pm
Our data has grown since I last reported this about 6 weeks ago:

Code: [Select]
Processed 201 highway systems.
Processed 23612 routes with a total of 501626 points and 478014 segments.
Title: Re: Project Statistics
Post by: Markkos1992 on May 29, 2016, 06:26:25 pm
I would not say this is a huge issue but looking at my stats (http://tm.teresco.org/user/?u=markkos1992) I saw this:

Stats by Region
Pennsylvania-Percent Clinched 11.3% (only showing one decimal place)

Stats by System (always showing two decimal places, even showing 0.00%)
US Interstate Highways-Percent Clinched 10.70%
US Future Interstate Highways 7.60%

Basically, do we want the statistics to be consistent to two decimal places, 3 significant figures, etc. or is this such a non-issue to where I am making an issue out of nothing?
I also snipped a copy of it for myself in case I send in another update.

-Mark

Am I reading correctly that the issue here is that there's a trailing 0 on the percentages in systems but not in regions? If so, I just fixed it.

Yes, that was basically my point.
Title: Re: Project Statistics
Post by: Jim on May 31, 2016, 04:14:57 pm
A good statistic: there are currently 0 non-FP datacheck errors being reported for active systems.
Title: Re: Project Statistics
Post by: Jim on June 17, 2016, 08:30:35 am
As some of you are aware, I use our project's data to create graphs (the mathematical/data structure with vertices and edges) that I use in academic projects.  My efforts this week have been to generate those within the Python site update program rather than as a post-processing step, and I've made a lot of progress.  Anyway, I now have a graph of all of our active and preview that has 329,559 vertices and 357,536 edges.  Each vertex represents one or more colocated waypoints (the colocated waypoints of intersecting or concurrent routes are collapsed to a single vertex) and each edge represents a pair of waypoints that are connected by one or more routes.  Again, concurrent routes are represented by a single edge.  By comparison, when I last generated these graphs a few years ago from CHM data, there were 263,705 vertices and 288,298 edges.

I've also been able to generate graphs for each region, and the following lists each region that has at least one active or preview route in TM with the number of vertices and number of edges in that region's graph.  The variety of sizes here is one of the great values of this data to my academic project.  Students can use the small graphs for initial implementation and testing, then move on to larger graphs for more extensive testing and empirical analysis of algorithm complexity.

Code: [Select]
AB (2812,2932)
ABW (27,36)
AFG (686,686)
AK (1464,1460)
AL (3075,3170)
ALA (63,59)
ALB (617,616)
AND (48,46)
AR (1991,2014)
ARM (508,515)
AUT (971,977)
AZ (2139,2197)
AZE (440,438)
BC (4443,4485)
BEL (986,1009)
BGD (323,323)
BGR (940,967)
BIH (306,303)
BLR (665,671)
BRB (86,105)
BRN (44,42)
BTN (167,166)
CA (2648,2710)
CHE (735,736)
CHN-AH (389,393)
CHN-BJ (229,232)
CHN-CQ (396,403)
CHN-FJ (546,554)
CHN-GD (691,703)
CHN-GS (521,517)
CHN-GX (435,441)
CHN-GZ (500,502)
CHN-HA (454,459)
CHN-HB (566,572)
CHN-HE (630,632)
CHN-HI (100,100)
CHN-HN (543,546)
CHN-HL (571,570)
CHN-JL (346,348)
CHN-JS (432,440)
CHN-JX (469,472)
CHN-LN (577,586)
CHN-NM (665,662)
CHN-NX (161,162)
CHN-QH (399,398)
CHN-SC (662,667)
CHN-SD (536,548)
CHN-SH (111,111)
CHN-SN (843,856)
CHN-SX (439,443)
CHN-TJ (92,91)
CHN-XJ (779,777)
CHN-XZ (324,323)
CHN-YN (812,808)
CHN-ZJ (489,498)
CO (3210,3435)
CRM (117,116)
CT (1942,2416)
CYP (290,303)
CZE (984,990)
DC (63,58)
DE (652,650)
DEU (4377,4318)
DNK (1183,1263)
ENG (12969,15611)
ESP (5769,5807)
EST (500,510)
FIN (4173,4298)
FL (2563,2706)
FRA (6449,6609)
FRH (198,210)
GA (3158,3370)
GEO (381,384)
GLP (115,121)
GRC (1215,1210)
GU (124,148)
GUF (98,98)
HI (554,577)
HKG (190,201)
HRV (439,437)
HUN (590,595)
IA (3429,3759)
ID (2029,2104)
IDN (254,250)
IL (4439,5218)
IMN (141,169)
IN (3207,3853)
IND-AP (192,190)
IND-AS (49,48)
IND-BR (97,95)
IND-CT (49,48)
IND-DL (33,30)
IND-GJ (14,13)
IND-HR (60,56)
IND-JH (38,36)
IND-KA (163,162)
IND-MH (346,344)
IND-ML (37,36)
IND-MN (45,44)
IND-MP (195,192)
IND-NL (31,30)
IND-OR (149,147)
IND-PB (56,54)
IND-RJ (22,19)
IND-TG (115,112)
IND-TN (173,172)
IND-UP (189,185)
IND-UT (15,14)
IND-WB (133,131)
IRL (1647,1707)
IRN (1862,1863)
ISR (110,109)
ITA (2983,2976)
JAM (232,238)
JEY (49,53)
KAZ (2280,2289)
KGZ (361,359)
KHM (250,249)
KOR (1087,1124)
KS (3632,3932)
KY (13272,16963)
LA (1430,1503)
LAO (507,506)
LKA (115,113)
LTU (423,436)
LUX (841,925)
LVA (447,455)
MA (2280,2762)
MAF (7,6)
MAR (287,283)
MB (216,217)
MD (3681,3284)
MDA (351,353)
ME (3919,4296)
MEX-BC (69,67)
MEX-BCS (7,6)
MEX-CHIH (81,73)
MEX-CHIS (47,43)
MEX-COAH (25,20)
MEX-COL (16,14)
MEX-DF (21,18)
MEX-DGO (72,70)
MEX-GRO (71,65)
MEX-GTO (38,35)
MEX-HGO (46,36)
MEX-JAL (83,80)
MEX-MICH (100,93)
MEX-MOR (46,41)
MEX-NAY (47,43)
MEX-NL (48,43)
MEX-OAX (30,28)
MEX-PUE (109,95)
MEX-QRO (26,24)
MEX-QROO (6,5)
MEX-SIN (79,74)
MEX-SLP (48,43)
MEX-SON (59,56)
MEX-TAB (5,4)
MEX-TAM (12,10)
MEX-TLAX (34,25)
MEX-VER (100,91)
MEX-YUC (11,10)
MEX-ZAC (22,19)
MKD (234,235)
MI (3950,4270)
MLT (173,197)
MMR (580,578)
MN (4910,5320)
MNE (353,356)
MO (6466,7072)
MP (190,237)
MS (1705,1738)
MT (4115,4320)
MTQ (85,91)
MYS (783,789)
MYT (42,40)
NB (2840,3077)
NC (5964,7130)
NCL (157,156)
ND (1936,2100)
NE (3415,3758)
NH (2400,2664)
NIR (1012,1121)
NJ (2154,2385)
NL (265,264)
NLD (1343,1395)
NM (3452,3750)
NOR (4263,4291)
NPL (306,305)
NS (1711,1861)
NT (543,539)
NV (1798,1833)
NY (8110,9261)
NZL (112,105)
OH (11088,12932)
OK (3924,4468)
ON (3931,3999)
OR (4407,4584)
PA (9140,9123)
PAK (929,932)
PE (1114,1507)
PHL (92,89)
POL (1457,1458)
PR (241,240)
PRK (145,142)
PRT (1094,1108)
PYF (237,242)
QC (995,982)
REU (122,128)
RI (539,687)
RKS (191,195)
ROU (4571,4775)
RUS (5520,5526)
SC (3800,4763)
SCT (3995,4337)
SD (2048,2235)
SGP (117,124)
SK (264,260)
SPM (12,10)
SRB (466,461)
SVK (487,489)
SVN (553,562)
SWE (2203,2208)
THA (948,952)
TJK (594,597)
TKM (406,404)
TN (2436,2615)
TUN (64,61)
TUR (2203,2185)
TWN (259,263)
TX (13333,15049)
UKR (1682,1700)
UT (2423,2534)
UZB (638,642)
VA (4963,5812)
VI (237,325)
VNM (621,620)
VT (1367,1525)
WA (3315,3514)
WI (4881,5533)
WLF (42,48)
WLS (1682,1836)
WV (3234,3382)
WY (2351,2466)
YT (1186,1181)
Title: Re: Project Statistics
Post by: Jim on July 04, 2016, 11:29:13 pm
Today's addition of deub3 as a preview system moved TM to over 800,000 miles of clinchable highways in the active and preview systems taken together.  Thanks to all who have contributed and continue to contribute to our highway data expansion!
Title: Re: Project Statistics
Post by: mapcat on July 04, 2016, 11:38:16 pm
Nice! Any goals in mind for end-of-year?
Title: Re: Project Statistics
Post by: Jim on July 31, 2016, 12:20:13 am
We've had some new users submit list files this week, bringing us to 136 list files loaded into the update currently in progress.  Over 100 of those have been created or updated in the last 6 months, so I'd consider most to be active users.

Over 24,000 .wpt files are now processed as part of a site update.

The SQL file that repopulates the database on each site update is now over 4,000,000 lines long.
Title: Re: Project Statistics
Post by: Jim on August 08, 2016, 12:12:23 pm
For a paper I'm writing about the graphs I generate from the TM data, I wanted to see the distribution of edge lengths in the "tm-master.tmg" graph.  I thought an exponential distribution would be most useful.  Units are miles:

Code: [Select]
Edge length distribution (exponential):
0.0 <= len < 0.125: 4308
0.125 <= len < 0.25: 9289
0.25 <= len < 0.5: 23572
0.5 <= len < 1.0: 50177
1.0 <= len < 2.0: 73762
2.0 <= len < 4.0: 71648
4.0 <= len < 8.0: 47886
8.0 <= len < 16.0: 11255
16.0 <= len < 32.0: 1760
32.0 <= len < 64.0: 333
64.0 <= len < 128.0: 44
128.0 <= len < 256.0: 6

This is the graph that has hidden waypoints collapsed, so the lengths are essentially lengths between visible points in our .wpt files.

I was a bit surprised that we had 50 places where it's over 64 miles between visible points.  Here they are:

Code: [Select]
E123/AH62@ImeKom to E123/AH62@Syu via E123,AH62 length 211.0824
AH4@Qah to AH4@X208 via AH4 length 150.6198
AH42@ChaRd to AH42@YiLoc via AH42 length 150.4283
AH32@BayNuur to AH32@A22_W via AH32 length 148.6031
AH42@S308 to AH42@Tan via AH42 length 142.8158
E003@Min to E003@R180_W via E003 length 131.0283
E003@Bar to E003@Dar via E003 length 113.3032
AH32@Bay_W to AH32@BayOvoo via AH32 length 109.4872
G0613@Yen to G0613@G214_Zhe via G0613 length 107.4038
AH2@Dal_E to AH2@AhmWal via AH2 length 106.5611
BC97@BucRivPP to BC97@Rd254 via BC97 length 105.9764
G3011/AH42 to AH42@S308 via AH42 length 102.0576
AH78@Rav_N to AH78@Nay via AH78 length 102.0325
AH2@Fah to AH2@Nos via AH2 length 97.6226
AH32@Urg to AH32@Durv via AH32 length 91.2911
G50@S233 to G50@G318_Lib via G50 length 91.0735
AH3@Ula to AH3@Urg via AH3 length 90.5063
AH75@R92_E to AH75@Kha via AH75 length 88.5040
AH70@R36_E to AH70@Jan via AH70 length 87.5963
AH32@G45/G1202&G12@G45/G1202&G45@G12/G1202&G1202@G12/G45 to G45@X147 via G45 length 84.8840
AH4@Tol_E to AH4@A17&AH32@A3 via AH4 length 84.4882
E40Nuk/AH63@Jas to E40Nuk@Kar&AH63@Kar_W via E40Nuk,AH63 length 84.4761
BC97/BC97Con@BC/YT to BC97@LiaRivPP via BC97 length 82.3130
G65_S/G78_E to AH1@G65_N&G65@G80_E&G80@G65_N via G65 length 78.7951
AH32@Durv to AH32@Ald via AH32 length 77.1011
AH1@AFG/IRN to AH1@JamiRd via AH1 length 76.7270
AH77@Awb to AH77@Puni via AH77 length 76.1823
AH2@Taf to AH2@NokKun via AH2 length 75.2716
AH4@Tas|CHN-XJ to AH4@CHN/PAK via AH4 length 74.9304
AH4@Alt to AH4@Ton via AH4 length 74.4814
AH3@Air to AH3@Sai_N via AH3 length 73.6239
AH51@Dar to AH51@ZhobWanaRd via AH51 length 73.4893
G5012@S2/S20 to G65/G5012 via G5012 length 72.1187
G56_E/G76_E to G56(621)/G4215 via G56 length 72.0961
BC37@NinPP to BC37/BC37A via BC37 length 72.0237
AH42@GonExpy&G6Hai@G0613&G0613@G6 to AH42/G6Hai@G109_Das via AH42,G6Hai length 71.5764
AH1@FarRd to AH1/AH71 via AH1 length 71.0943
G35@HuaRd to G35/G72 via G35 length 70.5915
BC37@CasRd to BC37@BouSt via BC37 length 70.3705
AH70@R36_W to AH70@ToR44 via AH70 length 70.0952
AH6@X904 to AH6@Bay_W via AH6 length 69.4362
AH71@Kha_N to AH71@FarRd via AH71 length 69.2148
G42@S312_Wudu to G42@HB/CQ via G42 length 68.9330
E6Kir@Rv92_E&Rv92@E6_E to E6Kir@E75_S&E75@E6_W via E6Kir length 68.2212
AH2@NokKun to AH2@Yak via AH2 length 68.1582
G3012Yar@G315_YenS to G3012Yar@SanExpy via G3012Yar length 66.6719
M41@Karo to M41@Ran via M41 length 66.6389
NT3@ChanLakeTP to NT3@MosCrkTr via NT3 length 65.7823
AH2@R82_N&AH70@R82 to AH2@Anar_W&AH70@Anar via AH2,AH70 length 64.9629
NT1@WalCrkTr to NT1/NT3 via NT1 length 64.0154
Title: Re: Project Statistics
Post by: oscar on August 08, 2016, 02:55:47 pm
I was a bit surprised that we had 50 places where it's over 64 miles between visible points.  Here they are:

Code: [Select]
E123/AH62@ImeKom to E123/AH62@Syu via E123,AH62 length 211.0824
AH4@Qah to AH4@X208 via AH4 length 150.6198
AH42@ChaRd to AH42@YiLoc via AH42 length 150.4283
AH32@BayNuur to AH32@A22_W via AH32 length 148.6031
AH42@S308 to AH42@Tan via AH42 length 142.8158
E003@Min to E003@R180_W via E003 length 131.0283
E003@Bar to E003@Dar via E003 length 113.3032
AH32@Bay_W to AH32@BayOvoo via AH32 length 109.4872
G0613@Yen to G0613@G214_Zhe via G0613 length 107.4038
AH2@Dal_E to AH2@AhmWal via AH2 length 106.5611
BC97@BucRivPP to BC97@Rd254 via BC97 length 105.9764
G3011/AH42 to AH42@S308 via AH42 length 102.0576
AH78@Rav_N to AH78@Nay via AH78 length 102.0325
AH2@Fah to AH2@Nos via AH2 length 97.6226
AH32@Urg to AH32@Durv via AH32 length 91.2911
G50@S233 to G50@G318_Lib via G50 length 91.0735
AH3@Ula to AH3@Urg via AH3 length 90.5063
AH75@R92_E to AH75@Kha via AH75 length 88.5040
AH70@R36_E to AH70@Jan via AH70 length 87.5963
AH32@G45/G1202&G12@G45/G1202&G45@G12/G1202&G1202@G12/G45 to G45@X147 via G45 length 84.8840
AH4@Tol_E to AH4@A17&AH32@A3 via AH4 length 84.4882
E40Nuk/AH63@Jas to E40Nuk@Kar&AH63@Kar_W via E40Nuk,AH63 length 84.4761
BC97/BC97Con@BC/YT to BC97@LiaRivPP via BC97 length 82.3130
G65_S/G78_E to AH1@G65_N&G65@G80_E&G80@G65_N via G65 length 78.7951
AH32@Durv to AH32@Ald via AH32 length 77.1011
AH1@AFG/IRN to AH1@JamiRd via AH1 length 76.7270
AH77@Awb to AH77@Puni via AH77 length 76.1823
AH2@Taf to AH2@NokKun via AH2 length 75.2716
AH4@Tas|CHN-XJ to AH4@CHN/PAK via AH4 length 74.9304
AH4@Alt to AH4@Ton via AH4 length 74.4814
AH3@Air to AH3@Sai_N via AH3 length 73.6239
AH51@Dar to AH51@ZhobWanaRd via AH51 length 73.4893
G5012@S2/S20 to G65/G5012 via G5012 length 72.1187
G56_E/G76_E to G56(621)/G4215 via G56 length 72.0961
BC37@NinPP to BC37/BC37A via BC37 length 72.0237
AH42@GonExpy&G6Hai@G0613&G0613@G6 to AH42/G6Hai@G109_Das via AH42,G6Hai length 71.5764
AH1@FarRd to AH1/AH71 via AH1 length 71.0943
G35@HuaRd to G35/G72 via G35 length 70.5915
BC37@CasRd to BC37@BouSt via BC37 length 70.3705
AH70@R36_W to AH70@ToR44 via AH70 length 70.0952
AH6@X904 to AH6@Bay_W via AH6 length 69.4362
AH71@Kha_N to AH71@FarRd via AH71 length 69.2148
G42@S312_Wudu to G42@HB/CQ via G42 length 68.9330
E6Kir@Rv92_E&Rv92@E6_E to E6Kir@E75_S&E75@E6_W via E6Kir length 68.2212
AH2@NokKun to AH2@Yak via AH2 length 68.1582
G3012Yar@G315_YenS to G3012Yar@SanExpy via G3012Yar length 66.6719
M41@Karo to M41@Ran via M41 length 66.6389
NT3@ChanLakeTP to NT3@MosCrkTr via NT3 length 65.7823
AH2@R82_N&AH70@R82 to AH2@Anar_W&AH70@Anar via AH2,AH70 length 64.9629
NT1@WalCrkTr to NT1/NT3 via NT1 length 64.0154

I don't know about the others, but the ones for NT, and at least one of the three for BC, there really are no intersections with named roads (or even named hiking trails, as with the two NT entries) for those segments of Arctic highways.
Title: Re: Project Statistics
Post by: Jim on August 08, 2016, 05:28:39 pm
I don't know about the others, but the ones for NT, and at least one of the three for BC, there really are no intersections with named roads (or even named hiking trails, as with the two NT entries) for those segments of Arctic highways.

That was my assumption.  I have no problem with these long stretches existing where they make sense.
Title: Re: Project Statistics
Post by: Jim on December 21, 2016, 12:19:29 pm
We are under 25 commits to the HighwayData repository from reaching 10,000.  I hope the 10,000th will be a good one!
Title: Re: Project Statistics
Post by: michih on December 21, 2016, 12:43:46 pm
I hope the 10,000th will be a good one!

How many commits out of 9,975 have been bad? ;)
Title: Re: Project Statistics
Post by: yakra on December 21, 2016, 02:19:31 pm
How many commits out of 9,975 have been bad? ;)
I know I've done at least a couple that made zero changes to zero files...
Title: Re: Project Statistics
Post by: Jim on January 31, 2017, 10:16:50 pm
Two new users submitted files today, making tonight's site update the first that will ingest list files from 150 users.
Title: Re: Project Statistics
Post by: Jim on February 24, 2017, 11:59:39 pm
We have passed 900,000 miles of active+preview routes.  Well done all!  How long before we can get to 1 million?
Title: Re: Project Statistics
Post by: michih on February 25, 2017, 03:10:14 am
It took almost 8 months from the 800,000 miles to the 900,000 miles milestone. I guess we might reach 1m by the end of the year.

btw: both milestones were "caused" by me :D
Title: Re: Project Statistics
Post by: yakra on February 28, 2017, 01:31:58 am
I'm almost tempted to say we're at one Irv, but nay... it would be nice to call an Irv a nice round number, but it isn't a constant unit of measure. Rather, one Irv is the number of miles on Irv Gordon's 1966 1800S. Which is somewhere over 3 million. Once TM has more mileage than Irv -- now THAT will be a milestone!
Title: Re: Project Statistics
Post by: Jim on May 30, 2017, 10:53:20 pm
We've exceeded 20,000 routes in active systems.
Title: Re: Project Statistics
Post by: michih on June 17, 2017, 06:40:03 am
We've exceeded 30,000 routes in active+preview systems.
Title: Re: Project Statistics
Post by: michih on June 18, 2017, 02:49:03 am
We have 7 travelers with more than 100,000mi in active+preview now. Congrats to froggie :)

The candidates to join the club next are okroads, mapmikey and mefailenglish which have a little bit more than 90,000mi now.

I'll only exceed 50,000mi soon.
Title: Re: Project Statistics
Post by: froggie on June 18, 2017, 10:30:20 pm
Hit mine just in active only.  Finally updated some of my lists (namely Virginia...still only partway through that).
Title: Re: Project Statistics
Post by: bejacob on June 19, 2017, 10:17:35 am
I'm looking to hit 100,000 miles in active systems this year. Already there in active +preview. Not sure where I'll be driving yet. I have some around Omaha in August. I keep planning to "sneak"  ;) across the state line into Indiana to clinch my last couple segments of I-69 between Indianapolis and Fort Wayne. I've mainly been collecting counties west of the Mississippi this year, so travels closer to home have been minimal. On the plus side, I'll be picking up a bunch of mileage in Wales at the end of summer.

I think I can pick up another 1,800 miles in active systems this year. We'll see. It's good to have goals.  :)
Title: Re: Project Statistics
Post by: mapcat on June 19, 2017, 12:27:37 pm
I'm looking to hit 100,000 miles in active systems this year. Already there in active +preview. Not sure where I'll be driving yet. I have some around Omaha in August. I keep planning to "sneak"  ;) across the state line into Indiana to clinch my last couple segments of I-69 between Indianapolis and Fort Wayne. I've mainly been collecting counties west of the Mississippi this year, so travels closer to home have been minimal. On the plus side, I'll be picking up a bunch of mileage in Wales at the end of summer.

I think I can pick up another 1,800 miles in active systems this year. We'll see. It's good to have goals.  :)

No interest in clinching usaoh? Cheapest way to 100,000.  :D  Or, in your case, 108,000.
Title: Re: Project Statistics
Post by: yakra on June 20, 2017, 03:28:30 am
I might go to New Hampshire again some day...  ::)

On a more serious note, one of these days I'm going to have to pick off some of the last of the low-hanging fruit in York/Cumberland/Oxford counties. I know that @deathtopumpkins has more USAME mileage than me... Just how much, I'm not certain, as there are a few broken lines in his .list file for recently updated routes. And, well -- this simply will not do.  8)
Title: Re: Project Statistics
Post by: bejacob on June 20, 2017, 08:34:17 am
I'm looking to hit 100,000 miles in active systems this year. Already there in active +preview. Not sure where I'll be driving yet. I have some around Omaha in August. I keep planning to "sneak"  ;) across the state line into Indiana to clinch my last couple segments of I-69 between Indianapolis and Fort Wayne. I've mainly been collecting counties west of the Mississippi this year, so travels closer to home have been minimal. On the plus side, I'll be picking up a bunch of mileage in Wales at the end of summer.

I think I can pick up another 1,800 miles in active systems this year. We'll see. It's good to have goals.  :)

No interest in clinching usaoh? Cheapest way to 100,000.  :D  Or, in your case, 108,000.

Interest, yes. Inclination, not at the moment.

I'm working on it from time to time. I've covered all the routes in Franklin county (where I live) and in all the adjacent counties with the exception of OH47 in Union county. I've even driven a fair bit of the counties that touch those surrounding counties.  I'll probably work on the remaining usaus routes in OH first picking up whichever usaoh routes I can in the process.

My travel priorities are
County seat visit always take precedence. In the last couple years, I've factored in highway clinching to my travels. They do tend to dovetail reasonably well. I've still got a ways to go on collecting counties http://www.mob-rule.com/user/bejacob (http://www.mob-rule.com/user/bejacob). I know many TM users understand. :D
 
Title: Re: Project Statistics
Post by: sipes23 on June 20, 2017, 10:51:26 pm
I might go to New Hampshire again some day...  ::)

On a more serious note, one of these days I'm going to have to pick off some of the last of the low-hanging fruit in York/Cumberland/Oxford counties. I know that @deathtopumpkins has more USAME mileage than me... Just how much, I'm not certain, as there are a few broken lines in his .list file for recently updated routes. And, well -- this simply will not do.  8)

It distresses me that I'm in 5th place in Maine. Of course, being in Wyoming isn't helping that situation. It also distresses me that I'm not in 1st place in Wyoming. I suspect that will be rectified by the end of the summer--unless Spui Ninja really racks up the miles.
Title: Re: Project Statistics
Post by: the_spui_ninja on June 24, 2017, 11:26:14 am
It distresses me that I'm in 5th place in Maine. Of course, being in Wyoming isn't helping that situation. It also distresses me that I'm not in 1st place in Wyoming. I suspect that will be rectified by the end of the summer--unless Spui Ninja really racks up the miles.

Come at me bro!  ;D

I guess it makes more sense for you to be 1st in WY since you live there; I only live REALLY REALLY close to WY (i.e. I can go for a run in WY at home even though I live in SD).
Title: Re: Project Statistics
Post by: Rothman on July 27, 2017, 02:14:41 pm
A tangential note looking at the 158 users that have clinched interstate mileage:

The state in which the highest number of users that have clinched some interstate mileage is Pennsylvania: 133.  Not surprising, but I could think of other states I might have guessed as well (Ohio, Illinois or Texas).

Puerto Rico has the lowest at 12.  Alaska's at 18.  Hawaii = 26.

Title: Re: Project Statistics
Post by: Jim on August 15, 2017, 10:54:09 pm
With a couple new preview systems we are now over 1 million clinchable miles!  Thanks to all who contribute.  That's an amazing number.

Have to say I really like seeing my usanp travels on my maps!
Title: Re: Project Statistics
Post by: Jim on September 29, 2017, 10:54:06 pm
With 2 new activations tonight, we are at 200 active systems!  Thanks to all who have made this possible.  It looks like we had 97 active systems when we brought over CHM data a few years ago.  I continue to be amazed by and very grateful to all of you who continue to expand and improve our highway data.
Title: Re: Project Statistics
Post by: michih on September 30, 2017, 03:41:43 am
The last 15 systems are from Si.
Title: Re: Project Statistics
Post by: si404 on September 30, 2017, 05:40:38 am
The last 15 systems are from Si.
Really? Certainly usatn, islth and swel weren't that long ago (swel was the 14th most recent by my count, islth the 15th, usatn the 16th). The last 13, sure!

I guess it helps to have had lots of small and simple systems ready and waiting for a binge of peer-review from you. Also, it's been a month since I peer-reviewed something, so I better get on that.

The system binge will dry up soon as our 'Tier 4' drive is nearly over. 2 Canadian Provinces, 5 US States and 1 US Territory on Preview, 1 Canadian Province, 4 US States and 1 US Territory not there yet. 5 European countries on Preview and 3 not there yet.

Sure there's a few other things (Europe Tier 5, things like New York Parkways, National Park Highways, etc), and there's always Asia, Africa and Australia, but we're slowly moving towards a point where the project is almost entirely maintenance and not much creation.
Title: Re: Project Statistics
Post by: michih on September 30, 2017, 05:51:19 am
The last 15 systems are from Si.
Really? Certainly usatn, islth and swel weren't that long ago (swel was the 14th most recent by my count, islth the 15th, usatn the 16th). The last 13, sure!

Ok, I've counted asiah 3 times because there are 3 system update entries for Pakistan, Iran and Afghanistan...
Title: Re: Project Statistics
Post by: Quidditch33 on October 02, 2017, 10:11:24 am
The state in which the highest number of users that have clinched some interstate mileage is Pennsylvania: 133.
I find it funny I've never even been near Pennsylvania. I should probably head east sometime...
Title: Re: Project Statistics
Post by: Jim on November 25, 2017, 10:43:15 pm
At the moment, we have exactly 23,000 routes in active systems.
Title: Re: Project Statistics
Post by: Jim on December 01, 2017, 10:13:33 pm
mapcat's list file pull request today was the 1000th pull request on the UserData repository.
Title: Re: Project Statistics
Post by: Jim on March 21, 2018, 09:48:59 pm
We have recently passed 40,000 routes in active and preview systems.
Title: Re: Project Statistics
Post by: Jim on April 03, 2018, 10:25:25 pm
We now have over 500,000 unique locations used as waypoints in some TM route.  503,967 at the moment, to be exact.
Title: Re: Project Statistics
Post by: froggie on April 04, 2018, 07:18:01 pm
I added a bunch when I finally updated my list for Tennessee...noted nobody's included several of the TN routes I've been on.
Title: Re: Project Statistics
Post by: michih on April 05, 2018, 05:20:01 pm
I think Jim refers to the  number of unique locations (second to last line) (http://tm.teresco.org/logs/siteupdate.log) in TM routes - not waypoints used by TM travelers.
Title: Re: Project Statistics
Post by: mapcat on May 26, 2018, 05:20:56 pm
Just noticed we have 200 users now.
Title: Re: Project Statistics
Post by: yakra on June 08, 2018, 01:36:09 am
What is the single longest, by mileage, root file in the project?
Can be in an active, preview, or even devel system. Nothing commented out, though.
Title: Re: Project Statistics
Post by: michih on June 08, 2018, 03:59:44 am
I think you've analyzed it and you want us to guess? I think it might be this: http://travelmapping.net/hb/index.php?u=michih&r=rus.ah030
Title: Re: Project Statistics
Post by: Jim on June 08, 2018, 07:40:32 am
The TM database knows, but I won't give the answer in case this is a trivia question instead of a request for this information.  The one @michih mentions is the 7th-longest.
Title: Re: Project Statistics
Post by: si404 on June 08, 2018, 07:49:09 am
The one @michih mentions is the 7th-longest.
Though it is the longest that is also an entire connected route.

There's 11 roots over 1500 miles (worked out manually).
Title: Re: Project Statistics
Post by: yakra on June 08, 2018, 12:27:11 pm
Not a trivia question. Request for info. :)
Title: Re: Project Statistics
Post by: Jim on June 08, 2018, 01:25:46 pm
Here's your top 10:

+------------+--------+-------+--------+--------+--------+--------------+---------+
| systemName | region | route | banner | abbrev | city   | root         | mileage |
+------------+--------+-------+--------+--------+--------+--------------+---------+
| asiah      | RUS    | AH6   |        | Irk    | Irkusk | rus.ah006irk | 2657.65 |
| eure       | RUS    | E30   |        |        |        | rus.e30      |  2066.9 |
| eure       | RUS    | E22   |        |        |        | rus.e22      | 1967.68 |
| asiah      | RUS    | AH8   |        |        |        | rus.ah008    | 1897.87 |
| eure       | RUS    | E105  |        |        |        | rus.e105     | 1833.21 |
| asiah      | RUS    | AH6   |        |        |        | rus.ah006    | 1799.98 |
| asiah      | RUS    | AH30  |        |        |        | rus.ah030    |  1716.3 |
| argrn      | ARG    | RN3   |        |        | (Main) | arg.rn003    | 1665.57 |
| asiah      | KAZ    | AH61  |        |        |        | kaz.ah061    | 1638.46 |
| asiah      | MNG    | AH32  |        |        |        | mng.ah032    | 1568.76 |
+------------+--------+-------+--------+--------+--------+--------------+---------+
Title: Re: Project Statistics
Post by: si404 on June 08, 2018, 02:01:35 pm
Anyone want to guess the 11th that is over 1500 miles?
Title: Re: Project Statistics
Post by: michih on June 08, 2018, 04:27:32 pm
No, but rus.ah006irk should be rus.ah006 and arg.rn040 (https://en.wikipedia.org/wiki/National_Route_40_(Argentina)) might soon beat them all (> 3,000mi) :D
Title: Re: Project Statistics
Post by: si404 on June 09, 2018, 02:55:50 pm
No, but rus.ah006irk should be rus.ah006
Why? Yes, the former is 857.67 miles (32.3%) longer than the latter, but it's clearly the case that people are much more likely to drive in European Russia than Siberia. As such, the European Russian bit is more major.

The 11th over 1500 miles is the AH4 in China (all in Xinjiang Uyghur Autonomous Region). Over half of that distance is freeway!
Title: Re: Project Statistics
Post by: yakra on June 10, 2018, 06:37:25 am
the former is 857.67 miles (32.3%) longer than the latter
Title: Re: Project Statistics
Post by: Bickendan on June 10, 2018, 02:26:17 pm
I find it amusing that BC 97 doesn't even make the list.
Title: Re: Project Statistics
Post by: Jim on June 10, 2018, 04:38:54 pm
I find it amusing that BC 97 doesn't even make the list.

Comes in at #18 but #1 in the western hemisphere.
Title: Re: Project Statistics
Post by: si404 on June 11, 2018, 10:42:51 am
Comes in at #18 but #1 in the western hemisphere.
Err, Argentina RN3?

I've heard some terrible definitions of 'Western Hemisphere' that exclude western Europe and western Africa (if you mean 'The Americas' then use it - it's shorter and far less arbitrary*!), but to exclude the southern hemisphere.  ::)


*a week ago I crossed the meridian twice and didn't notice until I'd done it - in Greenwich Park! The first was literally feet away from the observatory grounds and it wasn't marked and only when I got to the end of the path and saw that the other side of the fence was the courtyard with people taking photos of them with a leg either side of a metal plate running along the floor and beyond that London...
Title: Re: Project Statistics
Post by: Jim on June 14, 2018, 08:02:42 pm
We've recently blown past 20,000 commits to the HighwayData repository.
Title: Re: Project Statistics
Post by: yakra on June 15, 2018, 12:51:59 am
Northernmost point: NOR E69 End @ 71.166714°, 25.780427°
Westernmost point: WLF T1Fut Tol @ -14.251073°, -178.180518°
Easternmost point: NZL SH35 RanRd @ -37.795416°, 178.410419°
Southernmost point: ARG RN3Ush End_S @ -54.855220°, -68.576712°, having recently surpassed NZL SH1Wai End (-46.613277°, 168.357711°) by > 6 degrees.
Title: Re: Project Statistics
Post by: yakra on June 18, 2018, 12:21:14 am
There is only one shaping point in Washington DC.
https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/DC/usanp/dc.rockcrkpkwy.wpt#L9
Are there any regions with none?
Title: Re: Project Statistics
Post by: si404 on June 18, 2018, 03:44:17 am
Liechtenstein, Saint Martin and Saint Pierre and Miquelon have none. SPM has more than just the one route that's part of another system (LIE having part of cheh's H16, MAF having glpn's N7)

I've not bothered looking at places where all we have is one freeway route (eg Gabon).
Title: Re: Project Statistics
Post by: Jim on July 16, 2018, 07:55:32 am
We've added around 8 or 10 new users in the last week.  Easily the largest growth since the initial move from CHM.  Typically I'd see a new person once every couple weeks or so.
Title: Re: Project Statistics
Post by: michih on July 16, 2018, 12:46:58 pm
We have 216 users now. 16 new users have joined in the last 7 weeks.

Just noticed we have 200 users now.
Title: Re: Project Statistics
Post by: compdude787 on July 18, 2018, 01:56:20 pm
Probably has to do with the move to the travelmapping.net domain.
Title: Re: Project Statistics
Post by: Jim on August 21, 2018, 11:13:55 pm
I realized my list file now has 3784 lines, which got me wondering how many people have files that long.  Mine is 16th longest.   One user (vespertine) has over 8000 lines, two more are over 7000, two more over 6000, and 2 more over 5000.  94 of our 224 users have at least 1000 lines in their list files.
Title: Re: Project Statistics
Post by: froggie on August 22, 2018, 06:43:21 am
I'd be one of the over 6K....
Title: Re: Project Statistics
Post by: michih on August 22, 2018, 09:50:55 am
Mine is 16th longest.

You are 17th in total stats. I guess that the relation of total mileage and lines is more or less similar for all (oscar + mapcat are over 7k).
Title: Re: Project Statistics
Post by: Jim on August 22, 2018, 10:13:22 am
This reminds me of a very old exchange on CHM, soon after the expansion beyond Interstates meant more users had more lines in their files:

http://clinched.s2.bizhat.com/viewtopic.php?t=174

We have no coded limit on list file length in TM.
Title: Re: Project Statistics
Post by: Markkos1992 on August 22, 2018, 04:00:01 pm
I realized my list file now has 3784 lines, which got me wondering how many people have files that long.  Mine is 16th longest.   One user (vespertine) has over 8000 lines, two more are over 7000, two more over 6000, and 2 more over 5000.  94 of our 224 users have at least 1000 lines in their list files.

I should have over 1000 lines (991 right now) once I send in the next update to my list file.
Title: Re: Project Statistics
Post by: cl94 on August 22, 2018, 04:35:13 pm
I crossed 1,900 lines with the cross-country trip I just finished. Only added a net of ~105 lines, though, as I closed some gaps in OH and IL as part of it, making the net gain roughly 0 in those states. Next big trip will likely toss me over 2,000, but who knows when that will happen.

I know a "new" user (that most of us know) will likely be getting his account up and running this winter. I would not be shocked if he joins the 5,000+ club once he has everything in, possibly higher.
Title: Re: Project Statistics
Post by: si404 on August 23, 2018, 02:39:15 am
I guess that the relation of total mileage and lines is more or less similar for all (oscar + mapcat are over 7k).
Not really as something like

TX I-10 NM/TX TX/LA

is 1 line with nearly 900 miles for it, whereas my nearly 900 lines in England gets me less than 6000 miles.

If you've mostly done lengthy routes, and covered most of them, then your .list file is shorter for many more miles than someone who has mostly done short routes, or short bits of routes and so has lots of lines that contribute little to total mileage.
Title: Re: Project Statistics
Post by: bejacob on August 23, 2018, 08:15:29 am
I realized my list file now has 3784 lines, which got me wondering how many people have files that long.  Mine is 16th longest.   One user (vespertine) has over 8000 lines, two more are over 7000, two more over 6000, and 2 more over 5000.  94 of our 224 users have at least 1000 lines in their list files.

Currently 6776 lines. Never really paid much attention to the "lines." I always just looked at the mileage. I did notice that I have traveled over 75,000 segments as well. Also something I overlooked in the past.
Title: Re: Project Statistics
Post by: osu-lsu on August 23, 2018, 02:50:02 pm
Well, my log file shows 1215 lines. Where as the stats board shows I've traveled 1195 routes.
What's the difference (besides the math)?
Title: Re: Project Statistics
Post by: yakra on August 23, 2018, 03:06:53 pm
Sometimes one line credits you with multiple routes:
ME I-295 4 9
is good for some of US1 and a little ME26.

And sometimes multiple lines only serve one route:
ME I-295 20 22
ME I-295 28 31


Looks like in your case the latter outweigh the former.
Title: Re: Project Statistics
Post by: vdeane on August 25, 2018, 03:12:41 pm
Mine currently (well, it will as of the next update) has 1359 lines.

And sometimes multiple lines only serve one route:
ME I-295 20 22
ME I-295 28 31


Looks like in your case the latter outweigh the former.
Probably the same for me, since I include concurrencies where I know about them.
Title: Re: Project Statistics
Post by: froggie on September 02, 2018, 09:32:29 am
On the subject of lines, I took a trip yesterday that had the net effect of reducing the number of lines on my list by 13...basically filling gaps.
Title: Re: Project Statistics
Post by: michih on September 30, 2018, 02:27:39 am
More than 10,000 forum posts now (this is 10,009). And more then 100,000 page views per month.

http://forum.travelmapping.net/index.php?action=stats
Title: Re: Project Statistics
Post by: yakra on October 13, 2018, 02:42:19 am
The longest vertex label in any graph file, at 143 characters:

US129@US129/441BusWat_N&US129BusWat@US129_N&US441@US129/441BusWat_N&US441BusWat@US441_N&GA15@US129/441&GA24@US129/441BusWat_N&GA24BusWat@GA24_N

This is going to be very neato to look at in the HDX-lite (http://yakra.teresco.org/tmtools_demos/tmg2html/GA-region.tmg.html) and I shall surf it up posthaste! 8)
Title: Re: Project Statistics
Post by: michih on October 14, 2018, 08:47:45 am
With the next site update we'll have more than 25,000 routes for more than 800,000 miles in 213 active systems :)
Title: Re: Project Statistics
Post by: yakra on November 05, 2018, 04:21:33 pm
As of Nov  4 23:42 (https://github.com/TravelMapping/HighwayData/tree/a46d6d9b7ca2f2f452f7e3ebe7123e109e51ced2), the WaypointQuadtree contains 46678 total nodes.

No, wait. This number should be 1 + a multiple of 4. Trying again...
62237 total nodes.
46678 would have been the number of bottom-level nodes actually containing waypoints.
Title: Re: Project Statistics
Post by: yakra on November 06, 2018, 12:21:22 pm
Once DataProcessing#122 (https://github.com/TravelMapping/DataProcessing/pull/122) gets merged, the WaypointQuadtree would have (for that same revision of the HighwayData repo):
42725 total nodes, with 32044 bottom-level nodes containing waypoints.
That leaves 10681 refined nodes that contain no waypoints, but only 4 child nodes.

10681 * 2 = 21362 = the number of edges it would take to make a visual representation of the QuadTree in .tmg format. (+2 for W & E boundaries on the whole thing if you wish, = 21364.) That's a bit smaller than usai-system-simple.tmg.

Taking the simple route and not merging colocated vertices, that's 42724 or 42728 vertices, a bit smaller than ASI-continent-simple.tmg.
Title: Re: Project Statistics
Post by: yakra on November 07, 2018, 01:08:09 pm
Just for fun, I made a graph of the WaypointQuadtree:
http://yakra.teresco.org/tests/tmg/Quadtree/WaypointQuadtree-good.tmg
http://yakra.teresco.org/tests/tmg/Quadtree/WaypointQuadtree-good.tmg.html

https://github.com/TravelMapping/DataProcessing/pull/126/files
The WaypointQuadtree has been initialized all these years with the latitude and longitude bounds swapped. It hasn't broken anything, but just led to a sub-optimal distribution of child nodes.
After fixing it, we're down from 42757 to 35165 total nodes with the latest HighwayData.

How does it affect the time to process the total siteupdate.py time, skipping graphs?
Total run time: [394.3] -> [390.1]
Probably not a significant difference.

Edit: Another fun potential project:
What are the deepest-level, geographically smallest nodes, and how many of this size are there?
Of these, which contain the most waypoints? The most unique locations?

The smallest refined node I've found with a bit of eyeball scanning is near the Maughan Library in Westminster:
Paste this into wptedit for a visual:
Code: [Select]
SW_A http://www.openstreetmap.org/?lat=51.503906&lon=-0.131836
NW http://www.openstreetmap.org/?lat=51.525879&lon=-0.131836
NE http://www.openstreetmap.org/?lat=51.525879&lon=-0.087891
SE http://www.openstreetmap.org/?lat=51.503906&lon=-0.087891
SW_B http://www.openstreetmap.org/?lat=51.503906&lon=-0.131836
This node is itself refined into four sub-quadrants.
Which of these contains the most points or unique locations, as well as if there are more nodes of this size (or smaller) elsewhere, will take a programmatic solution.
Title: Re: Project Statistics
Post by: si404 on November 07, 2018, 04:31:26 pm
the Maughan Library in Westminster
1) That is in the City of London - as seen by the City's Crest over its entrance, or the boundaries on the map). OK, over the road is part of the City of Westminster (but see 2).
2) No resident of that urban area would call that part of town over the road 'Westminster'. Most would be surprised to see that it was LB Westminster (even I, a map geek, was somewhat surprised it wasn't LB Camden like the area just to the north)

But other than that, proud that London is the most dense, and surprised it's that bit of it - missing some of the densest bits of Central London's road network and containing a lot of the least dense area within the 'Ring of Steel'.
Title: Re: Project Statistics
Post by: yakra on November 07, 2018, 05:09:43 pm
That's what I get for just doing a quick Wiki walk -- Maughan Library -> Strand Campus -> OK, that's where it is? Sure! :)
"LB" means London Borough, I take it?

A little more digging (No further programming yet, just some spreadsheetery) reveals:
This node is 13 steps away from the master node that represents the whole world.
It is the only node of this size.
How many points/unique locations it or its four children contain is still an open question.

How about nodes 12 steps away from the master node?
There are 20 of those, with the majority in the UK. Three are in Puerto Rico. One at the Cincinnati OH / Covington KY line. Seems natural, with dense road networks in these places. And there's one in... Portland, meaning I was probably a bit too generous with waypoints when designing US1Alt, ME77 & pals back in the day. :P

How about:
The least dense node with 1 or more waypoints?
Title: Re: Project Statistics
Post by: si404 on November 07, 2018, 07:15:54 pm
"LB" means London Borough, I take it?
Yep.
Quote
How many points/unique locations it or its four children contain is still an open question.
For it: 51 points (non hidden, all but 7 junctions between two routes). 69 edges between them (one a concurrency) and 26 between them and points not inside the box (two a concurrency).

I copyied (roughly in terms of actual locations) the HDX across onto a screengrab of the wpteditor with the box on

(https://i.postimg.cc/8cqDDQVK/quadtree.png)
Title: Re: Project Statistics
Post by: yakra on November 07, 2018, 07:18:27 pm
Looks like we had almost the same idea. :D
(https://i.postimg.cc/SxZXFRvD/Quadtree-London.png)
Title: Re: Project Statistics
Post by: yakra on November 07, 2018, 08:03:34 pm
Here are the other 13th-level nodes, with a quick-n-dirty name I picked for each.

CodeQuick-n-Dirty Name
MAADCDCCCBDAAHosford-Abernethy
MABDDBADBBDACCarrick Hill
MABDDBBCADDCDBelfast-IMN Ferry
MABDDBBDCCDDCMoss Side
MABDDBCBBBACAHarold’s Cross
MABDDBDABBBABPoulton-Liscard-Egremont
MABDDBDABBBBAKensington
MABDDBDBCBCADSmethwick
MABDDBDBCBCBCDartmouth Circus
MABDDBDDBDBCDKensal Green - Harrow Road
MABDDBDDBDBDCEuston Square
MABDDBDDBDBDDMile End
MABDDBDDBDDBANine Elms Square
MABDDBDDBDDBBNew Cross Gate
MABDDDBDABAAASt Saviour, Jersey
MADAABBBCCCCAPortland ME
MADAACABBBDDACovington-Newport
MADCBACACDDBDJardines
MADCBACADCCAABuena Vista Santurce
MADCBACADCCACBosque Urbana del Neuvo Milenio

Go to yakra.teresco.org/tests/tmg/Quadtree/WaypointQuadtree.tmg.html
Zoom in a bit, search for the code in the vertex/edge list, and click.
Center your mouse, Alt+Tab away, move mouse away from canvas, Alt+Tab back*, and click the OSM or Google links.

*Yes, I plan to eventually improve (https://github.com/yakra/tmtools/issues/79) that...

OKAY I AM GOING TO CLOSE DOWN MY WEB BROWSER AND STEP AWAY FROM THE COMPUTER NOW
Title: Re: Project Statistics
Post by: yakra on November 08, 2018, 01:56:17 am
https://github.com/TravelMapping/DataProcessing/pull/126/files
The WaypointQuadtree has been initialized all these years with the latitude and longitude bounds swapped. It hasn't broken anything, but just led to a sub-optimal distribution of child nodes.
After fixing it, we're down from 42757 to 35165 total nodes with the latest HighwayData.
Compare these side-by-side in two browser tabs:
http://yakra.teresco.org/tests/tmg/Quadtree/WaypointQuadtree-good-NoMerc.tmg.html
http://yakra.teresco.org/tests/tmg/Quadtree/WaypointQuadtree-bug-NoMerc.tmg.html

With the bug, The nodes along the western edge of the map have their eastern boundaries, and centers, asymptotically approaching -90°, rather than the normal -180°.
The de facto W bound of each node is -90°, but points W of there can still be inserted normally, because they're W of the parent node's center -- be it 0°, -45°, -67.5°, -78.75°, etc.
As more points are added and these nodes are refined, they effectively become narrower and narrower "stripes" stretching all the way west.

The mirror image applies along the eastern edge, of course.

A couple of our final unrefined nodes:
Code: [Select]
NE_A http://www.openstreetmap.org/?lat=35.191956&lon=-89.998627
SE http://www.openstreetmap.org/?lat=35.189209&lon=-89.998627
SW http://www.openstreetmap.org/?lat=35.189209&lon=-90.000000
NW http://www.openstreetmap.org/?lat=35.191956&lon=-90.000000
NE_B http://www.openstreetmap.org/?lat=35.191956&lon=-89.998627
...
SE_A http://www.openstreetmap.org/?lat=35.131531&lon=-89.998627
SW http://www.openstreetmap.org/?lat=35.131531&lon=-90.000000
NW http://www.openstreetmap.org/?lat=35.134277&lon=-90.000000
NE http://www.openstreetmap.org/?lat=35.134277&lon=-89.998627
SE_B http://www.openstreetmap.org/?lat=35.131531&lon=-89.998627
A bit smaller than central London, innit! ;)

With latitude, things are less interesting: there are just four extra nodes each N of the N pole & S of the S pole, that never receive any waypoints.
Title: Re: Project Statistics
Post by: yakra on December 13, 2018, 11:27:01 am
I realized my list file now has 3784 lines, which got me wondering how many people have files that long.  Mine is 16th longest.   One user (vespertine) has over 8000 lines, two more are over 7000, two more over 6000, and 2 more over 5000.  94 of our 224 users have at least 1000 lines in their list files.
How many lines in the average .list file?
How many HighwaySegments does the average traveler have .listed?
I'm more interested in the number explicitly .listed, before concurrency augmentation takes place.
Title: Re: Project Statistics
Post by: Jim on December 13, 2018, 02:56:00 pm
Here are the current numbers of lines per .list file.  Note that some will be invalid lines, comments, or blank lines, so consider them a bit on the high side in many cases.  The average number of lines per file is 1235.8.

Code: [Select]
    8437 vespertine.list
    7930 mapcat.list
    7234 oscar.list
    7074 bejacob.list
    6364 froggie.list
    5877 chaddean.list
    5768 dharwood.list
    4937 okroads.list
    4463 charliezeb.list
    4332 mapmikey.list
    4213 ntallyn.list
    4144 justjake.list
    3972 lkefct.list
    3933 dcm55343.list
    3833 terescoj.list
    3833 michih.list
    3776 bhemphill.list
    3758 mefailenglish.list
    3492 duke87.list
    2963 htm_duke.list
    2919 terminal_moraine.list
    2782 valedc03ls.list
    2759 aaroads.list
    2743 skatcher.list
    2721 klundgren.list
    2719 johninkingwood.list
    2669 wadsteckel.list
    2665 ua747sp.list
    2460 dave1693.list
    2380 jeffm.list
    2347 jonfmorse.list
    2281 panda80.list
    2243 mikeandkristie.list
    2165 cinx.list
    2147 rlee.list
    2142 roadgeek_adam.list
    2110 cl94.list
    1925 barefoot_driver.list
    1922 sbeaver44.list
    1922 afarina.list
    1880 master_son.list
    1870 pnrrth.list
    1865 dfilpus.list
    1847 drebbin37.list
    1809 philimon.list
    1791 deathtopumpkins.list
    1714 bogdymol.list
    1709 lowenbrau.list
    1706 regoarrarr.list
    1688 squatchis.list
    1680 jerseyman4.list
    1668 julmac.list
    1625 hoopitypoop.list
    1623 ngrier.list
    1618 tikester.list
    1578 pahighways.list
    1570 sipes23.list
    1563 wphiii.list
    1550 mirage45331.list
    1548 nrm1221.list
    1497 hoss6884.list
    1495 imgoph.list
    1490 capn.list
    1470 quidditch33.list
    1466 gpw.list
    1456 niels.list
    1441 synkdorbit.list
    1438 dantheman.list
    1425 kramer.list
    1384 kjslaughter.list
    1383 vdeane.list
    1365 griffith.list
    1365 cabiness42.list
    1361 tckma.list
    1348 sneezy.list
    1336 dcharlie.list
    1316 1995hoo.list
    1284 norheim.list
    1284 new_friends_gr.list
    1270 codyg1985.list
    1259 osu_lsu.list
    1245 morriswa.list
    1236 bobcobb.list
    1232 si404.list
    1206 scott_stieglitz.list
    1182 mojavenc.list
    1144 keithcavey.list
    1118 jackgaynor.list
    1105 markkos1992.list
    1103 extremebandman.list
    1100 mc49399.list
    1086 ChrisZwolle.list
    1068 verruckte_dan.list
    1061 eucitizen.list
    1044 the_spui_ninja.list
    1033 njroadhorse.list
    1027 bickendan.list
    1024 gman2337.list
     960 angelsfreeek.list
     957 mwasleski.list
     955 yakra.list
     953 presidentman.list
     950 jwood.list
     921 jimvette.list
     915 tbwillie.list
     913 tag42481.list
     904 roadguy2.list
     898 jbum86MASTER.list
     889 ssgtcrusty.list
     888 crosboro7.list
     869 intheam.list
     864 spinoza.list
     844 Ugnaught2.list
     844 25or6to4.list
     841 JamesMD.list
     835 thefxexpert.list
     829 7_8.list
     828 jstalica.list
     826 clong.list
     817 dough4872.list
     815 baugh17.list
     794 thing342.list
     766 radison.list
     764 cougar1989.list
     763 navigator.list
     729 eth.list
     694 pianocello130.list
     691 osu97gp.list
     688 mvak36.list
     681 clark1mt.list
     654 neilbert.list
     652 iowahighways.list
     651 snowedin.list
     641 dgolub.list
     637 mariethefoxy.list
     625 tomhart.list
     615 highplainstrvlr.list
     613 epzik8.list
     597 w9tam.list
     593 roukan.list
     592 jpinyan.list
     591 Beerman.list
     574 hurricanehink.list
     572 Chikara.list
     566 twinsfan87.list
     564 eidderf.list
     541 DJCane.list
     492 lakewy17.list
     487 foresthills93.list
     483 drfrankenstein.list
     480 paulthemapguy.list
     480 opspe.list
     479 rschen7754.list
     476 yipcoyote.list
     476 rickmastfan67.list
     475 dnthrox.list
     475 bulldog1979.list
     458 route56.list
     455 neroute2.list
     448 lamsalfl.list
     436 jweeks.list
     431 snowmatt8.list
     429 based8.list
     424 ohroadscholar.list
     419 myselfalso.list
     408 tarheel61581.list
     404 inagaddadavida.list
     403 mr_matt_k.list
     392 rebelgtp.list
     386 jjbers.list
     382 cyhighways.list
     375 thehighwayman3561.list
     374 dscarroll.list
     370 jayhawkco.list
     330 bubaclex.list
     328 verumsolum.list
     303 dsm4cy.list
     303 compdude787.list
     292 voyager105.list
     290 ibexto.list
     287 dylucktrocket.list
     275 Aseluit.list
     263 dsaneus.list
     261 moshitea.list
     237 roadgeek99.list
     237 along.list
     207 georgiaroadgeek.list
     206 bm7.list
     205 atsiatas.list
     203 ran4sh.list
     192 intelati49.list
     191 slorydn1.list
     191 1.list
     190 xorodejon.list
     168 happy5214.list
     166 electronym.list
     162 tjj25.list
     161 peperodriguez2710.list
     150 paddy.list
     149 sounderbruce.list
     130 gimmicks.list
     128 xcvxcvxcv.list
     125 golubcar.list
     118 boris.list
     117 scheidler.list
     115 riiga.list
     113 harvey.list
     110 sammi.list
     108 es92.list
     103 skoutr1.list
      98 sercamaro.list
      88 finnedude.list
      75 jordancarrpeterson.list
      75 dctransit.list
      73 mepaulrye.list
      72 noelbotevera.list
      71 vinoman64.list
      70 kurzov.list
      66 whopperman.list
      66 sfisher.list
      66 philman.list
      62 vcap36.list
      60 polabare.list
      53 dognm16.list
      50 usaidhello.list
      45 Qiviuq.list
      35 robringstad.list
      26 rgentry.list
      26 ThelwallViaduct.list
      21 superblu2007.list
       8 riehlj.list
       8 YaxStarTest.list
       1 benjamingrove47.list
Title: Re: Project Statistics
Post by: yakra on December 13, 2018, 06:20:23 pm
How many HighwaySegments does the average traveler have .listed?
I'm more interested in the number explicitly .listed, before concurrency augmentation takes place.
I'm working from a somewhat outdated version of the HighwayData repo here locally, but here's what I get:
4281202 traveler-segments. (More recent additions, such as usaal -> preview, are certain to increase this.)
Divided by 231 .list files, that's 18533.3 segments per .list.

Most-clinched segment is VA I-95 84 86, with 128 travelers.
Edit: There may be other segments tied at 128 travelers. I didn't check for more; this was simply the first one found.
Title: Re: Project Statistics
Post by: froggie on December 13, 2018, 09:21:52 pm
^^ According to my log, I have 6,100 "good lines".
Title: Re: Project Statistics
Post by: Jim on December 14, 2018, 08:31:03 am
I was playing around with a little SQL this morning (isn't everyone?) and built a query that gives the number of TM "segments" clinched by user:

Code: [Select]
select traveler, count(*) as segments from clinched group by traveler order by segments desc;
Code: [Select]
+--------------------+----------+
| traveler           | segments |
+--------------------+----------+
| oscar              |   153495 |
| mapcat             |   150511 |
| vespertine         |   117445 |
| charliezeb         |   105478 |
| dharwood           |    83569 |
| froggie            |    80287 |
| bejacob            |    80211 |
| duke87             |    68985 |
| mefailenglish      |    68303 |
| mapmikey           |    65753 |
| valedc03ls         |    65667 |
| lkefct             |    64822 |
| okroads            |    64619 |
| michih             |    63874 |
| justjake           |    62768 |
| barefoot_driver    |    60315 |
| terminal_moraine   |    59856 |
| terescoj           |    59777 |
| aaroads            |    57313 |
| jonfmorse          |    54048 |
| bhemphill          |    48231 |
| pnrrth             |    47555 |
| ntallyn            |    45193 |
| dcm55343           |    45188 |
| chaddean           |    44314 |
| jeffm              |    42817 |
| panda80            |    42233 |
| wadsteckel         |    41384 |
| ua747sp            |    41200 |
| master_son         |    40915 |
| julmac             |    40457 |
| cl94               |    37368 |
| hoopitypoop        |    37201 |
| tikester           |    36098 |
| dfilpus            |    35514 |
| johninkingwood     |    35350 |
| intheam            |    34161 |
| ngrier             |    33431 |
| bobcobb            |    33124 |
| drebbin37          |    33049 |
| jimvette           |    32706 |
| sipes23            |    32464 |
| skatcher           |    32378 |
| htm_duke           |    32057 |
| klundgren          |    32000 |
| roadgeek_adam      |    31969 |
| norheim            |    30813 |
| rlee               |    29691 |
| angelsfreeek       |    29611 |
| cinx               |    29571 |
| deathtopumpkins    |    29381 |
| gman2337           |    29222 |
| highplainstrvlr    |    28904 |
| ChrisZwolle        |    28153 |
| ssgtcrusty         |    27452 |
| mikeandkristie     |    27109 |
| capn               |    26825 |
| dcharlie           |    26637 |
| kramer             |    26441 |
| codyg1985          |    26297 |
| new_friends_gr     |    26171 |
| sneezy             |    25486 |
| mirage45331        |    25463 |
| dave1693           |    24465 |
| quidditch33        |    23891 |
| eucitizen          |    23808 |
| bogdymol           |    23496 |
| jerseyman4         |    23402 |
| lowenbrau          |    23112 |
| sbeaver44          |    22892 |
| wphiii             |    22849 |
| osu_lsu            |    22535 |
| tckma              |    22370 |
| pahighways         |    22301 |
| regoarrarr         |    22107 |
| afarina            |    21978 |
| jstalica           |    21580 |
| niels              |    21087 |
| whopperman         |    20714 |
| mojavenc           |    20684 |
| hoss6884           |    20624 |
| cabiness42         |    20566 |
| 1995hoo            |    20450 |
| bickendan          |    20267 |
| squatchis          |    20163 |
| the_spui_ninja     |    19359 |
| synkdorbit         |    19024 |
| jackgaynor         |    18851 |
| philimon           |    18825 |
| dnthrox            |    18796 |
| Ugnaught2          |    18780 |
| scott_stieglitz    |    18728 |
| jweeks             |    18538 |
| w9tam              |    18352 |
| vdeane             |    18334 |
| keithcavey         |    18238 |
| imgoph             |    18048 |
| thehighwayman3561  |    17984 |
| nrm1221            |    17806 |
| crosboro7          |    17512 |
| jayhawkco          |    17441 |
| 25or6to4           |    17365 |
| griffith           |    17331 |
| tag42481           |    17298 |
| gpw                |    17003 |
| dantheman          |    16915 |
| snowedin           |    16911 |
| lamsalfl           |    16895 |
| spinoza            |    16604 |
| morriswa           |    16218 |
| hurricanehink      |    15985 |
| njroadhorse        |    15945 |
| thing342           |    15487 |
| kjslaughter        |    15443 |
| mc49399            |    15422 |
| presidentman       |    15272 |
| mvak36             |    15063 |
| DJCane             |    14968 |
| verruckte_dan      |    14937 |
| twinsfan87         |    14804 |
| mwasleski          |    14633 |
| Based8             |    14450 |
| yipcoyote          |    14310 |
| jwood              |    14293 |
| rebelgtp           |    14152 |
| paulthemapguy      |    14068 |
| JamesMD            |    13722 |
| 7_8                |    13456 |
| clong              |    13335 |
| inagaddadavida     |    13310 |
| clark1mt           |    13252 |
| yakra              |    13214 |
| opspe              |    12994 |
| thefxexpert        |    12851 |
| foresthills93      |    12803 |
| tbwillie           |    12668 |
| radison            |    12665 |
| navigator          |    12636 |
| cougar1989         |    12374 |
| osu97gp            |    12364 |
| markkos1992        |    12348 |
| extremebandman     |    12250 |
| jbum86MASTER       |    11733 |
| pianocello130      |    11591 |
| epzik8             |    11523 |
| eth                |    11453 |
| neilbert           |    10979 |
| rschen7754         |    10796 |
| iowahighways       |    10784 |
| baugh17            |    10781 |
| Beerman            |    10107 |
| Chikara            |    10057 |
| eidderf            |     9856 |
| si404              |     9558 |
| ibexto             |     9533 |
| roadguy2           |     9455 |
| lakewy17           |     9032 |
| tomhart            |     8973 |
| slorydn1           |     8808 |
| route56            |     8756 |
| jpinyan            |     8410 |
| mariethefoxy       |     8381 |
| drfrankenstein     |     8259 |
| roukan             |     8162 |
| along              |     8128 |
| dough4872          |     8069 |
| bulldog1979        |     7573 |
| intelati49         |     7159 |
| snowmatt8          |     6930 |
| myselfalso         |     6878 |
| dgolub             |     6850 |
| moshitea           |     6811 |
| cyhighways         |     6802 |
| atsiatas           |     6642 |
| paddy              |     6522 |
| Aseluit            |     6345 |
| bubaclex           |     6201 |
| electronym         |     6117 |
| ran4sh             |     6082 |
| happy5214          |     5801 |
| dsaneus            |     5643 |
| rickmastfan67      |     5545 |
| dsm4cy             |     5445 |
| tarheel61581       |     5441 |
| dscarroll          |     5323 |
| neroute2           |     5117 |
| voyager105         |     5043 |
| ohroadscholar      |     4866 |
| compdude787        |     4860 |
| tjj25              |     4366 |
| verumsolum         |     4301 |
| gimmicks           |     4240 |
| dylucktrocket      |     4199 |
| jjbers             |     4162 |
| mr_matt_k          |     4152 |
| roadgeek99         |     4090 |
| georgiaroadgeek    |     3605 |
| bm7                |     3583 |
| skoutr1            |     3303 |
| peperodriguez2710  |     3267 |
| sammi              |     2897 |
| xcvxcvxcv          |     2810 |
| es92               |     2605 |
| riiga              |     2539 |
| sfisher            |     2503 |
| sounderbruce       |     2386 |
| harvey             |     2222 |
| dctransit          |     2142 |
| boris              |     2091 |
| rgentry            |     2047 |
| xorodejon          |     1898 |
| vinoman64          |     1878 |
| 1                  |     1712 |
| vcap36             |     1712 |
| golubcar           |     1639 |
| kurzov             |     1395 |
| scheidler          |     1210 |
| sercamaro          |     1197 |
| finnedude          |     1190 |
| mepaulrye          |     1109 |
| robringstad        |     1070 |
| riehlj             |      912 |
| polabare           |      902 |
| philman            |      811 |
| dognm16            |      804 |
| noelbotevera       |      779 |
| ThelwallViaduct    |      605 |
| jordancarrpeterson |      566 |
| superblu2007       |      489 |
| usaidhello         |      152 |
+--------------------+----------+
Title: Re: Project Statistics
Post by: Jim on December 14, 2018, 08:39:14 am
Here's another.

Code: [Select]
select segmentid, count(*) as travelcount from clinched group by segmentid order by travelcount;
This gives all segments ordered by number of travelers.  It's 440,000+ lines long, but we can see that 13 segments are traveled by 129 travelers each, which is the most of any.  I'd have to expand the query to join with the segments and probably routes tables to get meaningful information about those segments like the end waypoints and the name of the route.
Title: Re: Project Statistics
Post by: froggie on December 14, 2018, 09:39:49 am
^ Is there a fairly easy way to determine how many route segments have been traveled by only one user, aggregated by region and/or system, compared to the total number of segments?
Title: Re: Project Statistics
Post by: Jim on December 14, 2018, 10:07:35 am
^ Is there a fairly easy way to determine how many route segments have been traveled by only one user, aggregated by region and/or system, compared to the total number of segments?

That's among the things I'd like to add.  Somewhere in the forum or in a GitHub issue, this was referred to by someone as a "TM Pioneer" - the only traveler to clinch a segment/route/connected route.  I think I just need to take a day to experiment with some interesting SQL queries and get them into appropriate existing or new places in the web front end.  I envision maps where segments are colored by number of travelers, possibly with some special highlighting of segments traveled by a single user.
Title: Re: Project Statistics
Post by: oscar on December 14, 2018, 11:31:02 am
I envision maps where segments are colored by number of travelers, possibly with some special highlighting of segments traveled by a single user.

Based on my own travels, you'll have quite a few route segments traveled by a single user, especially in preview systems like cansk. Might not be "special" enough to warrant highlighting.
Title: Re: Project Statistics
Post by: yakra on December 14, 2018, 01:21:13 pm
^ Is there a fairly easy way to determine how many route segments have been traveled by only one user, aggregated by region and/or system, compared to the total number of segments?
aggregated by system:
http://yakra.teresco.org/tmtools_demos/pioneers/outdated_UserData/pioneers.log
Edit: Ignore this for now. List Names are showing up incorrectly. E.G., tikester's trailblazing segments of either CA US101BusPas or CA US101HisPas are showing up as CA US101 proper. :(
Fixed.

Edit: I should note that this is also only for segments explicitly .listed by a traveler, without any augments for concurrencies.
Title: Re: Project Statistics
Post by: froggie on December 14, 2018, 02:14:49 pm
^ Something's not working with your script and/or output, Eric.  I recognized several segments in Alabama that the logs recognize I've been on, but someone else is shown on your list as the sole clincher.
Title: Re: Project Statistics
Post by: yakra on December 15, 2018, 12:30:21 am
Interesting. What are some examples? I'll definitely need to look into this.
Title: Re: Project Statistics
Post by: yakra on December 15, 2018, 02:36:39 am
The code I used to produce the original log was an in-progress C++ version of siteupdate.
I added similar code to siteupdate.py to make the same log.
the log (http://yakra.teresco.org/tmtools_demos/pioneers/outdated_UserData/pioneers_python.log)
the diff (http://yakra.teresco.org/tmtools_demos/pioneers/outdated_UserData/pioneers.python-to-cpp.diff)
I don't see the problem you described as you describe it, but I do see a very similar problem:
I recognized several segments in New Brunswick that the logs recognize Oscar has been on, but I am shown on my list as the sole clincher.

In the DIFF, I don't see anything in Alabama. I see two three possibilities:
1. Your segments are ones that you didn't explicitly .list, but acquired via a concurrency with another route.
2. A similar problem exists in the original siteupdate.py.
3. I goofed and didn't run my program with up-to-date UserData.

Whatever's going on here, thank you for the bug report. Some detective work is in order.
Maybe even a thread split...
Title: Re: Project Statistics
Post by: froggie on December 15, 2018, 07:59:59 am
Yes, the problem I saw is similar in nature to what you saw with NB and Oscar.  Regarding your possibilities, it's not #1..I did explicitly list the routes in my list (the first example I noticed being AL 10 near the Mississippi line).
Title: Re: Project Statistics
Post by: yakra on December 15, 2018, 12:45:30 pm
Yes, the problem I saw is similar in nature to what you saw with NB and Oscar.  Regarding your possibilities, it's not #1..I did explicitly list the routes in my list (the first example I noticed being AL 10 near the Mississippi line).
Indeed. I see in froggie.list (https://github.com/TravelMapping/UserData/blob/35e1850c3f6e226d6a831fb1f9941b800f3430f6/list_files/froggie.list#L97):
AL AL10 MS/AL US43
...and mapcat is listed as the pioneer on AL AL10 ComSt LinAve for example, even in the Python version (http://yakra.teresco.org/tmtools_demos/pioneers_python.log).
This suggests to me that there's something fishy in the original siteupdate.py. The code I added was short & simple & straightforward, and I don't see any room for something to have gone wrong with this small addition...
Code: [Select]
# after processing traveler list files

segment_count = 0
print(et.et() + "writing pioneers.log",end="",flush=True)
pioneerslog = open('pioneers.log','w')
for h in highway_systems:
    for r in h.route_list:
        for seg in r.segment_list:
            segment_count += 1
    if len(seg.clinched_by) == 1:
                pioneerslog.write(str(seg) + " " + seg.clinched_by[0].traveler_name + "\n")
    print(".",end="",flush=True)
print("")
pioneerslog.write(str(segment_count) + " total segments.\n")
pioneerslog.close()

sys.exit()

# before reading updates.csv
Title: Re: Project Statistics
Post by: yakra on December 15, 2018, 01:47:58 pm
D'OH!
Somehow I skipped getting my UserData repo up-to-date.
I pulled in the latest changes from GitHub, and saw 115 additions to froggie.list.
This should cure the Alabama problems (I'm going to test again), but I think some other bugs will still remain.

Edit: OK, try this:
New Python log (http://yakra.teresco.org/tmtools_demos/pioneers/20181215/pioneers_python.log) (consider this the definitive one)
New C++ log (http://yakra.teresco.org/tmtools_demos/pioneers/20181215/pioneers_cpp.log) (this one's buggy)
Their diff (http://yakra.teresco.org/tmtools_demos/pioneers/20181215/pioneers.python-to-cpp.diff) (I still have stuff to work on...)

Our westernmost pioneer on AL10 is now froggie, starting at AL69.
Title: Re: Project Statistics
Post by: yakra on December 21, 2018, 02:04:51 pm
Here are the current numbers of lines per .list file.  Note that some will be invalid lines, comments, or blank lines, so consider them a bit on the high side in many cases.  The average number of lines per file is 1235.8.

Code: [Select]
    1027 bickendan.list
     955 yakra.list
      66 whopperman.list
Hm. Out of curiosity, how did you compile this list?
Title: Re: Project Statistics
Post by: Jim on December 21, 2018, 04:23:55 pm
Here are the current numbers of lines per .list file.  Note that some will be invalid lines, comments, or blank lines, so consider them a bit on the high side in many cases.  The average number of lines per file is 1235.8.

Code: [Select]
    1027 bickendan.list
     955 yakra.list
      66 whopperman.list
Hm. Out of curiosity, how did you compile this list?
  • yakra.list (https://github.com/TravelMapping/UserData/blob/1dbe5ed41250d3ae46a42cd4babfdda4576449df/list_files/yakra.list) is correct, at 955 lines.
  • bickendan.list (https://github.com/TravelMapping/UserData/blob/3101895c4f121a7598ce4f068a47cc4b297c5078/list_files/bickendan.list) has 1028 lines, with no newline @ EOF.
  • whopperman.list (https://github.com/TravelMapping/UserData/blob/6309036c44102eb3325d49515b32c5eef3b3cb1e/list_files/whopperman.list) is a unique, interesting case. Note how GitHub doesn't display new line numbers for most new lines. Most of the newlines use only the 0x0D character, as opposed to the Unix 0x0A or DOS/Windows 0x0D0A. I have to wonder if whopperman initially drafted this file on classic Mac OS (https://en.wikipedia.org/wiki/Newline#Representation). I'm counting 828 lines (791 good lines (http://travelmapping.net/logs/users/whopperman.log)). GitHub shows 67. With the absence of a newline @ EOF, we're down to 66 as shown above.
In the list_files directory,

Code: [Select]
wc -l * | sort -nr
Title: Re: Project Statistics
Post by: yakra on December 22, 2018, 01:26:11 am
wc --help
sort --help
Boom! Got it. :)
Title: Re: Project Statistics
Post by: Jim on December 22, 2018, 07:53:43 am
wc --help
sort --help
Boom! Got it. :)

If course you meant

man wc
man sort
Title: Re: Project Statistics
Post by: yakra on December 22, 2018, 12:32:05 pm
Never really been a fan of man pages, for some reason. I'll just take the "digest version" of a --help, most of the time.
Title: Re: Project Statistics
Post by: yakra on January 04, 2019, 01:48:30 am
What's the largest WPT file, by filesize?
If that's not convenient to answer, which WPT file has the most waypoints?
tx.us087.wpt, at 26026 bytes, has 282 points.
Looking to see if there's anything larger, unless anyone else comes up with an answer first.

Edit:
largest WPT by filesize is /home/yakra/TravelMapping/HighwayData/hwy_data/RUS/asiah/rus.ah006irk.wpt, at 58882 bytes.
largest WPT by point count is /home/yakra/TravelMapping/HighwayData/hwy_data/RUS/asiah/rus.ah006irk.wpt, at 886 points.

The largest .list file, meanwhile, was much easier to find, with all the .lists in the same directory.
It's vespertine.list, at 195814 bytes and 849 lines.
Title: Re: Project Statistics
Post by: oscar on January 04, 2019, 07:32:45 am
The largest .list file, meanwhile, was much easier to find, with all the .lists in the same directory.
It's vespertine.list, at 195814 bytes and 849 lines.

vespertine.list's log file shows 8434 good lines, plus a few "bad lines", mainly for Mississippi state routes for which there isn't a preview or active system. Two other list files are over 7000 good lines.

As for wpt files, BC 97 and CA 1 were once competitive for "largest file", and may still be in North America. But both were recently streamlined, and neither comes close to rus.ah006irk.wpt.
Title: Re: Project Statistics
Post by: yakra on January 04, 2019, 01:30:12 pm
Oops. I meant 8499 lines IIRC. Total line count including blanks and comments.
Title: Re: Project Statistics
Post by: michih on January 06, 2019, 02:40:44 am
More than 1.2 million miles (1,200,964 mi) in preview + active systems now.
Title: Re: Project Statistics
Post by: si404 on January 12, 2019, 02:20:17 pm
The Highway Data Repository has just had its 2500th pull request.
Title: Re: Project Statistics
Post by: Jim on January 12, 2019, 08:19:06 pm
The Highway Data Repository has just had its 2500th pull request.

Pull requests + Issues.  We've had 2348 pull requests and 153 issues now.
Title: Re: Project Statistics
Post by: yakra on January 14, 2019, 01:25:52 pm
The HighwayData repository has just had pull request #2500. ;)
Title: Re: Project Statistics
Post by: michih on January 14, 2019, 01:31:11 pm
No, it's still 2371.
Title: Re: Project Statistics
Post by: yakra on January 14, 2019, 10:58:35 pm
We're at 2373rd pull requst, which is number 2526, nominally.
Title: Re: Project Statistics
Post by: yakra on January 15, 2019, 12:54:12 am
More than 1.2 million miles (1,200,964 mi) in preview + active systems now.
Right now:
active only = 884948.64 mi
active+preview = 1221787.36 mi
Title: Re: Project Statistics
Post by: si404 on January 15, 2019, 04:09:37 am
Right now:
active only = 884948.64 mi
active+preview = 1221787.36 mi
Well that's what comes of my making two systems active and 18 preview this year - bigger numbers...
Title: Re: Project Statistics
Post by: Bickendan on January 26, 2019, 05:23:48 pm
What's the largest WPT file, by filesize?
If that's not convenient to answer, which WPT file has the most waypoints?
tx.us087.wpt, at 26026 bytes, has 282 points.
Looking to see if there's anything larger, unless anyone else comes up with an answer first.

Edit:
largest WPT by filesize is /home/yakra/TravelMapping/HighwayData/hwy_data/RUS/asiah/rus.ah006irk.wpt, at 58882 bytes.
largest WPT by point count is /home/yakra/TravelMapping/HighwayData/hwy_data/RUS/asiah/rus.ah006irk.wpt, at 886 points.

The largest .list file, meanwhile, was much easier to find, with all the .lists in the same directory.
It's vespertine.list, at 195814 bytes and 849 lines.
AUSWA N1 clocks in at 827 points, but has a length of 3300 miles
Title: Re: Project Statistics
Post by: yakra on February 20, 2019, 09:44:17 pm
The easternmost vertex within 100 miles of Siena College falls on the MA/NH line.
Title: Re: Project Statistics
Post by: froggie on February 21, 2019, 11:45:05 am
^ It's not like Vermont and New Hampshire have a lot of east-west width...
Title: Re: Project Statistics
Post by: yakra on February 21, 2019, 02:16:08 pm
Yup.  I just thought it was neat that it was a state line point.
Title: Re: Project Statistics
Post by: michih on March 10, 2019, 04:17:34 pm
With today's new preview systems (turd+ausm) we do no longer have any traveler with more than 20% of preview+active systems mileage clinched.
Title: Re: Project Statistics
Post by: Jim on March 31, 2019, 09:41:35 pm
Some time recently we first passed the 50,000 mark for the number of .wpt files being ingested across active, preview, and devel systems.
Title: Re: Project Statistics
Post by: michih on April 16, 2019, 12:00:02 pm
More than 900,000mi in active systems now :)
Title: Re: Project Statistics
Post by: Jim on May 20, 2019, 10:34:53 pm
With the implementation of traveled format graphs (thanks again @yakra!), and in response to an email I received from a user, I put together a small program that reports the least- and most-traveled segments in a graph.  Running on the full tm-master-traveled.tmg graph, which has 481,044 edges, there are 190,498 not traveled by anyone.

Before I report the most-traveled edges, I'll give a chance for guesses.  There are 2 of them tied, traveled by 138 of our 241 users, and they're consecutive edges along a single route.  What do you think? 

Title: Re: Project Statistics
Post by: yakra on May 20, 2019, 11:18:52 pm
VA I-95 near the Springfield Interchange. A bit south of it. Or wait, now I'm second-guessing myself. Was it closer to Richmond?
IIRC this was mentioned upthread -- only one of the segments, noting that it was tied but not specifying what with.

OK, I just cheated and looked at VA-region-traveled.tmg, and the two segments immediately south of the beltway have 137 travelers. Which ones have 138? Dunno. Anyone else?

Edit: I made a temporary mod to siteupdate.cpp, and found the segments. It was easier than writing something new to parse graphs. :) They are not where I expected.
Title: Re: Project Statistics
Post by: si404 on May 21, 2019, 05:04:58 am
There are 2 of them tied, traveled by 138 of our 241 users, and they're consecutive edges along a single route.  What do you think?
That there's a shaping point shared between those two edges?
Title: Re: Project Statistics
Post by: Jim on May 21, 2019, 07:10:31 am
There are 2 of them tied, traveled by 138 of our 241 users, and they're consecutive edges along a single route.  What do you think?
That there's a shaping point shared between those two edges?

No, 3 consecutive exits off a limited-access highway.
Title: Re: Project Statistics
Post by: Eth on May 21, 2019, 12:10:50 pm
I decided to look through my own travels, figuring I was likely one of the travelers, and I think I've found it:

DE I-95 4A 4B
DE I-95 4B 5A

Those segments show as being driven by 92.62% of DE I-95's total 149 drivers, and if my math is correct that would work out to 138.
Title: Re: Project Statistics
Post by: Jim on May 21, 2019, 12:17:38 pm
I decided to look through my own travels, figuring I was likely one of the travelers, and I think I've found it:

DE I-95 4A 4B
DE I-95 4B 5A

Those segments show as being driven by 92.62% of DE I-95's total 149 drivers, and if my math is correct that would work out to 138.

These are the winners.  Lots of people on the Delaware Turnpike.
Title: Re: Project Statistics
Post by: Jim on May 21, 2019, 12:26:24 pm
Next TM traveler trivia question: of all of the graphs generated for the METAL project (http://travelmapping.net/graphs/) which one has the most-traveled least-traveled segment?  That is, look at each graph and find its least-traveled segment.  Then find the largest such value.  Guesses?
Title: Re: Project Statistics
Post by: si404 on May 21, 2019, 06:21:24 pm
TM-Master!  :P

I'm guessing you don't want to include the everything one. Asia has an awful lot of untravelled (and so least-travelled) segments, but I'm not sure that's the winner.
Title: Re: Project Statistics
Post by: Jim on May 21, 2019, 08:23:49 pm
TM-Master!  :P

I'm guessing you don't want to include the everything one. Asia has an awful lot of untravelled (and so least-travelled) segments, but I'm not sure that's the winner.

The master graph definitely has some 0-traveler segments, so it's part of the 334-way tie for last place in this ranking.

In the other 52 graphs, every segment is clinched by at least one traveler.  The question is, for which graph is that minimum number of clinchers on any segment maximized.

The "area" graphs tend to be clustered near the top of this list because they're most likely to be in places people go like big cities.  However, the winner, and it's the winner by a significant margin, is a region graph.
Title: Re: Project Statistics
Post by: yakra on May 21, 2019, 10:44:58 pm
The master graph definitely has some 0-traveler segments, so it's part of the 334-way tie for last place in this ranking.

In the other 52 graphs, every segment is clinched by at least one traveler.
Don't you mean, the other 65 graphs?

The question is, for which graph is that minimum number of clinchers on any segment maximized.

The "area" graphs tend to be clustered near the top of this list because they're most likely to be in places people go like big cities.  However, the winner, and it's the winner by a significant margin, is a region graph.
Spoiler! (http://forum.travelmapping.net/index.php?topic=3030.msg13952#msg13952) :)
Title: Re: Project Statistics
Post by: si404 on May 22, 2019, 03:46:53 am
The master graph definitely has some 0-traveler segments, so it's part of the 334-way tie for last place in this ranking.
Misread it as most least-travelled sections (I think Europe wins that as it has so many edges, and fewer travellers than North America), rather than the highest value for least-travelled section  :-[

Got the answer you are looking for as soon as I realised what it was you were asking for. A small graph in an urban area without many routes to deal with.
Title: Re: Project Statistics
Post by: Jim on May 22, 2019, 06:57:15 am
The master graph definitely has some 0-traveler segments, so it's part of the 334-way tie for last place in this ranking.

In the other 52 graphs, every segment is clinched by at least one traveler.
Don't you mean, the other 65 graphs?

I deleted a bunch that were invalid.  For some reason, the France "IGNORE TEST" systems confuse graph generation.

Related to that, if I can get a test DB to be more usable, can those test systems be moved out of the production DB?
Title: Re: Project Statistics
Post by: yakra on May 22, 2019, 10:20:45 am
I deleted a bunch that were invalid.  For some reason, the France "IGNORE TEST" systems confuse graph generation.
They break the assumption that an edge lives within a single region.
https://github.com/TravelMapping/DataProcessing/issues/205
The region of an edge is that assigned to its canonical segment, which is that passed to the HGEdge constructor, which is the first segment on a concurrency list for concurrent segments.
Title: Re: Project Statistics
Post by: Jim on May 22, 2019, 01:36:41 pm
For our graphs with at least one traveled segment, here's what we have.  Possibly the most surprising to me is that, given the size of the MD state highway system, that every segment in the state has been traveled by at least 4 TM users.

GraphLeast-traveled edgeMost-traveled edge
DC-region-traveled.tmg13123
naples25-area-traveled.tmg970
siena25-area-traveled.tmg798
chicago25-area-traveled.tmg6126
nyc20-area-traveled.tmg5128
mhc25-area-traveled.tmg582
dc20-area-traveled.tmg4137
MD-region-traveled.tmg4135
baltimore25-area-traveled.tmg4135
siena50-area-traveled.tmg498
MAF-region-traveled.tmg45
NJ-region-traveled.tmg3132
NY-region-traveled.tmg3110
ubuffalo50-area-traveled.tmg3106
kc20-area-traveled.tmg3102
MS-region-traveled.tmg382
DE-region-traveled.tmg2138
usai-system-traveled.tmg2138
OH-region-traveled.tmg2118
IN-region-traveled.tmg2114
CT-region-traveled.tmg2112
WI-region-traveled.tmg2103
RI-region-traveled.tmg2102
siena100-area-traveled.tmg2101
MA-region-traveled.tmg2100
NH-region-traveled.tmg298
boston20-area-traveled.tmg297
IA-region-traveled.tmg296
sfbay50-area-traveled.tmg289
MI-region-traveled.tmg288
MEX-QROO-region-traveled.tmg25
MEX-YUC-region-traveled.tmg25
MEX-BCS-region-traveled.tmg22
VA-region-traveled.tmg1137
IL-region-traveled.tmg1126
stlouis25-area-traveled.tmg1122
muhlenberg25-area-traveled.tmg1100
seattle25-area-traveled.tmg196
HI-region-traveled.tmg136
cantch-system-traveled.tmg135
innsbruck25-area-traveled.tmg120
LIE-region-traveled.tmg19
DEU-BE-region-traveled.tmg18
MLT-region-traveled.tmg17
MEX-BC-region-traveled.tmg16
ABW-region-traveled.tmg14
ESP-IB-region-traveled.tmg13
NT-region-traveled.tmg13
MEX-JAL-region-traveled.tmg12
MEX-CAM-region-traveled.tmg11
MEX-COL-region-traveled.tmg11
MEX-TAB-region-traveled.tmg11
NA-continent-traveled.tmg0138
USA-country-traveled.tmg0138
USA-national-traveled.tmg0138
tm-master-traveled.tmg0138
usaus-system-traveled.tmg0136
GA-region-traveled.tmg0127
TN-region-traveled.tmg0123
PA-region-traveled.tmg0122
FL-region-traveled.tmg0120
SC-region-traveled.tmg0112
USA-newengland-traveled.tmg0112
MO-region-traveled.tmg0111
NC-region-traveled.tmg0110
KY-region-traveled.tmg0108
WV-region-traveled.tmg0107
CO-region-traveled.tmg0103
AR-region-traveled.tmg099
ME-region-traveled.tmg097
WA-region-traveled.tmg096
omaha30-area-traveled.tmg096
NE-region-traveled.tmg092
grandisland50-area-traveled.tmg092
NV-region-traveled.tmg091
SD-region-traveled.tmg091
CA-region-traveled.tmg089
LA-region-traveled.tmg089
MN-region-traveled.tmg088
AL-region-traveled.tmg086
CAN-country-traveled.tmg086
ON-region-traveled.tmg086
UT-region-traveled.tmg085
KS-region-traveled.tmg084
la125-area-traveled.tmg081
OK-region-traveled.tmg080
AZ-region-traveled.tmg077
WY-region-traveled.tmg076
TX-region-traveled.tmg075
VT-region-traveled.tmg075
OR-region-traveled.tmg073
ND-region-traveled.tmg072
NM-region-traveled.tmg071
albuquerque50-area-traveled.tmg071
MT-region-traveled.tmg067
austin25-area-traveled.tmg066
ID-region-traveled.tmg064
QC-region-traveled.tmg047
montreal25-area-traveled.tmg047
OCE-continent-traveled.tmg036
BC-region-traveled.tmg033
wolfcreek50-area-traveled.tmg025
ENG-region-traveled.tmg023
EUR-continent-traveled.tmg023
EUR-freeways-traveled.tmg023
GBR-country-traveled.tmg023
british-isles-traveled.tmg023
london25-area-traveled.tmg023
AB-region-traveled.tmg021
AK-region-traveled.tmg021
CAN-maritimes-traveled.tmg021
NB-region-traveled.tmg021
eure-system-traveled.tmg021
AUT-region-traveled.tmg020
DEU-BY-region-traveled.tmg019
DEU-country-traveled.tmg019
FRA-country-traveled.tmg019
FRA-region-traveled.tmg019
BEL-region-traveled.tmg018
CHE-region-traveled.tmg018
DEU-HE-region-traveled.tmg018
DEU-BW-region-traveled.tmg017
DEU-RP-region-traveled.tmg017
ITA-region-traveled.tmg017
NS-region-traveled.tmg017
PE-region-traveled.tmg017
LUX-region-traveled.tmg016
DEU-NW-region-traveled.tmg015
PR-region-traveled.tmg015
west-indies-traveled.tmg015
NLD-country-traveled.tmg014
NLD-region-traveled.tmg014
CZE-region-traveled.tmg013
MB-region-traveled.tmg012
SVN-region-traveled.tmg012
DEU-SL-region-traveled.tmg011
DNK-country-traveled.tmg011
DNK-region-traveled.tmg011
ISL-region-traveled.tmg011
SVK-region-traveled.tmg011
copenhagen25-area-traveled.tmg011
DEU-NI-region-traveled.tmg010
DEU-SN-region-traveled.tmg010
DEU-ST-region-traveled.tmg010
ESP-AN-region-traveled.tmg010
ESP-country-traveled.tmg010
HRV-region-traveled.tmg010
HUN-region-traveled.tmg010
IRL-region-traveled.tmg010
SK-region-traveled.tmg010
WLS-region-traveled.tmg010
DEU-TH-region-traveled.tmg09
POL-region-traveled.tmg09
PRT-region-traveled.tmg09
SCT-region-traveled.tmg09
SWE-region-traveled.tmg09
DEU-BB-region-traveled.tmg08
DEU-HH-region-traveled.tmg08
ESP-CT-region-traveled.tmg08
NIR-region-traveled.tmg08
NOR-region-traveled.tmg08
DEU-HB-region-traveled.tmg07
ESP-AR-region-traveled.tmg07
NL-region-traveled.tmg07
YT-region-traveled.tmg07
AND-region-traveled.tmg06
DEU-MV-region-traveled.tmg06
DEU-SH-region-traveled.tmg06
ESP-MD-region-traveled.tmg06
ESP-PV-region-traveled.tmg06
ESP-VC-region-traveled.tmg06
MEX-country-traveled.tmg06
MNE-region-traveled.tmg06
SRB-region-traveled.tmg06
VI-region-traveled.tmg06
BIH-region-traveled.tmg05
ESP-CL-region-traveled.tmg05
ESP-CM-region-traveled.tmg05
ESP-EX-region-traveled.tmg05
FIN-country-traveled.tmg05
FIN-region-traveled.tmg05
LTU-region-traveled.tmg05
LVA-region-traveled.tmg05
ASI-continent-traveled.tmg04
BGR-region-traveled.tmg04
BLZ-region-traveled.tmg04
ESP-CB-region-traveled.tmg04
ESP-MC-region-traveled.tmg04
ESP-NC-region-traveled.tmg04
EST-region-traveled.tmg04
GRC-region-traveled.tmg04
ISR-region-traveled.tmg04
MKD-region-traveled.tmg04
ROU-region-traveled.tmg04
AFR-continent-traveled.tmg03
AUS-NSW-region-traveled.tmg03
AUS-QLD-region-traveled.tmg03
AUS-country-traveled.tmg03
BRB-region-traveled.tmg03
ESP-AS-region-traveled.tmg03
ESP-GA-region-traveled.tmg03
ESP-RI-region-traveled.tmg03
GU-region-traveled.tmg03
MAR-region-traveled.tmg03
PHL-region-traveled.tmg03
PSE-region-traveled.tmg03
ALB-region-traveled.tmg02
AUS-NT-region-traveled.tmg02
CHN-BJ-region-traveled.tmg02
CHN-country-traveled.tmg02
ESP-CN-region-traveled.tmg02
FRO-region-traveled.tmg02
GLP-region-traveled.tmg02
HKG-region-traveled.tmg02
KOR-region-traveled.tmg02
MEX-EMEX-region-traveled.tmg02
MEX-GTO-region-traveled.tmg02
MEX-NAY-region-traveled.tmg02
NZL-region-traveled.tmg02
RKS-region-traveled.tmg02
RUS-region-traveled.tmg02
SGP-region-traveled.tmg02
SPM-region-traveled.tmg02
THA-region-traveled.tmg02
TUR-region-traveled.tmg02
TWN-region-traveled.tmg02
ARE-region-traveled.tmg01
AS-region-traveled.tmg01
AUS-ACT-region-traveled.tmg01
AUS-SA-region-traveled.tmg01
AUS-VIC-region-traveled.tmg01
AUS-WA-region-traveled.tmg01
AZE-region-traveled.tmg01
BGD-region-traveled.tmg01
BHR-region-traveled.tmg01
BLR-region-traveled.tmg01
BWA-region-traveled.tmg01
CHN-GD-region-traveled.tmg01
CHN-HA-region-traveled.tmg01
CHN-HE-region-traveled.tmg01
CHN-SH-region-traveled.tmg01
CHN-YN-region-traveled.tmg01
CYM-region-traveled.tmg01
CYP-region-traveled.tmg01
EGY-region-traveled.tmg01
GEO-region-traveled.tmg01
IDN-region-traveled.tmg01
IMN-region-traveled.tmg01
IND-MH-region-traveled.tmg01
IND-country-traveled.tmg01
JAM-region-traveled.tmg01
JEY-region-traveled.tmg01
JOR-region-traveled.tmg01
JPN-region-traveled.tmg01
KAZ-region-traveled.tmg01
KGZ-region-traveled.tmg01
KHM-region-traveled.tmg01
MDA-region-traveled.tmg01
MEX-CHIH-region-traveled.tmg01
MEX-DF-region-traveled.tmg01
MEX-HGO-region-traveled.tmg01
MEX-MICH-region-traveled.tmg01
MEX-PUE-region-traveled.tmg01
MEX-QRO-region-traveled.tmg01
MEX-SON-region-traveled.tmg01
MEX-TLAX-region-traveled.tmg01
MEX-VER-region-traveled.tmg01
MTQ-region-traveled.tmg01
MYS-region-traveled.tmg01
NAM-region-traveled.tmg01
NPL-region-traveled.tmg01
PYF-region-traveled.tmg01
QAT-region-traveled.tmg01
TTO-region-traveled.tmg01
UKR-country-traveled.tmg01
UKR-region-traveled.tmg01
UZB-region-traveled.tmg01
VNM-region-traveled.tmg01
ZAF-region-traveled.tmg01
ZMB-region-traveled.tmg01
ZWE-region-traveled.tmg01
Title: Re: Project Statistics
Post by: si404 on May 22, 2019, 02:17:40 pm
Related to that, if I can get a test DB to be more usable, can those test systems be moved out of the production DB?
No! There's no point hiding them when it's easier to make them go live, which I hope to do by the end of the month.
Title: Re: Project Statistics
Post by: Jim on May 22, 2019, 02:20:24 pm
Related to that, if I can get a test DB to be more usable, can those test systems be moved out of the production DB?
No! There's no point hiding them when it's easier to make them go live, which I hope to do by the end of the month.

Sounds like a good plan to me, thanks.
Title: Re: Project Statistics
Post by: michih on May 22, 2019, 02:44:13 pm
Related to that, if I can get a test DB to be more usable, can those test systems be moved out of the production DB?
No! There's no point hiding them when it's easier to make them go live, which I hope to do by the end of the month.

? tmtest can be used with exactly the same data as the production db but we can "play" with it as desired, e.g. adding future regions to check that data is fine.

However, thanks for working on going live with "splitting France" :)
Title: Re: Project Statistics
Post by: michih on August 27, 2019, 01:30:48 pm
We have 100 preview systems now (235 active and 12 devel systems).
Title: Re: Project Statistics
Post by: Jim on August 27, 2019, 01:50:28 pm
We have 100 preview systems now (235 active and 12 devel systems).

I'd be very happy if we could convince everyone to focus on peer review of preview systems to get them activated rather than developing more new systems.
Title: Re: Project Statistics
Post by: si404 on August 28, 2019, 11:09:48 am
I'd be very happy if we could convince everyone to focus on peer review of preview systems to get them activated rather than developing more new systems.
That's my aim at least (yes, I know I just made a handful of systems preview, but that's part of the activation process) :P
Title: Re: Project Statistics
Post by: michih on September 06, 2019, 01:58:18 pm
We have 250 users now.
With the next site update, we'll also have 250 active systems :)

Upcoming milestones: 50,000 preview+active routes and 1,000,000 miles in active systems.
Title: Re: Project Statistics
Post by: mapcat on September 06, 2019, 08:21:09 pm
250* users  ;)
Title: Re: Project Statistics
Post by: si404 on September 07, 2019, 03:47:28 am
we'll also have 250 active systems
251!

We're 72,058 miles away from 1,000,000 on active systems, with 4,385 coming in next pull. So 67,673 miles to go. Which is probably about 10 system activations time (depending, of course, on which systems, but I'm making educated guesses).
Title: Re: Project Statistics
Post by: michih on September 07, 2019, 04:52:03 am
250* users  ;)

List files, not travelers ;)
Title: Re: Project Statistics
Post by: michih on September 07, 2019, 10:43:38 am
we'll also have 250 active systems
251!

Yes, but no! I just wrote that we reach a milestone. I knew that it would be 251 but: http://travelmapping.net

The number of active systems was 245 yesterday. The number of preview systems was 91 yesterday.
You've activated six systems.
The number of active systems is 250 today. The number of preview systems is 86 today.
Sorry, I don't get it what went wrong...
Title: Re: Project Statistics
Post by: yakra on September 12, 2019, 01:38:15 pm
We have one single segment that carries 9 concurrent routes:

IN I-465 46 47
IN I-69FutInd 47(465) 46(465)
IN IN37 I-465(47) I-465(46)
IN IN67 I-465(47) I-465(46)
IN US31 47(465) 46(465)
IN US36 I-465(47) I-465(46)
IN US40 I-465(47) I-465(46)
IN US52 I-465(46) I-465(47)
IN US421 I-465(47) I-465(46)
Title: Re: Project Statistics
Post by: osu-lsu on September 12, 2019, 10:38:08 pm
We have one single segment that carries 9 concurrent routes:

IN I-465 46 47
IN I-69FutInd 47(465) 46(465)
IN IN37 I-465(47) I-465(46)
IN IN67 I-465(47) I-465(46)
IN US31 47(465) 46(465)
IN US36 I-465(47) I-465(46)
IN US40 I-465(47) I-465(46)
IN US52 I-465(46) I-465(47)
IN US421 I-465(47) I-465(46)


Of course it would be I-465 around Indy.  ::)
Title: Re: Project Statistics
Post by: CharlotteAllisonCDTG on September 13, 2019, 12:56:32 pm
Are there any other seven-highway concurrencies?  I know of one in Georgia (if you count one unsigned highway).
Title: Re: Project Statistics
Post by: rickmastfan67 on September 18, 2019, 12:58:10 am
Are there any other seven-highway concurrencies?  I know of one in Georgia (if you count one unsigned highway).

This one in GA?  https://goo.gl/maps/H9tjfrsJxzfXqMmJ8

All 7 are signed. (US-1, US-23, US-301, GA-4, GA-15, GA-23, GA-121)
Title: Re: Project Statistics
Post by: US 89 on October 06, 2019, 01:19:50 am
Are there any other seven-highway concurrencies?  I know of one in Georgia (if you count one unsigned highway).

This one in GA?  https://goo.gl/maps/H9tjfrsJxzfXqMmJ8

All 7 are signed. (US-1, US-23, US-301, GA-4, GA-15, GA-23, GA-121)

There's a concurrency in Athens between GA 10 Loop, US 29, US 78, US 129, US 441, GA 8, GA 15, and the unsigned GA 422, which makes eight highways.
Title: Re: Project Statistics
Post by: CharlotteAllisonCDTG on October 06, 2019, 10:20:11 am
This was the concurrency I was thinking of.