airborne | RSpec driven API testing framework | Unit Testing library

After much trawling through the R spatial jungle I haven't yet found an existing function to extract the horizontal CRS component. The function below is my attempt to write one. I've tested it with old and new LiDAR data, where the older data has a simple (just horizontal) CRS and the new data has a compound CRS.

I'm sure there must be an existing and better way.

Update 2021-11-01: Tweaked the function to accept any spatial object compatible with the sf::st_crs() function.

After much head banging, I finally figured out the root cause of this. And it's a bit obscure..

The wireless video transmitter in the drone is able to dynamically change the video bitrate depending on the radio link's available bandwidth. Or put in another way: When the drone is too far away or there is strong interference, the video quality degrades.

When this happens, video frames (contained in only one slice within a single NAL) start to become significantly smaller. Since I'm reading 512-byte chunks of an h264 stream with no particular alignment and forwarding them to GStreamer as GstBuffers, if the size of data needed for one frame is lower than 512 bytes, there is a possibility that a buffer contains multiple frames. In this case, h264parse sees this as N different buffers with identical timestamps. The default behavior then seems to be to ignore both upstream PTS and DTS and try to compute the timestamp based on the duration of the frame by reading the VUI from the SPS, which is not present in my stream. Therefore, the buffer leaving the source pad of h264parse will have no PTS and no DTS, thus making mp4mux complain.

As I've previously mentioned, my stream is quite simple so I wrote a simple parser to detect the beginning of each NAL. This way I can 'unpack' the stream coming from the USB hardware and make sure that every buffer pushed into my pipeline will contain only one NAL (therefore, as much as one frame), independently timestamped.

And for redundancy, I added a probe attached to the sink pad of my tee element to make sure I have correct timestamps in every buffer through it. Otherwise, they're forced to the running time of the element like this.

I think the issue here is that your data is double nested... there is a key referenced_tweets within referenced_tweets.

The output is as expected and in line with the structure of your json, which is quite convoluted (multiple levels).

The "type" column is deriving it's values from the one level.

Besides what @stefan suggested, there are two ways in which you can do this (that I know of). The first is using ifelse() (I moved the relevant part to the end):

Yes options.style must be a function - look at: https://leafletjs.com/reference-1.7.1.html#geojson-style

Change your code:

Here is a base R option using ´outer+max.col`

Based on your comment I made a few revisions to make the platform movement a bit smoother. I also made it so the same function can be used for both the upward and downward motion.

I changed
get 'http://localhost:3000/api/v1/users', { }, { 'params' => {'param_key' => 'param_value' } } to get 'http://localhost:3000/api/v1/users', params => {'param_key' => 'param_value' } } and it works.