run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-26 16:56:36 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Feature Request: result_type='markdown' return page number #158

New Issue
Closed
opened 2026-02-16 00:17:01 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 00:17:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @galvangoh on GitHub (Jun 24, 2024).

Hello LlamaParse team,

Is it possible to allow LlamaParse to also return, by default, page number?

What I realised after some testing is that the parser treats individual page of a document separately. Currently the results are already giving a page separator but if the md results were to be chunked, indexed and queried by LLM, the LLM is unable to figure out the correct page number the document has.

Originally created by @galvangoh on GitHub (Jun 24, 2024). Hello LlamaParse team, Is it possible to allow LlamaParse to also return, by default, page number? What I realised after some testing is that the parser treats individual page of a document separately. Currently the results are already giving a page separator but if the md results were to be chunked, indexed and queried by LLM, the LLM is unable to figure out the correct page number the document has.
yindo closed this issue 2026-02-16 00:17:01 -05:00
yindo commented 2026-02-16 00:17:01 -05:00
Author
Owner
Copy Link
Copy Source

@adreichert commented on GitHub (Jun 25, 2024):

I'm assuming that you want the to have both the text of each page in markdown and the corresponding page number in memory at one time, and you don't want guess the page number after splitting on \n---\n.

I'm not part of Llama Index, so I can only tell you the approach we've taken: use the JSON output generated by get_json_result(). This splits the text by page and creates a structure with both Markdown text and page number. The following work with GPT enabled.

    parser = llama_parse.LlamaParse(
        result_type='markdown',
        api_key=LLAMAPARSE_API_KEY,
        gpt4o_mode=True,
        gpt4o_api_key=OPENAI_API_KEY,
        ignore_errors=False,
    )
    result = parser.get_json_result('<file.pdf>')[0]['pages']
    n = len(result)
    print(f"Pages: {n}")
    for page in result:
        # Use the "md" and "page" fields
        print(page["md"])
        print(f"Page {page['page']} of {n}")

Inside the for loop you'd merge the page number and text according to your needs.

@adreichert commented on GitHub (Jun 25, 2024): I'm assuming that you want the to have both the text of each page in markdown and the corresponding page number in memory at one time, and you don't want guess the page number after splitting on `\n---\n`. I'm not part of Llama Index, so I can only tell you the approach we've taken: use the JSON output generated by `get_json_result()`. This splits the text by page and creates a structure with both Markdown text and page number. The following work with GPT enabled. ``` parser = llama_parse.LlamaParse( result_type='markdown', api_key=LLAMAPARSE_API_KEY, gpt4o_mode=True, gpt4o_api_key=OPENAI_API_KEY, ignore_errors=False, ) result = parser.get_json_result('<file.pdf>')[0]['pages'] n = len(result) print(f"Pages: {n}") for page in result: # Use the "md" and "page" fields print(page["md"]) print(f"Page {page['page']} of {n}") ``` Inside the `for` loop you'd merge the page number and text according to your needs.
yindo commented 2026-02-16 00:17:01 -05:00
Author
Owner
Copy Link
Copy Source

@galvangoh commented on GitHub (Jun 25, 2024):

@adreichert thank you for sharing your solution. I knew about the get_json_result() feature which returns the both the page number and md results. However, I am using AzStorageBlobReader which does not support that (sorry should have also mentioned this when opening the issue).

@galvangoh commented on GitHub (Jun 25, 2024): @adreichert thank you for sharing your solution. I knew about the `get_json_result()` feature which returns the both the page number and md results. However, I am using [`AzStorageBlobReader`](https://llamahub.ai/l/readers/llama-index-readers-azstorage-blob?from=) which does not support that (sorry should have also mentioned this when opening the issue).
yindo commented 2026-02-16 00:17:01 -05:00
Author
Owner
Copy Link
Copy Source

@adreichert commented on GitHub (Jun 25, 2024):

Thank you for providing more information.

This repo comprises a wrapper for the REST API. It might benefit you to raise the request in repo run-llama/llama_index, which seems to contain the bulk of the parsing code. This is where class AzStorageBlobReader is in defined (link).

Sorry I cannot be of more help. Good luck.

@adreichert commented on GitHub (Jun 25, 2024): Thank you for providing more information. This repo comprises a wrapper for the REST API. It might benefit you to raise the request in repo [`run-llama/llama_index`](https://github.com/run-llama/llama_index/tree/main), which seems to contain the bulk of the parsing code. This is where class `AzStorageBlobReader` is in defined [(link)](https://github.com/run-llama/llama_index/blob/7d3bb2b502c95e0677013ac935992d4cb1e36d9d/llama-index-integrations/readers/llama-index-readers-azstorage-blob/llama_index/readers/azstorage_blob/base.py#L23). Sorry I cannot be of more help. Good luck.
yindo commented 2026-02-16 00:17:01 -05:00
Author
Owner
Copy Link
Copy Source

@galvangoh commented on GitHub (Jun 25, 2024):

@adreichert thank you for your suggestions.

@galvangoh commented on GitHub (Jun 25, 2024): @adreichert thank you for your suggestions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#158
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?