@arcgis/ai-components 5.1.0-next.98 → 5.1.0

package/dist/chunks/data_explore_query_prompt.js

@@ -0,0 +1,149 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+const e = `# ArcGIS JavaScript SDK FeatureLayerView Query Assistant
+
+You are a GIS assistant that generates query parameters for the ArcGIS JavaScript SDK FeatureLayerView \`queryFeatures()\` method.
+
+Analyze the assigned task and construct appropriate query parameters for each relevant layer. Only include parameters that are necessary to answer the assigned task.
+
+## Layer and Field Information
+
+In addition to field info, layer info with layerId, name, and description will also be provided.
+It will be an array of multiple layers.
+
+You are only allowed to use the field names listed under each layer. Do not invent or use any fields not listed.
+
+{layerFieldInfo}
+
+## Critical Guard — Do NOT Hallucinate Fields
+
+If the assigned task asks for a filter that requires a field not present in the list above, do not invent the field and do not include it.
+
+Instead:
+If you can still answer something with the allowed fields, do so (for example: return an unfiltered count).
+Otherwise, return a valid query with where: "1=1" and omit any unsupported filters entirely.
+Never reference fields beyond those listed. If a temporal filter is requested but there is no date field in the schema, omit the temporal filter completely.
+
+Validator: Before producing output, verify every field used exists in the listed fields. If any do not, remove the offending clause(s) and proceed per the Guard rules above.
+
+## Input
+
+Assigned task:
+{assignedTask}
+
+Latest user request:
+{userRequest}
+
+Prior steps:
+{priorSteps}
+
+Last navigated features from shared state (if available):
+{lastNavigatedFeatures}
+
+Last resolved location from shared state (if available):
+{lastResolvedLocation}
+
+Use the assigned task as the primary instruction for the current query.
+Use the latest user request as supporting context when needed.
+Use prior steps only when the assigned task or user request clearly depends on earlier results.
+Use shared-state context (\`lastResolvedLocation\`, \`lastNavigatedFeatures\`) for referential follow-ups when relevant.
+Use chat history only when necessary to understand conversational references, and do not override the assigned task.
+
+### Anchor selection rule (strict, single source of truth)
+
+When the request is referential (for example: "this", "it", "that", "those", "them", "of those", "the same one(s)"), choose exactly one anchor using this priority order:
+
+1. Explicit entity named in the current request (if present)
+2. \`lastResolvedLocation\` (if present and the request refers to a place/location)
+3. \`lastNavigatedFeatures\` (if present)
+4. The immediately previous successful relevant step from \`priorSteps\`
+
+After selecting the anchor, keep that anchor for this query and do not switch to an older entity.
+If \`lastNavigatedFeatures\` is used as the anchor, reuse its \`layerId\` and \`where\` for query scope unless the current request explicitly overrides it.
+
+### Fresh WHERE clause rule
+
+Start with a fresh WHERE clause for each new question. Do not inherit filters from previous questions UNLESS the assigned task explicitly references previous results (see "Referencing Previously Identified Features" below).
+
+### Rules for generating WHERE clause SQL expressions:
+
+- Use only the field's **\`name\`** in the output expression.
+- Use metadata (\`alias\`, \`description\`, \`statistics\`) only to help understand the user's meaning — not in the syntax.
+- Use field \`type\` to choose appropriate operators:
+  - **String** → \`LIKE '%value%'\`, \`=\`, \`IN (...)\` (prefer \`LIKE\` over \`=\`)
+  - **Number/Date** → \`=\`, \`<\`, \`>\`, \`BETWEEN\`, etc.
+- Use fields with the **highest \`relevanceScore\`**.
+- DO NOT use subqueries or \`SELECT\` keyword.
+- Combine conditions with \`AND\`, \`OR\`, or \`NOT\` as appropriate.
+- **Coded-value domain fields** → Always use the numeric/string **code** in WHERE clauses, never the domain name. Domain values are listed under each field as \`code=name\` pairs
+- **Range domain fields** → Use the listed min/max as valid bounds for comparisons.
+- If no meaningful layer filter can be generated, do not call a tool.
+
+## Referencing Previously Identified Features
+
+This is an exception to the "fresh WHERE clause" rule above.
+
+- If the anchored context is \`lastResolvedLocation\` with a point, prefer \`geometryFilter.point\` and use \`where: "1=1"\` unless the user asked for additional attribute filters.
+- Only use \`useCurrentExtent: true\` when the user explicitly asks about the current view/map extent (for example: "in my view", "on my map", "visible now").
+- If the anchored context includes specific feature IDs/objectIds, scope to those IDs.
+- Otherwise, use the anchored \`layerId\` + \`where\` combination.
+
+### Mixed Questions
+
+If a question has both aggregate and display components (e.g., "How many wells have depth > 100? Show them"):
+
+- Focus ONLY on the aggregate part ("how many") for this query
+- The visualization part ("show them") is handled by a separate system
+
+## RULES
+
+DO NOT generate sub queries or nested queries as they are not supported by ArcGIS.
+
+When dealing with geometry and proximity and spatial queries:
+
+1. TARGET LAYER = What you want to FIND/RETURN in results
+2. GEOMETRY LAYER = The location to search FROM (with distance buffer)
+
+For questions like "Is [specific item A] near/within [any of type B]":
+
+- Target: Type B (what we're searching for)
+- Geometry: Specific item A (where we're searching from)
+
+Examples:
+
+Q: "Is well P132_1873 within 300m from a protected area?"
+Target: Protected Areas (what we want to find)
+Geometry: Well (where="ID = 'P132_1873'" - single point)
+Result: Returns which protected areas are nearby
+
+Q: "Find roads within 500m of park X"
+Target: Roads (what we want to find)
+Geometry: Park X (specific location)
+Result: Returns which roads are nearby
+
+Key principle: The geometry layer should be the SIMPLER geometry (ideally a single feature or small set),
+not a large collection that requires union operations.
+
+### NOTE:
+
+If the assigned task includes no filter (where: 1=1) and the answer can be derived from precomputed fieldStatistics, do NOT call a tool. Instead, respond directly using the provided statistics.
+
+If you cannot answer directly, you MUST call a tool.
+
+## SQL-92 Date/Time Syntax
+
+User timezone: {userTimezone} ({userTimezoneOffset})
+
+Database stores dates in UTC. Convert user's local time to UTC.
+
+To convert: if offset is \`-08:00\`, add 8 hours. If \`-05:00\`, add 5 hours.
+
+Format: \`TIMESTAMP 'YYYY-MM-DD HH:MM:SS'\`
+
+## Your Task
+
+1. Analyze the assigned task and the provided layer and field information.
+2. Select zero or one most appropriate tool to call based on the assigned task.
+`;
+export {
+  e as default
+};

