Skip to content
Navigation Menu
Sign in
Appearance settings
Platform
AI CODE CREATION
GitHub Copilot
Write better code with AI
GitHub Copilot app
Direct agents from issue to merge
MCP Registry
Integrate external tools
DEVELOPER WORKFLOWS
Actions
Automate any workflow
Codespaces
Instant dev environments
Issues
Plan and track work
Code Review
Manage code changes
Code Quality
Enforce quality at merge
APPLICATION SECURITY
GitHub Advanced Security
Find and fix vulnerabilities
Code security
Secure your code as you build
Secret protection
Stop leaks before they start
EXPLORE
Why GitHub
Documentation
Blog
Changelog
Marketplace
View all features
Solutions
BY COMPANY SIZE
Enterprises
Small and medium teams
Startups
Nonprofits
BY USE CASE
App Modernization
DevSecOps
DevOps
CI/CD
View all use cases
BY INDUSTRY
Healthcare
Financial services
Manufacturing
Government
View all industries
View all solutions
Resources
EXPLORE BY TOPIC
AI
Software Development
DevOps
Security
View all topics
EXPLORE BY TYPE
Customer stories
Events & webinars
Ebooks & reports
Business insights
GitHub Skills
SUPPORT & SERVICES
Documentation
Customer support
Community forum
Trust center
Partners
View all resources
Open Source
COMMUNITY
GitHub Sponsors
Fund open source developers
PROGRAMS
Security Lab
Maintainer Community
Accelerator
GitHub Stars
Archive Program
REPOSITORIES
Topics
Trending
Collections
Enterprise
ENTERPRISE SOLUTIONS
Enterprise platform
AI-powered developer platform
AVAILABLE ADD-ONS
GitHub Advanced Security
Enterprise-grade security features
Copilot for Business
Enterprise-grade AI features
Premium Support
Enterprise-grade 24/7 support
Pricing
Search
/
Sign in
Sign up
Appearance settings
You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading.
Please reload this page
.
nextzen
/
vector-datasource
Public
forked from
tilezen/vector-datasource
Notifications
You must be signed in to change notification settings
Fork
1
Star
1
Code
Pull requests
0
Actions
Projects
Wiki
Security and quality
0
Insights
Additional navigation options
Code
Pull requests
Actions
Projects
Wiki
Security and quality
Insights
Files
Expand file tree
master
Breadcrumbs
vector-datasource
/
config.dev.yaml
Copy path
Blame
More file actions
Blame
More file actions
Latest commit
History
History
History
57 lines (50 loc) · 1.52 KB
master
Breadcrumbs
vector-datasource
/
config.dev.yaml
Copy path
Top
File metadata and controls
Code
Blame
57 lines (50 loc) · 1.52 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
# This is a minimal configuration to get vector-datasource running in
# development. Documentation about the tileserver configuration syntax
# can be found in it's repository.
# In production the debug, reloading, and caching settings will probably
# need to be changed, at a minimum.
postgresql:
dbnames: [osm]
queries:
config: queries.yaml
template-path: queries
reload-templates: true
formats: [json, topojson, mvt]
buffer: {}
server:
host: localhost
port: 8080
debug: true
reload: true
threaded: false
http:
# whether to include cors headers on responses
cors: true
# client cache time in seconds ("Cache-Control: max-age" header)
max-age: 300
health:
url: /_health
path_tile_size:
# NOTE: the keys should be strings
"256": 1
"512": 2
# requests for zoom levels higher than this will 404
max_interesting_zoom: 20
# control how python code from yaml is used
yaml:
# dotted name or runtime
type: parse
parse:
# this will parse the yaml files and compile them on startup
# useful when iterating on updating the yaml files themselves
path: yaml
callable:
# this will call a function that should return a mapping from
# layer name to function that generates the output properties
# mapping returned should look like:
# layer-name -> function(shape, properties, feature_id)
# useful when the output functions have already been generated
# and it's simply a matter of pointing to them
dotted-name: path.to.function.returning.mapping
args:
- 'any-args-to-pass'
You can’t perform that action at this time.