GeoTools | Swift Library to Aid in the Creation of Custom Geometry | 3D Animation library

i had the same situation and i think if you want to update your tiles postgis solution(medium article) is much faster and easier.

but if you just want to read raster tiles as a static map, the file system solution is much faster and you can keep your data with some structure like {z(directory)}/{x(directory)}/{y(tile)} and i recommend to take a look at tippecanoe project. it's a perfect way for static map, even better than file system solution.

if you just want to change styles any time you want i recommend to use vector tiles. it's so much faster.

I think it is just a different way to represent binary columns in PostGIS and in JSON. The WKB is a binary field, meaning it is has bytes with arbitrary values, many of which has no corresponding printable characters. PostGIS prints it out using HEX encoding, thus it looks like '01060000208A7A...' - hex digits, but internally it is just bytes. Kafka's JSON uses BASE64 encoding instead for exactly the same binary message.

Let's test with a prefix of your string,

For your first issue with axis order you have fallen for a common beginner's problem of assuming that you know what the axis order of a projection is, and in the case of ESPG:4326 that it is fixed.

For example, the following code:

I think you want to set up your function to take a pair of Strings or Doubles (or whatever those attributes are) so something like:

TL;DR Sort of, probably, it depends.

GDAL provides a lot of import and export formats and a few specific tools to manipulate raster data. I'm being a little old fashioned here and assuming that when you say GDAL you only mean rasters (if you also mean OGR and vectors then it mostly still applies).

Meanwhile, GeoTools provides a pluggable data import and export system to allow you to use and convert many types of raster (and vector) data and a full ecosystem of processes that can be applied to that data. It even includes Jiffle to allow you to allow your users to write scripts to process them.

Finally, GeoTools allows you to style and display (or print) your data using OGC standard SLD styling (or CSS and YAML variants).

Obviously, as a GeoTools developer I'm probably biased but in you are doing geography in Java then GeoTools is a great tool to do it.

It's hard to be sure as there are some elements missing from your code but I get reasonable looking results from this code:

To create an empty coverage you need to use the GridCoverageFactory and one of the create methods. Since you are not constructing from an existing image you need to provide some memory for your raster to be stored in (this can also hold any initial values you want). For this your choices are a float[][] or a WritableRaster. Finally, you need a Envelope to say where the coverage is and what it's resolution is (otherwise it is just an array of numbers), I favour using a ReferencedEnvelope so that I know what the units are etc, so in the example below I have used EPSG:27700 which is the OSGB national grid so I know that it is in metres and I can define the origin somewhere in the South Downs. By specifying the lower left X and Y coordinates and the upper right X and Y as resolution times the width and height (plus the lower left corner) the maths all works out to make sure that the size of my pixels is resolution.

So keeping it simple for now you could do something like:

In case of build.gradle, use the following.

In case of higher version of gradle like 6, use below.

implementation 'org.geotools:gt-coverage:24.2'

In case of lower version of gradle like 4, use the below.

compile group: 'org.geotools', name: 'gt-coverage', version: '24.2'

After making changes, use your favorite ide, refresh the gradle project. Once it is done, you will be able to import the class.

Dependecies are defined by groupId, artifactId and version. You only referenced groupId and version.