> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/fr/commandes-powershell/new-udmapmarker.md). # New-UDMapMarker New-UDMapMarker place un marqueur à une latitude et une longitude données, ou à partir de GeoJSON, sur un New-UDMap dans PowerShell Universal, avec des icônes et des fenêtres contextuelles personnalis ### Synopsis Crée un marqueur de carte. ### Syntaxe ```powershell New-UDMapMarker [-Id ] -Longitude -Latitude [-Attribution ] [-Opacity ] [-ZIndex ] [-Popup ] [-Icon ] [] New-UDMapMarker [-Id ] [-Attribution ] [-Opacity ] [-ZIndex ] [-Popup ] [-Icon ] -GeoJSON [] ``` ### Description Crée un marqueur de carte. ### Paramètres #### -Id L'id du marqueur de carte. La valeur par défaut est un nouveau GUID. ``` Required? false Position? named Default value ([Guid]::NewGuid()) Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Longitude La longitude du marqueur de carte. ``` Required? true Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Latitude La latitude du marqueur de carte. ``` Required? true Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Attribution L'attribution du marqueur de carte. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Opacity L'opacité du marqueur de carte. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -ZIndex L'index z du marqueur de carte. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Popup La fenêtre contextuelle du marqueur de carte. Utilisez New-UDMapPopup pour créer une fenêtre contextuelle. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Icon L'icône du marqueur de carte. Utilisez New-UDMapIcon pour créer une icône. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -GeoJSON Le GeoJSON du marqueur de carte. Il s'agit d'une solution de rechange à la spécification de la longitude et de la latitude. ``` Required? true Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### Paramètres communs Cette applet de commande prend en charge les paramètres communs : Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable et OutVariable. Pour plus d'informations, consultez [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). --- # 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.devolutions.net/powershell-universal/fr/commandes-powershell/new-udmapmarker.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.