xPress Model

The GEOSPAN xPress model is designed as a subset of the existing gPro tier. No new API calls or endpoints are introduced, while others are limited in the xPress model tier. This approach simplifies integration for integrators who require fast models with the basic functionality, while maintaining compatibility with the broader gPro API.

For an overview of why and when to order an xPress model, see Introducing xPress. Here, learn how to order an xPress model, and read about the technical details and differences between the xPress model and the gPro model.

Choose the roof_model_express product

To get an xPress model, use the products value roof_model_express when creating an order.

Check in real time for gPro API support of the xPress model: when you have ordered the roof_model_express product, any gPro API that does not support the xPress product—for example model sharing—returns a 415.

Note

The gPro overview has a dropdown in the upper right corner of the screen that toggles between gPro and xPress models for easy filtering.

gPro and xPress model versions dropdown gPro and xPress model versions dropdown

The same endpoints and underlying infrastructure mean you can easily transition to the full gPro tier without additional integration, as the foundational API structure and calls remain consistent.

What’s different in the xPress model?

  • Order the xPress model: Use roof_model_express for your products value when you make a call to the /order API to get faster computations and reduced processing costs without sacrificing accuracy for basic requirements.
  • DOCX-Only file export: xPress exports only the DOCX format.
  • No Job sharing support: You cannot share the xPress model through the API or the Geospan gSuite user interface.
  • 2D-Only structure coordinates: Structure coordinates in the xPress API are flattened to 2D, optimizing data processing and storage for applications that do not require 3D representations.