TEHCC Wiki:Community portal: Difference between revisions
Jump to navigation
Jump to search
(add note about clearing up trail distances) |
No edit summary |
||
Line 15: | Line 15: | ||
**Remove prefixes from trails of systems/parks - semantic wiki easily connects them, don't need prefix anymore and it messes with the page name. | **Remove prefixes from trails of systems/parks - semantic wiki easily connects them, don't need prefix anymore and it messes with the page name. | ||
**Start listing and reviewing campgrounds/campsites? - Mostly for my/Tim's interest. I've started my own list and I thought why not to share. | **Start listing and reviewing campgrounds/campsites? - Mostly for my/Tim's interest. I've started my own list and I thought why not to share. | ||
**Trail Infobox updates | **Trail Infobox updates | ||
***Modify trail infobox to have distance from Kingsport, Johnson City, and Bristol - this would allow the automatic trail list to have it | ***Modify trail infobox to have distance from Kingsport, Johnson City, and Bristol - this would allow the automatic trail list to have it | ||
Line 25: | Line 24: | ||
***Make it more units tolerant, instead of forced mi/hr etc, allow page entry of anything which the site will interpret as needed | ***Make it more units tolerant, instead of forced mi/hr etc, allow page entry of anything which the site will interpret as needed | ||
***Clear up "Distance" field - I propose for Out-n-back and segments, it's the one-way length, loops would be full trip. This seems consistent with most hike guides | ***Clear up "Distance" field - I propose for Out-n-back and segments, it's the one-way length, loops would be full trip. This seems consistent with most hike guides | ||
**Create Park Trail template - should be simple #ask query referencing PAGENAME | **Create Park Trail template - should be simple #ask query referencing PAGENAME | ||
**Modify trails list and trails map templates to automatically get it using #ask query | **Modify trails list and trails map templates to automatically get it using #ask query |
Revision as of 20:36, 6 September 2015
Things We are/I am working on and thinking about
- Current efforts
- Conversion from googlemap to display_map extension - most done, need to ferret out the rest. Since I can't search for it I've been using the list of oldest last edits.
- Adding "park" parameter to trail Infoboxes. This allows wiki functions to easily find/list all trails within a park. Currently conflicted on Warriors Path State Park and its Mountain Bike Trail system. Should they be two separate "parks" or one park? Both? Question is how we want it to show up on the park's page of trails. Separate or all as one? A separate optional parameter of "group" - but how would the auto trails list work? All trails without a group or park, all parks and groups? Can that be done?
- As they're found, start marking trail pages that need cleanup if you don't have the time when you see it. So far I have created Category:No Trail KML and Category:Stub. I've thought about, needs pictures, better map pins, description details, etc...
- Someday/Maybe - Things to discuss
- Start a "trail routes" or "trail plan" page type to create suggested trip plans. Use the new semantic wiki to be able to easily find and link on park pages separate from the trails list (prime culprit is Bays Mountain which has many trails only accessible from other trails)
- Create a standard Parks page (i.e. separate from trails category and Infobox)? Something as many are using the trail Infobox which I think messes things up for the semantic queries.
- Cleanup categories - do we need the specified category if the semantic property assignments already do that?
- Setup GPS (GPX?) waypoint and track downloads. Need to investigate options with new display_map extension
- Run Special Pages->Unused Files to find unreferenced files. Delete or add as appropriate. Ones used solely for embedded Google Maps don't show as used, add to page anyway to get it off the list (to make finding real problems easier) and make finding the pictures easier
- Run Special Pages->Broken links and fix problems found
- Remove prefixes from trails of systems/parks - semantic wiki easily connects them, don't need prefix anymore and it messes with the page name.
- Start listing and reviewing campgrounds/campsites? - Mostly for my/Tim's interest. I've started my own list and I thought why not to share.
- Trail Infobox updates
- Modify trail infobox to have distance from Kingsport, Johnson City, and Bristol - this would allow the automatic trail list to have it
- Add coordinates for parking and trail head, one line, trail type (out and back vs loop), include terminus coordinates if appropriate
- Modify to hide unused fields - Park done, which others?
- Remove nearest medical?
- Investigate how "trail use" would best work with semantic wiki so we can include it on trails lists (park and system)
- Remove use of custom coordinate extension and just use semantic features, also convert to lat,lon format
- Make it more units tolerant, instead of forced mi/hr etc, allow page entry of anything which the site will interpret as needed
- Clear up "Distance" field - I propose for Out-n-back and segments, it's the one-way length, loops would be full trip. This seems consistent with most hike guides
- Create Park Trail template - should be simple #ask query referencing PAGENAME
- Modify trails list and trails map templates to automatically get it using #ask query
- How to only get parks and trails with no parks?...
- Return the Talk tab to its original/real name and give us a spot to actually "talk" about the trail. Trip reports then their own page (one for each report or one for all reports on a trail?) then use #ask query to list them on the trail page. Trail page could list last X trip reports in descending date.
- Move map pins and details to semantic properties and use semantic maps to list them? This would allow easier listing elsewhere. Is it a problem that needs this change?
- Create a park template/style/IB something...