ZOO-Project 2.1.0

In the Azure Portal, open Marketplace, search for ZOO-Project, select the SecureAnyCloud publisher entry, and click Create.

On the Networking tab, attach a network security group that allows inbound TCP 22 from your management IP range and TCP 80 from your client networks (the WPS and OGC API endpoints). Click Review + create, wait for validation, then click Create. Deployment takes around two minutes.

# Accept the Marketplace terms once per subscription (required before the first CLI deploy)
az vm image terms accept --urn sac1647283583153:zoo-project-ubuntu-24-04:default:latest
az vm create \
  --resource-group my-geo-rg \
  --name zoo-project \
  --image sac1647283583153:zoo-project-ubuntu-24-04:default:latest \
  --size Standard_B2s \
  --admin-username azureuser \
  --generate-ssh-keys \
  --public-ip-sku Standard
# Open port 80 to your client network:
az vm open-port --resource-group my-geo-rg --name zoo-project --port 80 --priority 900

SSH in as azureuser. Confirm that the FastCGI gateway and nginx are both active and that the health endpoint responds:

systemctl is-active nginx zoo-fcgiwrap curl -s -o /dev/null -w 'health: HTTP %{http_code}\n' http://localhost/healthz

Expected output:

active active health: HTTP 200

The per-VM endpoint URLs are recorded at /root/zoo-project-info.txt. They are resolved to this VM's public IP on first boot.

Ask the server which processing services it offers, using the classic OGC WPS 1.0.0 interface.

curl -s "http://localhost/cgi-bin/zoo_loader.cgi?service=WPS&version=1.0.0&request=GetCapabilities" -o /tmp/wps-capabilities.xml head -8 /tmp/wps-capabilities.xml

The response is a wps:Capabilities XML document. This command lists the advertised process identifiers:

curl -s "http://localhost/cgi-bin/zoo_loader.cgi?service=WPS&version=1.0.0&request=GetCapabilities" \
  | grep -oE '<ows:Identifier>[^<]+' | sed 's/<ows:Identifier>/ - /'

HelloPy is the simplest process. It is a Python service that takes a literal string input and returns a welcome message, and it proves the Execute pipeline end to end:

curl -s "http://localhost/cgi-bin/zoo_loader.cgi?service=WPS&version=1.0.0&request=Execute&Identifier=HelloPy&DataInputs=a=sac&RawDataOutput=Result"

Expected output:

Hello sac from Python World !

Buffer is a real geospatial process built on GDAL and GEOS. Give it a GeoJSON polygon and a buffer distance, and it returns the buffered geometry as GML. In this example, a 10 by 10 square is buffered outward by 1 unit. Note the resulting bounding box, -1,-1 to 11,11:

curl -s -G "http://localhost/cgi-bin/zoo_loader.cgi" \
  --data-urlencode 'service=WPS' \
  --data-urlencode 'version=1.0.0' \
  --data-urlencode 'request=Execute' \
  --data-urlencode 'Identifier=Buffer' \
  --data-urlencode 'DataInputs=InputPolygon={"type":"Polygon","coordinates":[[[0,0],[0,10],[10,10],[10,0],[0,0]]]}@mimeType=application/json;BufferDistance=1' \
  --data-urlencode 'RawDataOutput=Result' -o /tmp/buffer-result.gml head -12 /tmp/buffer-result.gml

ZOO-Project also serves the modern OGC API - Processes interface at /ogc-api/. This command lists the processes collection as JSON:

curl -s http://localhost/ogc-api/processes \
  | python3 -c 'import sys,json; d=json.load(sys.stdin); print("numberTotal:", d["numberTotal"]); [print(" -", p["id"]) for p in d["processes"][:12]]'

This command retrieves a single process description:

curl -s http://localhost/ogc-api/processes/Buffer \
  | python3 -c 'import sys,json; d=json.load(sys.stdin); print(d["id"], "-", d["title"])'

The OGC API landing document (http://localhost/ogc-api/) links the conformance, processes and jobs resources. Each process is also available as HTML at /ogc-api/processes/<id>.html.

• Server configuration: /usr/lib/cgi-bin/main.cfg is the ZOO-Kernel main configuration (server metadata, temp paths, GDAL/PROJ environment). On first boot, the advertised server host is set to this VM's public IP.
• Services directory: /usr/lib/cgi-bin/. Each process is a .zcfg descriptor plus its service implementation (.zo shared object for the compiled OGR/GDAL services, .py for Python services). Add your own services here by dropping in a .zcfg and its implementation.
• FastCGI gateway: zoo-fcgiwrap.service runs fcgiwrap as www-data on unix:/run/zoo-project/fcgiwrap.sock, and nginx proxies to it. After changing services, restart with sudo systemctl restart zoo-fcgiwrap nginx.
• Web server: /etc/nginx/sites-available/zoo-project routes /cgi-bin/, /ogc-api/, /healthz and the static landing page.