Comments (6)
I was going to write something about the tree, but then I noticed the top of the page linked
The scope of this project is US public access lands administered by the US Government. However, the principles in this project plan may be applicable to other public lands at the state and local level
OpenMapTiles needs to work everywhere. Their recommendations are built around paths with Land Managers, while most paths don't have a Land Manager in the sense they are talking about. I suspect most footpaths are far more similar to a sidewalk than a footpath on public lands, but would welcome an analysis.
I think two attributes are the best method of doing this. One for access with three possible values - yes (including plain highway=footway with no other tags), sort of, and no access. The other would be surface, also with three possible values - paved, unpaved, or unknown. The cartographer making a style could then choose if they wanted emphasis on access or surface, depending on their needs.
from openmaptiles.
I am presently hosting a trails vector layer for OSM US's trail project (the working group and the OpenTrailMap.us map). It's accessible here for anyone that wants to play with it: https://d1zqyi8v6vm8p9.cloudfront.net/trails.json
That's outside of OpenMapTiles of course, but it's fairly easy to generate custom layers for this kind of thing in planetiler.
The schema I've used to generate that trails layer is here.
from openmaptiles.
Hi, I think that the easiest way could be just to extend the access
attribute to "if access=no
or access=private
or informal=yes
" then the value will be access=no
.
from openmaptiles.
IMO that's too little information. You certainly couldn't implement the example rendering tree linked.
from openmaptiles.
I think two attributes are the best method of doing this. One for access with three possible values - yes (including plain highway=footway with no other tags), sort of, and no access.
I think that would work 👍
The other would be surface, also with three possible values - paved, unpaved, or unknown. The cartographer making a style could then choose if they wanted emphasis on access or surface, depending on their needs.
This is already there and played a big part in my being able to build V1 of OpenTrailStash! (The field is just blank when unknown) https://openmaptiles.org/schema/#surface
from openmaptiles.
Which, thinking about it, could be implemented similarly to the surface
tag. access
currently only exists with a value of false
. It could be updated to also include true
when tags imply access is allowed and remain absent for the "sort of" case. It should(I guess if styles use ["has", "access"]
some styles may have a regression) have no impact on existing styles using the access
tag but enable better styling going forward.
from openmaptiles.
Related Issues (20)
- Add shop=bakery and shop=butcher as they are currently not rendered HOT 1
- Feature request: Add more tags for places and POIs HOT 3
- Show tertiary roads on lower zoom levels HOT 3
- Error - failed to create network openmaptiles_default HOT 2
- POI for `amenity=university` is incorrectly conflated with `office=university`
- Beach names missing HOT 2
- Network property is in Germany set to `road` even a `network` is available
- How do I update coastlines / oceans from OSM? HOT 4
- Unsigned routes should not be included in the transportation_name layer HOT 3
- error generating some tile HOT 1
- Cable cars are neither rendered nor exported into mbtiles HOT 4
- Wrong rank for "Seminole Nation": 3 instead of 1
- Wetlands show much darker (even black) at zoom level 13 and up. HOT 2
- Error: SQLITE_ERROR: cannot start a transaction within a transaction HOT 2
- Roads on upper zoom levels are too segmented. HOT 1
- Ensure that place points are always inside their boundaries
- Excessive growth of .mbtiles file size with updates HOT 1
- Update the pathway to Wayson Auto Sdn Bhd HOT 1
- Add support for `landuse=flowerbed`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openmaptiles.