Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#4428 closed defect (wontfix)

Nominatim results display a confusing reference to "Catania CTR Zone 2"

Reported by: erbioton Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: Cc:


Searching for a street in Ragusa, Italy, with Nominatim, the place is displayed with a confusing reference to "Catania CTR Zone 2" and "Ragusa Ibla" while it should only display the town name: "Ragusa".

Change History (4)

comment:1 Changed 7 years ago by datendelphin

nominatim indexes Catania CTR Zone 2 as locality, which is wrong.

comment:2 in reply to:  1 Changed 7 years ago by datendelphin

correction, it indexes it because

"-- any feature more than 5 square miles is probably worth indexing" functions.sql, placex_insert()

maybe worth indexing, but using it as part of an address is something different.

comment:3 Changed 7 years ago by twain

Resolution: wontfix
Status: newclosed

The way is tagged:

aeroway = ctr

which is an undocumented tag which even I don't understand.

Nominatim makes the assumption that it is an airport boundary and that this train station is within that boundary. Personally I think airspaces don't belong in the dataset and if they do they certainly shouldn't be tagged as aeroway = ctr.

Data error - please fix the data instead.

comment:4 Changed 7 years ago by twain

Found this documented on the wiki:

As per this I'm going to delete these airspace ways which will resolve the problem.

Note: See TracTickets for help on using tickets.