Current tent views are from the side (lengthwise) and from the front. An overhead or footprint view is also important. Tents with large footprints have more restrictive pitching options than tents with smaller footprints.

Support two person functionality.

Key issues:

• Different heights
• Irregular floor shapes
• Assymetric fly shapes

The Tent class needs configuration to mark tents as discontinued and/or state that there is no longer a valid link to the manufacturer's website.

Example: .setUrl("https://zpacks.com/products/hexamid-pocket-tarp") is an invalid link. ZPacks now sells a pocket tarp with doors.

User report:

The units of measurement could do well with some more consistency. On the home screen, weight is shown as "g", whereas on the recommend screen, it's displayed as "gm". The latter is confusing, as the letter m usually means meter. (Example: Nm, Newtonmeters, as a unit of torque)

Additionally, I would put the metric/imperial checkbox somewhere at top and have it applied globally. A slide switch would be neat, something like the one you can sometimes see on websites with a facebook like button integration. When I opened the page for the first time, the checkbox for metric was unchecked, yet all of the units were in cm. On the recommend page, only imperial units are displayed without any option to switch to metric.

Pyramid tents usually have a trekking pole in the center area of the tent. Tent.setFrontInteriorPeakOffset() specifies this peak. The person sits to the right of this peak based on the result of the Tent.frontMiddleOfSittingSpot() function.

setFrontInteriorPeakOffset should be redefined to be the position of a trekking pole.
The trekking pole should be drawn in the front-facing diagram.

Tents are currently configured in a massive gTents global variable. This would be more elegant and maintainable if a proper schema were defined (yaml perhaps) and each tent was defined in its own file. The key point is that this data should continue be statically loaded from a single request.