nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem with zoom in ArcGis OnLine

LeandroCalabrese

Hi,

We have added in an ArcGis OnLine map application some Buenos Aires district polygons. The data is stored in Oracle Locator, using a local projection System (Posgar 2007, Faja 5, csid 5347), and we published it using a WS in our local server. In WebAppBuilder , the polygons seem to fit the base map:

The strange thing comes when we zoom using the attributes table. When we double click in any row, the application zooms to Kasakhstan:

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

BrianHall1

I am not using ArcSDE, but I did notice that you can't zoom into a selected row in the "view attribute table" in AGOL if the name you gave your GIS layer in the TOC (via rightclick > properties>general) is not the same name as the file in your local GDB.

PascualBenito

As follow up to my earlier question/comment. We did further testing and I believe we have discovered that the problem is not in WAB, but is actually possible BUG in ArcGIS Server when returning results for spatial layer that is coming from a non-ArcSDE geography type that is in different projection than the rest of the layers. In our case problem is actually happening on ArcGIS Server side of things and strongly looks like is a bug in how it is handling returning the geometry coordinates for queries against a feature class which is not an ArcSDE feature but is a SQL Spatial geometry object. ArcGIS Server is asked to return the coordinates for the feature in Web Mercator (e.g. meters), but it is incorrectly returning the lat long values of the coordinates and then attempting to go there in Web Mercator system which is close to 0,0, and sends us off to west coast of Africa.

We tested out the map request directly from the ArcGIS Server Rest endpoint and this is how we isolated problem:

This is example of the query that WAB was running when we clicked on attribute table:

WAB sends request to zoom to feature which is in WGS84 SQL Spatial geometry (and should should be returning geometry in Web Mercator wkid=102100 coordinates):

https://servername/arcgis/rest/services/PWA/ACPWA_MaintStar_Viewer/MapServer/101/query?f=json&where=&returnGeometry=true&spatialRel=esriSpatialRelIntersects&objectIds=5&outFields=*&outSR=102100

Response - appears that ArcGIS Server returns Long/Lat values for coordinates instead of the requested Web Mercator:
{"displayFieldName":"wo_no","fieldAliases":{........:"edited_by","edit_dt":"edit_dt","ESRI_OID":"ESRI_OID"},
"geometryType":"esriGeometryPoint","spatialReference":{"wkid":102100,"latestWkid":3857},"fields":
....
"approved_by":null,"approved_by_desc":null,"problem":"Needs desilting","wo_comments":null,"insp":0,"inspection_type":null,"insp_By":null,"insp_By_desc":null,
"insp_By_user":null,"rating":0,"edited_by":"APPADMPASCUAL","edit_dt":1456250125000,"ESRI_OID":5},"geometry":{"x":-122.06906986999996,"y":37.699190387000044}}]}

We are using ArcGIS Server 10.3.1. We are going to be opening support ticket with ESRI.

PascualBenito

Hi Leonardo, just curious if you ever resolved this issue or learned more about the source of problem? We're having similar issue where we have a feature class coming from SQL Spatial that is defined in WGS 84. Our MXD and Map Service is in California State Plane NAD83 (all of our other data is in this projection), and whenever you click on the feature in the Portal (or AGOL) map viewer or WAB attribute table, the map pans over to (0,0) instead of to the actual feature location (which shows up fine on the map). At the moment my theory is that there is some bug in AGOL map viewer attribute table widget that is getting confused with the fact that the feature has different spatial reference than the map service and because data is not coming from ArcSDE source (I assumed that ArcGIS server takes care of reprojecting on the fly etc..). The problem doesn't occur if I publish the layer alone as WGS84, but I was hoping to keep everything in a single map service because of some other custom widgets that operate on the map service layers.

DanPatterson_Retired

The data are definitely projected using

Projected Coordinate System: POSGAR_2007_Argentina_Zone_5 and it has the right longitude for its central meridian, the problem must be with the way it is being translated to decimal degrees. Interesting though, is the latitude of origin is -90, is there a chance that the negative for longitude is getting truncated?

LeandroCalabrese

Robert

Here I attached the file you requested .

ba_districts.tozip.zip

CustomerNo.PNG

RobertScheitlin__GISP

Leandro,

Could you provide a zip containing some Buenos Aires district polygons as a shapefile for testing?

DanPatterson_Retired

longitudes -60ish Beunos Aries, 60ish Kazakhstan ... not a coinidence I suspect, missing the -ve sign or E vs W is not being translated somewhere to numeric format

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.