Zum Hauptinhalt gehen

Feature offset with instant search results

Kommentare

6 Kommentare

  • Permanently deleted user
    I had the same issue. I had to apply a geographic transformation on the data frame in the mxd (to WGS 1984), republish the service, then delete and recreate the instant search index. Then everything aligned properly.
    0
  • Permanently deleted user
    Thanks, Rebecca. I did see the other thread on this. I'm only using base maps in my UTM projection, though, so why would there be a transformation necessary? Were you using Esri base maps, or was your issue similar to mine with local base maps?
    0
  • Permanently deleted user
    I'm using my own data for basemaps. I went throught this issue with support and they told me that somehow instant search uses WGS 1984 which requires the transformation (or something like that). The transformation worked for me to get it working for now. Hopefully they'll address this in future releases.
    0
  • Permanently deleted user
    Good to know that there is something I can try! Thank you very much.
    0
  • Permanently deleted user
    I'm still getting an offset after adding a transformation to the mxd, republishing, deleting the index and re-creating it: just a smaller offset. I guess this is acceptable.

     

    _img_ alt="feature offset" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000XZi5&feoid=Body&refid=0EM60000000XqFd"_/_img_
    0
  • Permanently deleted user

    I know it is an older case. But how do you do the transformation? Do I need to contact support for help with this, or is it something that can be done relatively easy with our support?  

     

     

    Thanks,

     

    Nataliya

     

     
    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.