-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Raid maps with extractions and POI #55
Comments
Hey, thanks for pointing out the project was unknown to me so far. I / we at Tarkov Database have been planning this for a very long time and have been working on it for about 2 weeks now. A first version will probably be released in December (so maybe a Christmas present? Let's see ;-)) I will be posting status updates here regularly in the future. |
Just a small question, does your service use the Google Map API? I have only seen people doing this with Minecraft maps and I just want to know how, is your service open-source/planning to become open-source? |
We use our own infrastructure, no external services. This is built with open standards and existing open source software. |
Sorry for the long wait! I released a first early version of Customs last Saturday Next up is the spatial / layer data implementation into the REST API. As soon as it is done, Customs will be completed and more maps will be worked on. I assume that Veritas will address the implementation in BB once the API work is completed. |
The API implementation has been completed in the meantime and the map has also been changed to a more precise measurement method. Demo https://streamable.com/0bed5 Currently I am working on the implementation of Shoreline. When the implementation in Battle Buddy will follow, I can't say at the moment, this is entirely up to |
Would be cool to be able to view each map and locate the points of interest and extraction points for SCAVs/PMCs. Reference website: http://www.gamemaps.co.uk/game/tarkov
The text was updated successfully, but these errors were encountered: