> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/technical-notes/well-seeker-pro-technical-notes/compass-edm-slot-exports-incorrect-surface-location.md). # Compass EDM: Slot Exports Incorrect Surface Location ## Description Within Compass, when the **Wellhead Location** is selected as **Slot**, the wellhead data is not exporting correctly in the EDM file. When this EDM file is imported into Well Seeker X the surface location for the well will be as per the information in the EDM file, but not the same as the user entered in Compass. ## Solution Within Compass, when exporting to EDM file, always lock the well head location to **Map**. Recommendation: Regardless of export method, double check both the surface and bottom hole **map coordinates** in Well Seeker after importation. --- # 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.innova-drilling.com/introduction/technical-notes/well-seeker-pro-technical-notes/compass-edm-slot-exports-incorrect-surface-location.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.