ExB Search widget should not assume output spatial reference to be EPSG 4326
183
0
02-10-2026 05:55 AM
by
I was very happy to discover the ExB Search widget supports projected coordinate systems. All you have to do is include the EPSG code when you enter the coordinates. It is documented here.
When you use this feature, a request is sent to the GeometryServer to transform the coordinates. However, when I examined the web traffic I can see the requested output spatial reference is EPSG 4326:
Our basemaps are in EPSG 2953. Why does the Search widget presume I want the output in EPSG 4326? This extra transformation degrades the output accuracy.
My Idea - Add configuration options to the Search widget to allow me to:
- set the preferred output spatial reference, or
- set the preferred output spatial reference to match the spatial reference of the basemap.