You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(12) |
Sep
(12) |
Oct
(56) |
Nov
(65) |
Dec
(37) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(59) |
Feb
(78) |
Mar
(153) |
Apr
(205) |
May
(184) |
Jun
(123) |
Jul
(171) |
Aug
(156) |
Sep
(190) |
Oct
(120) |
Nov
(154) |
Dec
(223) |
| 2005 |
Jan
(184) |
Feb
(267) |
Mar
(214) |
Apr
(286) |
May
(320) |
Jun
(299) |
Jul
(348) |
Aug
(283) |
Sep
(355) |
Oct
(293) |
Nov
(232) |
Dec
(203) |
| 2006 |
Jan
(352) |
Feb
(358) |
Mar
(403) |
Apr
(313) |
May
(165) |
Jun
(281) |
Jul
(316) |
Aug
(228) |
Sep
(279) |
Oct
(243) |
Nov
(315) |
Dec
(345) |
| 2007 |
Jan
(260) |
Feb
(323) |
Mar
(340) |
Apr
(319) |
May
(290) |
Jun
(296) |
Jul
(221) |
Aug
(292) |
Sep
(242) |
Oct
(248) |
Nov
(242) |
Dec
(332) |
| 2008 |
Jan
(312) |
Feb
(359) |
Mar
(454) |
Apr
(287) |
May
(340) |
Jun
(450) |
Jul
(403) |
Aug
(324) |
Sep
(349) |
Oct
(385) |
Nov
(363) |
Dec
(437) |
| 2009 |
Jan
(500) |
Feb
(301) |
Mar
(409) |
Apr
(486) |
May
(545) |
Jun
(391) |
Jul
(518) |
Aug
(497) |
Sep
(492) |
Oct
(429) |
Nov
(357) |
Dec
(310) |
| 2010 |
Jan
(371) |
Feb
(657) |
Mar
(519) |
Apr
(432) |
May
(312) |
Jun
(416) |
Jul
(477) |
Aug
(386) |
Sep
(419) |
Oct
(435) |
Nov
(320) |
Dec
(202) |
| 2011 |
Jan
(321) |
Feb
(413) |
Mar
(299) |
Apr
(215) |
May
(284) |
Jun
(203) |
Jul
(207) |
Aug
(314) |
Sep
(321) |
Oct
(259) |
Nov
(347) |
Dec
(209) |
| 2012 |
Jan
(322) |
Feb
(414) |
Mar
(377) |
Apr
(179) |
May
(173) |
Jun
(234) |
Jul
(295) |
Aug
(239) |
Sep
(276) |
Oct
(355) |
Nov
(144) |
Dec
(108) |
| 2013 |
Jan
(170) |
Feb
(89) |
Mar
(204) |
Apr
(133) |
May
(142) |
Jun
(89) |
Jul
(160) |
Aug
(180) |
Sep
(69) |
Oct
(136) |
Nov
(83) |
Dec
(32) |
| 2014 |
Jan
(71) |
Feb
(90) |
Mar
(161) |
Apr
(117) |
May
(78) |
Jun
(94) |
Jul
(60) |
Aug
(83) |
Sep
(102) |
Oct
(132) |
Nov
(154) |
Dec
(96) |
| 2015 |
Jan
(45) |
Feb
(138) |
Mar
(176) |
Apr
(132) |
May
(119) |
Jun
(124) |
Jul
(77) |
Aug
(31) |
Sep
(34) |
Oct
(22) |
Nov
(23) |
Dec
(9) |
| 2016 |
Jan
(26) |
Feb
(17) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(8) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(4) |
Nov
|
Dec
|
| 2017 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
(13) |
2
(12) |
3
(3) |
4
(13) |
5
(13) |
6
(2) |
|
7
(5) |
8
(17) |
9
(9) |
10
(10) |
11
(16) |
12
(8) |
13
(10) |
|
14
(1) |
15
(5) |
16
(5) |
17
(7) |
18
(13) |
19
(9) |
20
|
|
21
|
22
(2) |
23
(3) |
24
(5) |
25
(5) |
26
(14) |
27
(1) |
|
28
(2) |
29
(18) |
30
(5) |
31
(22) |
|
|
|
|
From: Adam M. <ram...@gm...> - 2007-10-13 22:41:02
|
On 13/10/2007, Jeff Whitaker <js...@fa...> wrote: > Adam: See the basemap examples directory - there's plenty of examples > there using pylab.colorbar. Thanks, that was what I was after - the appropriate module and method. Cheers Adam |
|
From: Jeff W. <js...@fa...> - 2007-10-13 16:17:44
|
Adam Mercer wrote: > Hi > > Is there a way that I can add a colour bar to a basemap plot detailing > the value represented by each colour? > > Cheers > > Adam > > Adam: See the basemap examples directory - there's plenty of examples there using pylab.colorbar. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449 325 Broadway Boulder, CO, USA 80305-3328 |
|
From: Adam M. <ram...@gm...> - 2007-10-13 16:01:40
|
On 13/10/2007, Jeff Whitaker <js...@fa...> wrote: > Adam: Same as with any other plot created with matplotlib. You can use > the 'figsize' keyword to pylab.figure in conjunction with the 'dpi' > keyword to pylab.savefig. For details see Thanks, I was unsure whether or not is used the same system. Cheers Adam |
|
From: Jeff W. <js...@fa...> - 2007-10-13 15:35:22
|
Adam Mercer wrote: > Hi > > How can I set the size of the plot produced by basemap, as I need to > create a nice high resolution plot for a publication? > > Cheers > > Adam > Adam: Same as with any other plot created with matplotlib. You can use the 'figsize' keyword to pylab.figure in conjunction with the 'dpi' keyword to pylab.savefig. For details see http://www.scipy.org/Cookbook/Matplotlib/AdjustingImageSize -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449 325 Broadway Boulder, CO, USA 80305-3328 |
|
From: Adam M. <ram...@gm...> - 2007-10-13 15:33:25
|
Hi Is there a way that I can add a colour bar to a basemap plot detailing the value represented by each colour? Cheers Adam |
|
From: Adam M. <ram...@gm...> - 2007-10-13 15:18:27
|
Hi How can I set the size of the plot produced by basemap, as I need to create a nice high resolution plot for a publication? Cheers Adam |
|
From: Jeff W. <js...@fa...> - 2007-10-13 14:48:31
|
Charles Seaton wrote: > I have noticed that matplotlib.toolkits.basemap.Basemap supports a smaller > set of projection arguments than the underlying function > matplotlib.toolkits.basemap.pyproj.Proj and was wondering if there is a > fundamental limitation on the functionality of Basemap that prevents it from > handling proj arguments such as x_0, y_0, ellps, datum, and init? > > I would like to be able to use all of the very nice functionality built into > Basemap on standard projections such as Oregon State Plane Coordinate > System-North NAD27 (which can be generated using pyproj.Proj with the > following proj arguments: > > orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(\ > proj='lcc',lat_1=44.33333333333334,lat_2=46,lat_0=43.66666666666666,\ > lon_0=-120.5,x_0=609601.2192024384, y_0=0,ellps='clrk66',datum='NAD27') > > or even more simply by > orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(init='epsg:32026') > or > orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(init='nad27:3601') > > but Basemap() won't accept the necessary arguments > > Would this be a matter of modifying the Basemap __init__ function to > recognize a longer list of possible arguments or is there a larger issue I'm > not seeing, or a bunch more code that would require modification? > > thanks, > > Charles Seaton > Research Associate > OHSU/ STC-CMOP > Charles: Unfortunately, there's more to making a map than getting the map projection transformation right. There's lots of special case code for different projections in basemap to take care of coastline polygons that go over the edge of the map region, drawing of meridians and parallels, drawing the map projection boundary, etc. It looks like the projection you want is lambert conformal with a Clark66 ellipsoid. You should be able to use Basemap with projection='lcc', and rsphere set to a tuple that defines the Clark66 ellipsoid. Is there a reason that won't work? -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449 325 Broadway Boulder, CO, USA 80305-3328 |
|
From: Jeff W. <js...@fa...> - 2007-10-13 14:40:25
|
Charles Seaton wrote:
> I would like to use a higher resolution coastline than the high resolution
> coastline optionally provided with (specifically, I would like to use the
> NOAA/NOS Medium Resolution Coastline). I can see two ways to do this:
>
> Option 1) Create a coastline file using the in the NOAA/NOS data in the same
> format as the data files used by the basemap toolkit. I couldn't find a
> description of this format, but it appears that it is partially explained by
> the code snippet:
>
> if line.startswith('P'):
> area = float(linesplit[5])
> west,east,south,north =
> float(linesplit[6]),float(linesplit[7]),float(linesplit[8]),float(linesplit[9])
> typ = int(linesplit[3])
>
> So the first line of the existing high resolution coastline is:
> P 0 169598 1 W 79866900.000 -17.53378 190.35911 -34.83044 77.71958
>
> Which should be interpreted as
> typ = 1
> area = 79866900.000
> west = -17.53378
> east = 190.35911
> south = -34.83044
> north = 77.71958
>
> area is used to control whether this segment of coastline is displayed
> the directions are the bounding box for the coastline segment
> I am not clear on how typ is used (I see it getting manipulated, but I don't
> see it ever getting used), or what its acceptable values are. I am also not
> clear what the first, second and fourth values of the line are (not counting
> the initial 'P'). Any help with this format would be appreciated.
>
> Option 2) Load a coastline by whatever means I choose as a list of lists of
> touples (or some other format?) and then transform those values using the
> basemap object. If the coastline were easily expressed as a pair of lists or
> arrays lon,lat, then I could simply use
>
> b=basemap(...)
> coastx,coasty = b(lcoastlon,coastlat)
>
> but the coastline is made up of multiple segments (islands, etc). Is the
> best way to transform a collection of segments simply to loop over the
> segments?
>
> coast = [ [(x11,y11),... (x1n,y1n)], [(x21,y21),... (x2n,y2n)],...
> [(xn1,yn1),...(xnn,ynn)] ]
> newcoast = []
> for c in coast:
> ln,lt = map(list,zip(*c))
> x,y = m(ln,lt)
> newcoast.append(zip(x,y))
>
> Once I have a transformed list of lists of touples, I can replace the
> basemap objects coastsegs
> b.coastsegs = newcoast
>
> and then draw the coastline using the built-in
> b.drawcoastlines()
>
> Or is there some method that I am missing?
>
>
>
Charles: If you can get the coastlines in a shapefile, that's probably
the easiest way to do it. See the fillstates.py example for reading in
and plotting shapefiles on maps.
-Jeff
--
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
325 Broadway Boulder, CO, USA 80305-3328
|
|
From: Charles S. <cs...@st...> - 2007-10-13 04:08:14
|
I have noticed that matplotlib.toolkits.basemap.Basemap supports a smaller set of projection arguments than the underlying function matplotlib.toolkits.basemap.pyproj.Proj and was wondering if there is a fundamental limitation on the functionality of Basemap that prevents it from handling proj arguments such as x_0, y_0, ellps, datum, and init? I would like to be able to use all of the very nice functionality built into Basemap on standard projections such as Oregon State Plane Coordinate System-North NAD27 (which can be generated using pyproj.Proj with the following proj arguments: orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(\ proj='lcc',lat_1=44.33333333333334,lat_2=46,lat_0=43.66666666666666,\ lon_0=-120.5,x_0=609601.2192024384, y_0=0,ellps='clrk66',datum='NAD27') or even more simply by orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(init='epsg:32026') or orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(init='nad27:3601') but Basemap() won't accept the necessary arguments Would this be a matter of modifying the Basemap __init__ function to recognize a longer list of possible arguments or is there a larger issue I'm not seeing, or a bunch more code that would require modification? thanks, Charles Seaton Research Associate OHSU/ STC-CMOP -- View this message in context: http://www.nabble.com/projections-in-matplotlib.toolkits.basemap-Basemap-vs.-pyproj.Proj-tf4617163.html#a13186371 Sent from the matplotlib - users mailing list archive at Nabble.com. |
|
From: Charles S. <cs...@st...> - 2007-10-13 03:26:45
|
I would like to use a higher resolution coastline than the high resolution
coastline optionally provided with (specifically, I would like to use the
NOAA/NOS Medium Resolution Coastline). I can see two ways to do this:
Option 1) Create a coastline file using the in the NOAA/NOS data in the same
format as the data files used by the basemap toolkit. I couldn't find a
description of this format, but it appears that it is partially explained by
the code snippet:
if line.startswith('P'):
area = float(linesplit[5])
west,east,south,north =
float(linesplit[6]),float(linesplit[7]),float(linesplit[8]),float(linesplit[9])
typ = int(linesplit[3])
So the first line of the existing high resolution coastline is:
P 0 169598 1 W 79866900.000 -17.53378 190.35911 -34.83044 77.71958
Which should be interpreted as
typ = 1
area = 79866900.000
west = -17.53378
east = 190.35911
south = -34.83044
north = 77.71958
area is used to control whether this segment of coastline is displayed
the directions are the bounding box for the coastline segment
I am not clear on how typ is used (I see it getting manipulated, but I don't
see it ever getting used), or what its acceptable values are. I am also not
clear what the first, second and fourth values of the line are (not counting
the initial 'P'). Any help with this format would be appreciated.
Option 2) Load a coastline by whatever means I choose as a list of lists of
touples (or some other format?) and then transform those values using the
basemap object. If the coastline were easily expressed as a pair of lists or
arrays lon,lat, then I could simply use
b=basemap(...)
coastx,coasty = b(lcoastlon,coastlat)
but the coastline is made up of multiple segments (islands, etc). Is the
best way to transform a collection of segments simply to loop over the
segments?
coast = [ [(x11,y11),... (x1n,y1n)], [(x21,y21),... (x2n,y2n)],...
[(xn1,yn1),...(xnn,ynn)] ]
newcoast = []
for c in coast:
ln,lt = map(list,zip(*c))
x,y = m(ln,lt)
newcoast.append(zip(x,y))
Once I have a transformed list of lists of touples, I can replace the
basemap objects coastsegs
b.coastsegs = newcoast
and then draw the coastline using the built-in
b.drawcoastlines()
Or is there some method that I am missing?
--
View this message in context: http://www.nabble.com/coastlines-in-matplotlib.toolkits.basemap-tf4617110.html#a13186210
Sent from the matplotlib - users mailing list archive at Nabble.com.
|