Pipfrosch Press

Rana kauffeldi Range Map

Hi, I’m Android. My pRNG is randomly random

Rana Kauffeldi Range Map

This figure is released under the Creative Commons Attribution-ShareAlike 4.0 International license (a variant of copyleft).

This is a vector version of Feinberg, Newman, et. al. (2014) pg. 4 Figure 1. Rasterized PNG versions of the vector image are also available.

This is not a simple trace. It is a manually created labor of love that took me about two weeks to tediously create using a text editor, a calculator, and a web browser. Even though I can grok the SVG specification, I can not figure out how to use the Inkscape GUI and I can not afford Illustrator, so creating the vector paths manually with a text editor was the only option I had.

Under the afore mentioned Creative Commons license, you are free to use this figure without payment as long as you adhere to the license. However your generosity in payment, if you can afford to do so, would be greatly appreciated. If you use this figure, you can send a payment (whatever you desire) to paypal.me/pipfrosch. Thank you.

This figure is provided in SVG, PDF, and EPS versions as well as rasterized PNG in various sizes. Before using the PDF or EPS versions, please see the note on PDF and EPS images towards the bottom of this page.

Attribution Versions

Two versions of attribution are available in the figure itself. The first fully complies with the CC BY-SA 4.0 license, the second mostly does but lacks a reference to the license URL, something I personally do not care about being omitted but it is part of the license. If using the second, you probably should in good faith provide a link to the CC BY-SA 4.0 license in the document that uses it, just to make sure lawyers are happy. They can get quite grumpy when simple measures to ensure compliance are not taken. Both images below are hyperlinks that will open the image to the full size of your browser window.

[Rana kauffeldi map]
Version with Full CC BY-SA 4.0 compliance
[Rana kauffeldi map]
Version with Partial CC BY-SA 4.0 compliance

Differences from Original

There are some minor differences between my version of the figure and the version that appears in Feinberg, Newman, et. al. (2014) but these differences are not substantial and should not change the interpretation of the range map. The most notable differences are listed below.

My Map Original Map Description
[Tip of Penninsula Mine] [Tip of Penninsula Original] At the top of the Delmarva Penninsula, I have a difference in how the thick lines come together. This was done to avoid lines passing through the Chesapeake Bay.
[Tip of Penninsula Mine] [Tip of Penninsula Original] The blocky range of Rana pipiens in Connecticut was smoothed out. Some (but not all) other blocky ranges were smoothed out too, but that is the biggest smoothing I did.

Additionally, the original map has an arrow pointing to the type locality on Staten Island, but without text indicating what the arrow means. The article itself indicates what the arrow means. In my use case for the map, noting the type locality was not as important as it obviously is in the original species description, so I simply placed a bright yellow border around the the type locality star.

Download Options

Figure with Full License Complying Box:

SVG
AtlanticCoastFullLicenseBox.svg
PDF
AtlanticCoastFullLicenseBox.pdf
EPS
AtlanticCoastFullLicenseBox.eps
PNG 2000x1054
AtlanticCoastFullLicenseBox2000x1054.png
PNG 1536x809
AtlanticCoastFullLicenseBox1536x809.png

Figure with Partial License Complying Text:

SVG
AtlanticCoastAltLicenseText.svg
PDF
AtlanticCoastAltLicenseText.pdf
EPS
AtlanticCoastAltLicenseText.eps
PNG 2000x1054
AtlanticCoastAltLicenseText2000x1054.png
PNG 1536x809
AtlanticCoastAltLicenseText1536x809.png
PNG 1024x540
AtlanticCoastAltLicenseText1024x540.png

The next groups are intended for typesetting purposes, for those who do not wish to have the license text embedded in the image for aesthetic reasons but instead wish to comply with the license by giving the attribution elsewhere in their typeset document. Only PDF and EPS versions are provided.

Figure without license box but with legend text:

PDF
AtlanticCoastNoLicenseBox.pdf
EPS
AtlanticCoastNoLicenseBox.eps

Figure without any text:

PDF
AtlanticCoastNoText.pdf
EPS
AtlanticCoastNoText.eps

PDF and EPS Image Notes

These vector versions are intended for use with typesetting software, such as LaTeX.

