Polygon corruption when changing projections
Home › Forums › Natural Earth Map Data › Physical Vectors › Land › Polygon corruption when changing projections
- This topic has 9 replies, 1 voice, and was last updated 14 years, 3 months ago by
David Medeiros.
-
AuthorPosts
-
December 6, 2011 at 5:24 pm #4297
NathanielKeymasterAre you using the latest version 1.4 off the website today?
December 6, 2011 at 5:30 pm #4298
David MedeirosParticipantSorry forgot to mention that, yes, I just downloaded a new copy of the data set this morning just to be sure. If you want to see what this looks like you can go here: http://www.cartotalk.com/index.php?showtopic=7777
December 6, 2011 at 6:04 pm #4299
NathanielKeymasterWhat extents does the NE data show in geographic before you project it? Is it all within the ±90/±180 envelope?
December 6, 2011 at 6:15 pm #4300
David MedeirosParticipantI just arrived at work and don’t have the file or software here to look at. I’ll check this afternoon when I get home and get back to you.
December 6, 2011 at 11:45 pm #4301
David MedeirosParticipantNathaniel, I’m looking at the file now, not sure what you are referring to. None of the polygon extends beyond the art board in Illustrator if that’s what are you asking about.
December 7, 2011 at 12:31 am #4302
NathanielKeymaster@David:
In QGIS (available for Mac for free), you can view the extent metadata for the countries SHP:
Extents:
In layer spatial reference system units : xMin,yMin -180,-89.9998 : xMax,yMax 180,83.6338
Not sure how to get that in MP. Don’t see it immediately in my copy.
So if you’re using 1.4, this error shouldn’t be happening. In fact, when I project to Winkel Tripple, I get the expected result. My guess is your page is set to be small (letter?) and when MP imports the data, it rounds out of the ±180/±90 envelope, creating this problem?
I suggest you take it up with MP support and report back here, please.
_Nathaniel
December 7, 2011 at 1:23 am #4303
David MedeirosParticipantOk, I tried it with a page set to 24″ x 24″, re projected with no issues so it is the page size. Not sure I understand why that matters since the imported map always fill the page width exactly no matter the size. I’ll take it up with MP and see what they say. Thanks!
December 7, 2011 at 2:02 am #4304
NathanielKeymasterIf your map is that small, you should consider using the 50m NE data, not the 10m data.
_Nathaniel
December 7, 2011 at 3:32 am #4305
David MedeirosParticipantI’m actually using the 110m data. The final product is a small global locator map about 2″x3″, part of a larger route map for magazine publication.
http://www.sonic.net/~dmed/MedeCart/Portfolio_files/Darien%20Gap-01.jpg
-
AuthorPosts
You must be logged in to reply to this topic.













