telenav / open-source-spec Goto Github PK

Requirements for our tech blog:

• Simple, supports needed features only, refuse to fancy
• tags
• archive
• comments

Examples

• Github + HEXO https://zhuanlan.zhihu.com/p/26625249

Vector tile service provide map data in tile format and enable consumers to render map content. A specific geographical area will have a 1-to-1 mapping to certain tile. The widely used solution is: Using Web Mercator for the projection of reference, using google tile scheme for tile extent convention, and using MapBox's vector tile specification as interface.

The experiment we want to have is:

• Set up vector tile service follows MapBox's vector tile specification based on open source solution and professional data(map data and traffic), use Map Box's SDK to render the result.
• There are many candidates could do the work. This page contains some of open source solutions and this page contains our experiment about Tegola + OSM data. For anyone we picked, need to provide evaluation on why we want it. Metrics like pre-processing time, activity of the community, integration with professional data, remaining major issues are important for us to make the decision.
• Must use professional map data + traffic
• Integrate with MapBox's SDK helps us play with the solution

More Info

• https://github.com/mapbox/awesome-vector-tiles/

I need some help guys. I cant understand that the 'Basic Changes of Convert OSM to OSRM Edge-expanded Graph' in 'Understanding OSRM Graph Representation'. In my opinion, the segment with particular is a node in OSRM graph,but the last figure in 'Basic Changes of Convert OSM to OSRM Edge-expanded Graph' is not clear. Blue points represent the OSM point, and a segment between to OSM points equals a edge in graph, why the red line(a segement) include two black points? And I think its contradicting.

https://github.com/Telenav/open-source-spec/blob/master/fb_cpp_stack/doc/cpp_futures_instagram_notes.md

In the past 1 ~ 2 years, @wangyoucao577, @CodeBear801 work with team set up a bunch of microservices. We met lots of changeless and also spend time on things which is not matter that much, but when look back, all of us feel a great of improvement, as a developer and also as a high efficiency development team.

We want to write a series summaries for ourselves and also for the team, which would cover:

• How to clarify problem set with user story mapping
• How to write clear and meaningful document
• Generate external interface using open api
• Communication between sub-system via grpc, or via message bus
• Test driven development
• Code search patterns
• Continues integration via github action and trivas
• Continues deployment via jenkins and Kubernetes
• Set up shared development environment via remote development in container with vscode
• Set up local dependencies via docker compose
• Event driven(option)
• Distribute tracking(option)
• Log analysis(option)
• Idempotence(option)

How about create a folder called startupOS?