Cayetano Benavent

Hi @josh-mccord , I'm agree this issue is related to #244 & #183 We need to debug what is happening with new nodes. It is very helpful your contribution. Thanks,

Hi @tbicr , We suggest in ["Tips"](https://github.com/pgRouting/osm2pgrouting#tips) that you can use `--drop-author` and `--drop-version` flags with `osmconvert` to reduce size. If you would like to reduce more your dataset you...

Exactly, you need to define in mapconfig.xml your own use case or use this file directly. You have more xml config examples in the repository (you can tune as you...

Hi @Langlaeufer , - 40 is default max_speed: https://github.com/pgRouting/osm2pgrouting/blob/2adbbf361af7cbd45b8821a498ed586bd64bbf65/src/configuration/tag_key.cpp#L75 - The id has no meaning in OSM but the tag_name must be OSM tag. Thanks,

Hi @mkamaludeen , What version of osm2pgrouting are you using? Could you paste here the output of `osm2pgrouting -v`? Thanks,

@mkamaludeen `postgis` flag was removed several versions ago but we forgot to remove from docs. CC: @cvvergara I'm reviewing code and I found you left a comment (Can I remove...

I agree @dkastl . I'm going to remove this flag from README.

> This was discussed extensively in #25, but it feels worth revisiting. I think everyone feels good that the core recommendation is to use longitude, latitude in the WKB as...

> The broader question of what is a good, global CRS that is accurate and stays accurate through time is really a whole new issue for a far broader set...

> I would advice against recommending a CRS that defines axis order in the opposite way they actually are, as `EPSG:4326` does: it preserves the bad habit of using a...