> For the complete documentation index, see [llms.txt](https://illust.gitbook.io/illust-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://illust.gitbook.io/illust-studio/resources/smart-contract-audits/geospatial-registry-litepaper/time.md). # Time Publishers may want to include a time component in a Placement - either a start date that the Placement should not be considered valid until, or an end date where the placement should no longer be considered valid. They can do this by including a startTime or endTime parameter in the placement call, encoded in a TimeRange struct. This data will be placed on the blockchain, and placeOf queries will not include placements if the current block is not within the specified time range. Note that, as the GSR only supports a single placement per owner per asset (to facilitate easy lookups), it is not possible to use this to encode multiple future placements (as with a traveling show). Each placement also records its placement time (from block.timestamp), and exposes this in events and in the GSR data, for time-based views of GSR data. Dapps can then show how a single piece moved over time. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://illust.gitbook.io/illust-studio/resources/smart-contract-audits/geospatial-registry-litepaper/time.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.