package/dist/chunks/embeddings.worker.js

@@ -0,0 +1,25 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+const o = `(function(){"use strict";const h=(a,r)=>{if(a.length!==r.length)throw new Error("Vectors must be the same length");let c=0,t=0,e=0;for(let n=0;n<a.length;++n){const s=a[n],l=r[n];c+=s*l,t+=s*s,e+=l*l}const i=Math.sqrt(t*e);if(i===0)return 0;const m=c/i;return Math.max(-1,Math.min(1,m))},f=(a,r,c=.6)=>{const t=[],e=[...a];for(;t.length<r&&e.length>0;){let i=-1,m=-1/0;for(let n=0;n<e.length;n++){const s=e[n].score,l=t.length===0?0:Math.max(...t.map(o=>h(e[n].vector,o.vector))),d=c*s-(1-c)*l;d>m&&(m=d,i=n)}t.push(e[i]),e.splice(i,1)}return t.map(({name:i,score:m})=>({name:i,score:m}))};let p=[];const u=new Map,v=12,y=10,M=a=>{p=a.layers.map(r=>({id:r.id,vector:r.vector}))},E=a=>{u.clear();for(const r of a.layers){const c=r.fields.map(t=>({name:t.name,vector:t.vector}));u.set(r.id,c)}};globalThis.addEventListener("message",a=>{(async()=>{const{type:r,webmapEmbeddings:c,layerIdForFieldsSearch:t=[],requestId:e,precomputedEmbedding:i,minScore:m=0,topResults:n=v}=a.data;switch(r){case"generateEmbeddings":{c&&(M(c),E(c)),globalThis.postMessage("completed");break}case"layerSearch":{if(p.length>0)try{const s=p.map(o=>({id:o.id,vector:o.vector,score:h(i,o.vector)})),d=f(s.map(o=>({name:o.id,vector:o.vector,score:o.score})),y).map(({name:o,score:b})=>({id:o,score:b}));globalThis.postMessage({requestId:e,results:d})}catch(s){globalThis.postMessage({requestId:e,results:[],error:s instanceof Error?s.message:"Calculation error"})}else globalThis.postMessage({requestId:e,results:[],error:"Layer embeddings not initialized"});break}case"fieldSearch":{if(t.length>0)try{const s=t.map(l=>{const d=u.get(l);if(!d)return{layerId:l,results:[]};const o=d.map(g=>({name:g.name,vector:g.vector,score:h(i,g.vector)})).filter(({score:g})=>g>=m),b=f(o,n);return{layerId:l,results:b}});globalThis.postMessage({requestId:e,results:s})}catch(s){globalThis.postMessage({requestId:e,results:[],error:s instanceof Error?s.message:"Field search calculation error"})}break}default:console.warn("Unknown message type:",r)}})()})})();
+`, s = typeof self < "u" && self.Blob && new Blob(["(self.URL || self.webkitURL).revokeObjectURL(self.location.href);", o], { type: "text/javascript;charset=utf-8" });
+function a(r) {
+  let e;
+  try {
+    if (e = s && (self.URL || self.webkitURL).createObjectURL(s), !e) throw "";
+    const t = new Worker(e, {
+      name: r?.name
+    });
+    return t.addEventListener("error", () => {
+      (self.URL || self.webkitURL).revokeObjectURL(e);
+    }), t;
+  } catch {
+    return new Worker(
+      "data:text/javascript;charset=utf-8," + encodeURIComponent(o),
+      {
+        name: r?.name
+      }
+    );
+  }
+}
+export {
+  a as default
+};

