Latest Contributions by ReneRubalcava

That json is just an item that lives in ArcGIS Online. That won't change, and I think style updates are done as new items, so yes it's constant. Can you accomplish the same thing with the VT Style Editor? You can create your own style to use in your apps, and if you need to finetune it, you can edit the JSON in the editor. https://developers.arcgis.com/vector-tile-style-editor ... View more

When you use your built component in your application (the npm package) are you also using the ArcGIS JSAPI in your app? If so, you can't mix JSAPI instances in your app with your component. You'll see errors regarding the Accessor. This is equivalent to trying to create a MapView using @arcgis/core and loading a Map created with the CDN. It won't work. You can publish your component without including the JSAPI in your build, and let the build tools handle it in your app. I do something similar with this published utility library (https://github.com/odoe/explode). ... View more

Are you storing an instance of the Widget or Map in Vuex? You can't do that because Vuex wraps objects in native Proxy (nexted Proxies) and that will break our Accessor in the API. You can store the JSON instance of values or other things are interested in, but JSAPI instances. Here is a sample Vue application that uses Pinia (similar to Vuex) and only manages non-JSAPI data https://github.com/odoe/nearby-app ... View more

I checked that dataset and it is huuuge. You don't need to set the geometryType, GeoJSONLayer will figure it out, but the actual geojson takes a looong time to load. I was able to verify it changing the limit parameter to 1000. I could see some lines to verify that it's working. The GeoJSONLayer doesn't have a way to paginate over the results to try and stream them in. This is probably a case where it's better to download the GeoJSON and upload as a hosted FeatureService due to the sheer size. That dataset is still downloading on my machine, but this would definitely be a better candidate as a featureservice, because at that point we can take advantage of feature tiles, generalizing the geometries, and make it much more performant than raw geojson. Unless you can limit the results vie a where clause on the API, that's the route I would recommend. ... View more

This one is going to require a little bit of work to find what data you want, but can be done. Looking at the opendata console, you can request results as geojson and use the GeoJSONLayer. I think you would first want to pull in the datasets you are interested in. The API supports where clauses and other SQL queries, so you can limit to what you are interested in. Once you do that, you can grab. a dataset_id. I'm not familiar with this, but they look like long strings with domains maybe? Not sure that's what you're looking for, but it gets you to the next step.   This will give you the URL you can use to download the data in GeoJSON. https://data.opendatasoft.com/api/v2/catalog/datasets/zones-tendues-et-tres-tendues@dila/exports/geojson?select=*&limit=-1&offset=0&timezone=UTC Then you can use a GeoJSONLayer with customParameters to load it. https://codepen.io/odoe/pen/KKQPejP?editors=100   const geojsonLayer = new GeoJSONLayer({ url: url, // no parameters in this URL customParameters: { select: "*", limit: "-1", offset: "0", timezone: "UTC" }, copyright: "OpenDataSoft", renderer: renderer });   ... View more

Update your import syntax to import from the projection module. import * as projection from "@arcgis/core/geometry/projection"; Per here: https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-projection.html That should fix you all up!  ... View more

You don't need a typed Collection Collection.ofType(FeatureLayerView) When you do this, the Collection will try to initialize the added object as a new FeatureLayerView() and that doesn't work because it's already a class. If this is for TypeScript, you can do this. const featureLayersViews = new Collection<FeatureLayerView>(); ... View more