ArcSDE data won't appear at all zoom levels

[deleted-user-XYH0uc33lKDp]

I have a number of vector datasets I just loaded into ArcSDE (SQL Server 2008 R2, ArcSDE 10 sp2, geography datatype) and when I view the data in ArcMap 10 sp2 the data will display only if I am zoomed in closer than ~1:50m (it varies based on the dataset).  This is a problem for me since I am working with countrywide datasets and required to use the geography datatype. 

Is this a spatial index problem or is there some other setting that I need to alter?  I've tried a number of things that I read on the forums today but nothing seems to work.  And btw, my geomerty datatype SDE databases work fine at all scale levels. 

Thanks for in advance for any tips or ideas.

Ben Spaulding

[deleted-user-XYH0uc33lKDp]

and all the data are set as GCS_WGS_1984

[MelitaKennedy]

Hi Ben,

Two things to check--spatial index (does it look reasonable?) and try using sdelayer -o alter to update the layer's extent with the -E option.


sdelayer -o alter -l <table,column> [-e <entity_mask>] [-M <minimum_id>]
[-S <layer_description_str>] [-k <config_keyword>]
[-i {<service> | <port#> | <direct connection>}] [-s <server_name>]
[-D <database_name>] [Spatial_Index] [-L <ON | OFF>]
[-E <{empty | calc | xmin,ymin,xmax,ymax}>]
[-G {<projection_ID> | file=<proj_file_name}>]
[-P HIGH[{-R <SRID>|[Spatial_Ref_Opts]}]]
-u <DB_user_name> [-p <DB_user_password>] [-N] [-q]


Melita

[VinceAngelo]

This might be an artifact of the GEOGRAPHY restriction against antipodal construction (if the search
window exceeds 180 degrees of longitude, the search will fail).  I'm not sure how you're going to meet
the GEOGRAPHY requirement when multiple countries occur in more than one hemisphere.

- V

[deleted-user-XYH0uc33lKDp]

I can understand the mult-hemisphere problem, but I am having this issue with a features wholy located in a single hemisphere (northern and eastern, let's say) and about the size of Austria.

I'll try sdelayer command and see what happens.

thanks!

[deleted-user-XYH0uc33lKDp]

Quick update.  I changed my workflow and now only use geomerty datatypes and everything works perfectly.

[ShannonShields]

I can understand the mult-hemisphere problem, but I am having this issue with a features wholy located in a single hemisphere (northern and eastern, let's say) and about the size of Austria.

You are probably encountering the other Geography type limitation - features cannot extend past 90 degrees north or -90 degrees south. If you are zooming into northern Europe and the upper limit of your display window exceeds 90 degrees latitude then the spatial filter (zoom window extent) that is passed to SQL Server will fail and no results will be returned.

-Shannon