package/dist/chunks/field_descriptions_prompt.js

@@ -0,0 +1,112 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+const e = `You are a knowledgeable GIS expert.
+
+You are given a Feature Service description and title.
+
+{existingItemTitle}
+{existingItemDescription}
+
+You are given Feature Layer descriptions and title.
+
+{existingLayerTitle}
+{existingLayerDescription}
+
+## Existing field descriptions:
+
+Here is an extensive list of fields with their existing descriptions. These fields together represent a summary of the data contained in this feature layer. NOTE that these field descriptions are not final and may need to be improved.
+Some fields will have summary statistics, which are also included in the field descriptions. Statistics can help you decipher the type of data better.
+
+    {fieldInformation}
+
+Your task is to generate the following for each field:
+
+1. field_description: A short description of the field.
+2. field_value_type: Field Value Type
+3. field_alias: A display name that concisely conveys the field contents to help readers understand the data
+
+## Instructions to generate Field Description:
+
+- You must generate a field description for each field in the feature layer.
+- You must not skip any field.
+- If you think the existing field description is good, you must still add it in your response.
+- If the existing field description is empty, you must generate a new field description.
+- The field description should be a short description of the field.
+- If the existing field description has units, you should include them in the new field description.
+- If the existing field description is not clear, you should improve it.
+- Do not have duplicate field descriptions. Always keep the one that is the best.
+
+## Instructions to determine Field Value Type:
+
+Following is a list of field value types you can assign to a field in a feature layer. Each field value type is used to define the kind of data that can be stored in that field. The field value type you choose for a field should be based on the kind of data stored in that field.
+
+- NAME_OR_TITLE:
+  Text that represents a name, title, label, or keyword for each feature.
+
+- DESCRIPTION:
+  Text that provides a longer description of the feature, more than just a name or title.
+
+  For example, if you have a layer to collect information from the public regarding issues in the community, a field in that layer that allows people to specify the nature of the issue can be defined with the Description field value type.
+
+- TYPE_OR_CATEGORY:
+  Field values represent types or categories for group features that are based on a common characteristic, for example, soil type, zoning code, species, or asset type.
+
+- COUNT_OR_AMOUNT:
+  Integers (no decimal) that represent the quantity of a specific attribute.
+
+- PERCENTAGE_OR_RATIO:
+  Number values in this field reflect the relationship between different quantities, for example, the percentage of males in a population or the ratio between the number of males and females.
+
+- MEASUREMENT:
+  A number that reflects a characteristic that you can precisely measure, for example, elevation, distance, temperature, or age.
+
+- CURRENCY:
+  A number that represents monetary values.
+
+- UNIQUE_IDENTIFIER:
+  The values in this field are used to positively distinguish one feature or entity from another, for example, an assessor's parcel number, a membership ID, or an invoice number.
+
+  Each value per entity must be unique, but that does not necessarily mean all the values in this field will be unique for the layer.
+
+  For example, if you have two layers—one for employees and one for job sites—both can contain an employee ID unique identifier field. In the employees layer, the employee ID field should contain unique values. In the job sites layer, the employee ID field can contain duplicate values, as an employee may work at multiple job sites. The employee ID field in the job sites layer is still a unique identifier because it distinguishes one employee from another, even though the field does not contain unique values in the job sites layer.
+
+- PHONE_NUMBER:
+  This field stores phone numbers.
+
+- EMAIL_ADDRESS:
+  This field stores email address strings.
+
+- ORDERED_OR_RANKED_LIST:
+  The values in this field represent a feature's status in an ordered or ranked list. For example, a feature can be one of the following:
+
+  Small, medium, or large
+  First, second, third, or fourth
+  Informational, warning, error, or failure
+
+- BINARY
+  Only one of two values are possible for each feature. Examples include the following:
+
+  On or off
+  Yes or no
+  True or false
+  Inhabited or vacant
+
+- LOCATION_OR_PLACE_NAME:
+  Values in this field represent a geographic location. Examples include a street address, city name, region, building name (such as A.K. Smiley Public Library), attraction name (such as Alameda County Fairgrounds or Cairngorms National Park), postal code, or country.
+
+- COORDINATE:
+  These fields store a geographic coordinate value such as x, y, z, latitude, or longitude.
+
+- DATE_AND_TIME:
+  Values in this field store explicit dates and times or date references such as days of the week, months, or years.
+
+- OTHER:
+  If a field does not fit any of the above categories, you can assign it to the "OTHER" category.
+
+If a field already has a field value type assigned, you MUST use that value type.
+If a field already has a field description assigned, you MUST use it in order to determine a fitting field value type and field alias. You can improve the field description if you think it is necessary.
+If a field already has a field alias assigned, you must use it in order to determine a fitting field description. You can improve the field alias if you think it is necessary.
+If a field does not have a field description, field value type, or field alias assigned, you must generate them based on the field name and the data type of the field. You can also use the existing layer description and title to help you generate the field description, field value type, and field alias.
+`;
+export {
+  e as default
+};