All versions of TPE use a standard form of URL. You can construct your own URLs (e.g. via a scripting tool or by manually editing the address in your browser) and use them freely - they'll open in the web app, iOS or Android apps as normal.
Here's an example:
In this example, the parameters are used as follows:
|ll||63.939897,-17.369803||Red map pin location. Latitude, longitude coordinate pair in decimal degrees. Negative longitude is west.|
|center||63.9586,-17.3145||Center of map. Latitude, longitude coordinate pair in decimal degrees. Negative longitude is west.|
|z||9||Zoom level. Value between 0 and 21 (max value may be lower with certain map types selected)|
|spn||0.64,3.09||Span. Decimal degree pair showing latitude and longitude span. Equivalent to Zoom level. Use either.|
Date/time. Date and time in format YYYYMMDDHHnnss+ZZZZ.
'%2B' is the URL-encoded form of '+'
|sll||63.972628,-17.052924||Secondary pin location (optional). Latitude, longitude coordinate pair in decimal degrees. Negative longitude is west.|
Advanced Example (iOS)
A more advanced example from TPE for iOS that shows some additional parameters:
Here's a list of the new parameters not mentioned above:
|sh||5.00||Primary object height in metres. e.g. the height of the camera above the ground|
|ch||30.00||Secondary object height in metres. e.g. the height of a building|
|seo||-2.00||Primary elevation offset in metres. Correction to the automatically determined elevation above sea level for the primary map pin location.|
|ceo||4.00||Secondary elevation offset in metres. Correction to the automatically determined elevation above sea level for the secondary map pin location.|
Note: in settings in the iOS app, you can reverse the sense of primary and secondary depending on whether you are using the primary pin as the camera or subject location. The mappings shown in the table above from primary or secondary are reversed accordingly.