[mkgmap-dev] found multiple points with equal coord.....
From Ticker Berkin rwb-mkgmap at jagit.co.uk on Tue May 4 09:06:43 BST 2021
Hi Gerd & others This is a quite common physical set-up; a highway with another, more minor, highway/track/path leading off it with a "barrier" at the junction, inhibiting access to the minor highway. Often the only clear access restrictions visible on-the-ground are on the barrier, so these are what get represented in OSM. A minimal distance between the barrier and the major highway is needed to map this on OSM. mkgmap should handle this situation correctly. I haven't tried to understand why it didn't before, but if the patch fixes it then it should be applied. I've seen other examples of GPSMapEdit flagging errors like this: WARNING: Unexpected format of input data. Unexpected NodeID=936272 in turn restriction at (51.013083,-1.389384). The restriction will be ignored where there are very short section between the restriction and the junction node and I think it is just a GPSMapEdit problem. Ticker On Sun, 2021-05-02 at 08:46 +0000, Gerd Petermann wrote: > Hi all, > > the message > "Found multiple points with equal coords as CoordPOI at > http://www.openstreetmap.org/?mlat=56.835675&mlon=37.404949&zoom=17" > is produced because the nodes > https://www.osm.org/node/2924385337 > https://www.osm.org/node/2924351922 > are so close together that mkgmap could not distinguish the position. > No idea why someone maps a lift-gate less that close to the end of > the road, but of course mkgmap should not fail with this. > > The problem doesn't show up with the default style unless I add this > line in points rules: > barrier=*{ addaccess no;} > after > barrier=* & access=* {addaccess '${access|subst:private=>no}'} > Without this change the default style doesn't create a route > restriction for the barrier node > https://www.openstreetmap.org/node/2924385337 > > I've created a patch to fix this problem for good by adding a > hashmap but GpsMapEdit doesn't like the result: > Unexpected format of input data. Unexpected NodeID=136381 in turn > restriction at (56.835666 37.404950). The restriction will be > ignored. > > The old code didn't add the restriction, the new code does. > Now I am unsure if the "corrected" code causes more trouble than the > old. Maybe I should somehow detect the special case that a barrier > is very close to an end of a way which is not connected to other > ways? If I change the input data so that the end is a bit more away > GpsMapEdit doesn't complain. Is it just a problem in GpsMapEdit? > > Gerd > > ________________________________________ > Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag > von Thomas Morgenstern <webmaster at img2ms.de> > Gesendet: Samstag, 1. Mai 2021 08:56 > An: Development list for mkgmap > Betreff: [mkgmap-dev] found multiple points with equal coord..... > > Hi , > yesterday mkgmap r4587 gives me following message : 'found multiple > points with equal coord as CoordPOI at 56.835467 37.404949....... > The map seems okay. What shell I do with this message ?. Is this > meassage only a hint for incorrect data ? Or what else ? > > thomas > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
- Previous message: [mkgmap-dev] found multiple points with equal coord.....
- Next message: [mkgmap-dev] found multiple points with equal coord.....
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list