zilch | Exception collector/reporter/viewer | Analytics library

This happens because you're using the dynamic keyword which will trigger all sorts of calls from .NET. The corresponding code is this (found in .NET reference source):

Besides the solutions with formidable, there is another module which I have been using in my recent projects since 2019. The module express-form-data can be easily declared in your server file like:

You could use reduce

Geojson does not have any property in its specification that specifies the type of symbol (symbol shape, color, size, etc) that should be drawn. Geojson only specifies the geometry (point, line, polygon, etc) of the drawn object in geographic coordinates.

Of course you can use the properties property of a geojson feature to hold symbol data, it just has no effect on the rendering the feature unless you build that functionality yourself.

While geojson doesn't have any specifications for symbology, the geoPath generator in D3 let's you specify one part of a drawn symbol: the radius of a point (as points are dimensionless otherwise). However, other than this, d3-geo doesn't offer any support for drawing specific symbols, it can only project geometry.

To draw a symbol at a specific geographic coordinate, you'll want project the coordinate (projection([longitude,latitude])). Now you have a coordinate in pixel values, you can use that coordinate to draw your symbol. You don't want to try and draw the symbol in geographic coordinates as this isn't scalable and it is dependent on projection.

Here's a simple implementation with d3-symbol (I haven't drawn the rest of the world, just two points, but they are projected properly):

An import statement is only seeing libraries that you have already added to your project.

You mention using gradle. the gitlab page of said library tells you to add the following lines to your gradle script:

Why is the display being restricted to 2 decimal places?

By default the percent format specifier P is a percent to two decimal places. Use ToString("P7") if you want 7 decimal places.

And more importantly, how can I fix it so that it will expand out to more?

I didn't quite get what you meant by "fix it so it expands to more" - do you want it fixed or variable? You might have to use something like "0.0000000########%" for "at least 7 but up to 15 dp" (if that's what you meant by fixed/expanding)

If you are running your script via the source function or with the run command (from inside RStudio) you must explicitly call the print function on your ggplot commands. For example:

Well! Eljay got it faster in the comments, but here is the final code that will get you a compiling error trying to use a double implicitly

The Google Apps Script Log which is written to with Logger.log() gets cleared each time the script is run, and so after multiple invokations only the most recent call's logs will be shown.

As well as the regular log which can be written to with Logger.log(), Google Apps Script has two other methods of logging - Stackdriver logging and Stackdriver Error reporting. As per the Apps Script documentation:

Apps Script provides three different mechanisms for logging:

• The built-in Apps Script Logger, which is lightweight but persists only for a short time.

• The Stackdriver Logging interface in the Developer Console, which provides logs that persist for many days after their creation.

• The Stackdriver Error Reporting interface in the Developer Console, which collects and records errors that occur while your script is running.

Stackdriver Logging:

When you requre logging that persists for a longer time than per-run, Stackdriver logs are preferred. These are attached to the GCP project that is associated with the Apps Script project, and a simplified version can be found in the Apps Script dashboard. Exception logging can also be done via the Stackdriver logs. This log can be written to by using the console.log() method rather than Logger.log().

Stackdriver Error Reporting:

You can view your Stackdriver error reports in the GCP console.

• Google Apps Script Logging
  • Basic Logging
  • Stackdriver Logging
  • Exception Logging
  • Stackdriver Error Reporting
  • Logging Requirements
• Google Apps Script Class Logger

This answer was updated after other information came to light. As there are known issues with the Logging method of Google Apps Script, the original answer has been kept below.

The Logger.log() function should log everything passed to the method, and regardless of how many funcitons are run in a single call, all logs from all functions from within the call should be viewable in the logger. The only exception is if there are too many Logger.log() calls, and the logs are truncated.

As mentioned above, There is already a report on Google's Issue Tracker which detail the same kind of behaviour:

• 36764984 Visible to Public Logger.log() sometimes does not work

Google does seem to know about this issue but if it's causing problems you can file your own bug about it here.

You can also hit the ☆ next to the issue number in the top left on the aforementioned pages which lets Google know more people are encountering this and so it is more likely to be seen to faster.

I hope this is helpful to you!