New answers tagged

2

I think what happened here is that "PublicLibrary" got split into "LibrarySystem" and "LibraryBranch" databases, only the first of which has the information we need. allLibraries = EntityValue["LibrarySystem", "Entities"]; cities = EntityValue[allLibraries, EntityProperty["LibrarySystem", "City"]]; books = EntityValue[allLibraries, EntityProperty["...


2

What is the bug? It seems that GeoRegionValuePlot will not work correctly when two or more entities have the exact same value. Consider these examples (and ignore the legend, which is always wrong unless you give an explicit ColorFunction as below): GeoRegionValuePlot[{Entity[ "AdministrativeDivision", {"Arkansas", "UnitedStates"}] -> 1, Entity["...


7

It actually seems to work fine. You may have been tripped up by the use of Quantity and units, which may be a tad less than intuitive sometimes: p1 = GeoPosition[Entity["City", {"Bunnell", "Florida", "UnitedStates"}]]; With[{r = Quantity[40, "Kilometers"]}, GeoGraphics[ {Red, GeoCircle[p1, r], Blue, PointSize[Large], Point[p1]}, GeoScaleBar -> ...


5

A possible way to rotate a map is to use the freedom provided by an oblique projection. Obliqueness adds the three degrees of freedom of a general 3D rotation, namely the {lat, lon} coordinates of the new pole and a rotation around that point. In the future, the WL projection engine will support obliqueness for all projections, but currently some of the ...


7

Since version 10.0, the functions DayHemisphere[], NightHemisphere[], and DayNightTerminator[] are now built-in, and can be used with GeoGraphics[]. These three can either take a specified date, and will otherwise default to Now. One can now do things like this: GeoGraphics[{GeoStyling[GrayLevel[0, 2/3]], NightHemisphere[]}, GeoBackground -> ...


9

This is not a bug. When dealing with a map there are two different coordinate systems you need to handle, related by the cartographic projection you are using. First you have the {lat, lon} coordinates on the surface of the Earth's ellipsoidal model. These are the numbers in GeoPosition[{lat, lon}]. Then you have the coordinate {x, y} on the flat map of ...


6

To long for a comment: It seems that Geo-FrameTicks are not handled well unless we use "Equirectangular" GeoProjection. Even if it is a cylindrical projection, as a "Mercator" used here, the result's ticks seem to be rescaled badly. I can't find anything about that in documentation so I'm encouraging you to report that to WRI Support. Meanwhile use "...



Top 50 recent answers are included