DDTI Forums :: Forum

	11/15/2007 1:15:52 PM permalink
kpgardiner Posts 2	Im having display issues w/ a polygon layer. The layer in question (a shapefile) is our city zoning layer with 181 polygons/records. Those 181 polygons/records are broken down into 11 different zoning classifications and I display them by these classifications. My problem occurs when I zoom to layer extent, which covers our entire city (our city is not large at ~12.37 square miles.) Anyhow, when I zoom to layer extent several of the polygons dont display so I end up with what appears to be an incomplete patchwork of zones. Interestingly enough, if I use the magnify tool to move in on one of the "holes" the polygon appears. There doesnt appear to be any consistency 1) in terms of a scale at which polygons appear/dont appear; and 2) with which polygons appear when zoomed to layer extent, e.g. its not limited to any one class. BTW, scale dependency is off for the entire layer as well as for each class in my value theme. If theres anyone out there whos experienced this before and/or knows of a fix, your insight would be appreciated. Many thanks in advance. Kevin
	11/15/2007 1:40:25 PM permalink
csudr Posts 11	Hi Kevin, AccuGlobe tries to minimize rendering times by optimizing source geometries. It is possible that some polygons are not considered to be valid (they could be self intersecting for example) and that may throw off some of the calculations. What i suggest trying (use a copy of your backup files for each step): a) Try running Main menu->Tools->Verify Layer which will see if the geometries are valid b) Try using the Clean geometry option for verify layer. c) Otherwise, email a copy to support at ddti.net including the forum url Dave
	11/30/2007 1:32:58 PM permalink
kpgardiner Posts 2	Dave, Many thanks for your reply. I took your advice and ran the verify tool on my zoning layer. I did in fact have three self-intersecting polygons, so I went ahead and moved some vertices to eliminate those self-intersections. I ran the verify tool on that edited layer and the geometry was good (no self-intersections or any other problems.) Unfortunately, the edited layer is drawing the same as the one w/ the self-intersections, e.g. its not displaying several zones. Im going to go ahead and send a copy of the original and edited zoning layers to DDTI. Thanks again. Kevin
	1/2/2008 6:17:26 AM permalink
m_agerlin Posts 37	A similar (?) problem occurs if you use AccuGlobe to create buffers. Try to make 25 concentric buffer rings with 100 m distance around a point and use AccuGlobe to save the graphics as a shape file. The shape file is okay when viewed in other GIS-viewers (TatukGIS), but in AccuGlobe only random rings are displayed. The verify tool finds a lot of errors (!!) but running the tool does not help the viewing in AccuGlobe. Processing file C:\Program Files\DDTI\AccuGlobe 2007\Testeks\100m_rings.shp FID: 1 failed valid geometry check (TooFewPoints At position: (-0.504305043050429, 0.30750307503075, NaN)) FID: 2 failed valid geometry check (HoleOutOfShell At position: (199.49569495695, 0.30750307503075, NaN)) FID: 3 failed valid geometry check (HoleOutOfShell At position: (299.49569495695, 0.30750307503075, NaN)) FID: 4 failed valid geometry check (HoleOutOfShell At position: (399.49569495695, 0.30750307503075, NaN)) FID: 5 failed valid geometry check (HoleOutOfShell At position: (499.49569495695, 0.30750307503075, NaN)) FID: 6 failed valid geometry check (HoleOutOfShell At position: (599.49569495695, 0.30750307503075, NaN)) FID: 7 failed valid geometry check (HoleOutOfShell At position: (699.49569495695, 0.30750307503075, NaN)) FID: 8 failed valid geometry check (HoleOutOfShell At position: (799.49569495695, 0.30750307503075, NaN)) FID: 9 failed valid geometry check (HoleOutOfShell At position: (899.49569495695, 0.30750307503075, NaN)) FID: 10 failed valid geometry check (HoleOutOfShell At position: (999.49569495695, 0.30750307503075, NaN)) FID: 11 failed valid geometry check (HoleOutOfShell At position: (1099.49569495695, 0.30750307503075, NaN)) FID: 12 failed valid geometry check (HoleOutOfShell At position: (1199.49569495695, 0.30750307503075, NaN)) FID: 13 failed valid geometry check (HoleOutOfShell At position: (1299.49569495695, 0.30750307503075, NaN)) FID: 14 failed valid geometry check (HoleOutOfShell At position: (1399.49569495695, 0.30750307503075, NaN)) FID: 15 failed valid geometry check (HoleOutOfShell At position: (1499.49569495695, 0.30750307503075, NaN)) FID: 16 failed valid geometry check (HoleOutOfShell At position: (1599.49569495695, 0.30750307503075, NaN)) FID: 17 failed valid geometry check (HoleOutOfShell At position: (1699.49569495695, 0.30750307503075, NaN)) FID: 18 failed valid geometry check (HoleOutOfShell At position: (1799.49569495695, 0.30750307503075, NaN)) FID: 19 failed valid geometry check (HoleOutOfShell At position: (1899.49569495695, 0.30750307503075, NaN)) FID: 20 failed valid geometry check (HoleOutOfShell At position: (1999.49569495695, 0.30750307503075, NaN)) FID: 21 failed valid geometry check (HoleOutOfShell At position: (2099.49569495695, 0.30750307503075, NaN)) FID: 22 failed valid geometry check (HoleOutOfShell At position: (2199.49569495695, 0.30750307503075, NaN)) FID: 23 failed valid geometry check (HoleOutOfShell At position: (2299.49569495695, 0.30750307503075, NaN)) FID: 24 failed valid geometry check (HoleOutOfShell At position: (2399.49569495695, 0.30750307503075, NaN)) FID: 25 failed valid geometry check (HoleOutOfShell At position: (2499.49569495695, 0.30750307503075, NaN)) Check Completed!
pages: 1

|