Documentation? ODataRoute for root level actions - totally unclear.

[NetTecture]

if you head over to https://docs.microsoft.com/en-us/odata/webapi/attribute-routing you get a ton of information about routing (conventions and this page with attribttes) but EVERY single example is starting with an entity set.

This is not all there is.

There are unbound actions, too. And I now have to refer to REST (i.e. non odata) beause I can not get it working. And there is no documentation.

http://api.obb.tuev-daily.de/odata/$metadata

(which is valid) defines an action GeoCode. No entity set it is in the EntityContainer:

And defined as

This should result in the URL being "/Tools.GeoCode" (under the root folder). I can not enter this. Like at all. I always get

The path template 'Tools.GeoCode' on the action 'GeoCode' in controller 'Tools' is not a valid OData path template. Resource not found for the segment 'Tools.GeoCode'

for:

[ODataRoute("/Tools.GeoCode")]
and
[ODataRoute("Tools.GeoCode")]

Without proper documentation - this is not solvable. And possibly also an error.

[fairking]

I am trying to setup a simple sample but all fails. This Asp.Net Odata is totally mess.
For example (very simple, no crazy magic):

services.AddOData();
app.UseEndpoints(endpoints =>
{
    endpoints.EnableDependencyInjection();
    endpoints.Expand().Select().Count().OrderBy().Filter().MaxTop(100);
    endpoints.MapODataRoute("odata", null, GetEdmModel());
});

if I go to 'http://localhost:5001/odata/weatherforecast' I got my data, fine.
if I go to 'http://localhost:5001/odata/weatherforecast?$select=key,summary' it returns this [{"instance":null,"container":{},"modelID":"d5389bf8-1e44-43a4-8ab6-f0aed65a2231","untypedInstance":null,"instanceType":null,"useInstanceForProperties":false}, .... ]
if I go to 'http://localhost:5001/odata/$metadata' I got 404.

Example here: https://github.com/fairking/ODataTest

I cannot understand all of this.
Please guys make it more user friendly. Not some crazy megatron.
The Asp.Net Core 3.1 is total disaster and I am considering to move to node.js server framework. The main reason: lots of errors, very unclear what to do, errors don't give you an info about what is the problem.
Thanks.