@arcgis/portal-components 5.1.0-next.13 → 5.1.0-next.130

package/dist/cdn/FPAFR5IL.js

@@ -0,0 +1,109 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+import"./CFDTXKJ6.js";var 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\u2014one for employees and one for job sites\u2014both 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};

package/dist/cdn/FPKINYFN.js

@@ -0,0 +1,3 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+import"./CFDTXKJ6.js";var 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)}})()})})();
+`,r=typeof self<"u"&&self.Blob&&new Blob(["(self.URL || self.webkitURL).revokeObjectURL(self.location.href);",o],{type:"text/javascript;charset=utf-8"});function a(t){let e;try{if(e=r&&(self.URL||self.webkitURL).createObjectURL(r),!e)throw"";let s=new Worker(e,{name:t?.name});return s.addEventListener("error",()=>{(self.URL||self.webkitURL).revokeObjectURL(e)}),s}catch{return new Worker("data:text/javascript;charset=utf-8,"+encodeURIComponent(o),{name:t?.name})}}export{a as default};

package/dist/cdn/GOMFFUFI.js

@@ -0,0 +1,5 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+import"./CFDTXKJ6.js";var e=`## Additional System Context
+
+In addition to the user's inquiry prompt that precedes this system context, the current link chart has entities and relationships on it already, in the format of an array of objects containing identifiers and typeNames, in case this is needed for query generation (for example 'Add all records that are connected to people on this link chart to the link chart'). If the user is asking for a query that acts on 'the current link chart', 'my link chart', or similar then the cypher query should be filtered by the ids. For example, 'Match (n:Person)-[\\r]->(m) WHERE id(n) IN [\\'identifier1','identifier2'] return r, m. Curly braces (the '{' and '}' characters) are often part of identifier strings and should not be stripped out - the process of filtering by ids should not be altering the id strings. The entities and relationships that are on the current link chart are as follows:
+`;export{e as default};

package/dist/cdn/{QVXQMXLU.js → GPSI4ROI.js}

@@ -1,2 +1,2 @@
 /* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
-export default $arcgis.t(([c,{once:l}])=>{var D=(t,e,r)=>{let a=d(t,e,r);return a=m(r,a),a},d=(t,e,r)=>{let a=r.classificationMetadata.defaultValue,s=structuredClone(t)??{[e]:a};return s[e]??=a,s},$=(t,e)=>t&&Object.fromEntries(Object.entries(t).filter(([r])=>e.get(r)?.enabled!==!1)),m=(t,e)=>{let r=structuredClone(e);return Object.entries(t.attributes).forEach(([a,s])=>{if(r?.[a])return;let{uiElement:o,defaultValue:n}=s;switch(o){case"date":r&&(r[a]=p(s));break;case"multi-select":case"multi-grouped-select-nested":n&&r&&(r[a]=[n]);break;case"checkbox":n&&r&&(r[a]=n==="true");break;case"single-select":case"text":n&&r&&(r[a]=n);break}}),r?.fgi||delete r?.fgiOptions,r},p=t=>{let e=new Date,{type:r,defaultDateTimeline:a,defaultDateTimelineUnits:s}=t;if(r==="date"&&a&&s)switch(s.toLowerCase()){case"years":e.setFullYear(e.getFullYear()+a);break;case"months":e.setMonth(e.getMonth()+a);break;case"days":e.setDate(e.getDate()+a);break}let o=(e.getMonth()+1).toString(),n=e.getDate().toString();return`${e.getFullYear()}-${o.length===1?`0${o}`:o}-${n.length===1?`0${n}`:n}`},k=(t,e,r)=>{let a=e?.createdUser,s=e?.createdDate;return e={[r]:t,...a?{createdUser:a}:{},...s?{createdDate:s}:{}},e},U=async t=>{try{if(!t)return!1;t.loaded||await t.load();let e=t.portal.user??await l(()=>t?.portal.user);if(!e)return!1;let r=e.privileges.includes("portal:admin:updateItems");return i(t,e)||g(t,e)||r||t.access==="shared"&&await f(t,e)}catch(e){return console.error(e),!1}};function i(t,e){return t.owner===e.username}function g(t,e){let r=t.owner,a=t.itemControl==="admin",s=["esri_livingatlas","esri_demographics","esri_boundaries"];return t.portal?.isPortal&&!i(t,e)&&a&&r?.includes("esri_")&&!s.includes(r)?!1:a}var f=async(t,e)=>{let r=t.portal.restUrl,a=(await h(e,r)).result??[],s=(await b(t,r)).result??[];return a?.some(o=>s?.some(n=>o.id===n.id&&o.capabilities.includes("updateitemcontrol")))},h=async(t,e)=>{let r=`${e}/community/users/${t.username}`;try{return{result:(await c(r,{query:{f:"json"},responseType:"json"})).data?.groups??[]}}catch{return{error:{code:"unhandledError"}}}},b=async(t,e)=>{let r=t.id,a=`${e}/content/items/${r}/groups`;try{let s=await c(a,{query:{f:"json",method:"post"},responseType:"json"}),o=s.data?.admin??[],n=s.data?.member??[],u=s.data?.other??[];return{result:[...o,...n,...u]}}catch{return{error:{code:"unhandledError"}}}},j=(t,e)=>{let r=Date.now(),a=t?.portal.user?.username??"",{createdUser:s=a,createdDate:o=r}=e??{};return{createdUser:s,createdDate:o,lastEditedUser:a,lastEditedDate:r}};return{a:D,b:$,c:m,d:k,e:U,f:j}},"request","core/reactiveUtils")
+export default $arcgis.t(([{once:l},c])=>{var D=(t,e,r)=>{let a=d(t,e,r);return a=m(r,a),a},d=(t,e,r)=>{let a=r.classificationMetadata.defaultValue,s=structuredClone(t)??{[e]:a};return s[e]??=a,s},$=(t,e)=>t&&Object.fromEntries(Object.entries(t).filter(([r])=>e.get(r)?.enabled!==!1)),m=(t,e)=>{let r=structuredClone(e);return Object.entries(t.attributes).forEach(([a,s])=>{if(r?.[a])return;let{uiElement:o,defaultValue:n}=s;switch(o){case"date":r&&(r[a]=p(s));break;case"multi-select":case"multi-grouped-select-nested":n&&r&&(r[a]=[n]);break;case"checkbox":n&&r&&(r[a]=n==="true");break;case"single-select":case"text":n&&r&&(r[a]=n);break}}),r?.fgi||delete r?.fgiOptions,r},p=t=>{let e=new Date,{type:r,defaultDateTimeline:a,defaultDateTimelineUnits:s}=t;if(r==="date"&&a&&s)switch(s.toLowerCase()){case"years":e.setFullYear(e.getFullYear()+a);break;case"months":e.setMonth(e.getMonth()+a);break;case"days":e.setDate(e.getDate()+a);break}let o=(e.getMonth()+1).toString(),n=e.getDate().toString();return`${e.getFullYear()}-${o.length===1?`0${o}`:o}-${n.length===1?`0${n}`:n}`},k=(t,e,r)=>{let a=e?.createdUser,s=e?.createdDate;return e={[r]:t,...a?{createdUser:a}:{},...s?{createdDate:s}:{}},e},U=async t=>{try{if(!t)return!1;t.loaded||await t.load();let e=t.portal.user??await l(()=>t?.portal.user);if(!e)return!1;let r=e.privileges.includes("portal:admin:updateItems");return i(t,e)||g(t,e)||r||t.access==="shared"&&await f(t,e)}catch(e){return console.error(e),!1}};function i(t,e){return t.owner===e.username}function g(t,e){let r=t.owner,a=t.itemControl==="admin",s=["esri_livingatlas","esri_demographics","esri_boundaries"];return t.portal?.isPortal&&!i(t,e)&&a&&r?.includes("esri_")&&!s.includes(r)?!1:a}var f=async(t,e)=>{let r=t.portal.restUrl,a=(await h(e,r)).result??[],s=(await b(t,r)).result??[];return a?.some(o=>s?.some(n=>o.id===n.id&&o.capabilities.includes("updateitemcontrol")))},h=async(t,e)=>{let r=`${e}/community/users/${t.username}`;try{return{result:(await c(r,{query:{f:"json"},responseType:"json"})).data?.groups??[]}}catch{return{error:{code:"unhandledError"}}}},b=async(t,e)=>{let r=t.id,a=`${e}/content/items/${r}/groups`;try{let s=await c(a,{query:{f:"json",method:"post"},responseType:"json"}),o=s.data?.admin??[],n=s.data?.member??[],u=s.data?.other??[];return{result:[...o,...n,...u]}}catch{return{error:{code:"unhandledError"}}}},j=(t,e)=>{let r=Date.now(),a=t?.portal.user?.username??"",{createdUser:s=a,createdDate:o=r}=e??{};return{createdUser:s,createdDate:o,lastEditedUser:a,lastEditedDate:r}};return{a:D,b:$,c:m,d:k,e:U,f:j}},"core/reactiveUtils","request")

package/dist/cdn/HSYQIF6A.js

@@ -0,0 +1,2 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+import{a as u,b as g,c as k}from"./S2PHM4WZ.js";export default $arcgis.t(([q,x])=>{var c={},l={},d={};async function y({requester:t,key:r,id:o,cacheOption:a}){let e=d[r]?.[o]?.expireAt,n=!!e&&new Date().getTime()>e;if(c[r]?.[o]&&!n)return c[r][o];l[r]||(l[r]={}),(!l[r][o]||n)&&(l[r][o]=t());let i=await l[r][o];if(c[r]||(c[r]={}),d[r]||(d[r]={}),c[r][o]=i,a){let{expireAfter:m,getExpireAfterFromResult:s}=a,f=s||m?new Date().getTime()+(s?.(i)??m??0):null;d[r][o]={...d[r][o],expireAt:f}}return i}async function A({url:t,portal:r,params:o={},options:a={},method:e,abortControllerId:n,excludeJson:i}){let m=T(n)?.signal,{customToken:s,addTokenManually:f,addSSL:S,useProxy:b}=a,w={...o};if(!t.includes("f=")&&!i&&(w.f="json"),s)w.token=s;else if(f!==!1){let h=await E(r);h&&(w.token=h)}let C=S?M(t,r):t,P={query:w,method:e||"auto",...a,timeout:a.timeout||0,useProxy:b,...a?.disableIdentityLookup?{authMode:"anonymous"}:{}},$=await x(C,{signal:m,...P});return n&&(p[n]=void 0),$.data}var p={};function T(t){if(t)return p[t]&&p[t].abort(),p[t]=new AbortController,p[t]}var E=async t=>{let r=k(t);if(!t?.isPortal||!r)return g(t);let o=t?.user;if(!o&&r)return;let{token:a}=await y({requester:async()=>await I(t),key:"platformSelf",id:o?.id??t.id??"<unknown>",cacheOption:{getExpireAfterFromResult:e=>e.expires_in}});return a},I=async t=>{let r={"X-Esri-Auth-Client-Id":await L(t),"X-Esri-Auth-Redirect-Uri":window.location.href.replace(/#.*$/u,"")};return(await x(`${u(t)}/oauth2/platformSelf`,{authMode:"no-prompt",headers:r,withCredentials:!0,method:"post"})).data},L=async t=>(await y({requester:async()=>await q.getCredential(u(t),{oAuthPopupConfirmation:!1}),key:"credential",id:t.user?.id??"<unknown>"})).oAuthState?.appId??"arcgisonline";function M(t,r){return window.location.protocol==="https:"||r.allSSL?t.replace("http:","https:"):t}async function D(t,r,o){let a=`${o?"https://www.arcgis.com/sharing/rest/":u(r)}community/users/${t}`,e=a?.includes("www.arcgis.com")&&r.isPortal,n=a?.includes(".arcgis.com")&&!r.isPortal&&!r.user,i=e||n?{disableIdentityLookup:!0,addTokenManually:!1}:{};return await y({requester:async()=>{try{return await A({url:a,portal:r,options:i})}catch{return{username:t}}},key:"user",id:a})}var U=async t=>{let r=`${u(t)}/portals/${t.id}/users`;return await A({url:r,portal:t,params:{num:100,sortField:"lastlogin",sortOrder:"desc"}})};return{a:y,b:D,c:U}},"identity/IdentityManager","request")

package/dist/cdn/HWLUVMK4.js

@@ -0,0 +1,5 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+import"./CFDTXKJ6.js";var e=`## Additional System Context
+
+In addition to the user's inquiry prompt that precedes this system context, the current map has entities and relationships on it already, in the format of an array of objects containing identifiers and typeNames or type names that contain all entities or relationships of that type, in case this is needed for query generation (for example 'Add all records that are connected to people on this map to the map'). If the user is asking for a query that acts on 'the current map', 'my map', or similar then the cypher query should be filtered by the ids. For example, 'Match (n:Person)-[\\r]->(m) WHERE id(n) IN [\\'identifier1','identifier2'] return r, m. Curly braces (the '{' and '}' characters) are often part of identifier strings and should not be stripped out - the process of filtering by ids should not be altering the id strings. The entities and relationships that are on the current map are as follows:
+`;export{e as default};

package/dist/cdn/HYX2WOCT.js

@@ -0,0 +1,120 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+import"./CFDTXKJ6.js";var e=`## GIS Agent Orchestrator
+
+You are an orchestrator for an ArcGIS Maps SDK for JavaScript system.
+
+Your job is to decide the single best next agent to execute for the current step.
+
+---
+
+## Inputs
+
+You are given:
+
+- the latest user request
+- relevant chat history
+- the list of registered agents
+- optional prior steps from earlier agent executions
+
+---
+
+## Output
+
+Return either:
+
+- one decision with:
+  1. \`agentId\` \u2014 the next agent to execute
+  2. \`assignedTask\` \u2014 a clear, actionable task for that agent
+  3. \`requiresFollowUp\` \u2014 whether another orchestration step will likely be needed after this agent succeeds
+
+- or \`null\` if no registered agent applies
+
+---
+
+## Important
+
+- Return \`null\` only when the request is clearly outside the scope of all registered agents.
+- If any agent can take the next useful step, select the best one instead of returning \`null\`.
+
+---
+
+## Context
+
+### Latest user request
+
+{userRequest}
+
+### Registered agents
+
+Format:
+{{id: string, name: string, description: string}}[]
+
+{registeredAgents}
+
+### Prior steps
+
+Each step has:
+
+- \`agentId: string\`
+- \`assignedTask: string\`
+- \`summary: string\`
+- \`status: "success" | "failed" | "unknown"\`
+
+Use prior steps to:
+
+- Avoid repeating work that has already succeeded
+- Retry or adjust steps that failed when appropriate
+
+{priorSteps}
+
+---
+
+## Rules
+
+- Focus primarily on the latest user request.
+- Use relevant chat history only when the latest request clearly depends on earlier context; otherwise ignore it.
+- Use prior steps to determine what has already been attempted or completed.
+- Do not plan the full workflow up front. Only decide the next best step.
+- Prefer an agent that can directly complete the user\u2019s request.
+- Only break the request into multiple steps when necessary.
+- When multiple agents could help, choose the best fit instead of returning \`null\`.
+- Base the choice on the registered agent descriptions, not on whether the user used exact matching keywords.
+- If no agent can fully complete the request, but one agent can take the next useful step, choose that agent.
+- Do NOT reuse constraints from prior steps unless the current user request explicitly requires them.
+- Each step must reflect the current user request exactly.
+
+---
+
+## Constraint Interpretation
+
+Interpret the user\u2019s wording precisely:
+
+- Do not substitute one type of constraint for another (e.g., distance vs containment, range vs exact match, etc.)
+- If the user specifies a constraint, use it exactly
+- If the user does not specify a constraint, do not assume or infer one
+
+Do not reinterpret the request into a different form.
+
+---
+
+## Assigned Task Guidelines (IMPORTANT)
+
+- The \`assignedTask\` must match the user\u2019s request exactly in meaning
+- Do not add, remove, or transform constraints
+- Do not substitute one type of constraint for another
+- If a constraint is not explicitly stated, do not assume one
+
+- Keep the task short, specific, and directly executable
+- Keep wording close to the user\u2019s request with minimal transformation
+- Use only information explicitly present in the user request or provided context
+
+- The \`assignedTask\` may represent only part of the user\u2019s request when multiple steps are necessary
+
+---
+
+## requiresFollowUp Guidelines
+
+- \`requiresFollowUp\` should indicate a likely next agent step, not uncertainty about the current request
+- Set \`requiresFollowUp\` to \`true\` only when another orchestration step will likely be needed after this agent succeeds
+- Set \`requiresFollowUp\` to \`false\` when a successful result from this agent would likely complete the user-visible task
+`;export{e as default};

