POST
|
Thanks for your input. That is the Durandal that we are using, and it functioned as intended in the 4.6 version. I can go back and confirm that it was working correctly but I didn't notice any weird behavior until updating to 4.14, which is why I thought there might be some weird interplay with the downloaded SDK and Durandal. Also there doesn't seem to be any errors in the console that are thrown.
... View more
03-26-2020
08:32 AM
|
1
|
1
|
537
|
POST
|
Egge, I am currently testing on the latest version of chrome. I have gone through all of the sample applications in the same browser and they seem to work as intended, so it doesn't seem to be a browser issue. The main differences I can see in my application are that I am using multiple featureLayers populated by client-side graphics and I am using a downloaded version of the SDK due to incompatibility with Durandal. This does make sharing any representative test application somewhat difficult. Do you know of any outstanding issues regarding the downloaded SDK or any other functionality that could act as a work-around for displaying information? Sincerely, Tyler Lawson
... View more
03-26-2020
07:57 AM
|
1
|
3
|
537
|
POST
|
I have been in the process of updating an application from 4.6 to 4.14 and have noticed something weird happening with my popup templates. Whenever I click on a feature, it opens the popup but the title briefly appears before vanishing. It doesn't seem to be related to the features, featureLayer, or renderer as I created test objects of each and it acts the same. Picture of blank title: Code for feature: var testFeatures = []; var feature = { Id: "Test", geometry: new Point({ x: -96.8107, y: 33.1509 }), attributes: { Name: "Test", ObjectID: 1 } }; testFeatures.push(feature); FeatureLayer: var lyrTest = new FeatureLayer({ // create an instance of esri/layers/support/Field for each field object fields: [ { name: "ObjectID", alias: "ObjectID", type: "oid" }, { name: "Type", alias: "Type", type: "string" } , { name: "Name", alias: "Name", type: "string" } ], objectIdField: "ObjectID", geometryType: "point", spatialReference: { wkid: 4326 }, source: testFeatures, labelsVisible: true, renderer: testRenderer, id: "TestLayer" }); lyrTest.popupTemplate = templateTest; map.add(lyrTest); Renderer: var testRenderer = { type: "unique-value", field: "Name", uniqueValueInfos: [ { value: "Test", symbol: new SimpleMarkerSymbol({ color: "blue", outline: { color: "blue", width: 1 } }), label: "Test" } ] }; PopupTemplate: var templateTest = { title: "Test Title", outFields: ["*"], content: "This is a test" }; Any suggestions as to what could be going on would be appreciated.
... View more
03-25-2020
02:50 PM
|
0
|
5
|
639
|
POST
|
Are there any updates on when this will be available in the 100.x version?
... View more
10-10-2018
07:14 AM
|
0
|
2
|
1261
|
POST
|
Unfortunately I have not yet found a good solution. To the best of my knowledge, the current solution would be to host the map package layers on an arcgis server as tiled layers or feature layers and access them that way. Resources: Basemap | API Reference | ArcGIS API for JavaScript 4.8 FeatureLayer | API Reference | ArcGIS API for JavaScript 4.8
... View more
08-20-2018
10:02 AM
|
0
|
0
|
571
|
POST
|
Currently, I have a map loading with a default streets basemap that shows some information. I was wondering if there was any way to load a local Map Package (.mmpk) file and add the layers to the map, similar to the functionality in the ArcGIS Runtime SDK for .NET. Any information on the topic would be helpful. Sincerely, Tyler Lawson
... View more
04-16-2018
12:19 PM
|
0
|
2
|
961
|
POST
|
This seems to work perfectly. Thank you for the quick response.
... View more
03-15-2018
10:28 AM
|
0
|
1
|
900
|
POST
|
Hello, Currently, I am trying to get some symbols to display on a map using a xamarin uwp project, but I am having a problem reconciling the color properties of various symbols in UWP. It seems like the color properties (i.e TextColor, BackgroundColor, etc) are based on System.Drawing.Color, which is incompatible with UWP. Is there some way to set the color properties of the symbols in Esri.ArcGISRuntime.Symbology or are there any other options that would be more compatible with UWP that accomplish the same thing? I have tried using Xamarin.Color but so far it has not worked. Example (Drawing a rectangle to put on map): //Set draw mode and create geometry Esri.ArcGISRuntime.UI.SketchCreationMode drawMode = Esri.ArcGISRuntime.UI.SketchCreationMode.Rectangle; Esri.ArcGISRuntime.Geometry.Geometry geometry = await this.map.SketchEditor.StartAsync(drawMode, false); //Create fill symbol var fillSymbol = new Esri.ArcGISRuntime.Symbology.SimpleFillSymbol(SimpleFillSymbolStyle.Solid, color, new SimpleLineSymbol(SimpleLineSymbolStyle.Solid, color, 2)); //color throws an error because it is not of the correct type //Create graphic based on drawn geometry and fill symbol and add to map var graphic = new Esri.ArcGISRuntime.UI.Graphic(geometry, fillSymbol); this.map.GraphicsOverlays["MapShapes"].Graphics.Add(graphic); Affected symbols and properties: TextSymbol: BackgroundColor, Color, HaloColor, OutlineColor SimpleFillSymbol: Color SimpleLineSymbol: Color NOTE: Symbols can be added to the map and manipulated by using the default symbol (default constructor with no arguments), however I have not been able to manipulate any symbol's color properties. Any help on this issue would be appreciated.
... View more
03-15-2018
09:44 AM
|
0
|
3
|
1251
|
POST
|
Hello, I recently came across an error while creating routes using RouteTask.SolveRouteAsync(routeParameters). If you include barriers in the routeParameters and one of the barriers intersects a shape containing curves (hasCurves = true), then it will error out and say "Not implemented: operation does not support curves yet". I have come across this error previously when querying a featureLayer and got around it by using relationships that compare curveless geometries (i.e. envelopeIntersects() instead of Intersects()) however this does not seem to be a valid work-around for this situation since the route needs more precision than that and I have found no way to alter the way it calculates the route to avoid comparisions using curved geometries. Does anyone know if there is any information on when this functionality (operation supporting curved geometries) might be available?
... View more
08-30-2017
11:19 AM
|
0
|
5
|
2924
|
POST
|
Thank you for the response. Unfortunately, due to the way I am accessing data, those workarounds don't work for me currently. However I was able to find a different work-around where instead of utilizing spacial queries that don't support curves (Intersects), you can use one that compares geometries without curves (i.e envelopeIntersects). This doesn't work perfectly, but it does allow a rough estimate of whether a geometry with curves intersects with a polygon.
... View more
07-18-2017
09:40 AM
|
1
|
0
|
751
|
POST
|
Currently, I am trying to find which features from a layer intersect with a polygon. However when trying to project the feature's geometry or perform a query against it (i.e a query with a spatial relationship against the layer or GeometryEngine.Intersects()), I get the following error: "Not implemented: operation does not support curves yet". From what I can tell, it only throws this exception when the geometry's HasCurves property is true. When this property is false, all queries and projection works as expected. Is there currently a way to perform spatial queries against geometries with curves, or any workarounds? If not, is there any information on when such functionality might be available? Any help or information regarding this issue would be greatly appreciated.
... View more
07-12-2017
12:31 PM
|
2
|
2
|
1357
|
POST
|
Update: For some reason, adding a BaseMapGallery to the view got the map to display correctly. However when I try to add some modules to the define/require statement (i.e FeatureLayer) I get a 404 error regarding loading the moment.js.
... View more
06-01-2017
01:42 PM
|
0
|
0
|
220
|
POST
|
Currently, I am trying to get a simple map to display in an application that uses requireJS. I have read in multiple places that the DOJO AMD loader that is built into the ArcGIS API conflicts with the requireJS and that the best way to work around this is to rely on requireJS to handle loading using a path structure to reference the API. I am using a locally hosted version of the API and referencing it using paths in a require.config. This allows my application to reference the API and it seems to be loading the modules successfully (The containing divs are populated with the controls and the view.then(success) function activates), but when the map is loaded, it does not display anything. Using the same code in a simple HTML page works correctly, with the map loading and successfully displaying, so I think that the problem might be something to do with requireJS/Dojo compatability. There are also no errors thrown when loading it in a browser. Any help with this issue would be greatly appreciated. Paths statement: Controls: Result (Area in blue box is the loaded map control) :
... View more
06-01-2017
11:28 AM
|
0
|
1
|
768
|
Title | Kudos | Posted |
---|---|---|
1 | 03-26-2020 07:57 AM | |
1 | 03-26-2020 08:32 AM | |
1 | 07-18-2017 09:40 AM | |
2 | 07-12-2017 12:31 PM | |
2 | 09-25-2018 11:18 AM |
Online Status |
Offline
|
Date Last Visited |
08-26-2021
02:44 PM
|