I have a Web Service made using the **WebAPI** provided by ASP .NET MVC 4.
I know that the layer on top of which WebAPI works automatically handles **OData Queries** (such as `$filter`, `$top`, `$skip`), but what if I want to handle the filtering by myself?

[I don't simply return data from my database](https://i.stack.imgur.com/Bgv8W.jpg), but I have another layer which adds some properties, makes some conversions etc. So querying ALL of my data, converting them and returning them to the WebAPI class for OData filtering isn't just good enough. It's of course terribly slow, and generally a crappy idea.

So is there a way to **propagate the OData query parameters** from my WebAPI entry point to the functions I call to get and convert the data?

For example, a GET to `/api/people?$skip=10&$top=10` would call on the server:

```
public IQueryable<Person> get() {
    return PersonService.get(SomethingAboutCurrentRequest.CurrentOData);
}

```

And in `PersonService`:

```
public IQueryable<Person> getPeople(var ODataQueries) {
    IQueryable<ServerSidePerson> serverPeople = from p in dbContext.ServerSidePerson select p;
    // Make the OData queries
    // Skip
    serverPeople = serverPeople.Skip(ODataQueries.Skip);
    // Take
    serverPeople = serverPeople.Take(ODataQueries.Take);
    // And so on
    // ...

    // Then, convert them
    IQueryable<Person> people = Converter.convertPersonList(serverPeople);
    return people;
}

```