package/dist/cdn/IBYY5ORN.js

@@ -0,0 +1,122 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+import"./CFDTXKJ6.js";var e=`# ArcGIS Online Map Viewer \u2014 Layer Filter Tool Calling Assistant
+
+You are an assistant that helps manage layer filters and visual effects for **ArcGIS Online Map Viewer** by selecting and calling the appropriate tool.
+
+You may make **zero or one** tool call based on the assigned task.
+
+## You are given:
+
+Assigned task:
+{assignedTask}
+
+Latest user request:
+{userRequest}
+
+Prior steps:
+{priorSteps}
+
+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 clearly depends on earlier results.
+
+A list of layers, with layerId, layerSummary and each with associated field information
+{layerFieldInfo}
+
+FieldInfo:
+
+- \`name\`: the actual field name used in layer filter expressions
+- \`type\`: one of \`string\`, \`number\`, \`date\`, etc.
+- \`alias\`: a human-readable label
+- \`description\`: optional field metadata
+- \`statistics\`: such as min, max, unique values, etc.
+
+This is what the query tool returned:
+{queryResponse}
+
+## Your task
+
+1. Decide whether a tool call is needed (see "When to call a tool" below).
+2. If needed, determine \`targetLayer\` using the priority rules below.
+3. Select the most appropriate tool.
+
+## How to determine targetLayer (follow in order)
+
+Use the FIRST rule that matches:
+
+1. **queryResponse includes \`objectIds\` and \`objectIdField\`** \u2192 pass them as \`targetLayer.objectIds\` array and set \`where\` to \`"1=1"\`. Do NOT construct a WHERE clause with IN(...).
+
+2. **queryResponse includes a \`where\` clause** \u2192 copy that exact \`where\` string and the \`layerId\` into \`targetLayer\`. Do NOT regenerate, rephrase, or simplify it.
+
+3. **Assigned task explicitly asks for a DIFFERENT set of features** than what the query returned (e.g., query found declined apps but assigned task says "now highlight the approved ones"), OR the assigned task asks to clear/reset filters \u2192 generate a new WHERE clause using the rules in "Generating new WHERE clauses" below.
+
+### Also forward geometryFilter and useCurrentExtent
+
+If the query tool call in the message history used a \`geometryFilter\` (spatial/proximity query) or \`useCurrentExtent: true\`, include the same parameters in your tool call. Without them, the filter would apply to the entire layer instead of just the spatially scoped features.
+
+## When to call a tool
+
+ALWAYS call a tool when:
+
+- The assigned task asked to "show", "find", "locate", or "where is" something
+- The assigned task asked a question that identifies specific features (e.g., "which has the highest...?", "find all X that are Y")
+- The assigned task wants to clear or reset filters of the map
+
+### No tool call
+
+Make no tool call when:
+
+- The query returned zero features
+- The assigned task asked a pure aggregate/statistical question (e.g., "what is the average?", "how many total?")
+- No meaningful filter can be generated
+- The assigned task was fully answered by the query step with no need for map interaction
+- Even if objectIds are available in the query response, do not highlight features unless the assigned task explicitly asked to see, show, highlight or emphasize them
+
+## Generating new WHERE clauses (exception case only)
+
+Only use these rules when rule 3 above applies \u2014 i.e., the assigned task explicitly asked for a different feature set.
+
+- Use only the field's **\`name\`** in the expression \u2014 not the alias.
+- Use field \`type\` to choose operators:
+  - **String** \u2192 \`LIKE '%value%'\`, \`=\`, \`IN (...)\`
+  - **Number/Date** \u2192 \`=\`, \`<\`, \`>\`, \`BETWEEN\`, etc.
+- **Coded-value domain fields** \u2192 use the numeric/string **code**, never the domain name.
+- **Range domain fields** \u2192 use the listed min/max as valid bounds.
+- DO NOT use subqueries or \`SELECT\`.
+- Combine conditions with \`AND\`, \`OR\`, or \`NOT\` as appropriate.
+
+## 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'\`
+
+## Geometry and Spatial Queries (for setFeatureEffect)
+
+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)
+
+Q: "Find roads within 500m of park X"
+Target: Roads (what we want to find)
+Geometry: Park X (specific location)
+
+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.
+`;export{e as default};