Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uploaded polygon shapefile does not tile render properly upon zoom #3

Open
GoogleCodeExporter opened this issue Jan 14, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.upload the file
2.fusion tables>Visualize>Map>zoom in/out
3.certain features will not render at random 

What is the expected output? What do you see instead?
all features (polygons) should be visible at all zoom levels, but this is the 
problem.

What version of the product are you using? On what operating system?
Windows 7 on Chrome 

Please provide any additional information below.
these polygon layers have a large amount of boundary vertices

Original issue reported on code.google.com by [email protected] on 27 Sep 2012 at 1:44

Attachments:

@GoogleCodeExporter
Copy link
Author

This is not a problem with shpescape, it is a feature in fusion tables.  Fusion 
Tables does this so both the server and your computer do not get overloaded.

Original comment by [email protected] on 7 Oct 2012 at 11:41

@GoogleCodeExporter
Copy link
Author

Issue was resolved the long way:  Converted shapefile to kml in ArcMap using 
Conversion tool "Feature to KML" (only saves as .kmz), Opened in G-Earth, saved 
as .kml, opened in text editor (Npad++) and manually copy and pasted each 
coordinate scheme for every polygon (80 features) into new fusion table.

After doing this the first time I noticed something:  All of the features from 
the kml were enclosed as <MultiGeometry></MultiGeometry>  (not just the 
polygons of the file that were true multipart features.  When using Shpescape 
it only encloses multipart features in as <MultiGeometry>, (which makes sense), 
and all single part features as just <Geometry>.  Come to think about it I 
think I have had this problem before : if there is a multi-part feature that 
borders a single part feature (polygon) something (inconsistently) goes awry.

Thanks for your comments, I use your product frequently.

Original comment by [email protected] on 8 Oct 2012 at 7:24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant