It's possible to instantiate an OSRM object in Javascript like this:

    const osrmInstance = new OSRM({
        algorithm: 'CH',
        dataset_name: 'foo',
        mmap_memory: true
    });

This should throw an error - setting mmap_memory should require supplying a path, and this is incompatible with using dataset_name, which triggers using shared memory.

These opti

Need to:

• update the installation instructions for v1.0.0.
• create installation and osm loading helper scripts.
• update other documentation that is impacted by v1.0.0.
• update the manual in the app for v1.0.0.

for example highway=construction in New York fails without hints while highway=construction in "New York" works.

It may be nonobvious for a newbie and I assume that it is relatively easy to autocorrect or detect as likely cause for failure.

This works fine

export OUTPUT_PATH=/tmp/docs
jazzy --output=$OUTPUT_PATH --min-acl private -x clean,build,-workspace,OpenGpxTracker.xcworkspace,-scheme,OpenGpxTracker

If we change the scheme to OpenGpxTracker-Watch, it does not work

jazzy --output=$OUTPUT_PATH --min-acl private -x clean,build,-workspace,OpenGpxTracker.xcworkspace,-scheme,OpenGpxTracker-Watch

I just noticed a new addition to the NSI (ee271f6) which is for the car park operator Q-Park, which places the car park operator as the name of the car park.

However, I think many car parks have their own name (e.g Cedars Car Park), and so wouldn'

See section 12.4 of the User Guide (also, move that section to Developer's Guide, where its more appropriate).

I suggest that [landuse=basin] may be rendered with flat water-blue, and no strange green icon.

Example in a park :

https://www.qwant.com/maps/#map=18.21/48.8766543/2.2634781

And in the countryside :
![capture d ecran 2019-01-16 a 22 09 39](https://

We don't have a one stop shot, deep dive into all of the options available through the Places API and it'd be a good addition to the notebooks.

This would probably be quite useful, and easily added to opq (). Should probably also default to recurse down relation (>>).

We have a number of ways to supply test Atlas data. Some options include:

• leveraging the TestAtlas and supporting annotations
• using .txt Atlas files
• using .atlas.gz Atlas files
• supplying raw .osm files, created in JOSM

Each option has a specific use case. This task involves creating a README documenting each option, any standardization (for example - do not GZIP your text fi

From @ildar in #129:

Please implement lossless rotation 90°/180°/270° through EXIF. As an UI example see Shotwell application.
Thanks

We need a way to exclude certain ways (eg highway:motorway) (See https://wiki.openstreetmap.org/wiki/Key:highway).

This list may should be configurable to address specific users need.

Make use of above methods to convert console input to database string (UTF-8) and vice versa where appropriate. See LocationLookup.cpp for an example.

Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/45418421-make-use-of-localestringtoutf8string-and-vice-versa-in-demos?utm_campaign=plugin&utm_content=tracker%2F22109906&utm_mediu

Implement a better isochrones algorithm, a more detailed description can be found here.

If you are a new contributor this is perfect, get in touch by responding below. Your code will end up in our next release after finishing. What we think you can learn:

• More about geo-algorithms.
• More about routin

I am sorry if I missed something in the docs. To know how to integrate a map in an RMarkdown document, I had to look at the source of vignettes. Is the solution used in vignettes the simplest one? Then, is it documented somewhere? And last, could it be simplified? E.g. in order to be able to use maps like magick objects.

I'm following along with this tutorial. I am to read a pbf file into imposm.

imposm --read germany.osm.pbf

However, when I try to write to the database with

imposm --write --database osm --host localhost --user osm --port 5432

I get this error

`Traceback (most recent call last):
File "/usr/local/bin/imposm", line 9, in

At the main page for the this repo, there's no README, and hence no text after the file listing. What's missing is:

A brief explanation of what the app does. I don't mean how to operate it, but a summary of functionality as well as explaining things that are not present when such might reasonably be expected (e..g, if it does video, what about stills on command). Also does one need to have