WvW objective names
Debois Guilbert.6413:
Having a hard time determining objective names from the data returned by
https://api.guildwars2.com/v1/wvw/match_details.json
using the mapping in
https://api.guildwars2.com/v1/wvw/objective_names.json
Reminds me of map chat sometimes:
[API Dude]: 20 DR at Tower
[Commander Patience]: Which tower?
[API Dude]: Ummm… Tower?
[Commander Patience]: Can you tell me where it is on the map, NE, NW for example?
[API Dude]: Err… I can tell you that its id is 47.
[Commander Patience]: Sorry that doesn’t tell me where I need to go to assist.
[API Dude]: Let’s see… according to the API it’s called… “Tower”
[High Strung Dude]: —-- (my language filter is on)
Hope I haven’t overlooked something obvious.
The Talcmaster.7391:
I like the character names.
Annoying as it is, at least this problem can be solved by assigning each ID its own name instead of relying on what the program returns. The strange thing is that it goes between categorical naming (Tower) to more specific things for the supply camps (Red Mine, Fishing Village). About as easily solvable of a problem though.
El Do.9467:
I think these are correct, the points are after the name
id:1 = “Overlook”,25
id:2 = “Valley”,25
id:3 = “Lowlands”,25
id:4 = “Golanta Clearing”,5
id:5 = “Pangloss Rise”,5
id:6 = “Speldan Clearcut”,5
id:7 = “Danelon Passage”,5
id:8 = “Umberglade Woods”,5
id:9 = “Stonemist Castle”,35
id:10 = “Rogue’s Quarry”,5
id:11 = “Aldon’s Ledge”,10
id:12 = “Wildcreek Run”,10
id:13 = “Jerrifer’s Slough”,10
id:14 = “Klovan Gully”,10
id:15 = “Langor Gulch”,10
id:16 = “Quentin Lake”,10
id:17 = “Mendon’s Gap”,10
id:18 = “Anzalias Pass”,10
id:19 = “Ogrewatch Cut”,10
id:20 = “Veloka Slope”,10
id:21 = “Durios Gulch”,10
id:22 = “Bravost Escarpment”,10
id:23 = “Garrison”,25
id:24 = “Champion’s demense”,5
id:25 = “Redbriar”,10
id:26 = “Greenlake”,10
id:27 = “Ascension Bay”,25
id:28 = “Dawn’s Eyrie”,10
id:29 = “The Spiritholme”,5
id:30 = “Woodhaven”,10
id:31 = “Askalion Hills”,25
id:32 = “Etheron Hills”,25
id:33 = “Dreaming Bay”,25
id:34 = “Victors’s Lodge”,5
id:35 = “Greenbriar”,10
id:36 = “Bluelake”,10
id:37 = “Garrison”,25
id:38 = “Longview”,10
id:39 = “The Godsword”,5
id:40 = “Cliffside”,10
id:41 = “Shadaran Hills”,25
id:42 = “Redlake”,10
id:43 = “Hero’s Lodge”,5
id:44 = “Dreadfall Bay”,25
id:45 = “Bluebriar”,10
id:46 = “Garrison”,25
id:47 = “Sunnyhill”,10
id:48 = “Faithleap”,5
id:49 = “Bluevale Refuge”,5
id:50 = “Bluewater Lowlands”,5
id:51 = “Astralholme”,5
id:52 = “Arah’s Hope”,5
id:53 = “Greenvale Refuge”,5
id:54 = “Foghaven”,5
id:55 = “Redwater Lowlands”,5
id:56 = “The Titanpaw”,5
id:57 = “Cragtop”,10
id:58 = “Godslore”,5
id:59 = “Redvale Refuge”,5
id:60 = “Stargrove”,5
id:61 = “Greenwater Lowlands”,5];
credits goes to http://mos.millenium.org
Cliff Spradlin.3512:
Yeah, Weris did all the hard work of mapping objective IDs to names. Thanks for that.
We want to fix the objective names, they are definitely really bad right now through the API. At least they’re localized, so you can read ‘Tower’ in any language
smiley.1438:
I’ve collected some data (thanks to millenium.org
) and threw it into a DB. However, spanish tanslation is still missing – anyone here to help out?
https://gist.github.com/codemasher/bac2b4f87e7af128087e
Debois Guilbert.6413:
Thanks all. This was a big help.
Emtiarbi.3281:
I created a json with this, hope this help
edit: changed – with _ :P
edit2: Changed, thanks Debois
[{"obj_id" : 1 , “obj_name” : “Overlook” ,“obj_value” : 25},
{"obj_id" : 2 , “obj_name” : “Valley” ,“obj_value” : 25},
{"obj_id" : 3 , “obj_name” : “Lowlands” ,“obj_value” : 25},
{"obj_id" : 4 , “obj_name” : “Golanta Clearing” ,“obj_value” : 5},
{"obj_id" : 5 , “obj_name” : “Pangloss Rise” ,“obj_value” : 5},
{"obj_id" : 6 , “obj_name” : “Speldan Clearcut” ,“obj_value” : 5},
{"obj_id" : 7 , “obj_name” : “Danelon Passage” ,“obj_value” : 5},
{"obj_id" : 8 , “obj_name” : “Umberglade Woods” ,“obj_value” : 5},
{"obj_id" : 9 , “obj_name” : “Stonemist Castle” ,“obj_value” : 35},
{"obj_id" : 10 , “obj_name” : “Rogue’s Quarry” ,“obj_value” : 5},
{"obj_id" : 11 , “obj_name” : “Aldon’s Ledge” ,“obj_value” : 10},
{"obj_id" : 12 , “obj_name” : “Wildcreek Run” ,“obj_value” : 10},
{"obj_id" : 13 , “obj_name” : “Jerrifer’s Slough” ,“obj_value” : 10},
{"obj_id" : 14 , “obj_name” : “Klovan Gully” ,“obj_value” : 10},
{"obj_id" : 15 , “obj_name” : “Langor Gulch” ,“obj_value” : 10},
{"obj_id" : 16 , “obj_name” : “Quentin Lake” ,“obj_value” : 10},
{"obj_id" : 17 , “obj_name” : “Mendon’s Gap” ,“obj_value” : 10},
{"obj_id" : 18 , “obj_name” : “Anzalias Pass” ,“obj_value” : 10},
{"obj_id" : 19 , “obj_name” : “Ogrewatch Cut” ,“obj_value” : 10},
{"obj_id" : 20 , “obj_name” : “Veloka Slope” ,“obj_value” : 10},
{"obj_id" : 21 , “obj_name” : “Durios Gulch” ,“obj_value” : 10},
{"obj_id" : 22 , “obj_name” : “Bravost Escarpment” ,“obj_value” : 10},
{"obj_id" : 23 , “obj_name” : “Garrison” ,“obj_value” : 25},
{"obj_id" : 24 , “obj_name” : “Champion’s demense” ,“obj_value” : 5},
{"obj_id" : 25 , “obj_name” : “Redbriar” ,“obj_value” : 10},
{"obj_id" : 26 , “obj_name” : “Greenlake” ,“obj_value” : 10},
{"obj_id" : 27 , “obj_name” : “Ascension Bay” ,“obj_value” : 25},
{"obj_id" : 28 , “obj_name” : “Dawn’s Eyrie” ,“obj_value” : 10},
{"obj_id" : 29 , “obj_name” : “The Spiritholme” ,“obj_value” : 5},
{"obj_id" : 30 , “obj_name” : “Woodhaven” ,“obj_value” : 10},
{"obj_id" : 31 , “obj_name” : “Askalion Hills” ,“obj_value” : 25},
{"obj_id" : 32 , “obj_name” : “Etheron Hills” ,“obj_value” : 25},
{"obj_id" : 33 , “obj_name” : “Dreaming Bay” ,“obj_value” : 25},
{"obj_id" : 34 , “obj_name” : “Victors’s Lodge” ,“obj_value” : 5},
{"obj_id" : 35 , “obj_name” : “Greenbriar” ,“obj_value” : 10},
{"obj_id" : 36 , “obj_name” : “Bluelake” ,“obj_value” : 10},
{"obj_id" : 37 , “obj_name” : “Garrison” ,“obj_value” : 25},
{"obj_id" : 38 , “obj_name” : “Longview” ,“obj_value” : 10},
{"obj_id" : 39 , “obj_name” : “The Godsword” ,“obj_value” : 5},
{"obj_id" : 40 , “obj_name” : “Cliffside” ,“obj_value” : 10},
{"obj_id" : 41 , “obj_name” : “Shadaran Hills” ,“obj_value” : 25},
{"obj_id" : 42 , “obj_name” : “Redlake” ,“obj_value” : 10},
{"obj_id" : 43 , “obj_name” : “Hero’s Lodge” ,“obj_value” : 5},
{"obj_id" : 44 , “obj_name” : “Dreadfall Bay” ,“obj_value” : 25},
{"obj_id" : 45 , “obj_name” : “Bluebriar” ,“obj_value” : 10},
{"obj_id" : 46 , “obj_name” : “Garrison” ,“obj_value” : 25},
{"obj_id" : 47 , “obj_name” : “Sunnyhill” ,“obj_value” : 10},
{"obj_id" : 48 , “obj_name” : “Faithleap” ,“obj_value” : 5},
{"obj_id" : 49 , “obj_name” : “Bluevale Refuge” ,“obj_value” : 5},
{"obj_id" : 50 , “obj_name” : “Bluewater Lowlands” ,“obj_value” : 5},
{"obj_id" : 51 , “obj_name” : “Astralholme” ,“obj_value” : 5},
{"obj_id" : 52 , “obj_name” : “Arah’s Hope” ,“obj_value” : 5},
{"obj_id" : 53 , “obj_name” : “Greenvale Refuge” ,“obj_value” : 5},
{"obj_id" : 54 , “obj_name” : “Foghaven” ,“obj_value” : 5},
{"obj_id" : 55 , “obj_name” : “Redwater Lowlands” ,“obj_value” : 5},
{"obj_id" : 56 , “obj_name” : “The Titanpaw” ,“obj_value” : 5},
{"obj_id" : 57 , “obj_name” : “Cragtop” ,“obj_value” : 10},
{"obj_id" : 58 , “obj_name” : “Godslore” ,“obj_value” : 5},
{"obj_id" : 59 , “obj_name” : “Redvale Refuge” ,“obj_value” : 5},
{"obj_id" : 60 , “obj_name” : “Stargrove” ,“obj_value” : 5},
{"obj_id" : 61 , “obj_name” : “Greenwater Lowlands” ,“obj_value” : 5}]
Debois Guilbert.6413:
Hey Emtiarbi, looks good but you should add an id field so your data can be used for lookups.
Rawrfaec.6412:
Here is a JS version of smiley’s DB, still missing Spanish translations. Some values (namely map names) are changed to be more in line with the official API.
smiley.1438:
I’ve added the spanish translations and a .json to my gist:
https://gist.github.com/codemasher/bac2b4f87e7af128087e
re the map names: i’ve kept them short since they’re for internal use only, you’ll need to add translation anyway if you want to use them out of the DB – i didn’t want to add 3 more columns for just 4 different words
zwei.9073:
I created a json with this, hope this help
Yes, it helps, thank you very much!
SpaceCowboy.1398:
Hi all,
I’ve created an Excel Spreadsheet that spits out each row of data as JSON objects. So, you can just cut’n’paste the JSON Output column into a text file.
I’ve kept the id and name fields, and added full_name, type, points, map_id, map, and location.
map_id
I don’t know the value for these, but I imagine we’ll know sometime in the future.
map
This is placeholder until I get values for the map_id. I’ve abbreviated the values to keep the file size light. E – Eternal Battlegrounds, R – Red Borderlands, G- Green Borderlands, and B – Blue Borderlands.
location
This is really for my purposes where I want to know the general location of something on the map (e.g. NW = North West). You may want to replace this with coordinates or add coordinates in another field.
Enjoy!
-Cowboy
https://dl.dropboxusercontent.com/u/3559414/objective_names.zip
Devata.6589:
Any news about the Api going to return the correct names? I was planning on mapping the names myself when I found this thread, so it’s nice not having to do that but it would still be better if the Api simply returns the correct information so that if names or ID’s change, or when new maps / locations / objectives get added everything keeps working instead of ending up with broken code because you mapped those names hard-coded.
smiley.1438:
Well, there’s that pull request: https://github.com/arenanet/api-cdi/pull/8
Lawton Campbell.8517:
Am working on /v2/wvw/objectives right now, though due to the release process the earliest it can be deployed is the patch after next.
Devata.6589:
Am working on /v2/wvw/objectives right now, though due to the release process the earliest it can be deployed is the patch after next.
That is great to hear :-)
Thanks.
Can you tell what the structure will be like? Same as V1 but with correct names? Then I can already make the code correct.
Nabrok.9023:
Am working on /v2/wvw/objectives right now, though due to the release process the earliest it can be deployed is the patch after next.
Will that include co-ordinates and a last flipped timestamp?
Lawton Campbell.8517:
Am working on /v2/wvw/objectives right now, though due to the release process the earliest it can be deployed is the patch after next.
Can you tell what the structure will be like? Same as V1 but with correct names? Then I can already made the code right.
I actually haven’t started working on the structure yet — I’m still adding the bits and bobbles to one of the backend servers that the API “frontend” will use to get data.
Will that include co-ordinates and a last flipped timestamp?
That’s the goal, at least.
UnknownFreak.2805:
Will that include co-ordinates and a last flipped timestamp?
That’s the goal, at least.
Does not the last flipped timestamp need to be in the matchup details, since every matchup will have it’s own timestamp when something is flipped?
Lawton Campbell.8517:
Will that include co-ordinates and a last flipped timestamp?
That’s the goal, at least.
Does not the last flipped timestamp need to be in the matchup details, since every matchup will have it’s own timestamp when something is flipped?
Yeah, sorry, the flipped timestamp is in the match details (i.e., /v2/wvw/matches), the objective coordinates are in the objective details (i.e., /v2/wvw/objectives).
Devata.6589:
[Suggestion]
It would be nice if match details would also give the account-name of the person who claimed an objective. (if that information is available).
From a guild-perspective that is a nice to know information because, for the world an objective got claimed by guild x, but for guild x it got claimed by member y.
Lawton Campbell.8517:
[Suggestion]
It would be nice if match details would also give the account-name of the person who claimed an objective. (if that information is available).
AFAIK that’s not tracked by the map servers — so getting it routed through to the API is a pretty big task. We can look into it in the future, but it’s definitely not going to be available for the initial release of /v2/wvw/objectives.
Reincarnated.1754:
It would be nice if Sentry posts and Mercenary camps could be added to the Objectives
Oh, and if you want to go all the way, a contested time-stamp.
Devata.6589:
When we talk about additional information that would be nice to see,
How about ‘Same model as’, ‘The Titanpaw’ is the same as ‘The Godsword’ is the same as ‘The Spiritholme’.
And upgrades including build-time, available supply.
Personally I would only use “Same model as”, but it’s all useful information for many applications.