Nav Icon

Back Arrow Postholer.Com
Resource for Hikers

Login/Register
Log in or register for full access to site features & free downloads

COVID-19 Status & Maps
Daily status of the COVID-19 pandemic and its relationship to the trails.

Printed Maps & App
Stay found. Stay informead. Our premium printed topographic maps and matching app for a once in a lifetime adventure

OnLine Data Books
Free online data books for your favorite trail, distances, elevation, climate, way points, terrain & fauna

Google Maps
GPS aware Google maps, your location, topo, hybrid, satellite, trail track, way points, road, weather/snow overlays

Active Fires & Smoke
Know before you go! Get the lastest active fire & smoke information for your favorite trail

Snow Conditions
Get the lastest snow conditions for your favorite trail. Quantity, coverage, SNODAS, MODIS, historical and multi-year comparisons

Trip Planners
Create an extensive hike plan easily configurable to your hiking style. Distances, days, resupply, access points, etc

Trail Animals
Exhaustive resource for species ranges along your favorite trail. Includes amphibians, birds, mammals and reptiles.

Complete Gear Lists
Hundreds of complete gear lists by those that walked the walk.

Elevations Profiles
The big picture. Single elevation profile of your favorite trail.

Journal Tools
Search for a journal, create a journal, add/edit an entry, configure your journal, EMail updates, integrated Google trail map, PLB locations and more

Wall Maps
Print out your favorite trail to 6 feet high. Elevation chart and resupply locations.

Postholer Forum
Source for trail and site information or just talk about your favorite trail

Reflect vs OWS Requests

So, what's the difference? OWS is a formal standard that must be adhered to for proper results. Reflect is a non-standard service initialized with reasonable values, where possible, when required values are omitted.

Reflect makes life a whole lot easier. It will accept WMS and WFS requests. I've shamelessly taken the idea from geoserver and recreated it here. The single biggest advantage is sizing images. For WMS you are required to pass a height and width value, as well as a bounding box. The problem comes when trying to match the aspect ratio of your bounding box to the image dimensions. Without calculating it first you almost certainly end up with a pinched or squashed image. The calculation is trivial, but a pain having to do it every time, for every image size.

Give reflect a height or width only and the missing dimension will be calculated with the proper aspect ratio, regardless of input SRS. Reflect will also use popular settings if omitted. Following is an example.

Reflect example:OWS example:
   http://gis.postholer.com/services/reflect?
      layers=stateLines,trace
      &trail_id=2
      &height=300
      &t_srs=EPSG:900913
      &bbox=-126,24,-66,50
   http://gis.postholer.com/services/ows?
      service=WMS
      &request=GetMap
      &version=1.1.1
      &layers=stateLines,trace
      &trail_id=2
      &srs=EPSG:900913
      &bbox=-14026255.8,2753408.1,-7347086.4,6446275.8
      &format=image/png
      &height=300
      &width=300
reflect request WMS request

Another feature of reflect is the t_srs value. This will take your bounding box in lat/lon format and transform it to the t_srs SRS. This is handy for creating EPSG:900913 images (square pixels) while doing a conversion from your lat/lon to the image SRS. Lat/lon is assumed to be EPSG:4269. For reflect the default service=WMS and default request=GetMap.

That's it!

Postholer.Com © 2005-2020 - Sitemap - W3C