570 karma · joined September 10, 2017
Can you try to categorize what you hate about it? If it are specific things and not the general hurdle of figuring where goes what and what means what.
Absolutely! Solving what you are set out to do is a great result and I am super happy for them and their end result!
But this state of documentation (as you call it, I would also/rather consider all the needed background knowledge and lingo to be a hurdle) is all the more reason to just document their goal, their data(s), their abilities and capabilities and ask an expert for 15 minutes of their time for input and pointers. That is so much more efficient!
> We set the interpolation process running in QGIS on a Mac Pro and, a mere 11 days later, found ourselves the proud owners of a raster 250m2 grid layer
Probably done in minutes to hours with a properly setup PostGIS database and one query. "Data Journalists" seem to love it when things take long, thinking they are doing something super innovative and novel. Often it's just that they were using the wrong hammer...
> 1. Don’t use GeoTIFFs for geometric visualization
What? I am not sure what exactly the image is supposed to show but it seems like some rescaling/filtering. Not the fault of GeoTIFF.
Why not render the raster tiles locally? gdal2tiles or Tilemill can do that for you.
Why does Mapbox recommend LZW for compression? DEFLATE is usually much smaller and with the horizontal differencing predictor it should be even more smaller.
> 2. Your GeoJSON can probably be way smaller
Does Mapbox not support TopoJSON? That helps a lot for local data with quantisation.
> Because nothing in GIS is straightforward, attempting to round the values of 2.7m polygons using the field calculator in QGIS invariably resulted in the application crashing, even on a high-end Mac Pro. After several attempts using QGIS 2.16, 2.18 and 3.2,
Did they ask the community or even just provide a bug report? This should not happen from a QGIS fault.
Also, I noticed something very very dangerous you did:
.describe() will return a DataFrame with all those statistics. One column per numeric column of the input. One row per statistical value (like mean, std, etc). If you call .mean() on THAT DataFrame, you will get the mean of the statistical values per column, so e.g. the mean of columnA's count, mean, std, etc values. Definitely not what you want!
Instead, use either .mean() directly on your "data DataFrame" (not the one returned by .describe()). Or access the specific value from the result via .describe()['columnname']['mean'].
Use type() to see what you are getting:
>>> type(df.describe().mean())
<class 'pandas.core.series.Series'>
>>> type(df.describe().mean)
<class 'method'>
Something without parenthesis cannot be a method call, at least not from a normal viewpoint. Instead you are trying to access the attribute "mean" of the result of describe() if you run df.groupby(df.var1).describe().mean. This attribute might very well be a method itself (a method object).Last in that chain was describe(), so let's look at that: https://pandas.pydata.org/pandas-docs/stable/generated/panda...
It returns a "summary: Series/DataFrame of summary statistics", so calling .mean() on that, will call https://pandas.pydata.org/pandas-docs/stable/generated/panda...
Accessing .mean will instead return that method object itself.
By default pandas will return a string describing the data itself when printing a method:
>>> df.describe()
numeric n2
count 3.0 3.0
mean 2.0 3.0
std 1.0 1.0
min 1.0 2.0
25% 1.5 2.5
50% 2.0 3.0
75% 2.5 3.5
max 3.0 4.0
>>> df.describe().mean
<bound method DataFrame.mean of numeric n2
count 3.0 3.0
mean 2.0 3.0
std 1.0 1.0
min 1.0 2.0
25% 1.5 2.5
50% 2.0 3.0
75% 2.5 3.5
max 3.0 4.0>
>>> df.describe().mean()
numeric 2.00
n2 2.75
dtype: float64
I assume this is what threw you off? You are not using the "results" of .mean in further code but were just looking at them, right?> The NewsBlocks token sale is planned for Q4 2018. The token sale will fund the creation of the NewsBlocks blockchain, seed the content, and fund application development.
Spam your scam elsewhere.
Thanks!
Holy hell, that sounds like the utmost crazy privacy problem. Is it end-to-end encrypted?
One that wants to manipulate your mind, one that echochambers your discovery, one that censors arbitrarily.
All they learned is irrelevant details, sadly they did NOT say anything about the color of the top or the exact haptic feel of the third knob from the right.
Nothing about the vapourware tech to learn.
Skip and keep watching from your safe distance.
How does one company name from 70 years ago matter in the big picture anyways? Please don't assume that the rest of the world uses the same history syllabus like your US school might have. Did they at least also teach you who fabricated Agent Orange if they focused on manufacturers so much?
Citation needed...
First of all, the title should include "video of a predefined 360° turn".
And then they say something along the lines of "average accuracy of about 5mm" for joining the constructed modeled joints to their model, while you see the body wobbling around happily.
This is an impressive demo, but gah!