Developer Mode
Most API calls need the ID of something you can already see in the FlyPix app: a raster, a project, a vector, your tenant. Developer mode adds options to copy those IDs, or a whole item as JSON, straight from the app, so you don't have to look them up through the API first.
The options stay hidden until you turn developer mode on, so the app looks the same as before for anyone who doesn't need them.
Turning it on
- Open the account menu in the top-right corner of the header and choose Preferences.
- In the Developer section, switch on Developer Mode.
The setting is saved with your other preferences, and you can switch it off again the same way.
What it adds
When developer mode is on, the options menu (⋮) of a single item ends with a section of developer options, below a divider:
| Option | Copies |
|---|---|
| Copy Item ID | The item's own ID, for example Copy Raster ID. |
| Copy Project ID | The ID of the project the item belongs to, if it has one. |
| Copy Tenant ID | The ID of the tenant the item belongs to. |
| Copy as JSON | The whole item, as the app holds it, formatted as JSON. |
| Copy Polygon as WKB | The item's shape, for annotations, regions and suggestions. |
A notification confirms each copy. If the browser blocks access to the clipboard, the notification says so instead.
These options appear on the menus of:
- Data management: rasters, folders and workspaces.
- Dashboard: projects, models, datasets, frozen datasets and running trainings.
- Workspace: vectors, classes, regions, scenes, models, running trainings and running inferences. When you right-click an annotation, a region or a suggestion on the map, the menu also gets the developer options. For an annotation, they include Copy Vector ID.
Copy Polygon as WKB copies the shape as base64-encoded
WKB,
the same encoding the API uses for polygon fields, so you can paste it straight into a
request. Map coordinates are in EPSG:3857 (Web Mercator); WKB itself does not record the
projection.
Some items don't record which tenant they belong to, such as folders, vectors and classes. For those, Copy Tenant ID copies the ID of the tenant you are working in. You can only open these items from within that tenant.
Account menu
The account menu (top right of the header, and the menu next to your tenant on the Profile page) ends with Copy User ID and Copy Tenant ID. These copy your own user ID and the ID of the tenant you are working in.
Each tenant in the account menu's tenant list also gets its own ⋮ menu with Copy Tenant ID and Copy as JSON, so you can copy another tenant's details without switching to it.
Raster details
The Raster Details window has a ⋮ menu next to its title with the raster's developer options. It also has Copy GeoData as JSON, which copies the raster's geographic data: its extent, dimensions and channels.
GeoSense and Help Desk conversations
Each message gets a ⋮ menu beside it, next to its send time. It appears when you hover over the message, and stays visible on touch screens:
- Copy Content copies the message's content, Copy Contexts the context it was sent with, and Copy Message as JSON the whole message. Copy Message ID and Copy Thread ID copy those IDs.
- Below a divider, Copy Conversation Content and Copy Conversation as JSON copy the whole conversation. Copy Conversation Content copies every message's content in order, separated by a line of dashes.
The contexts themselves (the chips below a message, or above the message you are writing) are too small for a button, so right-click a context for Copy Context as JSON.
In a GeoSense conversation, Copy Content copies the message exactly as GeoSense
exchanges it: the XML-like markup described in
Message Format, not the rendered text. Copied
contexts are the context types described in
Message Context, with camelCase keys (artifactId)
where the API uses snake_case (artifact_id). See
GeoSense Message Formatting for the full contract. Help Desk
messages are copied as the support system sends them.
When developer mode is off, messages have no ⋮ menu, and right-clicking a context opens your browser's usual menu.
On a phone or tablet, a long-press on a context opens its menu on Android. iOS (iPhone and iPad) doesn't support this, so use a message's ⋮ menu and its Copy Contexts instead.
Using what you copy
IDs work anywhere the API reference asks for one. You can also include them when you contact support about a specific item.
Copy as JSON copies an item the way the FlyPix app represents it internally. Field names and the set of fields can differ from what the API returns for the same item. Use it to inspect or share an item, and use the API reference for the exact shape of API requests and responses.