StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20629634
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-12-17T08:50:20.423
FavoriteCount
0
LastActivityDate
2013-12-17T09:35:34.477
LastEditDate
2013-12-17T09:35:34.477
LastEditorUserId
1451109
OwnerUserId
1451109
ParentId
20520837
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
In the question you linked the whole part from <code>lat <- rev(lat)</code> to <code>temp <- t(temp)</code> was very specific to that particular OP dataset and have absolutely no universal value. <pre><code>temp.nc <- open.ncdf("~/Downloads/air.1999.nc") temp.nc [1] "file ~/Downloads/air.1999.nc has 4 dimensions:" [1] "lon Size: 144" [1] "lat Size: 73" [1] "level Size: 12" [1] "time Size: 365" [1] "------------------------" [1] "file ~/Downloads/air.1999.nc has 2 variables:" [1] "short air[lon,lat,level,time] Longname:Air temperature Missval:32767" [1] "short head[level,time] Longname:Missing Missval:NA" </code></pre> As you can see from these informations, in your case, missing values are represented by the value <code>32767</code> so the following should be your first step: <pre><code>temp <- get.var.ncdf(temp.nc,"air") temp[temp=="32767"] <- NA </code></pre> Additionnaly in your case you have 4 dimensions to your data, not just 2, they are longitude, latitude, level (which I'm assuming represent the height) and time. <pre><code>temp.nc$dim$lon$vals -> lon temp.nc$dim$lat$vals -> lat temp.nc$dim$time$vals -> time temp.nc$dim$level$vals -> lev </code></pre> If you have a look at <code>lat</code> you see that the values are in reverse (which <code>image</code> will frown upon) so let's reverse them: <pre><code>lat <- rev(lat) temp <- temp[, ncol(temp):1, , ] #lat being our dimension number 2 </code></pre> Then the longitude is expressed from 0 to 360 which is not standard, it should be from -180 to 180 so let's change that: <pre><code>lon <- lon -180 </code></pre> So now let's plot the data for a level of 1000 (i. e. the first one) and the first date: <pre><code>temp11 <- temp[ , , 1, 1] #Level is the third dimension and time the fourth. image(lon,lat,temp11) </code></pre> And then let's superimpose a world map: <pre><code>library(maptools) data(wrld_simpl) plot(wrld_simpl,add=TRUE) </code></pre> <img src="https://i.stack.imgur.com/Qagvv.png" alt="enter image description here">
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POR - Plotting netcdf climate data
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USplannapus
UserOwnerUserId
1. USplannapus
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POR - Plotting netcdf climate data
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks for the reply and example of the code that works, much appreciated.
 singulars
 PostPostId
 PO
 UserUserId
 USfjd

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.