Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Proposed fields to include in the "properties" object in the geojson we emit.
I think that they specify that everyone on the trail should be going one way or reverse to avoid collisions. Important for the mountain bike courses. But what does 1wayalternate mean?
I think SkiType should handle "classic", "skate", "both", or "na". How about trail length, handicap accessibility, and if dogs are allowed?
Right, I know of at least the following scenarios:
I don't know of a situation where the direction depends on mode of travel, but it might exist.
My main concern was to be able to draw little arrows on the map.
Revised proposal based on feedback and technical constraints
Note that field names are now lowercase, since some tools for handling the dataset are case-insensitive (e.g. SQLite)
winter and summer usage
The decision here depends almost entirely on what ogr2ogr will support easily. Personally, I think option 1 is technically the best, but I'm not sure how arrays as property values will flow through the GDAL tools.
Regardless, I believe the valid usage modes to be:
and I think it might make sense to add these (though I could see a dedicated field for "dog rules"):