> 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/da/powershell-kommandoer/new-udmapmarker.md). # New-UDMapMarker New-UDMapMarker placerer en markør på en given breddegrad og længdegrad, eller ud fra GeoJSON, på en New-UDMap i PowerShell Universal, med brugerdefinerede ikoner og pop op-vinduer. ### Synopsis Opretter en kortmarkør. ### Syntaks ```powershell New-UDMapMarker [-Id ] -Longitude -Latitude [-Attribution ] [-Opacity ] [-ZIndex ] [-Popup ] [-Icon ] [] New-UDMapMarker [-Id ] [-Attribution ] [-Opacity ] [-ZIndex ] [-Popup ] [-Icon ] -GeoJSON [] ``` ### Beskrivelse Opretter en kortmarkør. ### Parametre #### -Id Id'et for kortmarkøren. Dette er som standard et nyt GUID. ``` Required? false Position? named Default value ([Guid]::NewGuid()) Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Longitude Længdegraden for kortmarkøren. ``` Required? true Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Latitude Breddegraden for kortmarkøren. ``` Required? true Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Attribution Tilskrivningen for kortmarkøren. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Opacity Opaciteten for kortmarkøren. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -ZIndex z-indekset for kortmarkøren. ``` Required? false Position? named Default value 0 Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Popup Pop op-vinduet for kortmarkøren. Brug New-UDMapPopup til at oprette en pop op. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -Icon Ikonet for kortmarkøren. Brug New-UDMapIcon til at oprette et ikon. ``` Required? false Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### -GeoJSON GeoJSON for kortmarkøren. Dette er et alternativ til at angive længdegrad og breddegrad. ``` Required? true Position? named Default value Accept pipeline input? false Aliases Accept wildcard characters? false ``` #### Fælles parametre Denne cmdlet understøtter de fælles parametre: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable og OutVariable. Se [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216) for at få flere oplysninger. --- # 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/da/powershell-kommandoer/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.