Re: [OSM-dev] Nominatim 2.3 release announcement
On Sunday 05 October 2014, Sarah Hoffmann wrote: > > > > I figured that intention from the results i saw for various rivers. > > Still it would be good i think to distinguish between waterway > > relations and ways in the results. For larger rivers there are > > very often individual ways missing in the relation, most frequently > > side streams of course, so you rarely only get a sigle result with > > type=waterway:river. > > These are mapping errors, aren't they? As a rule, Nominatim does not > try to cover such errors, precisely so that mappers can easily spot > them and fix them. That is exactly my point, if you can distinguish between the waterway relation and such stray individual waterways this is much easier. But of course if the relation turns up reliably at the first place in the list this is much less critical. -- Christoph Hormann http://www.imagico.de/ ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Nominatim 2.3 release announcement
On Sun, Oct 05, 2014 at 06:51:24PM +0200, Christoph Hormann wrote: > On Sunday 05 October 2014, Sarah Hoffmann wrote: > > > > Well, the idea was to make only the 'river line' of rivers searchable > > and complete ignore the areas as they have only limited meanining > > from a geolocation point of view. So, it should show only waterway > > relations, waterway ways that are not part of a relation (and are not > > something potentially interesting like a waterfall) as well as > > natural=water. Of course, it's all heuristics because tagging is far > > from consistent. For some disussions see > > https://github.com/twain47/Nominatim/issues/155 > > I figured that intention from the results i saw for various rivers. > Still it would be good i think to distinguish between waterway > relations and ways in the results. For larger rivers there are very > often individual ways missing in the relation, most frequently side > streams of course, so you rarely only get a sigle result with > type=waterway:river. These are mapping errors, aren't they? As a rule, Nominatim does not try to cover such errors, precisely so that mappers can easily spot them and fix them. However, waterway relations 'should' get precedence over waterway ways in the ordering of results. How well that works we will have to see, once the reimported database is live. Sarah ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Nominatim 2.3 release announcement
On Sunday 05 October 2014, Sarah Hoffmann wrote: > > Well, the idea was to make only the 'river line' of rivers searchable > and complete ignore the areas as they have only limited meanining > from a geolocation point of view. So, it should show only waterway > relations, waterway ways that are not part of a relation (and are not > something potentially interesting like a waterfall) as well as > natural=water. Of course, it's all heuristics because tagging is far > from consistent. For some disussions see > https://github.com/twain47/Nominatim/issues/155 I figured that intention from the results i saw for various rivers. Still it would be good i think to distinguish between waterway relations and ways in the results. For larger rivers there are very often individual ways missing in the relation, most frequently side streams of course, so you rarely only get a sigle result with type=waterway:river. For the Rhine you for example currently get http://nominatim.openstreetmap.org/details.php?place_id=9161541869 for the Seine: http://nominatim.openstreetmap.org/details.php?place_id=9161541869 http://nominatim.openstreetmap.org/details.php?place_id=9182370138 for the Zambezi: http://nominatim.openstreetmap.org/details.php?place_id=9156313780 > I'm dimmly aware that there is a new proposal for water areas aiming > to unify fowing and standing water areas. I can't say I'm very happy > with it from a data processing point of view because it mixes primary > geographic objects that are of interest on its own (lakes etc.) with > secondary objects that only describe the area of another object > (i.e. river and riverline). Having to use a second tag to figure out > the meaning of the first is always problematic. Therefore, Nominatim > ignores the whole water=* issue in the hope that the tagging schema > doesn't really catch on. ;) I fully agree here, flowing and standing water should be a primary distinction - but there is of course also the opposite case with lakes being tagged waterway=riverbank. -- Christoph Hormann http://www.imagico.de/ ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Nominatim 2.3 release announcement
Hi, On Sun, Oct 05, 2014 at 11:03:39AM +0200, Christoph Hormann wrote: > On Sunday 05 October 2014, Sarah Hoffmann wrote: > > > > There are two new features that are most notable for users of the > > search engine: there is now support for waterway relations, which > > improves searching for rivers, [...] > > Nice. > > It seems though they are reported in the same way in the results lists > as river lines with 'River' which makes them hard to identify. Word of warning: although the instance at nominatim.osm.org (and consequently the search at osm.org) runs the latest code of Nominatim, it hasn't been reimported since waterwat relations have been introduced. The database has only changed to the new schema, where OSM object have been edited since. > In principle i would have four major classes for water features: > > * standing water areas (natural=water + water!=river/channel) > * flowing water areas (waterway=riverbank or natural=water + > water=river/channel) > * waterways (waterway tag but not waterway=riverbank) > * waterway relations Well, the idea was to make only the 'river line' of rivers searchable and complete ignore the areas as they have only limited meanining from a geolocation point of view. So, it should show only waterway relations, waterway ways that are not part of a relation (and are not something potentially interesting like a waterfall) as well as natural=water. Of course, it's all heuristics because tagging is far from consistent. For some disussions see https://github.com/twain47/Nominatim/issues/155 I'm dimmly aware that there is a new proposal for water areas aiming to unify fowing and standing water areas. I can't say I'm very happy with it from a data processing point of view because it mixes primary geographic objects that are of interest on its own (lakes etc.) with secondary objects that only describe the area of another object (i.e. river and riverline). Having to use a second tag to figure out the meaning of the first is always problematic. Therefore, Nominatim ignores the whole water=* issue in the hope that the tagging schema doesn't really catch on. ;) Sarah ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Nominatim 2.3 release announcement
If I search for river with Nominatim , I obtain all the features where there is river in the name. It would be interesting to have a syntax similar to Xapi and Overpass to be able to search for specific tag (ie. amenity=school). Pierre De : Christoph Hormann À : dev@openstreetmap.org Envoyé le : Dimanche 5 octobre 2014 5h03 Objet : Re: [OSM-dev] Nominatim 2.3 release announcement On Sunday 05 October 2014, Sarah Hoffmann wrote: > > There are two new features that are most notable for users of the > search engine: there is now support for waterway relations, which > improves searching for rivers, [...] Nice. It seems though they are reported in the same way in the results lists as river lines with 'River' which makes them hard to identify. In principle i would have four major classes for water features: * standing water areas (natural=water + water!=river/channel) * flowing water areas (waterway=riverbank or natural=water + water=river/channel) * waterways (waterway tag but not waterway=riverbank) * waterway relations -- Christoph Hormann http://www.imagico.de/ ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Nominatim 2.3 release announcement
On Sunday 05 October 2014, Sarah Hoffmann wrote: > > There are two new features that are most notable for users of the > search engine: there is now support for waterway relations, which > improves searching for rivers, [...] Nice. It seems though they are reported in the same way in the results lists as river lines with 'River' which makes them hard to identify. In principle i would have four major classes for water features: * standing water areas (natural=water + water!=river/channel) * flowing water areas (waterway=riverbank or natural=water + water=river/channel) * waterways (waterway tag but not waterway=riverbank) * waterway relations -- Christoph Hormann http://www.imagico.de/ ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Nominatim 2.3 release announcement
Hi, we are happy to announce the release of a new stable version 2.3 of Nominatim, the OSM search engine. There are two new features that are most notable for users of the search engine: there is now support for waterway relations, which improves searching for rivers, and POIs like shops and restaurants now can inherit their address from the building they are in. Next to that a lot of smaller bugs have been fixed and further tweaks to the search algorithm allow for improved ordering of results. This release also marks the arrival of a functional test suite for Nominatim. The new release is available at http://www.nominatim.org/release/Nominatim-2.3.0.tar.bz2 Installation instructions are at the usual place at http://wiki.openstreetmap.org/wiki/Nominatim/Installation You can always try the latest version of Nominatim on http://nominatim.openstreetmap.org Regards Sarah ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
