# Error starting local ORS engine

**URL:** <https://ask.openrouteservice.org/t/error-starting-local-ors-engine/6654>\
**Category:** openrouteservice\
**Created:** [November 7, 2024, 11:11am UTC](https://ask.openrouteservice.org/t/error-starting-local-ors-engine/6654 "2024-11-07T11:11:48Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![Jules](https://ask.openrouteservice.org/user_avatar/ask.openrouteservice.org/jules/32/187_2.png) [@Jules](https://ask.openrouteservice.org/u/Jules)\
**Post date:** [December 2, 2024, 2:37pm UTC](https://ask.openrouteservice.org/t/error-starting-local-ors-engine/6654/22 "2024-12-02T14:37:31Z")

</div>

Just a quick reply because I’m so hyped about the latest config changes.

You can now define a lot more with `profiles`, make complex combinations, and the profiles can be named as you like. e.g.:

```auto
ors:
    engine:
        profile_default:
            service:
                maximum_distance: 999999
            build:
                source_file: ./osm_file.pbf
        profiles:
            driving-car:
                enabled: true
            another-car:
                build:
                    source_file: ./another_osm_file.pbf
                enabled: true
                encoder_name: driving-car

```

Everything in `profile_default` applies to all other entries under `profiles` unless overwritten there. Every profile can have its own `source_file` (etc.) when `encoder_name` is present. Also, parameters are now “logically” split into build and service related things. `build` only relevant for building graphs that can be omitted when just loading an existing one.

Additionally, the way you call your entry in `profiles` defines how it can be accessed via the API. The above examples would relate to `/ors/v2/directions/driving-car` and `/ors/v2/directions/another-car`.

And all this can be configured as well 💯 % with ENV and properties (no YAML file required anymore):

```auto

ors.engine.profile_default.build.source_file=./osm_file.pbf
ors.engine.profiles.driving-car.enabled=true

```

and

```auto

ORS_ENGINE_PROFILE_DEFAULT_BUILD_SOURCE_FILE=./osm_file.pbf
ORS_ENGINE_PROFILES_DRIVING_CAR_ENABLED=true

```

Btw. the above two - line examples are everything you need to run ors from now on. Internal defaults make sure you have defaults we think make most sense, but you are free to overwrite any time.

So much more. I’ll stop for now 😊

---

<div class="post-metadata">

**Author:** ![agocurti](https://ask.openrouteservice.org/user_avatar/ask.openrouteservice.org/agocurti/32/3396_2.png) [@agocurti](https://ask.openrouteservice.org/u/agocurti)\
**Post date:** [December 2, 2024, 3:55pm UTC](https://ask.openrouteservice.org/t/error-starting-local-ors-engine/6654/23 "2024-12-02T15:55:38Z")

</div>

You are doing a great work. I’ll have to understand better… Thanks

[Previous page](https://ask.openrouteservice.org/t/error-starting-local-ors-engine/6654.md?page=1)
