Today I woke up for the first time in Aalborg. My colleague Enrico, who yesterday wrote the first post about this expedition, and I left from the hotel, walked through an underpass and came out in a wonderful park! In the end of this park there is the Aalborg Kongres & Kultur Center, the conference venue.
Very often, in our coding life, we forget one very simple yet important point to take care to: the importance of conflicts between packages.
When you load a library in best case the command line is executed with no problem. However, the console is sometimes stuffed with red messages that we often ignore, moreover when the function we need reach the desired goal.
Are you a heavy user of Sitecatalyst and the very famous R package RSitecatalyst to analyze your web analytics data and make insightful vizualitations?
Or wonder why the hell do you need to download lots of excel files to get a simple report from Adobe cloud?
From original post @ http://analyticsblog.mecglobal.it/analytics-tools/bashr/
In the world of data analysis, the term automation runs hand in hand with the term “scripting”. There’s not the best programming language, only the most suitable to perform the required function.
In our case, many data aggregation procedures are run from unix/linux servers, collecting API data in real time, so it becomes essential to make sure that data is formatted and correctly stored for the analysis/visualization needs.
Photos of the 6th MilanoR meeting (Milano; December 18, 2014)
In the R environment, different packages to draw maps are available. I lost the count by now; surely, sp and ggmap deserve consideration. Despite the great availability of R functions dedicated to this topic, in the past, when I needed to draw a very basic map of Italy with regions marked with different colours (namely a choropleth map), I had a bit of difficulties.