>"*is it possible, in OSMand, to build a filter customizing the query, independently from the predefined ones? Or how can add a specific custom filter?*".
As far as I know, the answer is no. The predefined settings within the query button are as specific as OsmAnd gets. >Another example could be filtering all sidewalks with a paved surface, i.e. with a query similar to "highway=footway AND footway=sidewalks AND surface=asphalt". The OSM feature "highway=*" is more problematic still in that OsmAnd doesn't recognize roads, footways, etc as categories within its search function. Over at the OSM wiki, some of the thinking regarding this issue can be found here: https://wiki.openstreetmap.org/wiki/Disabilities On Monday, June 3, 2019 at 6:20:29 AM UTC-7, Xavier wrote: > > On Mon, Jun 03, 2019 at 02:52:00PM +0200, Alessandro Sarretta wrote: > >Hi there and thanks to all for the interactions. > > > >On 03/06/19 08:59, Peter B wrote: > >>OsmAnd uses capacity:disabled= <number>, example capacity:disabled=1 > >>It is possible to create a user defined search with that: > >>In filters check "Dedicated places for disabled". > >>If works! > >>Of course you need the tagging in the data. I did not test other > taggings with disabled tags. > >>Peter > > > >The tag capacity:disabled=<number> is referred mainly to > >amenity=parking, and not to amenity=parking_space. > > > >So it describes the number of disabled parking spaces inside a car > >parking, but not the specific parking space. > > > >The use case I'm looking for is to help disabled people to reach > >exactly the space for them where to park, so that they can also plan > >which path (throught sidewalks that have e.g. a lowered kerb) to use > >to reach their destination. > > This use, while excellent, is *very* dependent upon OSM mappers not > simply drawing a large area around the permiter of a parking lot but > instead upon them mapping each individual parking space. > > Checking taginfo for amenity: > https://taginfo.openstreetmap.org/keys/amenity#values > > One finds 3,112,918 uses of amenity=parking (most of which are on an > area, i.e., most likely the outer permiter of the whole lot) but only > 222,624 uses of amenity=parking_space. > > Since it stands to reason that most amenity=parking areas will contain > plural parking spaces, this means that there are a huge number of > unmapped parking spaces in the real world. Until someone draws the > individual parking spaces in OSM, there will be, sadly, no way to route > an individual directly to the particular location of a disabled parking > space within a larger lot when the particular space is as yet unmapped. > > You might consider a MapRoulette (https://maproulette.org/) challenge > to encourage mapping of both parking spaces and further of the tags > that define individual disabled parking spaces. > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/2e18d236-8444-4a1a-812f-8b2df4136359%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
