Re: [Geocoding] [OpenStreetMap] #5429: search returns wrong postcode, knowing it better ...

2016-10-20 Thread OpenStreetMap 
#5429: search returns wrong postcode, knowing it better ...
--+--
  Reporter:  andreas.filsinger@…  |  Owner:  geocoding@…
  Type:  defect   | Status:  closed
  Priority:  critical |  Milestone:
 Component:  nominatim|Version:  2.0
Resolution:  invalid  |   Keywords:  postcode postal_code
--+--

Comment (by andreas.filsinger@…):

 I made the Remove. It now works as expected.

 (So my first commit to OSM is a Kill, puh)

--
Ticket URL: 
OpenStreetMap 
OpenStreetMap is a free editable map of the whole world

___
Geocoding mailing list
Geocoding@openstreetmap.org
https://lists.openstreetmap.org/listinfo/geocoding

Re: [Geocoding] [OpenStreetMap] #5429: search returns wrong postcode, knowing it better ...

2016-10-20 Thread OpenStreetMap 
#5429: search returns wrong postcode, knowing it better ...
--+--
  Reporter:  andreas.filsinger@…  |  Owner:  geocoding@…
  Type:  defect   | Status:  closed
  Priority:  critical |  Milestone:
 Component:  nominatim|Version:  2.0
Resolution:  invalid  |   Keywords:  postcode postal_code
--+--
Changes (by lonvia):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Sorry to say but this is a data error after all. The postcode comes from
 http://www.openstreetmap.org/node/25076969 which has a bad addr:postcode
 (and even a not so helpful note hinting that the addr:postcode tag is
 misused). As Neumünster makes up part of the address of Altdorferstrasse,
 the postcode is inherited. Remove the spurious addr:postcode on the town
 node and all will be well.

--
Ticket URL: 
OpenStreetMap 
OpenStreetMap is a free editable map of the whole world

___
Geocoding mailing list
Geocoding@openstreetmap.org
https://lists.openstreetmap.org/listinfo/geocoding

Re: [Geocoding] [OpenStreetMap] #5429: search returns wrong postcode, knowing it better ...

2016-10-20 Thread OpenStreetMap 
#5429: search returns wrong postcode, knowing it better ...
--+--
  Reporter:  andreas.filsinger@…  |  Owner:  geocoding@…
  Type:  defect   | Status:  new
  Priority:  critical |  Milestone:
 Component:  nominatim|Version:  2.0
Resolution:   |   Keywords:  postcode postal_code
--+--

Comment (by andreas.filsinger@…):

 result is "24534" (WRONG!)

 PolyLines both OK

 * http://orgamon.de/PLZ-24534-Poly.png
 * http://orgamon.de/PLZ-24539-Poly.png

 Correct Result should be:

 * http://orgamon.de/PLZ-24539-OK.png

--
Ticket URL: 
OpenStreetMap 
OpenStreetMap is a free editable map of the whole world

___
Geocoding mailing list
Geocoding@openstreetmap.org
https://lists.openstreetmap.org/listinfo/geocoding

[Geocoding] [OpenStreetMap] #5429: search returns wrong postcode, knowing it better ...

2016-10-20 Thread OpenStreetMap 
#5429: search returns wrong postcode, knowing it better ...
--+-
 Reporter:  andreas.filsinger@…   |  Owner:  geocoding@…
 Type:  defect| Status:  new
 Priority:  critical  |  Milestone:
Component:  nominatim |Version:  2.0
 Keywords:  postcode postal_code  |
--+-
 The Search "q=altdorferstr, neumuenster" (de) returns postcode 24534. It
 should return 24539.

 This is NOT an Error in the Data. Poly-Lines for both postcodes are
 correct (I try to attach 2 PNGs showing this).

 This is NOT a Street wich goes through 2 or more postcode claims, the
 whole street fully is inside 24539 Poly.

 It seems to me its a bug in the code checking if a point is in a Polygone
 or not. Or a bug in Creating placex Records while set up the Search-Basis.
 I do not know the path through the code adding PLZ Information to a found
 Street.

 Maybe Info-Addition "postcode" is done by "another" Table, not by
 PolyLines, based here on false Data, then please sorry - give me a hint to
 report this in correct manner.

 :-|
 Andreas

--
Ticket URL: 
OpenStreetMap 
OpenStreetMap is a free editable map of the whole world

___
Geocoding mailing list
Geocoding@openstreetmap.org
https://lists.openstreetmap.org/listinfo/geocoding