(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FDst3CEo.png&hash=78c5068dd4e7ea213fcacd114bb6b5e1de357661)
Hi all. I am excited to announce that my Highway☆ app is now available as a free download in the app store!
You can get it https://itunes.apple.com/us/app/highway-star/id1209913631?ls=1&mt=8 (https://itunes.apple.com/us/app/highway-star/id1209913631?ls=1&mt=8). Please do download it if you feel so inclined. And a big thank you to all who helped test and gave suggestions. Here is a screenshot from the final version.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F2SwbUit.jpg&hash=8646bb0438cf085c55af0eb9a40bfc2ff7d9c968)
So with 1.0 out in the world, here are what I see as the next steps:
1) Android version
2) Travel Mapping!
As always, feedback is welcome.
Cheers 😺
-Amanda (CatSynth)
Which routes are included in it? I made it a point the other day to drive home via KY 1144 and a portion of KY 498. Neither route registered nor gave me any points.
Oh dear. Thanks for letting me know. It should cover as many as possible, but I'm sure there are missing ones, especially in states I don't know so well. It's a mixture of a few different data sources (Open Street Maps, Wikipedia, etc.).
I will review Kentucky this afternoon and see what's up. Fortunately, adding new ones is a server/backend issue so doesn't require an app update.
Catsynth, do you want to know of highways that aren't shown? I'm in Louisiana, and it's much like Kentucky: tons of state routes, many of them short in length.
There were a handful in my hometown not shown. It's mostly the major, multi-parish highways that show up.
iPhone
Quote from: bassoon1986 on May 25, 2017, 06:20:31 PM
Catsynth, do you want to know of highways that aren't shown? I'm in Louisiana, and it's much like Kentucky: tons of state routes, many of them short in length.
There were a handful in my hometown not shown. It's mostly the major, multi-parish highways that show up.
iPhone
Yes please. Louisiana is definitely one of the states that gave me a tough time.
Quote from: hbelkins on May 25, 2017, 04:39:00 PM
Which routes are included in it? I made it a point the other day to drive home via KY 1144 and a portion of KY 498. Neither route registered nor gave me any points.
Hi! I added KY 498 and KY 1144 manually (and awarded you the points). That's quite a complex task in the current architecture, so I can't make a habit of it. It's best if I can ingest a canonical list of routes at once via a script. Any suggestions on a good data source for all KY routes is welcome.
Thanks
-Amanda
Quote from: catsynth on May 27, 2017, 02:22:06 PM
Quote from: hbelkins on May 25, 2017, 04:39:00 PM
Which routes are included in it? I made it a point the other day to drive home via KY 1144 and a portion of KY 498. Neither route registered nor gave me any points.
Hi! I added KY 498 and KY 1144 manually (and awarded you the points). That's quite a complex task in the current architecture, so I can't make a habit of it. It's best if I can ingest a canonical list of routes at once via a script. Any suggestions on a good data source for all KY routes is welcome.
Thanks
-Amanda
I appreciate that, and I wasn't really angling for points, just pointing out something that I thought you'd be interested in.
Which leads me to ask, how do you wish to receive reports of missing routes? I haven't yet downloaded the non-beta app but I didn't see a function in the test versions to do so.
As for a list of Kentucky routes, at one time there was a listing of truck weight classifications somewhere on KYTC's website that allowed sorting by route number. Since we're well into the 3000s for state routes (not including the 6000-series frontage roads, most of which are not posted except for far western Kentucky; or the hidden 9000-series for the parkways) and the system is constantly evolving as new routes are built and sections of the old routes are renumbered, that's probably the best option if you can find some way to import that information. I don't know where on the site that information is located, however. Possibly on the Division of Planning's section of the site.
Quote from: hbelkins on May 27, 2017, 03:26:35 PM
Quote from: catsynth on May 27, 2017, 02:22:06 PM
Quote from: hbelkins on May 25, 2017, 04:39:00 PM
Which routes are included in it? I made it a point the other day to drive home via KY 1144 and a portion of KY 498. Neither route registered nor gave me any points.
Hi! I added KY 498 and KY 1144 manually (and awarded you the points). That's quite a complex task in the current architecture, so I can't make a habit of it. It's best if I can ingest a canonical list of routes at once via a script. Any suggestions on a good data source for all KY routes is welcome.
Thanks
-Amanda
I appreciate that, and I wasn't really angling for points, just pointing out something that I thought you'd be interested in.
Which leads me to ask, how do you wish to receive reports of missing routes? I haven't yet downloaded the non-beta app but I didn't see a function in the test versions to do so.
As for a list of Kentucky routes, at one time there was a listing of truck weight classifications somewhere on KYTC's website that allowed sorting by route number. Since we're well into the 3000s for state routes (not including the 6000-series frontage roads, most of which are not posted except for far western Kentucky; or the hidden 9000-series for the parkways) and the system is constantly evolving as new routes are built and sections of the old routes are renumbered, that's probably the best option if you can find some way to import that information. I don't know where on the site that information is located, however. Possibly on the Division of Planning's section of the site.
Thanks, I appreciate the attention and support, so happy to add them [emoji3].
I don't have a specific button in the app for reporting missing highways yet. For now, I would suggest bundling them up in a support request (off of the MORE tab). I am also working on a way to automatically find misses in the algorithm, i.e., where a route candidate isn't matched properly.
And thanks for the info on the KYTC website! Will poke around and see what I can find.
-A
Quote from: bassoon1986 on May 25, 2017, 06:20:31 PM
Catsynth, do you want to know of highways that aren't shown? I'm in Louisiana, and it's much like Kentucky: tons of state routes, many of them short in length.
There were a handful in my hometown not shown. It's mostly the major, multi-parish highways that show up.
iPhone
I have a new system for locating and bulk-adding a lot of the missing short highways and such. I just added several hundred for Louisiana last night, and they now show up, like LA 998 in Belle Rose.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F5QqfoEj.jpg%3F1&hash=7c4211760dbc76b841e8baa29ae2a202651871d3)
(why this one? check out this article (http://www.catsynth.com/2011/09/fun-with-highways-la-998-belle-rose-louisiana/) :D)
I have also updated CT, DE, and NM. KY has a YUGE list, currently in the process of updating.
I went to Lexington today and the app picked up a bunch of 2xxx and 3xxx-series routes.
Incidentally, it didn't know I was driving on the four-lane Mountain Parkway but knew when I was in proximity to a 3xxx-series route.
I recall adding several KY parkways by hand. It's quite possible I missed the Mountain Parkway. Can add that one.
Bus. M-28 doesn't come up here in Michigan, yet it is a state-mainted highway. It didn't work in Explore nor when I was driving last night. (All of the business routes in Michigan are fully state highways).
H-63, a county highway appears when I scroll around on the Explore tab, but not any of the other county-designated highways like H-58. All of the BL/BS I-75s are coming up as if they were tagged as BS I-75 in Bay City, and the Bus. US 131s were coming up named after the list article on Wikipedia ("Business routes of U.S. Route 131"). US 127 didn't want to show on the Explore tab either. The three BL/BS I-196 appear missing as well.
Quote from: bulldog1979 on June 03, 2017, 01:30:03 PM
Bus. M-28 doesn't come up here in Michigan, yet it is a state-mainted highway. It didn't work in Explore nor when I was driving last night. (All of the business routes in Michigan are fully state highways).
H-63, a county highway appears when I scroll around on the Explore tab, but not any of the other county-designated highways like H-58. All of the BL/BS I-75s are coming up as if they were tagged as BS I-75 in Bay City, and the Bus. US 131s were coming up named after the list article on Wikipedia ("Business routes of U.S. Route 131"). US 127 didn't want to show on the Explore tab either. The three BL/BS I-196 appear missing as well.
Thanks for the info on those! We will review Michigan data. H-63 must have snuck in with recent updates ;).
A new update, 1.0.1 is now available in the app store!
On Sunday, June 4, I took a trip up to Grand Rapids, MI. I tested the app to make sure that it worked. There was one error that I caught on my phone... Indiana State Road 39 was caught twice... One that said SR 39 and the other one said IN 39...
Overall, great job on this app!!
Quote from: Great Lakes Roads on June 09, 2017, 02:42:46 PM
On Sunday, June 4, I took a trip up to Grand Rapids, MI. I tested the app to make sure that it worked. There was one error that I caught on my phone... Indiana State Road 39 was caught twice... One that said SR 39 and the other one said IN 39...
Overall, great job on this app!!
Aw, thanks! And hope it was a nice trip.
I ran into a similar redundancy on Friday here in California: both CA 16 and SR 16 registered simultaneously ;)
Pretty neat app; I downloaded it awhile ago, but just fired it up last night while watching TV. It immediately added DE 1 (which is OK because I'm about 100' from it where I sit), and also DE Alt 54, which to the best of my knowledge is at least half a mile away. Is it supposed to detect roads from that far away, or does the database have slightly incorrect info for Alt54 (which has its eastern end at DE 26). This is on my iPad, which doesn't have mobile internet.
Interesting that the overhead views are rather old-I'm guessing 2007 or so (based on the state of development of several lots near me).
Quote from: davewiecking on June 11, 2017, 12:46:06 PM
Pretty neat app; I downloaded it awhile ago, but just fired it up last night while watching TV. It immediately added DE 1 (which is OK because I'm about 100' from it where I sit), and also DE Alt 54, which to the best of my knowledge is at least half a mile away. Is it supposed to detect roads from that far away, or does the database have slightly incorrect info for Alt54 (which has its eastern end at DE 26). This is on my iPad, which doesn't have mobile internet.
Interesting that the overhead views are rather old-I'm guessing 2007 or so (based on the state of development of several lots near me).
It picks up roads that you're not actually on, but near. My experience yesterday bears that out. I was on KY 52 in Irvine, on the north side of the Kentucky River. The app picked up both KY 851 and KY 332x (there are a few 3000-series routes and I can't remember specifically which one) that are both on the other side of the river.
Also, if you have no cell signal, the app won't remember to add the roads. In Lee County, KY 52 intersects KY 1746 and KY 2453 in an area where there's no service. Those roads didn't show up when I reached an area with service.
Yes, it works by proximity to location. It was originally tuned from experience with a prototype on California freeways, but I might tighten the radius a bit in the future.
In terms of queuing up detections when no signal is present, that is a bit trickier to implement. But I will look into it for a future update :).
Re the proximity issue: might there be a way to make it user-selectable? Maybe just as a test version? Different folks could try different settings, and you might get some useful feedback. It just seems odd that I got credit for 2 roads without leaving the sofa; on the other hand I can imagine a situation where a California freeway is as wide as the distance from me to Alt DE54, so you need to build that kind of proximity into the App.
Hmm, that's a cool idea! I'll put a parameter for that in the next test version (though I am inclined to have a fixed value for app-store releases).
This week, focusing on the Android version, but will keep folks posted when the next iOS test version is ready. Any additional folks who want to get on the beta list are welcome :)
It looks like the app needs to be running in the foreground and in the "Live" page (not the "Me") page to pick up new routes... is that the case?
Also, a cool feature (but potentially a lot of work) is to have a Pokedex-like interface where all interstates are displayed, but the ones you haven't visited yet are just shadow shields. Same for US routes. ("gotta catch 'em all!")
Thanks for creating the app!
I gave this app a try on my last road trip. It picks up nearby roads nicely, but I also somehow got credit for US 258, which I was over 300 miles from at the time.
Quote from: kurumi on June 15, 2017, 01:41:26 AM
It looks like the app needs to be running in the foreground and in the "Live" page (not the "Me") page to pick up new routes... is that the case?
Also, a cool feature (but potentially a lot of work) is to have a Pokedex-like interface where all interstates are displayed, but the ones you haven't visited yet are just shadow shields. Same for US routes. ("gotta catch 'em all!")
Thanks for creating the app!
Thanks for the kind words. With respect to collecting while on different pages of the app, it *should* work at this point, though it doesn't automatically update the "Me" page in real time. I will log that as an enhancement for the next update.
With respect to the other "Gotta Catch-em All" feature, I definitely like it. It is a fair amount of work in terms of UX, but worth investigating :)
Quote from: fillup420 on June 15, 2017, 08:43:49 AM
I gave this app a try on my last road trip. It picks up nearby roads nicely, but I also somehow got credit for US 258, which I was over 300 miles from at the time.
Oh my, the radius is probably too large (as discussed in earlier posts), but it isn't *that* large :D
Feel free to report US 258 in the app (though posting here counts as a report as well).
Quote from: kurumi on June 15, 2017, 01:41:26 AM
It looks like the app needs to be running in the foreground and in the "Live" page (not the "Me") page to pick up new routes... is that the case?
That hasn't been the case with me. It seems to pick up roads when running in the background.
Quote from: hbelkins on June 15, 2017, 01:42:02 PM
Quote from: kurumi on June 15, 2017, 01:41:26 AM
It looks like the app needs to be running in the foreground and in the "Live" page (not the "Me") page to pick up new routes... is that the case?
If it picks up roads while on another page of the app, the "Live" icon should have one of those red dots on it.
That hasn't been the case with me. It seems to pick up roads when running in the background.
A new update is out today for beta users. It fixes a bug displaying larger scores, i.e., 1000+; and also tightens the window for discovery. On the Live view, it is now about 220m radius for the user's location. On Explore, it is the visible area on the screen but limited to 1.1km radius (so it doesn't try to find *everything* when zoomed way out).
If are not yet on the beta list and would like to be, please let me know. In any case, hoping to get an update in the store next week (before the July 4 holiday weekend).
I was in Pennsylvania for my cousin's graduation party... when I got into Pennsylvania, it didn't show Interstate 90 on my phone... can you go ahead and manually add that into my list?
Quote from: Great Lakes Roads on June 25, 2017, 09:51:34 PM
I was in Pennsylvania for my cousin's graduation party... when I got into Pennsylvania, it didn't show Interstate 90 on my phone... can you go ahead and manually add that into my list?
Yes, just fixed that one today! (There was a typo in the automated data for I-90 PA)
Quote from: catsynth on June 26, 2017, 12:32:21 AM
Quote from: Great Lakes Roads on June 25, 2017, 09:51:34 PM
I was in Pennsylvania for my cousin's graduation party... when I got into Pennsylvania, it didn't show Interstate 90 on my phone... can you go ahead and manually add that into my list?
Yes, just fixed that one today! (There was a typo in the automated data for I-90 PA)
And I should have read more carefully [emoji74]. Yes, happy to credit you I-90 in PA.
The new version (1.0.2) now available in the App Store!
Tighter window and improved detection, as well as improved display of scores, among other fixes.
Do you have to have the app actively open while driving or riding along a highway for it to pick up said highway? I ask because I left my phone awake (and plugged in) in the trunk of a motorcycle while riding tonight, but it didn't pick up US 141, perhaps because the phone went to sleep during the ride.
Quote from: bulldog1979 on June 29, 2017, 10:51:21 PM
Do you have to have the app actively open while driving or riding along a highway for it to pick up said highway? I ask because I left my phone awake (and plugged in) in the trunk of a motorcycle while riding tonight, but it didn't pick up US 141, perhaps because the phone went to sleep during the ride.
Yes, it currently needs to be open. Working on allowing background mode for a future update.
Quote from: catsynth on June 30, 2017, 01:49:09 PM
Quote from: bulldog1979 on June 29, 2017, 10:51:21 PM
Do you have to have the app actively open while driving or riding along a highway for it to pick up said highway? I ask because I left my phone awake (and plugged in) in the trunk of a motorcycle while riding tonight, but it didn't pick up US 141, perhaps because the phone went to sleep during the ride.
Yes, it currently needs to be open. Working on allowing background mode for a future update.
Then that (and a lack of cell signal in some places) is why the app missed a boatload of West Virginia state routes I was on today.
Quote from: hbelkins on June 30, 2017, 10:30:15 PM
Quote from: catsynth on June 30, 2017, 01:49:09 PM
Quote from: bulldog1979 on June 29, 2017, 10:51:21 PM
Do you have to have the app actively open while driving or riding along a highway for it to pick up said highway? I ask because I left my phone awake (and plugged in) in the trunk of a motorcycle while riding tonight, but it didn't pick up US 141, perhaps because the phone went to sleep during the ride.
Yes, it currently needs to be open. Working on allowing background mode for a future update.
Then that (and a lack of cell signal in some places) is why the app missed a boatload of West Virginia state routes I was on today.
Probably so. Offline tracking is going to a feature for the next major release as well. Sorry about the missed routes in WV.
Quote from: catsynth on June 30, 2017, 10:32:33 PM
Quote from: hbelkins on June 30, 2017, 10:30:15 PM
Quote from: catsynth on June 30, 2017, 01:49:09 PM
Quote from: bulldog1979 on June 29, 2017, 10:51:21 PM
Do you have to have the app actively open while driving or riding along a highway for it to pick up said highway? I ask because I left my phone awake (and plugged in) in the trunk of a motorcycle while riding tonight, but it didn't pick up US 141, perhaps because the phone went to sleep during the ride.
Yes, it currently needs to be open. Working on allowing background mode for a future update.
Then that (and a lack of cell signal in some places) is why the app missed a boatload of West Virginia state routes I was on today.
Probably so. Offline tracking is going to a feature for the next major release as well. Sorry about the missed routes in WV.
Would you consider doing a route "sweep", as in checking through the star data you have and go back and add the ones you've missed that haven't been reported, but without a total update?
Quote from: TheArkansasRoadgeek on July 01, 2017, 01:21:08 AM
Quote from: catsynth on June 30, 2017, 10:32:33 PM
Quote from: hbelkins on June 30, 2017, 10:30:15 PM
Quote from: catsynth on June 30, 2017, 01:49:09 PM
Quote from: bulldog1979 on June 29, 2017, 10:51:21 PM
Do you have to have the app actively open while driving or riding along a highway for it to pick up said highway? I ask because I left my phone awake (and plugged in) in the trunk of a motorcycle while riding tonight, but it didn't pick up US 141, perhaps because the phone went to sleep during the ride.
Yes, it currently needs to be open. Working on allowing background mode for a future update.
Then that (and a lack of cell signal in some places) is why the app missed a boatload of West Virginia state routes I was on today.
Probably so. Offline tracking is going to a feature for the next major release as well. Sorry about the missed routes in WV.
Would you consider doing a route "sweep", as in checking through the star data you have and go back and add the ones you've missed that haven't been reported, but without a total update?
I am not sure I completely understand. Can you clarify what data you are referring to?
Thanks
Android version progress update?
Quote from: JJBers on July 01, 2017, 01:22:15 PM
Android version progress update?
Working on it right now, actually :D. I hope to have an alpha version by next week. Please let me know if you would be interested in testing.
Quote from: catsynth on July 01, 2017, 01:53:42 PM
Quote from: JJBers on July 01, 2017, 01:22:15 PM
Android version progress update?
Working on it right now, actually :D. I hope to have an alpha version by next week. Please let me know if you would be interested in testing.
Sure! I'm already beta testing Google Maps, so I can easily handle another one
Quote from: JJBers on July 01, 2017, 02:35:41 PM
Quote from: catsynth on July 01, 2017, 01:53:42 PM
Quote from: JJBers on July 01, 2017, 01:22:15 PM
Android version progress update?
Working on it right now, actually :D. I hope to have an alpha version by next week. Please let me know if you would be interested in testing.
Sure! I'm already beta testing Google Maps, so I can easily handle another one
Also I have a question, is there a possible way to make it so you can insert travel highways without having the app to ping it, I already have a lot of traveled highways that I'll probably never travel again, so I was wondering if I could insert them to the profile, or not.
Quote from: JJBers on July 04, 2017, 11:35:00 PM
Quote from: JJBers on July 01, 2017, 02:35:41 PM
Quote from: catsynth on July 01, 2017, 01:53:42 PM
Quote from: JJBers on July 01, 2017, 01:22:15 PM
Android version progress update?
Working on it right now, actually :D. I hope to have an alpha version by next week. Please let me know if you would be interested in testing.
Sure! I'm already beta testing Google Maps, so I can easily handle another one
Also I have a question, is there a possible way to make it so you can insert travel highways without having the app to ping it, I already have a lot of traveled highways that I'll probably never travel again, so I was wondering if I could insert them to the profile, or not.
That is indeed an interesting question! There is no initial support for manual entry, but I'm thinking about how we might add that as part of the future Travel Mapping update...
Meanwhile, the Android version should be ready for initial beta testing by Monday. I'll probably start a separate thread for Android-specific issues and discussion.
Quote from: catsynth on July 07, 2017, 05:32:44 PM
Quote from: JJBers on July 04, 2017, 11:35:00 PM
Quote from: JJBers on July 01, 2017, 02:35:41 PM
Quote from: catsynth on July 01, 2017, 01:53:42 PM
Quote from: JJBers on July 01, 2017, 01:22:15 PM
Android version progress update?
Working on it right now, actually :D. I hope to have an alpha version by next week. Please let me know if you would be interested in testing.
Sure! I'm already beta testing Google Maps, so I can easily handle another one
Also I have a question, is there a possible way to make it so you can insert travel highways without having the app to ping it, I already have a lot of traveled highways that I'll probably never travel again, so I was wondering if I could insert them to the profile, or not.
That is indeed an interesting question! There is no initial support for manual entry, but I'm thinking about how we might add that as part of the future Travel Mapping update...
Meanwhile, the Android version should be ready for initial beta testing by Monday. I'll probably start a separate thread for Android-specific issues and discussion.
Is this going to be open or closed beta testing?
Sort of in between. Anyone in US + Canada welcome, but I need an email address for each tester to use with the Fabric.io Beta software that I use.
I'm actually ready to start distributing an initial build - main features in place, lots of ancillary features and formatting still in progress. If you PM me an email address you receive on your Android device, can send out a link to download soon :)
So, last week I went up to Minnesota for a mission trip up in Red Lake... I have a few things that you should probably fix on my list...
Missing shields- it appeared on my list, but does not show the shield itself (probably a glitch on my part):
US Highways: 14, 169, 2, 53, 61, 71 (all of those happened in Minnesota), 51 in Illinois
Wisconsin State Highway 26
Interstate 94 in Wisconsin
Just in case if you're wondering which roads I am missing, here it is... It's probably because either I wasn't paying attention or I had a weak signal or the app sometimes glitches out...
WI State Highway: 73, 58, 54, 95, 93, 169, 122
US Highway 151 in Wisconsin
US Highway 45 in Michigan
MN State Road: 200, 135, 61
MI State Road: 73, 183, 117, 93, 72, 61, 50, 78
If you can do that, that's great!! If not, then I will take a trip up there again someday...
Quote from: Great Lakes Roads on July 30, 2017, 02:46:01 PM
So, last week I went up to Minnesota for a mission trip up in Red Lake... I have a few things that you should probably fix on my list...
Missing shields- it appeared on my list, but does not show the shield itself (probably a glitch on my part):
US Highways: 14, 169, 2, 53, 61, 71 (all of those happened in Minnesota), 51 in Illinois
Wisconsin State Highway 26
Interstate 94 in Wisconsin
Just in case if you're wondering which roads I am missing, here it is... It's probably because either I wasn't paying attention or I had a weak signal or the app sometimes glitches out...
WI State Highway: 73, 58, 54, 95, 93, 169, 122
US Highway 151 in Wisconsin
US Highway 45 in Michigan
MN State Road: 200, 135, 61
MI State Road: 73, 183, 117, 93, 72, 61, 50, 78
If you can do that, that's great!! If not, then I will take a trip up there again someday...
I noticed a lot of TN/VA routes were missing, along with RI 78.
So I tested something out that worked well to get around the issue of tracking highways when I'm on the motorcycle. (It's essentially impossible to use the phone itself while riding.) I set my phone so it would not auto lock plugged it into an external battery. Then I left the phone in the trunk of the bike with the app open. This worked to snag me US 141, M-38 and M-26, but something went amiss and it did not pick up M-64. If you're adding these manually for me, I also would need US 2, US 141, WIS 70 and WIS 101 in Wisconsin plus US 2 in Michigan from Thursday night's ride, and I'm still waiting to claim Bus. M-28.
Hi all. Thanks for the missing-route reports! VA in particular is known to have quite a few gaps in our DB for some reason.
I will get to these and other "missing reports" soon, after I get the Android release out the door, hopefully next week :).
And yes, happy to credit the missing routes when reported...
-Amanda
Took a trip out towards Ohio earlier this week... (Columbus and Dayton, Ohio to be exact)... Also took a trip out to Ball State on my way back from Dayton, OH...
Routes that I missed because of low signal in the area:
Ohio State Route 196
Ohio State Route 385
Ohio State Route 245
U.S. 42
Ohio State Route 710
Ohio State Route 726
U.S. Route 40 in Indiana
Indiana State Road 37
Indiana State Road 213
Indiana State Road 14
BTW, on the next update, you should make the list go in this order: Interstates on top, U.S. routes in the middle, and state roads on the bottom for each state... and also on the next update, make the list of numbers from smallest to biggest (i.e. SR 1, SR 2, etc.)
New Version 1.1 in progress, with background highway-detection support!
I just sent out a preview to beta-testers.
Hi all!
I have *finally* had some time to get back to updates (pesky day job has been getting in the way).
a) A new iOS version will be submitted this week, with iOS 11 compatibility and other fixes.
b) I have deployed a new admin tool that will help me more efficiently respond to missing/missed highway requests. I have already started the processing of updating the database and crediting folks for missed routes.
Meanwhile, I have received and read bug reports and will be incorporating them into the next major releases for both platforms. Hoping to get started on the no-connectivity support, too.
As always, please let me know your thoughts, suggestions, concerns, etc.
Thanks!
-Amanda
I recently had to delete and reinstall the app on a couple of devices. When I tried to log in on the reinstalled versions using my Facebook credentials, it kept defaulting back to the login page. The problem seemingly resolved itself the next day, however.
Quote from: hbelkins on October 03, 2017, 12:22:50 PM
I recently had to delete and reinstall the app on a couple of devices. When I tried to log in on the reinstalled versions using my Facebook credentials, it kept defaulting back to the login page. The problem seemingly resolved itself the next day, however.
Was that by any chance last Thursday/Friday? The servers behind the app had a serious issue that fortunately, I was able to resolve.
Quote from: catsynth on October 03, 2017, 01:33:22 PM
Quote from: hbelkins on October 03, 2017, 12:22:50 PM
I recently had to delete and reinstall the app on a couple of devices. When I tried to log in on the reinstalled versions using my Facebook credentials, it kept defaulting back to the login page. The problem seemingly resolved itself the next day, however.
Was that by any chance last Thursday/Friday? The servers behind the app had a serious issue that fortunately, I was able to resolve.
Friday.
Quote from: hbelkins on October 03, 2017, 04:44:33 PM
Quote from: catsynth on October 03, 2017, 01:33:22 PM
Quote from: hbelkins on October 03, 2017, 12:22:50 PM
I recently had to delete and reinstall the app on a couple of devices. When I tried to log in on the reinstalled versions using my Facebook credentials, it kept defaulting back to the login page. The problem seemingly resolved itself the next day, however.
Yep, then definitely the server issue. Fixed Friday night.
Was that by any chance last Thursday/Friday? The servers behind the app had a serious issue that fortunately, I was able to resolve.
Friday.
1.1.1 is now available in the Apple App Store! Please update, especially if you have upgraded your device to iOS 11. (link is in my signature)
I am also caught up on missing-road reports that I had in my queue. Obviously, that will be an ongoing task...
Quote from: catsynth on October 06, 2017, 01:50:59 PM
1.1.1 is now available in the Apple App Store! Please update, especially if you have upgraded your device to iOS 11. (link is in my signature)
I am also caught up on missing-road reports that I had in my queue. Obviously, that will be an ongoing task...
I still need credit for M-64, M-67, M-203, US 2 in WI, US 141 in WI, WIS 70, and WIS 101 yet.
I got it! So, the onltcomplaint I have is the live camera is a little jerky...
If I could make a suggestion...
The app seems to be a data hog. I'm not sure how that could be remedied, but I'd think an option to view map only and not satellite view would help in that regard.
Quote from: hbelkins on October 07, 2017, 02:12:10 PM
If I could make a suggestion...
The app seems to be a data hog. I'm not sure how that could be remedied, but I'd think an option to view map only and not satellite view would help in that regard.
Yes, turning off Satellite will be added to the next feature release. That should reduce the data load quite a bit.
The app does send/receive route data frequently, depending on how fast one is moving, but the data sizes should be relatively small. There may be ways to optimize that as part of the new feature queuing up requests during poor connectivity, but not yet sure.
Hi all. I've been crazy busy with several projects in the last quarter of 2017, but I'm ready and excited to get back to the Highway☆ app!
It's been great to see people using it in the meantime, and watch myself sink in the leaderboard compared to others :D
On deck for both iOS and Android:
1) Offline/poor connectivity mode
2) Turn satellite/3D on and off on main view
Longer term:
3) Travel mapping
No specific time frames, but I'm hoping to get some things at least testing in January.
Thanks for your patience.
And here are some screenshots of the new iOS version! It should be ready for beta testing this coming week. If anyone wants to join in the next beta, please PM me.
(https://i.imgur.com/cFWxyu7.png)
(https://i.imgur.com/jguSLyT.png)
(https://i.imgur.com/49IeazQm.png)
Android version is already in progress as well, probably about a week behind iOS.
New iOS version is now available in the App Store.
https://itunes.apple.com/us/app/highway-star/id1209913631?mt=8
Android beta of 1.2.0 is out tonight.
I've been playing with the app now for about a week and like it. Catsynth posted in the TravelMapping forum (where I learned about it) seeking ways to incorporate TM data to enhance Highway☆, and suggested that this was the place for discussion.
It's not completely clear to me how TM data would/could be incorporated into this app, since its purpose seems to be different. H☆ users earn points for "encountering" different highways, not for travelling specific lengths of them; TM users record miles of travel on highways, which are considered "clinched" when a user has travelled all segments. Segments in TM exist between intersections with other highways, towns, and random points selected to make the files approximate the shape of the real-world road. Nothing in H☆ corresponds to those segments, which suggests that the framework for H☆'s route files would have to be completely redone. Also, H☆ gives users bonus credit for encountering a highway in additional counties (in the US), and there's no consideration given for county lines in TM.
As a TM user and now a Highway☆ user, I see a benefit to using both methods of tracking my travel, since they are different and serve different purposes. Since both provide rankings for users, and since this thread shows that Catsynth has already generously offered to manually add routes to users' files, it's conceivable that someone who's tracked travel on TM might wish to get credit for routes travelled prior to the development of H☆, which seems it would invite abuse. So I'd personally prefer to keep TM and H☆ separate.
Thank you for the thoughtful post, and sorry for my delay in replying (busy week).
I do definitely see differences between TM and H☆ in a lot of respects. But I do see some utility in extending the mission of H☆ to at least allow the creation of travel maps. On the H☆ side, one of the challenges is keeping it fun and engaging without always having to travel farther from home - I am thinking the ability to record and share trips is one way to do that. Another is clinching, but as pointed out, that is a much more difficult task. I'm up for doing architectural changes to the H☆ backend that would facilitate recording trips, although it does appear the goals or not completely the same as TM.
The point about people potentially abusing the system is a serious concern. At this point, I would not foresee people being allowed to bring past trips from TM or other sources into Highway☆
Open to more thoughts from both communities :)
Hi all. Just wanted to let you all know that I have broken ground on the next major release, which will include trip recording!
Basically, it's just a recording of the path of travel plus highways encountered along the way. It would be nice to filter it to ones actually traveled upon, if possible, but that is complicated.
Since this project is in the very early stages, there are both a lot of open questions, as well as opportunity for input from the community, so please do share your questions and ideas :)
Thanks!
- CatSynth (Amanda)
The iOS version of trip recording is now in early beta. If you are not in the beta program and would like to try it out, please message me.
There is still an open question of how to score trips, or whether to do so at all. Thoughts on this particular point are welcome.
Thanks!
Quote from: catsynth on March 28, 2018, 09:19:55 PM
The iOS version of trip recording is now in early beta. If you are not in the beta program and would like to try it out, please message me.
There is still an open question of how to score trips, or whether to do so at all. Thoughts on this particular point are welcome.
Thanks!
One point every mile? I'm not sure.
It also seems to not record highways after a while too. Not sure if it's a problem with Android 8.1 not sending out location data, or a app issue.
Did a quick jaunt into Vancouver a couple nights ago, up I-5 and back down I-205.
App missed US 30 Bypass (both times), OR 120 (this is ok, it's completely unsigned), and WA 501.
I also randomly got credit for OR 8 well before going to the Portland west metro, and the app doesn't pic up OR 224 or 212 when on I-205.
I also note a lack of singing OR 99W from I-405 or I-5 north of downtown, but given the ambiguity of 99W north of Tigard, I'm not concerned about it and won't be until ODOT advises me what to do for the Travel Mapping entry.
Thanks for the idea re: trip scoring.
If it's Android, was the app in the background when it stopped recording? I just got some reports of background service crashes.
Quote from: JJBers on June 07, 2018, 03:07:06 PM
Quote from: catsynth on March 28, 2018, 09:19:55 PM
The iOS version of trip recording is now in early beta. If you are not in the beta program and would like to try it out, please message me.
There is still an open question of how to score trips, or whether to do so at all. Thoughts on this particular point are welcome.
Thanks!
One point every mile? I'm not sure.
It also seems to not record highways after a while too. Not sure if it's a problem with Android 8.1 not sending out location data, or a app issue.
Thanks for the reports. I was actually in PDX a couple of months ago and had fun with the app myself there :)
OR 212 is definitely in the app, but I have observed inconsistency at freeway junctions so that may be it.
I will try and investigate the others as well.
Quote from: Bickendan on June 07, 2018, 06:59:29 PM
Did a quick jaunt into Vancouver a couple nights ago, up I-5 and back down I-205.
App missed US 30 Bypass (both times), OR 120 (this is ok, it's completely unsigned), and WA 501.
I also randomly got credit for OR 8 well before going to the Portland west metro, and the app doesn't pic up OR 224 or 212 when on I-205.
I also note a lack of singing OR 99W from I-405 or I-5 north of downtown, but given the ambiguity of 99W north of Tigard, I'm not concerned about it and won't be until ODOT advises me what to do for the Travel Mapping entry.
Downloading it now. It would be nice if this interfaced with tm.teresco.org. Maybe it does. I have not opened it yet - it's still downloading.
Quote from: tckma on July 19, 2018, 08:35:53 AM
Downloading it now. It would be nice if this interfaced with tm.teresco.org. Maybe it does. I have not opened it yet - it's still downloading.
Not yet, but that's absolutely on my list. The trip-recording feature was done with that in mind.