I am new to arcgis and i have tried to use the right terminology.

I have a Query Feature Class consisting of Polygons and points referrencing a non-geodatabase that I have published as a service via arcmap (10.3.1). This service appears to have published correctly and when querying the layer directly via a browser everything appears to work correctly, as it does inside arcmap prior to publishing.

When I import this into a map in arcgis-portal the service displays as I expect the polygons are projected over New Zealand as expected.

However when I use the data table in the map and "centre on selection" from the table drop down the map zooms to Italy when the polygon was displaying on New Zealand, with a blue outline of the shape I have selected over italy.

This is strange as when I import the service the polygon itself displays correctly as does the popup. This behaviour also appears using the query object in the web app builder. It only seems to appear on service based from queries and not when i publish the service via a file-geodatabase.

Has anyone seen this behaviour before?

These are how the geometires look intially

This is what happens when you center on selection or use the query widget the development tool

  • 1
    Assuming by "Query Feature Class", you mean Query Layer Are you certain that the field you've designated as the unique value field has no duplicate values? – Kirk Kuykendall Mar 23 '16 at 3:31
  • 1
    Do you have any geometries in your table that are over Italy? – Kirk Kuykendall Mar 23 '16 at 3:50
  • 1
    Have you checked the projection of the query layer as well as the projection of the data frame? – MickyT Mar 23 '16 at 5:44
  • 1
    Along the same lines as @MickyT - this sounds like an issue with the transformation between two projections. Can you check the basemap projection that is used on your map (or is it a default ArcGIS Online basemap?), what's the WKID? And of your published service based on the query feature class, what projection is given in the service definition? Ideally these should match, or have a transformation between the two which the Portal viewer can handle. Unfortunately the way Portal handles projections isn't ideal. – kes Mar 23 '16 at 11:00
  • 1
    "tried to use the right terminology" lol, Esri can't even decide what to call things and they keep changing their terminology. +1 just for that intro line, don't worry about it... – Stella Dec 28 '16 at 22:20

When viewing a feature or map service in the ArcGIS Portal Map Viewer if the mapservice projection doesn't match that of the basemap the viewer will try to re-project the layer using your Geometry Service*.

If this doesn't work you can either;

  1. Change the Basemap to one that matches your mapservice, or
  2. Project the data to match the basemap and publish, or
  3. Project the mapservice to match your basemap when publishing

Changing the Basemap

The default ArcGIS Online basemaps are in the Web Mercator Projection (WKID:3857), if your data is country specific you may be able to use a base map for that country or projection.

Project your data to match the Basemap

If your data is static or changes infrequently you could re-project to feature class to match the desired basemap, using the Project Tool. Be sure to specify a transformation if required for your project.

For advanced users with Query Layers your DBMS may offer native projection functions, e.g. for Oracle Spatial.

Reprojecting your Mapservice to match the basemap

Publishing your Mapservice in a different projection allows you to choose the best transformation for your data.

  1. In ArcMap, set the Projection of the map document Data frame and specify the desired transformation. For the ArcGIS Online default basemaps use the Web Mercator Projection (wkid:3857).
  2. Publish the map service and check the rest service definition is displaying the spatial reference code for the projection you specified. The query layer will be transformed by your ArcGIS Server instance on the fly.

If your mapservice is always used in this projection this should perform better than clients going via the Geometry Service to project the data.

Geometry Services

The re-projection in portal will use the Geometry Service from your organisation's utility services. If strange things are happening first check that this is setup and running.

The Geometry Service uses default transformations which may be not be appropriate for your projections, and unfortunately it isn't yet possible to configure or specify the transformations used by the geometry service.

|improve this answer|||||

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.