NetTopologySuite | NET GIS solution that is fast and reliable for the .NET | Map library

The answer basically try summarizing the different comments posted in the question.

The problem can be motivated for many different reasons.

The most important thing to keep in mind is that EB provides a nginx proxy for serving the application.

By default this proxy expects your application to listen on port 5000.

According to the logs you provided, the application seems to start properly and it successfully connect to the database.

As you pointed out, it reports that the application is listening on http://localhost:5000: it may not be a problem, but perhaps your application is listening only in a certain network interface/address.

Just to be sure, and in fact, at the end it seems to be the solution, configure your application Kestrel server to listen on the mask http://*:5000, using .UseUrls("http://*:5000") in your Startup class, for instance. This article provides several different options for configuring where the application should listen to.

var searchArea = geometryFactory.CreatePoint(searchAreCoordinate).Buffer(1000); // To me, this is 1000 meters because the SRID is WGS84.

This is fundamentally wrong. NTS does not care for any spatial reference system, it treats every coordinate as if it were planar.

If you have to work with geographic coordinates and want to buffer/measure with meters, you need to follow the instructions given in Srid ignored during client operations.

Support for mapping NodaTime Duration to PostgreSQL interval was only added in version 5 of the provider, you'll have to upgrade in order to use it. Note that the upcoming version 6 (to be released in a couple weeks) substantially improves NodaTime support in various ways - I'd recommend waiting and switching to that.

The QueryableMethods Class is Compatible with Microsoft.EntityFrameworkCore v5.0.0

Try removing the reference to EntityFramework by changing target framework to net5.0 .

Can you use IQuery<>.ToString() to display the actual SQL query being created? Maybe this will point you in the right direction. Also, maybe this answer is interesting.

Additionally, you might want to take a look at the database you are using. According to docs:

If an operation is server-evaluated by EF Core via SQL, the result's unit will be determined by the database.

Thanks to one of the maintainers of the library I got the answer.

Basically, I needed to upgrade to version 2.2 (which I already did at first to see if this would resolve the problem).

But second, I needed to configure the application to use the - in version 2.2 introduced - 'NextGen' overlay generator, which is not turned on by default.

To use the 'Next Gen' overlay generator, add the following code at some starup point in your application:

After a bunch of trials and errors, I founded a comprehensive solution to this.

when we dealing with a GeoJson file, each feature can (or even should!) save in a separate NetTopologySuite.Geometries.Geometry type. (in other words, I changed the structure of my table from one stand-alone table to two tables with a parent child relationship)

In fact, we don't need to serialize any things manually when are using NetTopologySuite.IO.GeoJSON4STJ. in our code, we only need to work with NetTopologySuite.Features.FeatureCollection and add NetTopologySuite.IO.Converters.GeoJsonConverterFactory to JSON converters when we add controllers. but there is also a trick here, at the registration time we should use NetTopologySuite.Geometries.GeometryFactoryEx instead of NetTopologySuite.Geometries.GeometryFactory (attention to the Ex word at the end). the reason for this is SQL server Require left-hand-rule (CCW) but GeoJson Required right-hand-rule (REFRENCE) so:

You need to calculate great circle distance. NetTopologySuite Point.Distance method returns the cartesian distance.

Try the following:

I think you have a misconception about how JsonConverters work. The reader does not give you the raw JSON. Instead it allows you to step through the tokens in the JSON one by one.

reader.Value is null because your converter is handling an object, not a string, and at the point your converter is called, the reader is positioned on the StartObject token. You need to call reader.Read() in a loop to advance through the object to get the property names and values until you reach the EndObject token.

Here is a fiddle that demonstrates that process, although it doesn't actually populate the Polygon. https://dotnetfiddle.net/MQE6N5

If you really want the JSON string inside the converter, you could load a JObject from the reader, and then call its ToString() method: