topic Re: CoordinateConversion widget use GeometryService instead of client-side projection in ArcGIS JavaScript Maps SDK Questions

Why CoordinateConversion widget use GeometryService instead of client-side projection ?

FlavieMoraux — Fri, 26 Jul 2019 09:29:31 GMT

Hy,

According to spatial reference of the map CoordinateConversion widget use a projection function of geometry service :

By default it is geometry service of ArcGIS Online, but possible to set client geometry service :

esriConfig.geometryServiceUrl = "....";

My questions are :

Why widget use geometry service when there is exactly what is needed client-side ?
Is it possible to use esri/geometry/projection function in standard CoordinateConversion widget for standards formats ?

Regards,

Flavie

Re: CoordinateConversion widget use GeometryService instead of client-side projection

RobertScheitlin__GISP — Fri, 26 Jul 2019 12:50:30 GMT

Flavie,

The likely reason is that the Projection class is a Large payload that the API team lets you decide if you want to load that heavy module. They do not assume that you want that amount out payload added to your app just because you are using the cordinateConversion widget. I don't believe that it is possible to specify that the widget uses the projection class instead of the default geomertyService.

Re: Why CoordinateConversion widget use GeometryService instead of client-side projection ?

FlavieMoraux — Mon, 29 Jul 2019 11:25:41 GMT

Yes, I understand that Projection class is a large payload, but in return it penalize performances for user.

Two modes would have been useful (geometry service or api).

Re: Why CoordinateConversion widget use GeometryService instead of client-side projection ?

RobertScheitlin__GISP — Mon, 29 Jul 2019 12:26:08 GMT

Then you need to contact esri tech support and request an enhancement.

Re: Why CoordinateConversion widget use GeometryService instead of client-side projection ?

FlavieMoraux — Mon, 19 Aug 2019 13:33:03 GMT

Problem occurs only with Internet Explorer 11 and this limitation is enounced in api documentation :

Internet Explorer 11 does not support WebAssembly, so the clientside projection engine will not work.

Client side projection engine work with Firefox and Chrome.