Yes, you are correct, the URL need a little massage that I think is as follows.
If the GEDCOM contains:
3 FILE https://trees.ancestry.com/rd?f=image&g ... 7378&pid=1
Then the image exists at:
https://www.ancestry.com/family-tree/tr ... a71d73a233
where in this example the tree id is 15707378 and the image id is c4a31e4e-069f-431d-a08a-5fa71d73a233
* New tool for generating navigable trees
- tatewise
- Megastar
- Posts: 28410
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: New tool for generating navigable trees
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: New tool for generating navigable trees
Mike, try https://mediasvc.ancestry.com/v2/image/ ... Quality=hq and see the difference.tatewise wrote:Yes, you are correct, the URL need a little massage that I think is as follows.
If the GEDCOM contains:
3 FILE https://trees.ancestry.com/rd?f=image&g ... 7378&pid=1
Then the image exists at:
https://www.ancestry.com/family-tree/tr ... a71d73a233
where in this example the tree id is 15707378 and the image id is c4a31e4e-069f-431d-a08a-5fa71d73a233
I need the image URL rather than a page that simply hosts the image.
- tatewise
- Megastar
- Posts: 28410
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: New tool for generating navigable trees
Yes, sorry, I confused myself, so the Ancestry URL needs resolving differently.
Taking my earlier example the image is at:
https://mediasvc.ancestry.com/v2/image/ ... nt=TreesUI
You do not need to be signed-in to Ancestry for that to work, as I've made it a Public tree, and the tree id is not needed.
Only the image id c4a31e4e-069f-431d-a08a-5fa71d73a233 needs to be extracted from the GEDCOM FILE URL.
The image id does not need a file-type suffix such as .jpg and in fact is ignored whatever is used.
The parameters can be ?client=TreesUI&imageQuality=hq or just ?client=Trees etc.
However, I suspect this only works for images uploaded to Ancestry by the user and not those obtained from Ancestry records.
( BTW: I have edited some of my earlier entries as the hyphens in some image id got omitted by accident. )
Taking my earlier example the image is at:
https://mediasvc.ancestry.com/v2/image/ ... nt=TreesUI
You do not need to be signed-in to Ancestry for that to work, as I've made it a Public tree, and the tree id is not needed.
Only the image id c4a31e4e-069f-431d-a08a-5fa71d73a233 needs to be extracted from the GEDCOM FILE URL.
The image id does not need a file-type suffix such as .jpg and in fact is ignored whatever is used.
The parameters can be ?client=TreesUI&imageQuality=hq or just ?client=Trees etc.
However, I suspect this only works for images uploaded to Ancestry by the user and not those obtained from Ancestry records.
( BTW: I have edited some of my earlier entries as the hyphens in some image id got omitted by accident. )
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry