[mkgmap-dev] FW: Should we exclued bridges from housenumber processing?
From Gerd Petermann gpetermann_muenchen at hotmail.com on Sun Jun 7 04:43:40 BST 2015
From: gpetermann_muenchen at hotmail.com To: gdt at ir.bbn.com Subject: RE: [mkgmap-dev] Should we exclued bridges from housenumber processing? Date: Sun, 7 Jun 2015 05:31:42 +0200 Hi Greg, > I don't see why an address shouldn't be valid just because it's on a > road that happens to be a bridge. It would be good to get pointers to > the situations where people think this proposed rule makes sense, and we > can then see if we think there are tagging errors. you are right, I should have mentioned the reason. The new housenumber code is much slower than the old one, the major reason is that it has to find matching roads without using the name. In the default style, I've added some rules to exclude roads which probably never should be used for adresses, e.g. motorways, ferries and ways created by the --make-opposite-cycleways option. Marios idea was that bridges and tunnels are like those, but it turned out that we have valid addresses on bridges and in level -1 areas. So, I think the short answer is "no, we should not exclude bridges" thanks for the feedback to all others too Gerd -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20150607/12c1d8bb/attachment.html>
- Previous message: [mkgmap-dev] Commit: r3612: use high precision when calculating the boundaries
- Next message: [mkgmap-dev] GUI for POI Search TYPES
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list