RainerU-2 wrote
Hello Kai,
Am 14.04.2013 21:47, schrieb Kai Krueger:
Perhaps I don't quite understand what you need, but does osm2pgsql not
already do this?
osm2psql creates a way entry in the planet_osm_line table for each member
of a
route relation. The name tag of the relation is
Kai Krueger kakrue...@gmail.com wrote:
So name:de and name:fr are already available in the standard osm2pgsql db.
Also all other tags of the route relation are in the db. Why osm2pgsql
translates the name tag into route_name, I don't know. Also I wonder why
there is so much special casing of
Am 15.04.2013 09:04, schrieb Kai Krueger:
If I am not mistaken, it tries to create one entry per relation. However, as
in its default mode, osm2pgsql does not create multi-geometries, there will
be one entry per contiguous geometry in the planet_osm_lines table. It is
not per member way. If
Am 13.04.2013 11:34, schrieb Shaun McDonald:
Another option is to use the hstore options of Postgres and osm2pgsql and
form the queries based on that.
Doing it that was will probably use less diskspace and avoid having too many
columns etc.
Currently hstore has no effect on ways created from
RainerU-2 wrote
Hello,
For map rendering I needed the local names of route relations such as
name:de,
name:fr. As osm2pgsql does only copy the name tag from the relation to the
related ways, I modified the program to copy all the name:xx tags to
route_name:xx on the ways.
Perhaps I don't
Hello Kai,
Am 14.04.2013 21:47, schrieb Kai Krueger:
Perhaps I don't quite understand what you need, but does osm2pgsql not
already do this?
osm2psql creates a way entry in the planet_osm_line table for each member of a
route relation. The name tag of the relation is copied as route_name
Hi Sven,
Am 12.04.2013 12:05, schrieb Sven Geggus:
Wouldnt it make more sense to copy all tags probably prefixing route_ to be
compatible to the existing code?
That's a good point. I will try to implement it like that.
Rainer
___
dev mailing list
Am 11.04.2013 19:57, schrieb RainerU:
As I am not familiar with github, I would need some hints how to proceed.
The usual approach would be fo fork the osm2pgsql repo, create a
feature-branch, check out that branch, change your code inside, test,
commit and push the new branch to your fork
RainerU ra...@sfr.fr wrote:
As it works fine and the risk of regression or side effects seems very low
to me, I propose to include this feature into the repository. Do the
maintainers of osm2pgsql agree?
Wouldnt it make more sense to copy all tags probably prefixing route_ to be
compatible to
Hello,
For map rendering I needed the local names of route relations such as name:de,
name:fr. As osm2pgsql does only copy the name tag from the relation to the
related ways, I modified the program to copy all the name:xx tags to
route_name:xx on the ways. As it works fine and the risk of
10 matches
Mail list logo
