|
POST
|
All internal, we're federated, using internal security (not enterprise or SAML), a pretty vanilla installation really.
... View more
03-18-2020
11:08 AM
|
0
|
0
|
1859
|
|
POST
|
Hello! FYI I opened a case with Esri tech support - which is still open. The analyst managed to recreate the issue; now I'm trying to convince them that this is a bug. Also FYI we're doing the same exercise with SharePoint Online vs. SharePoint on-premise and the results have been quite similar. Using OAuth against SPO is easy and straightforward; we still haven't gotten OAuth to work against SharePoint on-premise. Cheers!
... View more
03-17-2020
08:19 AM
|
0
|
2
|
1859
|
|
POST
|
We are currently evaluating the pros and cons of ArcGIS Online vs. ArcGIS Enterprise. Part of that evaluation involves determining the differences in implementing our automation toolsets. These are written in Python and consume ArcGIS via the REST API. In both ArcGIS Online and ArcGIS Enterprise we are serving a hosted feature service and an app (with its ClientID and ClientSecret). Both are shared with a group. For all intents and purposes, both the AGOL and the AGEnt implementation patterns are identical. Running with same code returns different results: An access token is obtained using the ClientID/ClientSecret. Using that access token to query the feature service returns the desired JSON payload when consuming from AGOL (i.e., features and geometries). Using the access token to query the feature service when consuming from AGEnt returns a code 498, Invalid token. Why is this happening to me? Below is the executed Python TIA query_string = {"client_id":appID,"client_secret":appSecret,"grant_type":"client_credentials"}
# get an access token
response00 = requests.post(tokenUrl, params=query_string)
access_token = response00.json()["access_token"]
where = "1=1" # MAGIC where clause
params = {"where": where, "outFields": "*", "f": "json", 'token': access_token}
response01 = requests.post(url = featureServiceQueryUrl, params = params)
# extracting data in json format
data01 = response01.json()
fields = data01.get('fields')
features = data01.get('features')
... View more
12-26-2019
10:21 AM
|
0
|
5
|
2044
|
|
POST
|
I think I already know the answer to this question (no), but I am querying here in case I missed something or anybody else has posited this idea. TIA.
... View more
12-02-2019
03:42 PM
|
1
|
1
|
1017
|
|
POST
|
No errors in console or in network traffic. esriConfig.request.proxyUrl and urlUtils.getProxyUrl() both have values i.e., the proxy URL after the proxyUrl has been set
... View more
10-02-2019
01:59 PM
|
0
|
1
|
2117
|
|
POST
|
Yes, pinging the proxy returns the expected results. The proxy is configured correctly. Thanks.
... View more
10-02-2019
12:02 PM
|
0
|
1
|
2117
|
|
POST
|
Below is simple code to add a secure webmap into a MapView. This issue is that the proxy URL in not pre-pending to the Portal item URL. Instead I get the login dialog. I expect to see a URL like this in my network traffic: https://MY_PROXY_URL/EsriResourceProxy/proxy.ashx?https://MY_PORTAL_URL/portal/sharing/rest/content/items/4b0a97623245423fb3cbdfb321f0970e which successfully returns content in the browser. This indicates that the proxy is properly configured and the values in proxy.config are correct. Instead, I see native URLs like this in my network traffic: https://MY_PORTAL_URL/portal/sharing/rest/content/items/4b0a97623245423fb3cbdfb321f0970e which informs me that I do not have permissions. So, my question is: how do I get my JS to format the request Url to be pre-pended with the proxy URL? TIA <script>
require([
"esri/views/MapView",
"esri/WebMap",
"esri/config"],
function(
MapView,
WebMap,
esriConfig) {
esriConfig.request.proxyUrl = "https://MY_PROXY_DOMAIN/EsriResourceProxy/proxy.ashx";
esriConfig.portalUrl = "https://MY_PORTAL_DOMAIN/portal";
var webmap = new WebMap({
portalItem: {
id: "4b0a97623245423fb3cbdfb321f0970e"
}
});
var view = new MapView({
map: webmap,
container: "viewDiv"
});
});
</script>
... View more
10-02-2019
10:47 AM
|
1
|
8
|
2274
|
|
IDEA
|
The advantage is obvious: don't need compiled code, there's heaps of Python developers, SOI/SOE's made much easier. Lofty, yes. But the return on that investment will be astronomical.
... View more
04-17-2019
09:29 AM
|
2
|
1
|
555
|
|
POST
|
I have a feature service that is fed by Survey123 inspections. I want to post-process the inspections that were collected in the past 24 hours and ignore all the other inspections. According to the documentation (https://developers.arcgis.com/rest/services-reference/query-feature-service-.htm) all I need is a time extent. For example "1546384695911,1546471095911" is the time extent for the 24 hours prior to about 0400P MST 1/2/2019. However the time parameters seem to have no affect on the filtering of returned records. For example, if I use the values from the API documentation (time=1199145600000, 1230768000000 (1 Jan 2008 00:00:00 GMT to 1 Jan 2009 00:00:00 GMT)), I still get result records, even though I know that there are no records between 1 Jan 2008 00:00:00 GMT to 1 Jan 2009 00:00:00 GMT. The documentation is pretty vague about what constitutes "time" and I am wondering what I'm not doing right. Does the feature service need to be time-aware? Any help or sage bits of wisdom would be much appreciated.
... View more
01-02-2019
04:36 PM
|
0
|
2
|
1325
|
|
POST
|
Thanks Kelly, your response didn't solve my problem, but it did focus my troubleshooting in a different and ultimately correct direction. The solution was to: Upgrade TypeScript to the latest version ( npm install -g typescript@latest ) Upgrade the ArcGIS type definitions to the latest version (npm install --save @types/arcgis-js-api) Update tsconfig.json to include the line "jsxFactory": "tsx" I now have a clean tsc and my widgets are correctly displaying in the DOM. Thanks again. Cheers!
... View more
09-28-2018
10:16 PM
|
1
|
0
|
1142
|
|
POST
|
We have a JSAPI v.4.3 application that we wanted to upgrade to 4.8. The application uses custom widgets that are built on TypeScript. I upgraded the TypeScript definitions when I changes the JSAPI version from 4.3 to 4.8. The 4.3 JS application uses: var view = new MapView({ map: webmap, container: "viewDiv" }); view.then(function(e){ // do something with e }) At 4.8, view.then() is replaced with view.when() However, this affects the constructor of our custom widgets (in TypeScript tsx file). Specifically: render() { return ( <div bind={this} class={CSS.base}> <!-- build a DOM here --> </div> ); } The application is failing with an error in Chrome: Uncaught (in promise) TypeError: Cannot read property 'createElement' of undefined at Object.MyWidget.render (MyWidget.tsx:50) Stepping through code in the debugger indicates that this exception occurs in the view.when(). The 'createElement' property indicates to me that an attempt is being made to create the DOM but that it cannot find itself. (?) The application is failing with an error in Firefox and MS browsers that are not thrown to the console – instead an alert is displayed in the browser (FF) or Developer Tools (MS) with the following text: Could not locate http://<URL>/<path>/MyWidget.tsx specified in http://<URL>/<path>/MyWidget.js. I have verified that the tsx is correctly specified in the js file, even though the browser says otherwise. I’m not sure how to reconcile these different exceptions, let alone resolve this issue. It is critical that we render the DOM, as it encapsulated our business logic. Does anyone have any thoughts on this issue? TIA
... View more
09-26-2018
09:54 PM
|
0
|
2
|
1582
|
|
POST
|
There was some discussion here about function Graphic.getDojoShape() works fine in js api 3. but it does not work in 4. Is there a more modern pattern for flashing graphics in the JSAPI 4x? TIA
... View more
05-24-2018
09:32 AM
|
0
|
1
|
780
|
|
POST
|
JSAPI4x I keep all my js code in a module (main.js) that loads when the page loads. I want to do some client-side projections - I'll need to include esri/geometry/projection. Unfortunately including esri/geometry/projection in a defined module thrown a 404 error: dojo.js:23 GET https://js.arcgis.com/4.6/esri/geometry/projection.js 404 () I can successfully load esri/geometry/projection in index.html - however I need to project in main.js. I'm not sure if I need to include other dojo or esri modules in order to include esri/geometry/projection. Make sense? define(
[
"dojo/_base/declare",
"dojo/_base/lang",
"esri/geometry/geometryEngineAsync",
"esri/geometry/projection",
"esri/identity/IdentityManager",
"esri/tasks/QueryTask",
"esri/tasks/support/Query",
"esri/Graphic",
"esri/layers/GraphicsLayer",
"esri/geometry/Polygon",
"esri/geometry/Polyline",
"esri/WebMap",
"esri/views/MapView",
"esri/views/2d/draw/Draw",
"dgrid"
],
function(
declare,
lang,
geometryEngineAsync,
projection,
IdentityManager,
QueryTask,
Query,
Graphic,
GraphicsLayer,
Polygon,
Polyline,
WebMap,
MapView,
Draw,
Grid
) {
return declare(null, {
aGeometry: null,
constructor: function () {
// console.log("constructor");
},
doSomething: function(){}
}
}) ...
... View more
05-23-2018
07:36 AM
|
0
|
1
|
1481
|
| Title | Kudos | Posted |
|---|---|---|
| 5 | 11-10-2021 12:27 PM | |
| 1 | 10-02-2019 10:47 AM | |
| 1 | 09-24-2021 08:40 AM | |
| 1 | 09-28-2018 10:16 PM | |
| 1 | 10-09-2015 08:26 PM |
| Online Status |
Offline
|
| Date Last Visited |
05-05-2023
03:51 AM
|