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

shapefiles check #13

Closed
springmeyer opened this issue Sep 4, 2011 · 2 comments
Closed

shapefiles check #13

springmeyer opened this issue Sep 4, 2011 · 2 comments

Comments

@springmeyer
Copy link
Member

The mapserver mapfile I think uses some shapefiles in wgs84. Early on we discussed with the mapserver team about ensuring these would be in mercator for the main test, and then there will likely be a fully reprojected test (where map request will be in wgs84).

So, just flagging an issue that we may need to change the style first thing next week when I can get more info on this.

shapefiles should be from: http://mapserver-utils.googlecode.com/svn/branches/imposm-branch/data/

@springmeyer
Copy link
Member Author

yep, it appears the mapserver style never made any changes (as discussed), so to match correctly we need to use the exact shapefiles (in some cases in 4326). as far as boundaries (the one custom shapefile) imposm branch got deleted it appears, so 'boundaries.shp' can be found in trunk at http://mapserver-utils.googlecode.com/svn/trunk/data/

springmeyer pushed a commit that referenced this issue Sep 5, 2011
…ct on performance (todo need to use shoreline300 and processed_p for high res) - refs #13
@springmeyer
Copy link
Member Author

closing this. now have references to both 4326 layers. next shapefile task is #18.

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

No branches or pull requests

1 participant