Where does IOcrPageObjectModel live in the IronOCR API?

IOcrPageObjectModel is an interface in the IronOcr namespace, shipped in IronOcr.dll. It extends a generic IDocumentPageObjectModel along with IBounded and IJsonSerializable.

How do you get an IOcrPageObjectModel in IronOCR?

Read the ObjectModel property on an OcrResult.Page. After IronTesseract.Read returns an OcrResult, index into one of its pages and access ObjectModel to obtain the page's object model.

Interface IOcrPageObjectModel

Object model for a PDF page

Namespace: IronOcr

Assembly: IronOcr.dll

Syntax

public interface IOcrPageObjectModel

When code needs a structured view of one OCR'd page rather than its flat text, IOcrPageObjectModel is the contract that supplies it. It models a page as a document object, so a consumer can treat the recognized content as positioned, bounded objects and serialize that structure to JSON. It is what OcrResult.Page hands back when asked for its object model.

A developer does not construct this type. You receive it from the ObjectModel property on an OcrResult.Page, after IronTesseract.Read has produced an OcrResult and you have indexed into one of its pages. Holding the interface rather than a concrete page model keeps the consumer decoupled from IronOCR's internal page representation.

The contract is composed from the interfaces it extends rather than a long member list of its own. It builds on a generic document-page object model, IBounded for the page's bounding geometry, and IJsonSerializable so the page structure can be written out as JSON for storage or downstream tooling. Reach for the object model when flat Text is not enough and the layout of the page matters.

The read results how-to traverses a result's pages and their content, and the searchable PDF how-to shows the page structure put to use.