[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-24 Thread Markus Metz
Maciej Sieczka wrote: Markus Metz pisze: That would be the fool proof solution to avoid horizontal lines. But then you have vertical lines... If you decide it's worth your time to provide that *as an option* in v.in.gshhs it'd be cool. Not right now, first I want to get grass7 topology

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-24 Thread Maciej Sieczka
Markus Metz pisze: Maciej Sieczka wrote: Markus Metz pisze: That would be the fool proof solution to avoid horizontal lines. But then you have vertical lines... If you decide it's worth your time to provide that *as an option* in v.in.gshhs it'd be cool. Not right now, first I want to

Re: [GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-23 Thread Maciej Sieczka
Maciej Sieczka pisze: I.e that e.g. Alaska is split into 2 pieces. Me so dumb! That's Chukchi Peninsula (and also some of the Fiji Islands, Wrangel Island). Maciek -- Maciej Sieczka http://www.sieczka.org ___ grass-dev mailing list

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-22 Thread Maciej Sieczka
Markus Metz pisze: Maciej Sieczka wrote: Markus Metz pisze: I thought this is true for GRASS. Generally, if you zoom/pan beyond the extend of the feature (raster or vector), nothing is displayed. This should not happen in latlon, Why not? Because it does not happen in GRASS:-) and

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-22 Thread Markus Metz
Maciej Sieczka wrote: It's not that every application is different, but that GRASS is different than all the rest in this regard - it seems. Again, I'm not saying GRASS or you are wrong, but could there be an optional switch to constrain GSHHS geometry exactly to -180 - 180 in v.in.gshhs to

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-22 Thread Maciej Sieczka
Markus Metz pisze: Maciej Sieczka wrote: It's not that every application is different, but that GRASS is different than all the rest in this regard - it seems. Again, I'm not saying GRASS or you are wrong, but could there be an optional switch to constrain GSHHS geometry exactly to -180 -

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-20 Thread Markus Metz
Maciej Sieczka wrote: Markus Metz pisze: I thought this is true for GRASS. Generally, if you zoom/pan beyond the extend of the feature (raster or vector), nothing is displayed. This should not happen in latlon, Why not? Because it does not happen in GRASS:-) and because latlon is not a

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-18 Thread Markus Metz
Maciej Sieczka wrote: I personally like the way QGIS or MapServer handles it - they just don't care and don't try to treat lat-long data as connected at the datum border. So they stop displaying maps beyond -180 or 180? West of Alaska is nothing? If Asia is displayed west of Alaska and Alaska

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-18 Thread Maciej Sieczka
Markus Metz pisze: Maciej Sieczka wrote: I personally like the way QGIS or MapServer handles it - they just don't care and don't try to treat lat-long data as connected at the datum border. So they stop displaying maps beyond -180 or 180? West of Alaska is nothing? Yes. This has the

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-17 Thread Maciej Sieczka
Markus Metz pisze: Maciej Sieczka wrote: Thanks for your v.in.gshhs GRASS 6 port. I have a problem: when importing full GSHHS extent, strange horizontal lines through the whole longitudal extent are present in the output GRASS vector map, which are *visible only in v.digit or QGIS*, but

[GRASS-dev] Re: v.in.gshhs - bogus horizontal lines

2009-03-16 Thread Markus Metz
Maciej Sieczka wrote: Markus, Thanks for your v.in.gshhs GRASS 6 port. I have a problem: when importing full GSHHS extent, strange horizontal lines through the whole longitudal extent are present in the output GRASS vector map, which are *visible only in v.digit or QGIS*, but never on the