>Is there some way of doing this just once; for example with some parseable
implication database, and library?
>...
>1. normalizing a database before usage, for example changing
> "highway=ford" to "ford=yes" and moving to modern lifecycle tags
The iD Editor has some JSON metadata about this ..
Interesting, I assume you are both aware of:
http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions
which covers just part of the problem space. For example to do it
properly you need to normalize vehicle types, add rules for
standing/parked vehicles and so on.
Simon
Am
On 17/11/16 11:51, Per Eric Rosén wrote:
> Hi!
>
> I have been making a few maps and applications using OSM data, mostly
> stored in postgis. In all cases, I have had to make custom carto rules /
> database post-processing / application rules to compensate for multiple
> ways of expressing the
On Thu, Nov 17, 2016 at 11:51:39AM +0100, Per Eric Rosén wrote:
> I have been making a few maps and applications using OSM data, mostly stored
> in postgis. In all cases, I have had to make custom carto rules /
> database post-processing / application rules to compensate for multiple
> ways of
Hi Per Eric,
What you are looking for is definitely on the wiki side.
The information isn't available as described for now but it would be
interesting to document tags like this.
And a new application/projet might not be necessary if wiki can support it.
That question was rose a few times ago.
Hi!
I have been making a few maps and applications using OSM data, mostly
stored in postgis. In all cases, I have had to make custom carto rules /
database post-processing / application rules to compensate for multiple
ways of expressing the same information in OSM. Also, in some cases,
for
6 matches
Mail list logo
