User talk:Vhasler

Help needed list:

Pin balloons for the infobox Google map are too big to see names. Any way to make smaller/more compact?--Vhasler 21:09, 9 March 2011 (EST)

The infobox should just be the trail head. If you want a detailed map, add another embedded Google map under the "map" section of the main article. Then it can be as big as needed. --Tim 06:47, 18 March 2011 (EDT)

How to upload kml files to show routes on Google Maps? Your "Sinking Creek" shows a folder I don't know how to reach? Have GPX file for Warriors' Backbone and Fall Creek Loop trails I was going to covert in Google Earth to kml.--Vhasler 16:26, 13 March 2011 (EDT)

Send KML's to me for the time being and I'll get them there. --Tim 06:47, 18 March 2011 (EDT)

For parks, I am thinking of creating recommended hike routes since some of the trails (like Pine at BMP) are just connectors, thus not really worthy of their own trail page. Willing to discuss further.--Vhasler 16:26, 13 March 2011 (EDT)

You can also create route pages that refer to several individual trail pages --Tim 06:47, 18 March 2011 (EDT)

How to make park map on "Grayson Highlands State Park" page smaller? Can it be put to the right of the Google Map?--Vhasler 22:08, 14 March 2011 (EDT)

See Grayson Highlands State Park, simply add a "|200px" or whatever size reduction to the file tag --Tim 06:47, 18 March 2011 (EDT)

I see that you copied the AT trail g-map from the main website. Need to understand how you plan to merge it with the main list or keep separate? Some of the destinations on the current list are really along the AT.--Vhasler 06:35, 16 March 2011 (EDT)

Not sure what I have planned, I do want to get the AT stuff over here as well for the same reasons as the other trails (easy editing, consistent,...). I'm thinking eventually The AT link on the main page would dump people over to here. I will eventually convert the AT trail map to use the embedded pins instead of a KML for easy modification. --Tim 06:47, 18 March 2011 (EDT)

Pins on the g-maps are to be for the trailhead - right? Jake has them all over. Was going to move the state park pins to the headquarters buildings.--Vhasler 06:35, 16 March 2011 (EDT)

Regular embedded gmaps can have whatever and as much as we want, pictures, features, etc... I'd say that infoboxes be just for trail heads --Tim 06:47, 18 March 2011 (EDT)

Standard for coordinates in infobox. Been using decimal formal DD.DDDDD,-DD.DDDDD, but more use to working in DD MM.MMM,-DD MM.MMM style. Yes, it would involve another conversion, but likely able to read right off the GPSr. So what is the standard? Add it to the creating trail info.--Vhasler 07:52, 16 March 2011 (EDT)

You have to be careful about not messing up the info boxes. See WPSP Devil's Backbone. The link to bring them over to Google maps so they can do a destination routing is now broken. My personal preference is the decimal format, but mostly because I know that's what Google maps understand. Not sure if it can tolerate DMS. Then if we display DMS but the pins in GMaps needs decimal, then we would be setting ourselves up for confusion. --Tim 06:47, 18 March 2011 (EDT)

How to delete a no longer used page? "Sinking Waters" is now "WPSP Sinking Waters" and "Devil's Backbone" is "WPSP Devil's Backbone" to maintain the consistency of having park prefix on their trails. Needed as "Overlook" and "Lakeside" are common to several parks. Have fixed all broken links, so the redirect pages are no longer required.--Vhasler 07:33, 17 March 2011 (EDT)

I'll take care of that, need sysop prvileges. --Tim 06:47, 18 March 2011 (EDT)