• Content Count

  • Joined

  • Last visited

Everything posted by DocSnyder

  1. In API, when I call the GetColors method, can you please add the ColorID for bricklink? I'm writing on a software that creates wish lists, but recalculation colors would be much easier when I get a mapping table from rebrickable API. Thanks in advance, Michael
  2. sorry for the late feedback: thanks for the fix!
  3. Hello, I'm working with LXF files and wondering: When I create a part with translight blue, it's material ID is 42. Thats LDRAW color 43. When I try to get all elements, for example, part ID=4073 (round plate 1x1), I only get an element for the light blue (which color ID is 41, element ID is 4163917. I'm not able to relate the parsed part from LXF to an element of this part in rebrickable API. Is this a bug? where is the difference between very light and light trans blue? thanks for any help, Michael EDIT: found out that LXF file stores the color with 42, but LEGO color for trans light blue is 143 according to the maping table...strange.
  4. Some more: - search for 32123: use 32123b instead (displayed on webpage for this part ID), but no elements are related, but only for 32123a - Part ID 60475 (1x1 brick with vertical clip): why is this related to a rebrickable ID 2996c01, that is unknown (but 2996 is a wheel??)
  5. Hello, Part 3062, which ID is used by LDD for 1x1 round brick, is not available, but is missing a rebrickable ID that leads to 3062b. In this case, my call returns an invalid part. Can this be fixed?
  6. Hello, I just have some performance issues in my WPF/C# Application when I start an API search to find parts by name. The connection string is like this: "search?key=12345678&type=P&query=head&format=xml" In browser, on your API test page, it takes about 1,5 seconds, my application takes about 7 seconds for the same query Code is: rebrickableClient = new HttpClient(); rebrickableClient.BaseAddress = new Uri(""); var test = rebrickableClient.GetAsync("search?key=" + rebrickableApiKey + "&type=P&query=" + searchPattern + "&format=xml"); HttpContent content = test.Result.Content; Anyone has an idea why I have this delay? Cheers, Michael
  7. I miss a color when I call get_colors: LDRAW ID = 38 (LEGOID 47), name : Trans_Neon_Orange (see
  8. for example, cheese slope 50746 or 1x1 round tile 6141 and round brick 6141 does not have a <name> node containing the part's name in the result. EDIT: same for 3062 Some name I can get using the rebrickble ID and call again get_part with this id. In case of 3062 is does not work, there is no rebrickable ID thats different from part ID: <?xml version="1.0"?> <root><part_id>3062</part_id><colors/><external_part_ids><lego_element_ids/></external_part_ids><related_parts/></root> remarkable thing: part ID 3062b returns the right part, 3062 seems to be no existing, neither @rebrickable database nor brinklink. But you have a valid image link to the white element: And LDD is also storing part ID 3062 in the LXF file. Should there be at least a part with ID 3062 and a rebrickable ID 3062b in your database to reach the correct item?
  9. awww..okay, I'll box some LEGO friends stuff together with some fabuland figs
  10. ha, you're right..but how can I see the actual element ID, and what means TLC discarding old ones and introduce new ones periodically?
  11. For Part 2431, 1x4 Tile, an element exists in Dark Green, Element ID = 4543949, but the URL does not return an element image. Same for Part 3004, 1x2 Brick, Element ID for white is 4613964.
  12. mistake...I wanted to check if a LDD part/color combination is a real/valid, but haven't checked if the colorID was existing in the color node collection, but only checked the lego element list...big facepalm...
  13. Part 30044 has no reference to element with color ID = 0 (black). I got this part in this color, see also Unfortunately I can't find an element ID anywhere, BL does not list it, the black one can only be found in 1 (and 1 rebootet) set:
  14. same for part no 3814 (see
  15. LDD is using (and storing in LXF file) part no. 94148 for a 2x2 plate. The get_part for this ID will return NO_PART, BrickOwl says this part no. belongs to part 3022 (see Thanks for correction. Michael
  16. Thank you....I will consider your proposal and create a new issue thread in the future. You should definitely use a free bug tracker system like
  17. Hey Nathan, thanks for the change. I've found another glitch: I've got some trouble with the new format: <?xml version="1.0"?> <root><part_id>3049</part_id><name>Slope 45° 2 x 1 [undetermined Underside]</name><year1>0</year1><year2>0</year2><category>Bricks Sloped</category><rebrickable_part_ids><0>3049b</0></rebrickable_part_ids><colors/><rebrickable_part_id>3049b</rebrickable_part_id></root> Visual C# tells me the following error when I try to load an XML file from the string: An exception of type 'System.Xml.XmlException' occurred in System.Xml.dll but was not handled in user code Additional information: Name cannot begin with the '0' character, hexadecimal value 0x30. Line 2, position 183. I don't know if XML allows node names starting with "0", hence this would be a strange restriction, could you please check this out? Thanks. EDIT: check out this please
  18. Now I'm totally out what is this "do not use this part" message?
  19. Arf...that means, the part ID I use to get a part is the bricklink ID? Strange BTW, is there some documentation about the relations of all the parts, molds, stickered stuff etc? It's very complicated to build a local database and manage all the exceptions. For example, I get a response for a part ID that only contains a rebrickable ID, no colors etc. I then use the rebrickable ID to get more information about that part sending a new request. But it's hard to relate all this together.
  20. I don't know exactly of this is a bug, but using API's get_part ledas to : 71075 has a rebrickable ID of 71076 and 71076 has a rebrickable ID of 71075 both parts are different (straight and bowed). I try t get information by navigation over rebrickable ID, but end up in a loop. Cheers, Michael
  21. Yes, I will try to get the appropriate ones, hence it will take more time But I'm afraid that I don't have every element, so you only get a few element fixes
  22. Hehe, I just wondered during my search why I have more parts in the result list since some minutes thanks for the change, the doc correction and the hint with the get_part_types function. you guys are really fast, I appreciate this quick support (You will get a free copy of my application ) I only have to find out, how are the lots of relations between parts, molds, stickered and printed working. I also found many part/color combinations without valid elements. I will give you a complete overview of those after my completion of adding all owned parts to my repository.
  23. In your API documentation: key - API Key format - How to display output data. Valid values: xml, json, csv, tsv callback - Optional JSONP callback function name type - Filter on one specific type of change (i.e. S, P, SI, etc), or leave blank for all. query - General search query. Search terms are additive. theme1 - Set Filter: Theme Level 1 theme2 - Set Filter: Theme Level 2 theme3 - Set Filter: Theme Level 3 min_pieces - Set Filter: List sets with >= this number of parts. max_pieces - Set Filter: List sets with <= this number of parts. min_year - Set Filter: List sets released >= this year. max_year - Set Filter: List sets released <= this year. part_type_id - Part Filter: Only list parts with this type/category ID. part_color - Part Filter: Only list parts that appear in this color. type=P works like a charm, this fulfills my need to add parts to my database but I've found one thing until now: when I search for "Slope 45", among the result is the 3040a (Slope 1x2 without bottom tube) but I don't get the 3040b (the one with bottom tube) EDIT: now I see, the results are limited by a maximum of 100, I have to set a more detailed search pattern, but changing the ganularity for the "Slope 45" to "Slope 45 Bottom" doesn't get the 3040b. Hence, you could add a page parameter, to return 1-100 (page=1), 101-200 (page=2) etc.