agek-tileserverdata (0.1.0)

Converts SLPK/TPKX/IFC/RVT/LAS/raster/mesh packages uploaded to an S3 input bucket into i3sREST or tile format in an output bucket, and (optionally) publishes the result as an ArcGIS Enterprise service item. Built for both the browser SPA and machine-to-machine callers (FME and similar) — both use the exact same endpoints and header scheme below.

Every endpoint except the health probes requires:

X-Portal-Token is obtained the same way for a browser SPA and a machine client — generateToken (client=requestip) for a scripted/scheduled caller, or an ArcGIS API Key for unattended production automation.

Two ways to run the full pipeline — pick whichever shape suits the integration. Both end up enqueuing the exact same background job with the same parameters.

Option A — one call

POST /upload (multipart form) with auto_publish=true, service_name, and X-Portal-Token set does everything: streams the file to S3, then immediately enqueues extraction + publish. The response is a Server-Sent-Events stream:

data: {"status": "uploading", "bytes_uploaded": 1048576, "total": 52428800, "progress_pct": 2.0}
...
data: {"status": "uploaded", "input_key": "tileserver/input/model.slpk"}
data: {"status": "queued", "task_id": "abc123", "task_name": "process_slpk", "poll_url": "/tasks/abc123"}

Take task_id from the final queued event and poll GET /tasks/{task_id}.

Option B — two calls (upload, then publish separately)

Useful for confirming the upload succeeded before committing to a publish, letting a user pick the service name/sharing afterwards, or re-publishing an already-uploaded file.

1. POST /upload with auto_publish omitted (defaults to false) — same SSE stream as above, but it stops after the uploaded event. Keep the input_key from that event.
2. POST /publish with {"portal_url", "input_key", "service_name", ...} and X-Portal-Token — enqueues the same extraction+publish job. Responds immediately with a TaskModel (id / poll_url), as plain JSON rather than a stream.

GET /tasks/{task_id} works for a task from either option above. Poll until status is SUCCESS or FAILURE; result then holds either the published service info (PackageResult: service_url, item_id, ...) or a FailureResult.

.slpk .tpkx .las/.laz/.zlas .tif/.tiff/.img/.ecw .ifc/.rvt .osgb/.obj/.dae. An .ifc/.rvt may also be uploaded as a .zip bundle together with georeferencing sidecars (.prj/.wld3) — the model file inside determines the task.

POST /tasks/process_slpk / POST /tasks/process_tpkx and their matching GET endpoints are deprecated — use POST /publish and GET /tasks/{task_id} instead, which work for every supported file type.

Upload a package to S3 and run it through extraction + publish, in one call or two. See the description above for the full sequence.

Look up past jobs and fetch a permanent link back to an originally-uploaded source file.

Liveness/readiness probes and a startup-config diagnostic view — not part of the integration flow.