> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/nl/producttour-webapp/satellietmonitoring/planet-scope-3-m-dagelijks-beelden-bestellen.md). # Planet Scope (3 m dagelijks) beelden bestellen Bestel Planet-beelden in GeoPard om Rx-kaarten, scoutingskaarten en vegetatie-inzichten te maken. ### Planet-beelden U kunt Planet-beelden rechtstreeks bestellen vanuit de GeoPard-gebruikersinterface op een perceelpagina. De functie moet eerst voor uw account worden ingeschakeld. ### Videotutorial {% embed url="" %} Planet-beelden in GeoPard precisielandbouwsoftware {% endembed %}
1\. Ga naar de perceelpagina en klik op het **Planet** pictogram.

2\. Kies het gewenste datumbereik en klik op **Aanvragen**.

3\. Rechtsonder ziet u de verwerkingsstatus.

4\. Zodra de beeldmetadata van Planet is ontvangen, worden de beeldstatistieken weergegeven in de **Satellietmonitoring** lijst.

5\. Bestel daarna de Planet-satellietfoto die het beste past. Aanbevolen conditie: “*schoon land % – 100*”.

6\. Het downloaden van Planet is bezig.

7\. De Planet-afbeelding is beschikbaar voor verdere analyses.

Planet Scope 3m-beeld, opgeschaald door GeoPard

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.geopard.tech/geopard-tutorials/nl/producttour-webapp/satellietmonitoring/planet-scope-3-m-dagelijks-beelden-bestellen.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.