How to tag if entering/parking with motorhome is possible?

Hey,

Most of the motorhome users seem to focus on apps like iOverlander and park4night instead of adding the suitable parks on OSM. The sad part of this is that their data is not open for everyone.

I would want to change this by making it easier to tag motorhome=yes or motorhome=no or motorhome=designated or motorhome=permissive.

I queried this data inside Europe and saw that this tag is commonly used in these:

  • tourism=camp_site
  • tourism=camp_pitch
  • amenity=parking
  • highway=service
  • amenity=parking_space
  • amenity=sanitary_dump_station
  • amenity=water_point

But overall there’s very little places which have these tags compared to the other apps I mentioned above.

What is a bit confusing for me is that id-tagging-schema for tourism=camp_site does not contain motorhome tag. Is assumed that even without motorhome tags they are allowed to enter because of the nature of the place?

It would be great that when using dedicated OSM editor in iphone/android like Go Map!! or Streetcomplete it would automatically prompt for these fields.

Ideally this would help the motorhome users to navigate into places where these big vehicles would not be harming other road users or residents.

Should I make a PR into the id-tagging-schema to help filling these tags in more places? Is there a better way to prompt editors to fill this field too.

Yes, in OSM, motorhomes are counted as Key:caravans - OpenStreetMap Wiki, so stopping areas are usually included under Tag:tourism=caravan_site - OpenStreetMap Wiki

The issue I can see with defining them further is what is a “motorhome”? :thinking:

Are you thinking:



https://cdn.prod.website-files.com/6527041853fda5913e2a6c5b/6849b571191cea51b2b1898f_new-dembell-1.jpg or even
https://image.made-in-china.com/2f0j00kaGBIEHqaobs/Premium-Double-Floor-Motorhome-by-Established-20-Year-RV-Brand.webp :stuck_out_tongue_winking_eye:

2 Likes

What I’m thinking is just absence of something like this :smile:

Well, wiki for tourism=camp_site does mention them. It was added there less then 3 years ago though, and it mentions discussion at https://community.openstreetmap.org/t/caravan-sites-and-campers so you might want to read up there.

Don’t know about Go Map!!, but if you wish for StreetComplete quest, it will need to be requested separately at their GitHub issues (i.e. updating id-tagging-schema won’t help for those additional tags)

1 Like

The problem with adding information to OSM is that it should be verifiable. If for instance you want to add information whether a wild camping site is reachable by motorhome, in iOverlander you just click a motorhome yes/no toggle field. But in OSM, motorhome=yes/no means that a way can or cannot legally be used by a vehicle defined as a “motorhome” in the laws of the country. To map practical accessibility, you’d have to add tags such as smoothness for the surface quality of the access road and maxweight for the bridge you might have to cross (it would have to be signposted). You can’t tag it if a site is unreachable because of low-hanging branches (unless there’s a legal max height sign there telling you that), a sharp curve between buildings that you can’t take with a long vehicle, etc.

Agree that the aim of OSM might be a different one than the aim of such portals. Like in OSM we do not want to have a place mapped where you can park your motorhome overnight at a beautiful river somewhere in the woods. But rather signposted places.

Most of the places still dont exist even as Key:impromptu - OpenStreetMap Wiki or ”informal”.

I dont personally care if we can tag a beatiful looking river in the background or not. The low hanging branches should be verifiable according to the standards of the link above. There is much more information tagged to OSM already than just what the signposts have but I would be happy to have even the sign posted information in OSM and the main problem is that adding that info to OSM is much more involved than in other apps for the general public :smiling_face_with_tear: