example of shapefile where basemap is not displaying

[GoogleCodeExporter]

GeoDa 1.7.35 (beta 1 July 2015)

See email of July 8, 2015 for link to shapefile.

"This county-level dataset has a .prj file but the basemap won't load. When you 
try to load it the map is reduced to a point."

Original issue reported on code.google.com by jkosc...@asu.edu on 8 Jul 2015 at 2:20

[GoogleCodeExporter]

this is a bug when the west/east get confused with maps having wide range.

Original comment by lixun...@gmail.com on 8 Jul 2015 at 9:49

• Changed state: Accepted
• Added labels: Milestone-Release1.8

[GoogleCodeExporter]

This bug will appear when the extent of the map is across the  longitude 180 
degree border. E.g.
the far west alaska (about 160 degree)  to east the longitude will from 160 ~ 
180 degree ~ then start from -180degree ~ (to east) 0 degree. 

Fix is propose in ci 3691.

Will be applied in build 1.7.37

Original comment by lixun...@gmail.com on 9 Jul 2015 at 6:03

• Changed state: Started

[GoogleCodeExporter]

another issue is the initial extent of the example data seems not matching the 
map (no basemap). This is caused by the reprojection "distorted" the map. So, 
when project that the extent of the "distorted" map with wgs84, the extent is 
not equal to the extent when project in wgs84.

Original comment by lixun...@gmail.com on 9 Jul 2015 at 6:04