Flight Analysts · Step 1

Publish a flight in the catalog

Publishing makes a closed flight visible in the catalog. You choose who may get it and attach a GeoXACML policy. That policy is signed into every certificate issued for the flight, so choose it carefully: a later edit does not change certificates already in customers' wallets.

Before you publish

Only closed flights can be published. Open flights appear in the list but are disabled and marked — open. It is good practice to check the flight first:

  • The operator closed the flight with a seal (the manifest's close reason is sealed), or you accept an unsealed flight knowingly.
  • The geoNFT was minted: the operator console shows NFT on Fabric, or the QGIS plugin returns Verified against the ledger.
  • The flight's area and time match what you are going to promise in the catalog.

Publish

  1. Sign in to portal.geonft.eu with your passkey and open Publish.
  2. Flight: choose the flight. Each entry shows the flight name the operator gave it and its deployment id, for example survey (dep-3fa85f64-…).

  3. Listing: choose

    • Included in the subscription — every active subscriber can pick up a license; or
    • Classified — customers must request access and you decide each request.
  4. GeoXACML policy: paste the policy document (required). See below.
  5. Press Publish.

The flight now appears in the Catalog with its listing. The portal stores a snapshot of the flight's label, times, area and datastreams, so the catalog keeps working even if Connected Systems is briefly unavailable.

The GeoXACML policy

Every published flight carries a GeoXACML 3 policy. It is the contract between you and the customer: it states under which conditions an observation of the flight may be validated. A geo-fence, for example, is written inside the policy; it is not a separate setting.

  • The portal stores the policy exactly as you paste it, byte for byte, and does not evaluate it.
  • When a customer picks up a certificate, those exact bytes become the certificate's policy attribute and are covered by the issuer's signature.
  • When the policy is evaluated, the revealed copy from the customer's wallet is used, never the copy on the offer. An edit after issuing therefore has no effect on certificates already issued.
  • Each observation is evaluated separately: the resource is the flight's deployment id plus the observation's geometry, the action is validate. Only Permit lets the observation proceed to ledger verification. An observation without a geometry is Indeterminate.

A minimal policy that permits validation everywhere:

<Policy xmlns="urn:oasis:names:tc:xacml:3.0:core:schema:wd-17"><Decision>Permit</Decision></Policy>

A geo-fenced policy permits validation only for observations inside an area. The sketch below shows the structure; use the function and data-type identifiers of the GeoXACML 3 decision point your organisation runs.

<Policy xmlns="urn:oasis:names:tc:xacml:3.0:core:schema:wd-17"
        PolicyId="urn:geonft:policy:dep-3fa85f64:munich-centre"
        RuleCombiningAlgId="urn:oasis:names:tc:xacml:3.0:rule-combining-algorithm:deny-unless-permit"
        Version="1.0">
  <Description>Validate observations inside the Munich city-centre fence</Description>
  <Target/>
  <Rule RuleId="inside-fence" Effect="Permit">
    <Condition>
      <Apply FunctionId="urn:ogc:def:function:geoxacml:3.0:geometry-within">
        <Apply FunctionId="urn:ogc:def:function:geoxacml:3.0:geometry-one-and-only">
          <AttributeDesignator Category="urn:oasis:names:tc:xacml:3.0:attribute-category:resource"
              AttributeId="urn:ogc:def:geoxacml:3.0:resource:geometry"
              DataType="urn:ogc:def:geoxacml:3.0:data-type:geometry" MustBePresent="true"/>
        </Apply>
        <AttributeValue DataType="urn:ogc:def:geoxacml:3.0:data-type:geometry">
          <gml:Polygon xmlns:gml="http://www.opengis.net/gml/3.2" srsName="EPSG:4326">
            <gml:exterior><gml:LinearRing>
              <gml:posList>48.1340 11.5790 48.1340 11.5850 48.1365 11.5850 48.1365 11.5790 48.1340 11.5790</gml:posList>
            </gml:LinearRing></gml:exterior>
          </gml:Polygon>
        </AttributeValue>
      </Apply>
    </Condition>
  </Rule>
</Policy>
Policies are permanent per certificate

Test a policy before you publish. To change the terms for future customers, withdraw the flight and publish it again with the new policy; existing certificates keep the old one until they are revoked.

What customers see

ListingCatalog showsAccess columnButton
Included in the subscriptionIncludedSubscriptionGet license with an active subscription, otherwise Subscribe
ClassifiedClassifiedRequestRequest access

Neither path issues a certificate by itself. Customers come back to their order and pick the certificate up into their wallet; see the consumer guide.