It is not too uncommon when using such software to desire versions of the figure that completely lack text, allowing the typographer to use the typesetting software to programmatically place the text on top of the image so that the fonts in the figure match the fonts in the rest of the document. That is my personally preferred method, it results in better font consistency. Other authors prefer not to. As such, versions of the PDF and EPS files with and without text are provided so you can choose which you prefer. It is still your responsibility to comply with the license, so attribution needs to be given in your document when you use a version of the figure that lack license information in the figure image.

As far as I am concerned, a reference in the bibliography is fine as long as the page that contains the figure notes the page in the bibliography that has the proper attribution.

Attribution needs to include a reference to the Feinberg, Newman, et. al. (2014) paper since this vector figure is based upon a bitmap figure in that paper, which also has a Creative Commons attribution license. Attribution also lets the reader find the context that goes with the range map.

The PDF and EPS files are generated from SVG using inkscape from the command line.

Important Pattern Fill Note

SVG has a concept called pattern fill. A repeating pattern node is defined and then used instead of a color to fill a path or shape element.

While the inkscape export does translate this to the EPS and PDF images, not all viewers properly display the pattern fill. For the PDF version of the figure here I did verify that current versions of FireFox, Chromium (and thus I assume Chrome), and Adobe Acrobat Reader do properly render the pattern fill, but some viewers (e.g. Evince) are buggy with pattern fill and do not always render it properly. Evince for example does seem to render it correctly when used within a rect node but does not always when a pattern is used as fill for a path node, it seems to depend upon the pattern itself.

With EPS I have questions, I do not know for sure that the pattern fills work with EPS. I suspect they do and I know they do at least partially, but they do not completely work in the EPS viewers I have. However, the PDF images also do not completely work in those EPS viewers but do work in Chromium and Acrobat Reader, so I already know there is a rendering bug in those viewers.

When I use either ghostscript to turn the EPS into a PDF or use LaTeX to embed the EPS into a PDF document, the pattern fills do not completely work, even when the resulting PDF is viewed with FireFox, Chromium, or Acrobat Reader. So it is possible the EPS itself is incorrect. However it is also possible that the rendering engine used to convert the EPS to PDF (ghostscript) is buggy, I just do not know which.

The safest thing to do is to use the PDF image and in the case of LaTeX, one of the engines that directly outputs PDF (like pdflatex). That works with non-buggy viewers.

If you can not use PDF images, then use the EPS and hope for the best. It is only an issue with the 'Zone of Potential Extirpation' pattern fill, the pattern fill seems to works in EPS with the 'Overlap' pattern fill. The way that 'Zone of Potential Extirpation' fails for me when using EPS, the zone is still visually distinguished, just not with a pattern fill that matches the legend where the pattern fill works because it is created with a rect opposed to a path node in the SVG.

My suspicion is the bug is in ghostscript, as all the problems seem to be with software that uses ghostscript. That would mean Inkscape is probably doing the right thing and the EPS file is correct. However since typesetting software often uses ghostscript, it is safer to use the PDF version of the figure if you can.

If you use LaTeX and you have other figures that make use of PSTricks, those figures will not work with an engine that outputs directly to PDF. However what I do in those cases, I create a dummy document and use the TeXtoEPS environment to generate an EPS image of those figures that use PSTricks, which I then can use in pdflatex with the epstopdf package declared in my preamble. It's hackish but it works. Most LaTeX documents do not use PSTricks and can just use a LaTeX engine that outputs PDF without needing to worry about that.

PNG Image Notes

Initial conversion from SVG to PNG was performed using inkscape from the command line. The result was then modified with the ImageMagick convert command to give a white background color opposed to transparent. Given the lossless natue of PNG and that no resizing was taking place, that second processing should have had no impact on the quality of the image.

PNG is a rasterized bitmap format. It does not scale as well as vector formats like SVG. The PNG images here are intended for web use. Every modern mainstream browser currently supports SVG however many social media sites do not support the upload the SVG images.

While it is of course possible to use PNG images in typeset documents, I do not recommend it. The biggest issue is that these PNG images contain text and text does not scale very well in either direction. With the vector versions, the fonts for the text can scale with changes in the rendered size of the image, remaining sharp.