https://drive.google.com/open?id=1X2p-NExZVjamjOi9GxGRDjnJZiELf9_D (https://drive.google.com/open?id=1X2p-NExZVjamjOi9GxGRDjnJZiELf9_D)
The concurrency of US 20 & NY 146 shows as unclinched, even though I have 100% of US 20 according to the stats on the right.
This is happening anywhere a clinched route is concurrent with a route I haven't entered into my .list.
Thanks - quick fix is in. It fixed the couple spots I checked. Let me know if you see it cropping up elsewhere.
I couldn't satisfy my curiosity on GitHub, as the code's not there yet. Which makes sense, with it all still undergoing heavy revision.
Gotta wonder how that happened, as siteupdate takes care of marking concurrencies as clinched, and all that info makes it into the DB.
I couldn't satisfy my curiosity on GitHub, as the code's not there yet. Which makes sense, with it all still undergoing heavy revision.
Even loading the initial graph (and table) with default zoom takes a few seconds. It's more when panning/zooming. Is it possible to display a "Loading..." message?
Working great now.
When the route table is more than one page long, if I have scrolled down the table a page or two and then pan to a new location, the table refreshes at approximately the same place rather than the top. Is that by design?
Would it be possible to give users the option of loading a scrollable mapview at the country or state level? Example: loading http://tmtest.teresco.org/user/mapview.php?units=miles&u=mapcat&rg=CO includes routes in surrounding regions. Entering "colorado" as the initial location and choosing "far"for the zoom level centers the map close to the center of Colorado, but the far northern part of the state is cut off. For someplace larger than Colorado, there's no way to see the entire region without zooming out, which requires a great deal of finesse and/or luck if you want the map to be perfectly centered.
Polylines do not appear to be stacked by tier.
Looking at my travels in Worcester MA, MA70 renders atop I-290.
Devel systems are showing up on the scrollable maps. I don't see them on pages without the &v parameter.
The reason it's expensive (as far as I can tell) is that it needs to look at both endpoints of each of 874,000+ segments and see if either is within the visible area of the map, and that we need to join the segments with waypoints (twice) to get locations, and with clinched to get whether each segment is clinched for the traveler.Thoughts on including beginning/end latitude/longitude directly in the segments table and eliminating the JOINs for a potential speedup?
-When you open the page, the first thing you see is something to enter in the lat/lon. Only after a few seconds of me looking at that and going "uhhh..." then I saw that I could enter in a city to go to. I think you should make this more prominent because nobody is going to know what lat/lon coordinates they want to start out at.
-Also, add an option to that screen to input username. It's kinda clunky to have to type that into the URL.
-When you open the page, the first thing you see is something to enter in the lat/lon. Only after a few seconds of me looking at that and going "uhhh..." then I saw that I could enter in a city to go to. I think you should make this more prominent because nobody is going to know what lat/lon coordinates they want to start out at.
-When you have the route table open, and the route table doesn't take up the whole length of the screen, you can't drag the map if you have the mouse cursor in that area.
The reason it's expensive (as far as I can tell) is that it needs to look at both endpoints of each of 874,000+ segments and see if either is within the visible area of the map, and that we need to join the segments with waypoints (twice) to get locations, and with clinched to get whether each segment is clinched for the traveler.Thoughts on including beginning/end latitude/longitude directly in the segments table and eliminating the JOINs for a potential speedup?
splitting out waypoint queries first then searching for segmentsGot a link to where this is done in the new code?
Quotesplitting out waypoint queries first then searching for segmentsGot a link to where this is done in the new code?
One weird thing I noticed: where state or US routes cross interstates, the state or US route draws on top of the interstate. Overlaps are handled correctly, and this doesn't happen between US and state routes, so it's a little odd. Regular mapview like we have for the regions doesn't do this.
Polylines do not appear to be stacked by tier.Already noted: https://github.com/TravelMapping/Web/issues/436
Looking at my travels in Worcester MA, MA70 renders atop I-290.
The tmtest version for scollable Mapview now has:
- rearranged and clarified search box.
- can click the map in the space below the routes table:D
Does anyone else want routes 100% clinched being indicated with a different backcolor similar to how traveled segments on the HB route table are indicated?
https://github.com/TravelMapping/Web/issues/440
(or a filter to "remove" all routes 100% clinched to ease seeing untraveled segments for planning trips?)
Does anyone else want routes 100% clinched being indicated with a different backcolor similar to how traveled segments on the HB route table are indicated?
https://github.com/TravelMapping/Web/issues/440
(or a filter to "remove" all routes 100% clinched to ease seeing untraveled segments for planning trips?)
I would support both.
Does anyone else want routes 100% clinched being indicated with a different backcolor similar to how traveled segments on the HB route table are indicated?I quite liked the color gradient from 0% -> 100% that CHM used to have.
https://github.com/TravelMapping/Web/issues/440
I like the idea of getting that information displayed, but is the Scrollable Mapview the best place for it?region.php & system.php perhaps?
Does anyone else want routes 100% clinched being indicated with a different backcolor similar to how traveled segments on the HB route table are indicated?I quite liked the color gradient from 0% -> 100% that CHM used to have.
https://github.com/TravelMapping/Web/issues/440
I like the idea of getting that information displayed, but is the Scrollable Mapview the best place for it?region.php & system.php perhaps?
I think it was something like a blue for 100%, down through the greens, yellows, oranges, to red for 0%. Whatever it was, I liked it.My memory as well. You can see it on the Wayback Machine. Someone posted a link recently; maybe it was in the Top Stats thread?
Does anyone else want routes 100% clinched being indicated with a different backcolor similar to how traveled segments on the HB route table are indicated?I quite liked the color gradient from 0% -> 100% that CHM used to have.
https://github.com/TravelMapping/Web/issues/440
It's been my goal to move in that direction site-wide where such shading makes sense. I think it was something like a blue for 100%, down through the greens, yellows, oranges, to red for 0%. Whatever it was, I liked it.Quote from: yakraI like the idea of getting that information displayed, but is the Scrollable Mapview the best place for it?region.php & system.php perhaps?
That might be better.
'd like to see it the very same way all over the site. Why to omit it on mapview only? Any performance issue?
'd like to see it the very same way all over the site. Why to omit it on mapview only? Any performance issue?
Two different things. I would want the shading of table entries based on % traveled everywhere it makes sense.
But the possibility of omitting 100% traveled routes, I don't think that belongs in Mapview.
I currently plan a little road trip for next weekend and I've realized that the reloading of the graph is not good. I always have to wait when I pan the map. Sure, it is necessary when I move "forward" but when I move back to the previous position, it is also reloaded. That's an disadvantage to the former mapview implementation. To be honest, I cannot plan my trip as before and need to use the old option now.
Albania Autoudhë (alba) |
ALB A1Thu 0.00 of 1.78 (0.0%)0.00 of 8.23 (0.0%) |
If the map area includes no routes at all, the route table shows one entry:
Albania Autoudhë (alba) ALB A1Thu 0.00 of 1.78 (0.0%)0.00 of 8.23 (0.0%)