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.