Travel Mapping
User Discussions => Other Discussion => Topic started by: Jim on May 02, 2017, 05:19:50 pm
-
My summer window of opportunity to do some TM development is almost here. I have plenty of ideas for enhancements and plenty of known problems that need attention, but I'm interested in hearing what all of you think should get some higher priority attention. I already know that I need to have a good chunk of my time focused on my related educational project, since that is how I can justify my ongoing efforts on TM in general, and I even have a small amount of funding to support it for the first time. But I also plan to do some TM-specific work that doesn't directly benefit the educational project.
-
Congratulations on making it through another semester. I know the feeling (my last final was today and everything's graded). And congratulations on the grant!
In no particular order, here are some things I hope you might try to tackle first:
Sorting of routes by mileage or clinched percentage (https://github.com/TravelMapping/Web/issues/112)
List of travelers who have traveled a system/region (https://github.com/TravelMapping/Web/issues/97)
New waypoint editor (https://github.com/TravelMapping/Web/issues/94)
Top Stats (https://github.com/TravelMapping/Web/issues/66)
Easier way to change default map colors for systems
-
On the Oregon side, I hope to fix the I-84/US 30 and I-5/OR 99 concurrency issues that the last Oregon update introduced (sorry, easily distracted by non-TM things :(), then work on the >OR 90 routes.
After that, start developing the (internal) Oregon Highway system to remove the non-signed Routes (that SHOULD be signed per ODOT) from the active system and map out the differences between the Highway and Route systems.
Hopefully all sooner than later.
-
A couple of small fixes on the stats -
1) instead of 'Miles Driven' and 'Routes Driven' it should be more mode-neutral 'Miles Traveled' and 'Routes Traveled'.
2) the ability to show figures in kilometres should be given.
Something I would find incredibly useful is the option to show intersecting routes.
-
A couple of small fixes on the stats -
1) instead of 'Miles Driven' and 'Routes Driven' it should be more mode-neutral 'Miles Traveled' and 'Routes Traveled'.
2) the ability to show figures in kilometres should be given.
Something I would find incredibly useful is the option to show intersecting routes.
The column title should probably be unit-neutral as well. "Length Traveled" was used in CHM with the ability to toggle between km and mi. below. Or the unit toggle could be in a more global position.
-
• ability to flag NMP FPs (https://github.com/TravelMapping/HighwayData/blob/master/nmpfps.log) in NMP files, E.G.
tx.geobushtpk@RenRd 32.997075 -96.67089 FP
tx.tx190@RenRd 32.997075 -96.670891 FP
• ability to display NMP FPs in the HDX with an alternate icon, E.G. a small yellow check-mark
-
Thanks. I think we have three categories. Each category has it's own priority for me.
A. Data processing bugs
Data processing is the base for data displayed in stats. I think the highest priority is having correct data. There are still some issues, e.g.:
- Overall rankings show "TBD" (https://github.com/TravelMapping/Web/issues/91)
- HB: Incorrect values in % column (traveled) (https://github.com/TravelMapping/Web/issues/103)
- ...
B. Features for users
1. km/mile conversion (https://github.com/TravelMapping/Web/issues/20)
Already started
2. Move domain name to travelmapping.net (http://tm.teresco.org/forum/index.php?topic=101)
Is it still planned? I have no problem with tm.teresco.org but we should establish travelmapping.net as soon as possible if we ever wanna do it.
3. Better way to select countries and regions:
* multi-region countries (https://github.com/TravelMapping/Web/issues/54)
* More accessible list or drop down box to select regions (https://github.com/TravelMapping/Web/issues/49)
* First step (https://github.com/TravelMapping/EduTools/pull/55) is already done
4. Open Highway Browser for specific routes from the map (https://github.com/TravelMapping/Web/issues/95)
I generally don't like the way how we do it now. I usually open the map of one or more regions displaying my data to see if my latest trip contains any new segment or I plan some detours for my next trip because of untraveled gaps.
5. Top Stats (https://github.com/TravelMapping/Web/issues/66)
6. List of travelers who have traveled a system/region (https://github.com/TravelMapping/Web/issues/97)
7. Better way to show update entry changes (http://tm.teresco.org/forum/index.php?topic=1849)
8. Front page design (http://tm.teresco.org/forum/index.php?topic=1851)
I think this might be done in combination with moving the domain name. If that's not planned now, my priority is quite low.
I have more ideas how we could design the "highway browser" or let's say "how to eliminate the HB" to make the handling easier but I think it's a way too far right now.
C. Features for developers
1. Automated update (https://github.com/TravelMapping/DataProcessing/issues/22)
- Minimum goal is that a contributor can check that the submitted (highway) data is correct and won't fail the next (manual) site update.
- Maximum goal is that an user sents an updated list file and the site is automatically updated
2. HDX integration
- File selection (https://github.com/TravelMapping/EduTools/pull/55) for graphs and NMP
- I wish that it would have the same code like the site itself. Every fix must be done twice, e.g. scroll bars are again visible in HDX etc.
3. Data check NMP (https://github.com/TravelMapping/Web/issues/187)
- Display errors on the site like other data checks
- Integrate "nmpfps.log" to "datacheckfps.csv"
- ...
4. Waypoint editor (https://github.com/TravelMapping/Web/issues/94)
Low priority right now but if CHM would be down one day, this would get the highest priority! Maybe we should do a first step?
5. Instruction Manual / "Rules"
Would get a high priority if CHM would be down one day. I think we should minimum "save the text" so that we don't have to start from scratch.
Of course, there are more minor issues reported on Github which might have less effort to be fixed.
-
When you go to a list of highways in a system - e.g. USAUS - and then click on a route that is in multiple states, it will give the per-state clinched/percentage but does not have an overall total for that route. Is that something that can be added?
-
When you go to a list of highways in a system - e.g. USAUS - and then click on a route that is in multiple states, it will give the per-state clinched/percentage but does not have an overall total for that route. Is that something that can be added?
That sounds useful to me. Can you give me an example of a URL that has the list but not the totals? I'm not always good at clicking around to find all of the ways to view our data.
-
http://tm.teresco.org/user/mapview.php?u=mapcat&rte=I-25 (http://tm.teresco.org/user/mapview.php?u=mapcat&rte=I-25)
-
http://tm.teresco.org/user/mapview.php?u=mapcat&rte=I-25 (http://tm.teresco.org/user/mapview.php?u=mapcat&rte=I-25)
I opened a GitHub issue to remind me (or, hopefully, other web front end volunteers) about this idea.
https://github.com/TravelMapping/Web/issues/174
-
4. Waypoint editor (https://github.com/TravelMapping/Web/issues/94)
Low priority right now but if CHM would be down one day, this would get the highest priority! Maybe we should do a first step?
Definitely. I decided to look at my CHM page recently just for fun and code on that site is already starting to break. I wouldn't count on it being around forever.
-
4. Waypoint editor (https://github.com/TravelMapping/Web/issues/94)
Low priority right now but if CHM would be down one day, this would get the highest priority! Maybe we should do a first step?
Definitely. I decided to look at my CHM page recently just for fun and stuff on that site is already starting to break. I wouldn't count on it being around forever.
EDIT: dammit, wanted to hit modify instead of quote and didn't notice. Mod fix?
-
Didn't we already have a makeshift waypoint editor somewhere around here?
-
Didn't we already have a makeshift waypoint editor somewhere around here?
http://tm.teresco.org/wptedit/wptedit.html
Yes, a first step - even with km/mi conversion - but I don't think that it can already be used. I've tried to import a route but it didn't work.
I thought about a more advanced "first step": useable but not yet 100% user-friendly/all wishes implemented.
-
Yeah, and the export doesn't quite work correctly. It doesn't format the code correctly.
-
Something else that could stand to be addressed over the summer is the backlog of threads in the Updates section of this forum. There's forum threads dating back to early 2016 that have not been resolved yet.
-
The first attempt at a TM waypoint editor was contributed by a user who I guess lost interest. It never got to the point of being especially useful.
-
I've saved a copy of Tim's CHM editor, in case his site ever goes down. If, in the future, Google's API ever changes & requires changes to the code again, I suppose we can open up the hood and tinker around.
For my $0.02, WPTedit (WPTEdit?) is full-featured, powerful, and intuitive (at least, for someone who's spent as much time with it as I have).
I've built up enough motor memory with it that's it's really second nature, and I have very little interest in switching to a new editing interface.
...If we want to add features and change things around, we can open up the hood and do that too.
I've idly thought of replacing [Load] [Load and Pan] with [Load] [Pan] [Zoom], but haven't looked into how I'd do it. Low priority; would require a Round Tuit.
The text, "Paste .wpt file lines in the text area above. Click Load and Pan above." could be parsed as "Paste .wpt file lines in the text area above. Click [Load] and [Pan] above." instead of "Paste .wpt file lines in the text area above. Click [Load and Pan] above." :) (Or, you know, like, edited to simply [Load])
-
I've saved a copy of Tim's CHM editor, in case his site ever goes down.
Good! That's the primary reason for having our own, simply because we can't depend on his lasting forever.
...If we want to add features and change things around, we can open up the hood and do that too.
I've idly thought of replacing [Load] [Load and Pan] with [Load] [Pan] [Zoom], but haven't looked into how I'd do it. Low priority; would require a Round Tuit.
The text, "Paste .wpt file lines in the text area above. Click Load and Pan above." could be parsed as "Paste .wpt file lines in the text area above. Click [Load] and [Pan] above." instead of "Paste .wpt file lines in the text area above. Click [Load and Pan] above." :) (Or, you know, like, edited to simply [Load])
Load-Pan-Zoom would be really helpful. Also, the elimination of obsolete map layers. It would be great to have it load OSM by default (or whatever a user wants as a default).
I wish I knew what "Th. Hwy." does, or means.
-
I wish I knew what "Th. Hwy." does, or means.
Me too!
-
Thickness of Highway. Basically the red lines move if you change the value.
-
I was remembering, apparently inaccurately, that we didn't have access to all of Tim's wptedit code in a usable form. It's good news if we can. In that case, the main reason I didn't just take a copy and put it on the TM site is probably that we don't have Tim's permission to do that with his code. I did get his permission to use his CHM code as a guide for what has become HDX, and that experience led to the development our current TM map infrastructure. However, I would not be comfortable just installing a copy of the current wptedit on our site, or using it as the starting code for an improved version, without permission.
-
True. But goldurnit, WPTedit is just Too Good.
ISTR you saying that you had a little communication with Tim after he went silent on the old forum... (What was it, about setting up infrastructure to allow multiple collaborators to ingest updates in his absence?) Have you heard from him at all since the TM project got underway, or is his disappearance just about that complete?
I've thought about how, if Tim were to come back, I'd make the "Please don't be upset; imitation is the sincerest form of flattery" argument -- CHM was just too good of an idea, and too well-loved by the roadgeek community, to just let it fade away and gather dust.
-
I did exchange a couple emails with Tim right before he disappeared for good about getting me set up to be able to process list file updates, bring in highway data updates, and run site updates. He implied that I was not the only person he was reaching out to about this, but I don't know who else was being considered/groomed to be able to help him out. But that was it for contact. Last message was in December 2014.
-
Thickness of Highway. Basically the red lines move if you change the value.
Are there times when we're supposed to change this?
-
Thickness of Highway. Basically the red lines move if you change the value.
Are there times when we're supposed to change this?
It was an experiment. I was told to loosen it a little to make better boundaries so that the files weren't too big and if we wanted the tighter stuff with dense shaping points at some point we could narrow it.
-
Grades for Spring 2018 should be submitted in the next 2 days or so, and I hope to be able to spend some of my time soon on TM fixes and enhancements. With the upcoming Google Maps API changes, perhaps a new WPT editor needs to be my focus. I kept hoping someone else would make one so I could focus on other things...