Latest Contributions by NicolasGIS

A functionality we kept being asked about, is the ability to visualize units occupancy across time in ArcGIS Indoors Space planner. We have lot of changes to manage and users coming for a defined period of time. It would be very nice if we could have "time-awareness" in the assignment (user will be in this unit from / to) and the ability then to visualize occupancy across  time thanks to a slider. Hope that makes sense ! Thanks for listening ... View more

Currently, ArcGIS Indoors floor display behaviour is inconsistent depending on the client used: - ArcGIS Indoors viewer / ArcGIS Space planner: display the current floor for the selected building (eg: floor 2 / VERTICAL_ORDER = 2) and all the others building floor displays floor R / VERTICAL_ORDER = 0 - ArcGIS Indoors nativ application: display the current floor for the selected building (eg: floor 2 / VERTICAL_ORDER = 2) and all the others building floor displays the very same floor 2 / VERTICAL_ORDER = 2 -ArcGIS Field Maps: display the current floor for the selected building (eg: floor 2 / VERTICAL_ORDER = 2) and hide all the others buildings floor For our campus, our favourite floor management display is the one of ArcGIS Indoors nativ application. It is the best way to understand the floor layout and the connexion between buildings.  ArcGIS Indoors viewer / ArcGIS Space planner current floor management is prone to confusion: you may think there is connexion between 2 buildings at floor 2 while there is not because the corridor connecting the 2 buildings is at floor R (VERTICAL_ORDER = 0). So (to me) it would be nice to either have the floor picker behaviour of ArcGIS Indoors nativ application in all ESRI clients supporting Indoors. Or if not possible because is some situations you would prefer another one, to be able to customize it at the application level. But from a developer perspective, it would be very nice if this configuration could be backported to the "ArcGIS Maps SDK for JavaScript" FloorFilter widget. Thanks for listening ! ... View more

Hello, In a webapplication, I using an ImageServer to query pixels values of several rasters through an ImageServer. I would like to extract the boundaries of the rasters so as to expose them to the end users of the web application (so that they know the area covered by the data they querying). I can't find a way to do so from an ImageServer service. If I publish the mosaic dataset as a MapServer, it's possible but ideally I would to avoid multiplying services for resources optimization. Did I miss anything ?  Thanks, Nicolas ... View more

Hello, I am facing an issue with ArcGIS Server network service. Whenever I try to solve a route with a barrier point of type 'added-cost', it fails with the following error:  "Point barriers cannot have a field value of BarrierType = \"ScaledCost\"." According to the documentation, it should be doable: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/barriers.htm It's also reproductible on ArcGIS Online routing service: https://codepen.io/NicolasGIS/pen/NWENNPY?editors=100  (copy paste code in RouteLayer sandbox as it requires a token: https://developers.arcgis.com/javascript/latest/sample-code/sandbox/?sample=layers-routelayer Did I miss anything or does it look like a BUG ?   Thanks,   Nicolas ... View more

Hello, Using ArcGIS Enterprise 11.1, I published a scaled based symbology FeatureServer and MapServer: https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/scale-based-symbol-classes.htm I created a JS API 4.27 application and noticed that my FeatureLayer does not honour this scaled based symbology. Digging a little more, I understood that it depends on its instantiation: - Instantiation with portalItem, works: const poiFLLayerByPortalItem = new FeatureLayer({    portalItem: {       id: "c3d95b4ce5df4882a6f73723492af00f"     } });   - Instantiation with a featureServer URL does not work:   const poiFLLayerByFLId = new FeatureLayer({    url: "https://ags.company.com/arcgis/rest/services/General/POI_TEST/FeatureServer/0" });   - Instantiation with a MapServer URL does not work either:   const poiFLLayerByMLId = new FeatureLayer({     url: "https://ags.company.com/arcgis/rest/services/General/POI_TEST/MapServer/0" });   It looks a bit weird to me: I would expect all featureLayer to be consistent in behaviour when consuming the same service. Is it a bug or somehow a feature I would miss ? Should a case be opened ?   Thanks,   Nicolas   PS: can share a URL illustrating this issue to JS API team if you want to have a quick look ... View more