Traveller Map - Poster/POST Example

Explanation

The Poster API supports the HTTP POST method for submitting custom sector data for rendering. Three variations are supported:

POST text/plain Content
POST File Attachment
POST Form Data

Usage:

http://travellermap.com/Poster.aspx?sector=SECTORNAME[&scale=N][&subsector=X][&rotation=R][&options=O]

Parameters:

sector - sector name, URL encoded (required)
scale - scale in pixels/parsec (default is 64)
subsector - subsector index (A-P) (optional; if not specified, whole sector is rendered)
rotation - rotate the image, 1 for 90° clockwise, 2 for 180°, 3 for 90° counterclockwise
options - rendering style options

Notes:

Image format depends on selected options ("Candy" produces JPEG, otherwise GIF)
If subsector is specified, only that subsector is rendered
Scale is pixels/parsec

POST text/plain Content

This cannot be done through a Web page except via XMLHttpRequest, which doesn't make a distinct demo than the examples below. However, it is the simplest format for most HTTP clients to work with.

POST with encoding type "text/plain"
Sector data is specified the content
Options specified in the URL query
Only sector data (.SEC) is supported, not metadata (borders, etc)

POST File Attachment

POST with encoding type "multipart/form-data"
Sector data is specified as an attachment named "file"
Options specified in the URL query and/or POST variables
Content is assumed to be text/plain, but in the future additional content types may be supported (e.g. "x-application/x-traveller-sector-v5")

Sector data:

Metadata in XML format may optionally be specified as an attachment named "metadata"
For an example, see FarFrontiers.xml; an aggregate of the data may be seen at here (WARNING: large file!)
Use the SectorMetaData API to fetch the site's XML metadata for a given sector

XML Metadata:

Additional options:

Scale:
Subsector:
Rotation:
Options:
Hex Numbers:
Style:
Format: