You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: extension/docs/github-copilot/getting-started/envi.md
+19-57Lines changed: 19 additions & 57 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,19 +2,32 @@
2
2
3
3
## Key Takeaways
4
4
5
-
ENVI's GitHub Copilot integration uses specialized MCP tools to run processing workflows, understand datasets, and solve remote sensing problems using expert approaches.
5
+
ENVI's GitHub Copilot integration uses specialized MCP tools to run processing workflows, understand datasets, and solve remote sensing problems.
6
6
7
7
**Requirements:**
8
8
9
9
- IDL 9.2 and ENVI 6.2 or newer
10
10
- ENVI Agent license feature
11
11
- Works alongside IDL Agent capabilities
12
12
13
-
**Key Difference:** ENVI uses a guided "happy path" approach with dedicated tools, unlike IDL's open-ended programming focus.
13
+
## Helpful Tips
14
+
15
+
::: tip
16
+
17
+
To guide the LLM to use ENVI, make sure to add "ENVI" to your requests. Here's some examples:
14
18
15
-
## How It Works
19
+
- Using ENVI can you do [awesome remote sensing workflow]
20
+
- Can you [insert request] with ENVI?
16
21
17
-
ENVI's integration centers on specialized MCP tools that enable GitHub Copilot to run ENVI processing, understand your datasets, and chain together workflows. This differs from the IDL integration—instead of open-ended programming, we guide the LLM through proven approaches using ENVI's established toolset.
22
+
:::
23
+
24
+
**Automatic Startup:** ENVI and IDL start automatically when needed—no manual intervention required.
25
+
26
+
**Built-in Prompts:** Start your chat with "/envi" to access pre-configured prompts designed for common remote sensing problems.
27
+
28
+
**Multi-File Data Sources:** For complex formats like Sentinel 2 or PlanetScope, provide the direct path to the root metadata file (e.g., "metadata.xml" for Sentinel 2 or "\_metadata.json" for Planet data). This ensures GitHub Copilot opens the correct dataset.
29
+
30
+
**Understanding Data:** Ask GitHub Copilot to query or describe datasets when you need more information. This works for all data types, including complex multi-file formats.
18
31
19
32
## What You Can Do
20
33
@@ -34,7 +47,7 @@ View rasters, vectors, and raster series datasets directly in ENVI.
34
47
35
48
Generate IDL routines and IDL Notebooks for repeatable workflows.
36
49
37
-
## Example Prompts
50
+
## Example Requests
38
51
39
52
Guide GitHub Copilot to use ENVI by adding phrases like "Using ENVI", "With ENVI", or "Can ENVI" to your requests.
40
53
@@ -43,7 +56,7 @@ Here are some examples to get started:
43
56
::: code-group
44
57
45
58
```[Open Datasets]
46
-
Can you open the ENVI file that lives "here" for me?
59
+
Can you open the data in "here" for me in ENVI?
47
60
```
48
61
49
62
```[Query Datasets]
@@ -61,54 +74,3 @@ and display the results?
61
74
```
62
75
63
76
:::
64
-
65
-
### Working with ENVI's Tools
66
-
67
-
**Built-in Prompts:** Start your chat with "/envi" to access pre-configured prompts designed for common remote sensing problems. These provide ready-to-use templates you can copy and customize.
68
-
69
-
Here are additional examples for exploring ENVI's capabilities:
70
-
71
-
::: code-group
72
-
73
-
```[Tool Questions]
74
-
Does ENVI have any tools for classification cleanup?
75
-
```
76
-
77
-
```[Planning #1]
78
-
Can you help me come up with a change detection workflow using
79
-
spectral indices with ENVI?
80
-
81
-
I have imagery located in "this" folder that I want to use.
82
-
83
-
I just want to plan a processing workflow, not run anything.
84
-
```
85
-
86
-
```[Planning #2]
87
-
/envi Can you help me detect change between two images using
88
-
machine learning?
89
-
```
90
-
91
-
```[Workflows]
92
-
Do you know any change detection workflows using ENVI?
93
-
```
94
-
95
-
```[IDL Notebooks]
96
-
/envi Help me come up with a data preparation workflow for the
97
-
sample data "here".
98
-
99
-
I don't want the processing to happen, instead please create
100
-
an IDL Notebook that I can then customize based on
101
-
other data sources.
102
-
```
103
-
104
-
:::
105
-
106
-
## Helpful Tips
107
-
108
-
**Automatic Startup:** ENVI and IDL start automatically when needed—no manual intervention required.
109
-
110
-
**Built-in Prompts:** Start your chat with "/envi" to access pre-configured prompts designed for common remote sensing problems.
111
-
112
-
**Multi-File Data Sources:** For complex formats like Sentinel 2 or PlanetScope, provide the direct path to the root metadata file (e.g., "metadata.xml" for Sentinel 2 or "\_metadata.json" for Planet data). This ensures GitHub Copilot opens the correct dataset.
113
-
114
-
**Understanding Data:** Ask GitHub Copilot to query or describe datasets when you need more information. This works for all data types, including complex multi-file formats.
Copy file name to clipboardExpand all lines: extension/docs/github-copilot/getting-started/idl.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,26 @@
2
2
3
3
## Key Takeaways
4
4
5
-
GitHub Copilot becomes an expert IDL programmer through specialized root-level instructions that automatically apply when you work with IDL code or notebooks.
5
+
IDL's GitHub Copilot integration enables GitHub Copilot to become an expert IDL programmer through specialized root-level instructions. These instructions are automatically applied when you work with IDL code or IDL Notebooks.
6
6
7
7
**Requirements:**
8
8
9
9
- IDL 9.2 or newer
10
10
- Instructions automatically load when IDL code or notebooks are open or attached
11
11
12
-
**What to Look For:** "GitHub Copilot: IDL" message in your chat when instructions load
12
+
**What to Look For:** "IDl Agent" message in your chat when instructions load
13
+
14
+
## Helpful Tips
15
+
16
+
**Automatic Startup:** IDL starts automatically when needed—no manual intervention required.
17
+
18
+
**Creating IDL Notebooks:** Explicitly request an "IDL Notebook" to ensure you get the native VSCode implementation rather than a Python/Jupyter notebook. Native IDL Notebooks require no additional setup or configuration.
13
19
14
20
## How It Works
15
21
16
22
GitHub Copilot is already an expert programmer across many languages. We've enhanced this expertise with specialized instructions that help it write better IDL code and understand your existing routines. These instructions apply automatically when you work with IDL files or notebooks, no manual setup required.
17
23
18
-
## Example Prompts
24
+
## Example Requests
19
25
20
26
GitHub Copilot has access to many tools and can handle a wide range of IDL-related tasks or requests. Here are some examples to get you started:
21
27
@@ -46,12 +52,6 @@ that goes through the bounding boxes one time (so it is more linear for performa
46
52
47
53
:::
48
54
49
-
## Helpful Tips
50
-
51
-
**Automatic Startup:** IDL starts automatically when needed—no manual intervention required.
52
-
53
-
**Creating IDL Notebooks:** Explicitly request an "IDL Notebook" to ensure you get the native VSCode implementation rather than a Python/Jupyter notebook. Native IDL Notebooks require no additional setup or configuration.
54
-
55
55
## Attaching Context
56
56
57
57
GitHub Copilot can incorporate various sources to better understand your code and provide more relevant answers. Click the paperclip icon in your chat to explore available options.
Copy file name to clipboardExpand all lines: extension/docs/github-copilot/index.md
+5-9Lines changed: 5 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,16 @@
1
1
# GitHub Copilot Integration
2
2
3
-
IDL for VSCode integrates seamlessly with GitHub Copilot, giving you AI-powered assistance for IDL programming and ENVI workflows. This integration is completely optional and designed to enhance your productivity.
3
+
IDL for VSCode integrates seamlessly with GitHub Copilot, giving you AI-powered assistants for IDL programming and ENVI workflows. This integration is completely optional for you to use and designed to enhance your productivity and help understand IDL and ENVI, not replace users.
4
4
5
5
**What You Get:**
6
6
7
+
IDL Agent and ENVI Agent which are powered by:
8
+
7
9
- Native GitHub Copilot support through Model Context Protocol (MCP)
8
10
- Smart IDL code generation with context-aware suggestions
9
11
- Automated ENVI workflows that mirror expert problem-solving approaches
10
12
- Automatic setup, no manual configuration required
This integration focuses on two powerful capabilities:
@@ -25,7 +21,7 @@ This integration focuses on two powerful capabilities:
25
21
26
22
## Understanding Model Context Protocol
27
23
28
-
The integration uses Model Context Protocol (MCP), a standardized interface that allows LLMs to run tools and interact with software. Think of MCP as a bridge between GitHub Copilot and IDL/ENVI.
24
+
The integration uses Model Context Protocol (MCP), a standardized interface that allows LLMs to run tools and interact with software. Think of MCP as a bridge between GitHub Copilot and IDL/ENVI on your computer.
29
25
30
26
## Automatic MCP Server Setup
31
27
@@ -47,6 +43,6 @@ IDL for VSCode includes an MCP server that configures and starts automatically,
47
43
**ENVI:**
48
44
49
45
- ENVI 6.2 or newer
50
-
- ENVI Agent license feature required
46
+
- ENVI Agent license feature required for ENVI MCP tools
51
47
52
48
The ENVI Agent license enables specialized tools optimized for remote sensing workflows, ensuring repeatable and reliable problem-solving approaches.
0 commit comments