# Page Not Found

The URL `producteurs/amenagements-cyclables/guide-de-numerisation` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Guide de numérisation](https://doc.transport.data.gouv.fr/type-donnees/amenagements-cyclables/ressources/guide-de-numerisation.md)
- [Foire aux questions](https://doc.transport.data.gouv.fr/type-donnees/amenagements-cyclables/ressources/foire-aux-questions.md)
- [Ressources](https://doc.transport.data.gouv.fr/type-donnees/amenagements-cyclables/ressources.md)
- [Administration des données](https://doc.transport.data.gouv.fr/type-donnees/amenagements-cyclables/administration-des-donnees.md)
- [Guide de publication](https://doc.transport.data.gouv.fr/administration-des-donnees/guide-de-publication.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://doc.transport.data.gouv.fr/type-donnees/amenagements-cyclables/ressources/guide-de-numerisation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://doc.transport.data.gouv.fr/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://doc.transport.data.gouv.fr/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/type-donnees/amenagements-cyclables/ressources/guide-de-numerisation.md`).

You may also use `Accept: text/markdown` header for content negotiation.