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

Southern Hemisphere misaligned #4

Open
Jeffreydaw opened this Issue Jul 7, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@Jeffreydaw
Contributor

Jeffreydaw commented Jul 7, 2017

Major Bug: The view and the data are offset from each other in the main map view for the Southern Hemisphere.

Details:
The details of this bug are a little strange. The problem only seems to exist at the max zoom. It is most visible when a point near the equator is viewed with the Basemap of "Esri world Imagery" is selected.

At max zoom, the view seems to be shifted about 70Km West from the data in the southern hemisphere. For the Basemaps of "Esri world Imagery" and "Esri Ocean Basemap" the problem is more visible since the basemap is in the correct location but the data and the Bathymetry maps are shifted. for the "ETOPO1 Topography" Basemap the problem is harder to see since the basemap is shifted the same amount as the layers on top.

The problem only exists in the global view map projection (the pole projections are fine)

Proving that the data is shifted from the view can be done using the "line" drawing tool.

selection_007

selection_005

In the above image the red rectangle shows where the map was displaying the land but the green rectangle shows where the land was accorading to the data. link

shift near the equator
url

Problem first noticed in Verson: 2ae745d

@Jeffreydaw Jeffreydaw added the minor bug label Jul 7, 2017

@Jeffreydaw Jeffreydaw changed the title from SEO not implemented to Southern Hemisphere misaligned Jul 7, 2017

@htmlboss htmlboss added severe bug and removed minor bug labels Jul 17, 2017

@Jeffreydaw

This comment has been minimized.

Contributor

Jeffreydaw commented Jul 28, 2017

According to Geoff this is likely a result of the script that was used to create the topographic Maps. The script was run slightly differently on each zoom level. There was probably a mistake for the max zoom level. He suggested using the same script that was used to creat the maps of the poles. This is a python script that can be found on Trinity in /home/gholden/src/regrid/regrid_script_webmerc.py OR /home/gholden/src/regrid/view regrid_script_3031.py

This running the script with the correct files and fixing any errors in the script should generate a proper topographical file which can to used to completely fix this problem. This is because the bathymetry and the mask for the heat map are both generated from the same file.

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