PlanetCatfish.com

Okay, I've culled through all families and edited all type localities which appeared on incorrect continents or clearly in mis-mapped open waters.

I must have done too much, because by the time I finished, Google Maps was refusing to map the coordinates of families for me without displaying that shadow overlay with the warning that it couldn't map stuff "This page can't load Google Maps correctly." I think I broke Google Maps.

Below is a semi complete list of the species I fixed and the errors I found. The list is semicomplete because in the beginning, I wasn't recording the problem found.

Cheers, Eric

Harttia depressa
Harttia uatumensis
Harttia trombetensis
Rineloricaria langei
Pareiorhina carrancas
Neoplecostomus pirangaensis
Panaqolus changae
Farlowella azpelicuetae
Olyra astrifera
Hypostomus hemicochliodon
Curculionichthys oliveirai
Parotocinclus jacumirim
Ancistrus cryptophthalmus
Sturisoma monopelte (the second value in a range of lats was treated as long)
Parotocinclus bahaiensis
Otothyropsis polyodon
Neoplecostomus watersi
Tetracamphilius pectinatus Written as 45° 06.5'S, 13° 48'E; Should be 04° 56.5'S, 13° 48'E
Brachyrhamdia thayeri
Pimelodella leptosoma (the second value in a range of lats was treated as long)
Phenacorhamdia unifasciata (S, not N)
Ammoglanis amapaensis W not E in type locality -54.587778
Ituglanis australis (error in type locality using " instead of ' for minutes of longitude)
Ituglanis bambui (error in longitude in type locality 446°23'W should be 46°23'W
Henonemus taxistigmus (the second value in a range of lats was treated as long)
Trichomycterus caipora (' symbol for ")
Trichomycterus itacambirussu (lat long simply listed in reverse order, but typed correctly)
Trichomycterus jequitinhonhae (lat long simply listed in reverse order, but typed correctly)
Trichomycterus landinga (lat long simply listed in reverse order, but typed correctly)
Trichomycterus maracaya (latitude and longitude reversed)
Trichomycterus pantherinus (symbol for seconds of Long mistyped as minutes symbol)
Trichomycterus payaya (latitude and longitude reversed)
Trichomycterus pirabitira error in original description, reporting long seconds as 95. perhaps 9.5"?
Astroblepus pholeter: ambiguity of latitude created by range of values, but data inconsistent with claim of 4 km north of Archidona
Pseudeutropius indigens: Latitude minutes typed with degree symbol, longitude plotted as 11 deg rather than 102degr

That's great, thanks a bunch! I am working through them now. This brings us on to problem 2: when a type locality is correct, why is in not being parsed/converted into the correct decimal lat/long numbers. However, this is not in the numbers I expected, seems there are a significant number of errors in the source data.

One reason might be that there are no seconds in the original text .e.g at 16°45'S, 42°18'W.

Jools

There was some kind of flaw in everything I checked. For some, the lat and long were correct but the authors reported them in the wrong order.

E.g, instead of 16°45'S, 42°18'W, their description was wrtten as 42°18'W, 16°45'S, and the parser can't handle that. It assumes the first number is lat no matter if E or W is included, and the parser defaults to positive numbers if the proper N/S or E/W letter is not found.

Cheers, Eric

Agreed, so I can address that. However, for example, has 12°34’59.3”S 38°18’59.6”W and it didn't handle that. Might be the ’ instead of a single quote ('). This could be because they used an Apple computer to first create the text.

Jools

Here is what the Type Locality updater does. The issue here is I suspect it has "unfixed" some of the work because the source data wasn't right or was not interpreted correctly. I need to fix this otherwise a lot of the hard work you are putting in will go to waste. I will, however, either re-apply it or ensure a fix somehow. Where the undernoted says "Update!" is where the software has identified a "fix" for the species above - so I will highlight/annotate them in order to understand what has occurred.

Jools

Henonemus taxistigmus, type locality=Rupununi River, Guyana, 2°-3°N, 50°20'W.
Lat=2, long=-3
ROW Lat=2, long=-50.333333

** Update! **
** Broken! **
Neosilurus pseudospinosus, type locality=Rocky pool of Ord River on Old Lissadel Station, Kimberley District, Western Australia, about 16°40'S, 128°83'E.
ROW Lat=0, long=0 - please review.
** Broken! **
Platydoras armatulus, type locality=Río Paraná, but not below 27°30'S, South America.
ROW Lat=0, long=0 - please review.
Ancistrus cryptophthalmus, type locality=Caverna Passa Três, about 300 meters into the cave, 13°20' to 13°52'S, 46°16' to 46°30'W, Rio São Vicente system, São Domingos, Goiás State, Brazil.
Lat=13.333333333333, long=13.866666666667
ROW Lat=-13.33333333, long=-46.266667

** Update! **
Hypostomus hemicochliodon, type locality=4.54 kilometers from Iquitos center, 3°45'07"S, 73°16'59"W. Río Amazonas drainage at Pampa Chica, Río Nanay, Peru.
Lat=-3.7519444444444, long=-73.283055555556
ROW Lat=-3.7519444444444, long=-73.28305556

** Update! **
Trichomycterus maracaya, type locality=Unnamed streamlet at the foothill of the Morro de Ferro, about 21°46'45"S, 46°31'50"W, rio Pardo basin, Poços de Caldas, Minas Gerais State, Brazil.
Lat=-21.779166666667, long=-46.530555555556
ROW Lat=-21.779167, long=-46.530556

** Update! **
Pseudeutropius indigens, type locality=Toh Daeng peat swamp, Khlong Pak Pla, 6°11'11"N, 102°01'32"E, Narathiwat Province, Thailand.
Lat=6.1863888888889, long=102.02555555556
ROW Lat=6.1833333333333, long=102.025556

** Update! **
** Broken! **
Corydoras(ln9) paragua, type locality=Río Paragua, northwestern bank, river mouth area, río Itenez system, Provincia J.M. Velasco, Departamento Santa Cruz, Bolivia, 13°31.842'S, 61°90.015'W.
ROW Lat=-13.53, long=-62.5 - please review.
Sturisoma monopelte, type locality=Rupununi River, Guyana, 2°-3°N, 50°20'W.
Lat=2, long=-3
ROW Lat=2, long=-50.333333

** Update! **
Brachyrhamdia thayeria, type locality=Amazonas, Maraã, Lago Amanã, Rio Japurá basin, 2°32’06"S, 65°43’02"W, Brazil, elevation 44 meters.
Lat=-2.535, long=-65.717222222222
ROW Lat=-2.535, long=-65.71722222

** Update! **
Leptodoras marki, type locality=Rio Trairão, Fresco-Xingú basin, tributary of Rio de Ponte, 15 kilometers south of Cumaru do Norte, 7°56'34"S, 50°47'48"W, Cumaru do Norte, Pará, Brazil.
Lat=-7.9427777777778, long=-50.796666666667
ROW Lat=-7.9427777777778, long=-50.796667

** Update! **
** Broken! **
Micropanchax ehrichi, type locality=Mali, southwest of Bamako near Samalofila [Samalofira], 12°15'N, 8°72'W [coordinates corrected].
ROW Lat=0, long=0 - please review.
** Broken! **
Farlowella smithi, type locality=Rio Madeira, about 200 miles east of 62°20'W, Amazonas State, Brazil.
ROW Lat=0, long=0 - please review.
Tetracamphilius pectinatus, type locality=Congo basin, tributary of River Luala 26 kilometers north of Kibunzi, 8 kilometers south of turnoff to Kibunzi, Luozi District, 45°06.5'S, 13°48'E, Republic of Congo.
Lat=-45.108333333333, long=13.8
ROW Lat=-4.941667, long=13.8

** Update! **
Otothyropsis polyodon, type locality=Água Clara, ribeirão Tamanduá, tributary to rio Verde, near São Domingos Hydroeletric Plant, upper rio Paraná basin, 20°04'03"N, 53°11'21"W, Mato Grosso dul Sul, Brazil.
Lat=20.0675, long=-53.189166666667
ROW Lat=-20.0675, long=-53.189167

** Update! **
** Broken! **
Hyphessobrycon agulha, type locality=Madeira River, about 200 miles east of 62°20'W, Brazil.
ROW Lat=0, long=0 - please review.
** Broken! **
Hyphessobrycon langeanii, type locality=Kilometer 476.3 of Ferronorte railroad, 17°25'08"S, 53°13'60"W, córrego Mosquito, município de Alto Araguaia, Mato Grosso, Brazil.
ROW Lat=-17.418888888889, long=-53.233333333333 - please review.
** Broken! **
Nannostomus digrammus, type locality=Rio Madeira about 200 miles east of 62°20'W, Brazil.
ROW Lat=0, long=0 - please review.
Parotocinclus bahiensis, type locality=Rio Itapicuru, on Federal highway BR 407, 8 kilometers north of Senhor do Bonfim to Juazeiro, Bahia State, Brazil, 40°11'01"W, 10°24'49"S.
Lat=40.183611111111, long=10.413611111111
ROW Lat=-10.413611, long=-40.183611

** Update! **
** Broken! **
Fundulopanchax amieti, type locality=Rainforest creek on the road from Koupongo, 500 meters west of Somakak, Sanaga system, southwestern Cameroon, 3°58'N, 10°89'E.
ROW Lat=0, long=0 - please review.
** Broken! **
Trichomycterus aguarague, type locality=Provice Gran Chaco, National Park Aguarague, Quebrada Timboycito, a Río Caiguami tributary, Tarija, Bolivia, 21°30'S, 63°60'W, elevation 700-800 meters.
ROW Lat=0, long=0 - please review.
** Broken! **
Ancistrus tolima, type locality=Quebrada El Pascado, 3.599306°N, -74.854556°W, vereda San Pablo, municipio de Dolores, departamento de Tolima, Colombia.
ROW Lat=0, long=0 - please review.
** Broken! **
Glyptothorax kurdistanicus, type locality=Serdesht, at Little Zab (36°N), River Bané basin, Iran, elevation 1500 meters.
ROW Lat=0, long=0 - please review.
Parotocinclus jacumirim, type locality=Brazil, Bahia State, Dias d’Ávila, rio Jacumirim, tributary of rio Jacuípe, on road BA-093 between municipalities of Dias d’Ávila and Mata de São João, 12°34’59.3”S 38°18’59.6”W.
Lat=12.566666666667, long=38.3
ROW Lat=-12.583139, long=-38.316556

** Update! **
Astroblepus pholeter, type locality=Jumandi cave in Latas, 4 kilometers north of Archidona, Napo Province, eastern Ecuador, 0°20'S to 0°40'S, 77°50"W.
Lat=-0.33333333333333, long=0.66666666666667
ROW Lat=-0.666667, long=-77.833333

** Update! **
** Broken! **
Amphilius ruziziensis, type locality=Lufiro River, upper reaches of Matchuza, Ruzizi River drainage, ca. 2°44'00"S, 29°02'99"E, Rwanda.
ROW Lat=0, long=0 - please review.
** Broken! **
Chaetostoma trimaculineum, type locality=Santiago River drainage, Morona-Santiago Province, confluence of the Changachangasa and Tutanangosa rivers and upstream in both, 02°35'51.18''S, 78°11'1038''W.
ROW Lat=-2.59755, long=-78.186216666667 - please review.
Trichomycterus caipora, type locality=Município de Conceição de Macabu, lagoa Feia drainagem rio Macabu basin, rio Macabu upstream if the confluence of rio Carocango and rio Macabu, 22°04'51.8"S, 41°58'55.3"W, Estado de Rio de Janeiro, Brazil.
Lat=-22.081055555556, long=-41.982027777778
ROW Lat=-22.081055555556, long=-41.982028

** Update! **
Trichomycterus jequitinhonhae, type locality=Córrego Laranjeiras, 16°45'S, 42°18'W, Rio Jequitinhonha basin, County of Coronel Murta, Minas Gerais State, Brazil.
Lat=-16.75, long=-42.3
ROW Lat=-16.55, long=-42.75

** Update! **
Trichomycterus landinga, type locality=Córrego Moquém, 16°45'S, 42°35'W, Rio Jequitinhonha basin, County of Coronel Murta, Minas Gerais State, Brazil.
Lat=-16.75, long=-42.583333333333
ROW Lat=-16.75, long=-42.583333

** Update! **
Trichomycterus pantherinus, type locality=Below waterfall near Fazenda Sete Quedas, Rio da Prata, Rio Santa Maria da Victória basin, 20°03'15.9''S, 40°32'20.5''W, Município Santa Leopoldina, Estado de Espírito Santo, Brazil, elevation 377 meters.
Lat=-20.054416666667, long=-40.539027777778
ROW Lat=-20.054416666667, long=-40.539028

** Update! **
Trichomycterus payaya, type locality=Riacho Olhos d'água on road BA-131, tributary to rio Itapicuru-mirim, rio Itapicuru drainage, between Miguel Calmon and Jacobina, 11°20'19.5''S, 40°36'21.9''W, Miguel Calmon, Bahia, Brazil, elevation 505 meters.
Lat=-11.33875, long=-40.606083333333
ROW Lat=-11.33875, long=-40.606083

** Update! **
** Broken! **
Trichomycterus pirabitira, type locality=Small stream between Carmo do rio Claro and Conceição da Aparecida, tributary of rio Grande, rio Paraná basin, ca. 21°8'53"S, 46°14'95"W, Estado de Minas Gerais: Município de Conceição da Aparecida, Brazil, elevation ca. 960 meters.
ROW Lat=-21.148056, long=-46.235972 - please review.
Pimelodella leptosoma, type locality=Rupununi River, Guyana, 2°-3°N, 50°20'W.
Lat=2, long=-3
ROW Lat=2, long=-50.33333

** Update! **
** Broken! **
Chiloglanis kabaensis, type locality=Mongo River, east of Marela, on N2, Kaba River (Little Scarcies) drainage, Guinea, 10.17023°N, 11.
ROW Lat=0, long=0 - please review.
Phenacorhamdia unifasciata, type locality=Ribeirão Santana, tributary of River São Bartolomeu, 15°50'S, 47°40'W, District Federal, Brazil.
Lat=-15.833333333333, long=-47.666666666667
ROW Lat=-15.833333, long=-47.666666666667

** Update! **
Curculionichthys oliveirai, type locality=Paraná State, boundry between municipalities of Cambira and Apucarana, ribeirão Cambira, affluent of rio Ivaí, upper rio Pananá basin, 23°38'54"S, 51°29'58"W, Brazil.
Lat=-23.648333333333, long=-51.499444444444
ROW Lat=-23.648333333333, long=-51.499444

** Update! **
Neoplecostomus watersi, type locality=Córrego da Cachoeira, Rio Correntes drainage, upper Rio Paraná basin, municipality of Aporé, Goiás state, Brazil, 18°34'50.8"S, 52°05'52.8"W.
Lat=-18.580777777778, long=-52.098
ROW Lat=-18.580778, long=-52.098

** Update! **
** Broken! **
Pseudomystus sobrinus, type locality=Stream about 15 kilometers south of Tuy Hoa, 12°53'05"N, 109°23'70"E, Phu Yen Province, Vietnam.
ROW Lat=0, long=0 - please review.

** Summary **
Total: 1739
Updates: 0
Strange: 22
Lost: 0
Broken: 17

I have amended the Type Locality updater to provide more user-friendly output, hence it now provides the undernoted. I propose we work this through and then I go back and re-apply the fixes.

1). ** Stored Lat/Long doesn't match type locality **
, type locality=Rocky pool of Ord River on Old Lissadel Station, Kimberley District, Western Australia, about 16°40'S, 128°83'E.
Parsed Lat=-16.666666666667, long=
Stored Lat=0, long=0

2). ** Stored Lat/Long doesn't match type locality **
, type locality=Río Paraná, but not below 27°30'S, South America.
Parsed Lat=-27.5, long=
Stored Lat=0, long=0

3). ** Stored Lat/Long doesn't match type locality **
, type locality=Río Paragua, northwestern bank, river mouth area, río Itenez system, Provincia J.M. Velasco, Departamento Santa Cruz, Bolivia, 13°31.842'S, 61°90.015'W.
Parsed Lat=-13.5307, long=
Stored Lat=-13.53, long=-62.5

4). ** Stored Lat/Long doesn't match type locality **
, type locality=Mali, southwest of Bamako near Samalofila [Samalofira], 12°15'N, 8°72'W [coordinates corrected].
Parsed Lat=12.25, long=
Stored Lat=0, long=0

5). ** Stored Lat/Long doesn't match type locality **
, type locality=Rio Madeira, about 200 miles east of 62°20'W, Amazonas State, Brazil.
Parsed Lat=62.333333333333, long=
Stored Lat=0, long=0

6). ** Stored Lat/Long doesn't match type locality **
, type locality=Madeira River, about 200 miles east of 62°20'W, Brazil.
Parsed Lat=62.333333333333, long=
Stored Lat=0, long=0

7). ** Stored Lat/Long doesn't match type locality **
, type locality=Kilometer 476.3 of Ferronorte railroad, 17°25'08"S, 53°13'60"W, córrego Mosquito, município de Alto Araguaia, Mato Grosso, Brazil.
Parsed Lat=-17.418888888889, long=
Stored Lat=-17.418888888889, long=-53.233333333333

. ** Stored Lat/Long doesn't match type locality **
, type locality=Rio Madeira about 200 miles east of 62°20'W, Brazil.
Parsed Lat=62.333333333333, long=
Stored Lat=0, long=0

9). ** Stored Lat/Long doesn't match type locality **
, type locality=Rainforest creek on the road from Koupongo, 500 meters west of Somakak, Sanaga system, southwestern Cameroon, 3°58'N, 10°89'E.
Parsed Lat=3.9666666666667, long=
Stored Lat=0, long=0

10). ** Stored Lat/Long doesn't match type locality **
, type locality=Provice Gran Chaco, National Park Aguarague, Quebrada Timboycito, a Río Caiguami tributary, Tarija, Bolivia, 21°30'S, 63°60'W, elevation 700-800 meters.
Parsed Lat=-21.5, long=
Stored Lat=0, long=0

11). ** Stored Lat/Long doesn't match type locality **
, type locality=Quebrada El Pascado, 3.599306°N, -74.854556°W, vereda San Pablo, municipio de Dolores, departamento de Tolima, Colombia.
Parsed Lat=3.599306, long=-74.854556
Stored Lat=0, long=0

12). ** Stored Lat/Long doesn't match type locality **
, type locality=Serdesht, at Little Zab (36°N), River Bané basin, Iran, elevation 1500 meters.
Parsed Lat=36, long=
Stored Lat=0, long=0

13). ** Stored Lat/Long doesn't match type locality **
, type locality=Lufiro River, upper reaches of Matchuza, Ruzizi River drainage, ca. 2°44'00"S, 29°02'99"E, Rwanda.
Parsed Lat=-2.7333333333333, long=
Stored Lat=0, long=0

14). ** Stored Lat/Long doesn't match type locality **
, type locality=Santiago River drainage, Morona-Santiago Province, confluence of the Changachangasa and Tutanangosa rivers and upstream in both, 02°35'51.18''S, 78°11'1038''W.
Parsed Lat=-2.59755, long=
Stored Lat=-2.59755, long=-78.186216666667

15). ** Stored Lat/Long doesn't match type locality **
, type locality=Small stream between Carmo do rio Claro and Conceição da Aparecida, tributary of rio Grande, rio Paraná basin, ca. 21°8'53"S, 46°14'95"W, Estado de Minas Gerais: Município de Conceição da Aparecida, Brazil, elevation ca. 960 meters.
Parsed Lat=-21.148055555556, long=
Stored Lat=-21.148056, long=-46.235972

16). ** Stored Lat/Long doesn't match type locality **
, type locality=Mongo River, east of Marela, on N2, Kaba River (Little Scarcies) drainage, Guinea, 10.17023°N, 11.
Parsed Lat=10.17023, long=
Stored Lat=0, long=0

17). ** Stored Lat/Long doesn't match type locality **
, type locality=Stream about 15 kilometers south of Tuy Hoa, 12°53'05"N, 109°23'70"E, Phu Yen Province, Vietnam.
Parsed Lat=12.884722222222, long=
Stored Lat=0, long=0

** Summary **
Total: 1739
Messages: 17
Updates: 0
Strange: 0
Lost: 0
Broken: 17

Working on , the first one, the problem here is that the parser doesn't appear to work with co-ordinates missing seconds data. However, a location does not need these to be valid and so the parser should be able to cope with this.

Jools

Jools wrote: 04 Oct 2020, 09:49Working on

Neosilurus pseudospinosus

, the first one, the problem here is that the parser doesn't appear to work with co-ordinates missing seconds data. However, a location does not need these to be valid and so the parser should be able to cope with this.

Does the parser convert the degrees minutes seconds to decimal form? If so, why doesn't accept the absence of seconds as 00.0''?

The parser needs to understand that where it was expecting seconds followed by a " but it finds a N,S,W or E then it can assume seconds equals zero. It's not robust enough to do that. It's not actually robust enough for a number of scenarios. Yet...

Jools

Hi Jools,

With , the big problem is you can't have more than 59.99999 minutes or seconds, and the authors reported 83 minutes in the longitude: 16°40'S, 128°83'E. I suspect the longitude should be approximately 128°43'E.

Likewise for , the longitude's minutes should probably be 61°50.25'W, not 61°90.015'W'. Changing 90 minutes to 50 minutes will place the pin at the mouth of the rio Paragua and rio Itenez.

has no coordinates other than "not below 27°30'.

Cuvier, G. and A. Valenciennes, 1840 wrote:M. d'Orbigny found it in Parana, but not below 27°30' south latitude; farther north it becomes very abundant. It is always kept in stony places where there are many currents, and does not bite on the line, so that it can hardly be obtained until October, when the river is very low. It gives off, when taken, the same dull sound as most siluroids.

So we should abandon attempts to plot a type locality pin for that species.


In fact all of these broken entries except #11 and #16 suffer either from min or sec =>60, or an unreported value for either lat or long.

The former can probably be inferred from context narrative if it's meaningful, but the latter should be ignored unless there is very specific text in the original description or a map to infer coordinates from.

#11 is problematic for two possible reasons: (1) because the coordinates include both the (-) symbol and (W) for longitude. That's apparently giving a map reader the equivalent of a double negative. And (2) the coordinates use decimals for degrees while also using the degree symbol. I don't think the parser likes that (and maybe it's a problem for minutes too).

#16 has both an incomplete and inaccurate description. The longitude is only partial and lacks a W or E. From the original description, the coordinates are 10.170238N, 11.399358W. Using those coordinates, the river is crossing the N1 highway (according to Google maps) rather than the N2 highway, and it's west of Marela, not east of it. However, in spite of these two incongruities, the coordinates place the pin exactly in the same spot as is shown on the illustration in their paper.

Cheers, Eric

OK, so a good way to sensibly fix this is to introduce a "corrected type locality" lat/long field. In 99 out of 100 cases it will be blank. However, where a type locality is wrong, misformatted or otherwise duff, then this can be used and will take precedence. If the issue persists, it means fresh (duff) data will not wipe out good work but can be periodically removed if the source data is improved. May also add a notes field to assist.

Leave it with me to implement that!

Jools

Thank you.

And the notes field is a great idea. I recall typing some comments about the lat and long for the Astroblepus I fixed. I didn't want it to go in the General field, so I modified the Distribution field. As I did so, I wondered if that would get overwritten later by a bot. That is the kind of info that belongs in a Notes or Comments type of field.

The idea of a secondary pair of fields for corrected lat and long seems wise. Just tell your code to ignore the official values if secondary (Corrected) are typed in.

Cheers, Eric

All the species described by Fowler (1913) are based on fish collected previously by someone else and the specimens were donated to the museum:

Fowler(1913) wrote:The fishes described in the present paper were collected by Mr.Edgar A. Smith, in 1912 and 1913. They were secured at various localities along the Madeira River or in its tributaries during Mr. Smith's last trip to Brazil.

This applies to 5). Farlowella smithi, 6). Hyphessobrycon agulha and 8 ).Nannostomus digrammus.

The type locality for these three species is nonsensical. Looking at the original article by Fowler (1913), the type locality is reported accurately - he actually wrote of the type localities, "Madeira River, about 200 miles east of W. Long. 62°20', Brazil." But if you drop a pin on the middle Rio Madeira (near Ipixuna region), you'll see that the longitude is exactly 62°20' W. So how do you go 200 miles east of that and also be on the Madeira river? The only way is to move northeast along the Madeira to Nova Olinda do Norte. This does keep you on the Madeira and you are about 200 miles east of 62°20'W, but that is an awfully circular way to describe what could have been an easy place to characterize, especially given that for all three of these species, the paratypes are collected in the vicinity of Porto Velho - therefore I'd expect the type localities are all further south east than Nova Olinda do Norte (unless Edgar Smith obtained the fish in a fish market upstream). But using the paratype info, even to say "Rio Madeira in the vicinty of Porto Velho" would be a more helpful location than what we have to go on.

2). ** Stored Lat/Long doesn't match type locality **
, type locality=Río Paraná, but not below 27°30'S, South America.
Parsed Lat=-27.5, long=
Stored Lat=0, long=0
Also a lost cause. Nothing to do here.

Jools wrote: 04 Oct 2020, 09:351). ** Stored Lat/Long doesn't match type locality **

Neosilurus pseudospinosus

, type locality=Rocky pool of Ord River on Old Lissadel Station, Kimberley District, Western Australia, about 16°40'S, 128°83'E.
Parsed Lat=-16.666666666667, long=
Stored Lat=0, long=0
Already addressed in a prior post with coordinates proposed. Make longitude = 128°43'E

3). ** Stored Lat/Long doesn't match type locality **

Corydoras(ln9) paragua

, type locality=Río Paragua, northwestern bank, river mouth area, río Itenez system, Provincia J.M. Velasco, Departamento Santa Cruz, Bolivia, 13°31.842'S, 61°90.015'W.
Parsed Lat=-13.5307, long=
Stored Lat=-13.53, long=-62.5
Already addressed in a prior post with coordinates proposed: Make longitude 61°50.25'W.

4). ** Stored Lat/Long doesn't match type locality **

Micropanchax ehrichi

, type locality=Mali, southwest of Bamako near Samalofila [Samalofira], 12°15'N, 8°72'W [coordinates corrected].
Parsed Lat=12.25, long=
Stored Lat=0, long=0
Samalofila is located at 12.268017, -8.558788. If you accept 12°15'N for the latitude, then you're left with a longitude around 8°33'W (I don't wish to be more precise since I'm not sure how you go from 72 to 33 or anything like it). So perhaps 12.25000, -8.56000 is a good approximation of type locality?


7). ** Stored Lat/Long doesn't match type locality **

Hyphessobrycon langeanii

, type locality=Kilometer 476.3 of Ferronorte railroad, 17°25'08"S, 53°13'60"W, córrego Mosquito, município de Alto Araguaia, Mato Grosso, Brazil.
Parsed Lat=-17.418888888889, long=
Stored Lat=-17.418888888889, long=-53.233333333333
You'll notice that the "stored lat" of -53.23333333 corresponds to 53°14' (which is what you get if you convert 13' and 60'' to all minutes). This coordinate (-17.418889, -53.233333) is also what is reported for Lima and Moreia, for a collection they have on file at GBIF. So I'd suggest it is the accurate interpretation of the description. In support of that, on Google Maps, that coordinate drops the pin on railroad tracks, which is consistent with the reference to a specific kilometer location along the Ferronorte railroad.

9). ** Stored Lat/Long doesn't match type locality **

Fundulopanchax amieti

, type locality=Rainforest creek on the road from Koupongo, 500 meters west of Somakak, Sanaga system, southwestern Cameroon, 3°58'N, 10°89'E.
Parsed Lat=3.9666666666667, long=
Stored Lat=0, long=0
Cross-checking these numbers with the records at GBIF, they do have collections at 3°58'N, 11°29'E, which would coincide with 10°89'E if you subtract off 60 seconds and add 1 minute. So I'd go with that: 3.966667, 11.483333

10). ** Stored Lat/Long doesn't match type locality **

Trichomycterus aguarague

, type locality=Provice Gran Chaco, National Park Aguarague, Quebrada Timboycito, a Río Caiguami tributary, Tarija, Bolivia, 21°30'S, 63°60'W, elevation 700-800 meters.
Parsed Lat=-21.5, long=
Stored Lat=0, long=0
This one is not easily resolvable. As with other species in this dilemma, you can imagine that the longitude is between 63°0'W and 64°0'W, but that doesn't correspond to any specific little stream which can be identified on Google Maps, and there are no townships or roads to reference. If you look at the original publication, they display a map showing all the collection sites, but they don't distinguish the type locality from those of paratypes. Rough eye-balling the map, I can pretty safely say the collection sites are distributed from -21.25 to -21.6 Lat, and -63.3 to -63.6 Long. Actually, I see on Google Maps that if you choose between -63.5 and -63.6 Long, you'll get inside the National Park Aguarague (mentioned for the type locality) on a mountain side. That is consistent with these being collected in mountain streams. So I'll arbitrarily say that your best record may be: -21.5, -63.6.

11). ** Stored Lat/Long doesn't match type locality **

Ancistrus tolima

, type locality=Quebrada El Pascado, 3.599306°N, -74.854556°W, vereda San Pablo, municipio de Dolores, departamento de Tolima, Colombia.
Parsed Lat=3.599306, long=-74.854556
Stored Lat=0, long=0
The parsed Lat/Long is correct. But it's confused by the combination of "-" in front of the number and "°W" after. Normally wouldn't add the minus sign if your designating west. Just go with 3.599306, -74.854556.

12). ** Stored Lat/Long doesn't match type locality **

Glyptothorax kurdistanicus

, type locality=Serdesht, at Little Zab (36°N), River Bané basin, Iran, elevation 1500 meters.
Parsed Lat=36, long=
Stored Lat=0, long=0
Based on description, Serdesht is a community approx. 2.5 km west of the Little Zab river, about 36°10'N Lat. If a horizontal line is drawn from Serdesht to the Little Zab, the coordinates can be approximated to be 36.159916, 45.534451. But without a longitude value or more precision on the latitude, this is merely an estimate.

13). ** Stored Lat/Long doesn't match type locality **

Amphilius ruziziensis

, type locality=Lufiro River, upper reaches of Matchuza, Ruzizi River drainage, ca. 2°44'00"S, 29°02'99"E, Rwanda.
Parsed Lat=-2.7333333333333, long=
Stored Lat=0, long=0
There is a small widening of the river in this area, and anything between 29°02'E and 29°03'E longitude drops the pin in the same area of the river. The seconds appear to be inconsequential in this case. Checking GBIF for records, they have 2°44'00''S, 29°02'E on file for specimens collected; that corresponds to which is -2.7333333, 29.033333

14). ** Stored Lat/Long doesn't match type locality **

Chaetostoma trimaculineum

, type locality=Santiago River drainage, Morona-Santiago Province, confluence of the Changachangasa and Tutanangosa rivers and upstream in both, 02°35'51.18''S, 78°11'1038''W.
Parsed Lat=-2.59755, long=
Stored Lat=-2.59755, long=-78.186216666667
It's the 1038''W that are throwing us off here - can't have more than 59.9999''. GBIF has a data point reported by the authors who described the species as -2.59755, -78.186217, the same as what you have in "Stored Lat". I'd say that's good.

15). ** Stored Lat/Long doesn't match type locality **

Trichomycterus pirabitira

, type locality=Small stream between Carmo do rio Claro and Conceição da Aparecida, tributary of rio Grande, rio Paraná basin, ca. 21°8'53"S, 46°14'95"W, Estado de Minas Gerais: Município de Conceição da Aparecida, Brazil, elevation ca. 960 meters.
Parsed Lat=-21.148055555556, long=
Stored Lat=-21.148056, long=-46.235972
Your stored longitude treats 46°14'95"W as 46°14'9.5"W, which is probably close and I'd recommend keeping that. Even so, the narrative problem with this species' type locality is that if you use the coordinates given, and even if you allow the authors some leeway on the latitude (e.g., instead of exactly 46°14'95"W, use a range of values between 46°14'W and 46°15'35"W (assuming that 95'' can also be translated as another 1'35''), then you can get a relatively narrow location just beside the rio Claro. BUT, that location is not "between Carmo do rio Claro and Conceição da Aparecida" as described by the authors. Rather the Lat/Long combination is southwest of Conceição da Aparecida, whereas Carmo do rio Claro is northeast of it. There are no locality pins on file at GBIF for this to cross check, and the original paper doesn't provide a map to cross-check.

16). ** Stored Lat/Long doesn't match type locality **

Chiloglanis kabaensis

, type locality=Mongo River, east of Marela, on N2, Kaba River (Little Scarcies) drainage, Guinea, 10.17023°N, 11.
Parsed Lat=10.17023, long=
Stored Lat=0, long=0
Already addressed in a prior post with coordinates proposed: 10.170238N, 11.399358W

17). ** Stored Lat/Long doesn't match type locality **

Pseudomystus sobrinus

, type locality=Stream about 15 kilometers south of Tuy Hoa, 12°53'05"N, 109°23'70"E, Phu Yen Province, Vietnam.
Parsed Lat=12.884722222222, long=
Stored Lat=0, long=0
At GBIF, one of the authors who described this species has specimens on file with the coordinates 12°53'05.0"N 109°23'42.0"E. That corresponds to 12.8847, 109.395. I'd recommend using that.

A small step has been made in so far as the computed lat/long which is refreshed from co-ords in the type locality field every time a data submission is made is complemented by a "regular" type locality lat/long field pair which can be manually input.

I am still tweaking how this data is used, but it means, I think, that data entered by a human will not get "nuked" by computed data. However, we will fall back to using the computed data if no human data (typically corrections) exist.

Cheers,

Jools

is fixed up. Will work through the others, slowly at first as this is fiddly, and there may be a few more bugs to squish...

Jools

Jools wrote: 13 Oct 2020, 19:11

Corydoras(ln9) paragua

is fixed up. Will work through the others, slowly at first as this is fiddly, and there may be a few more bugs to squish...
Jools

Thanks for the update. Will the new system deposit a type locality starred pin on the map? Or is that lost when revised coordinates are used? I don't see them on the map.

Cheers, Eric

It should once I fix it!

Jools

I think this is more or less fixed. However, I have a few other things I need to attend to before coming back to clean up the data. Will report back here when progress is being made! Meantime, I think it's safe to try out.

Cheers,

Jools

Okay, thanks

I've now updated the checker to ignore data where there is a manually entered type locality. It will only store a computed type locality lat/long if one doesn't already exist. The output after I fix a few entries is as follows:

TL02 - Stored Lat/Long doesn't match type locality
, type locality=A rocky pool of Ord River on Old Lissadel Station, Kimberley District, Western Australia, about 16°40'S, 128°83'E.
Parsed from above Lat=-16.666666666667, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

2). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Río Paraná, but not below 27°30'S, South America.
Parsed from above Lat=-27.5, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

3). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Rio Madeira, about 200 miles east of 62°20'W, Amazonas State, Brazil.
Parsed from above Lat=62.333333333333, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

4). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Madeira River, about 200 miles east of 62°20'W, Brazil.
Parsed from above Lat=62.333333333333, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

5). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Rio Madeira about 200 miles east of 62°20'W, Brazil.
Parsed from above Lat=62.333333333333, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

6). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Rainforest creek on the road from Koupongo, 500 meters west of Somakak, Sanaga system, southwestern Cameroon, 3°58'N, 10°89'E.
Parsed from above Lat=3.9666666666667, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

7). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Serdesht, at Little Zab (36°N), River Bané basin, Iran, elevation 1500 meters.
Parsed from above Lat=36, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

. TL02 - Stored Lat/Long doesn't match type locality
, type locality=Lufiro River, upper reaches of Matchuza, Ruzizi River drainage, ca. 2°44'00"S, 29°02'99"E, Rwanda.
Parsed from above Lat=-2.7333333333333, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

9). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Mongo River, east of Marela, on N2, Kaba River (Little Scarcies) drainage, Guinea, 10.17023°N, 11.
Parsed from above Lat=10.17023, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

10). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Stream about 15 kilometers south of Tuy Hoa, 12°53'05"N, 109°23'70"E, Phu Yen Province, Vietnam.
Parsed from above Lat=12.884722222222, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0

11). TL02 - Stored Lat/Long doesn't match type locality
, type locality=Sob River tributaries, lower Ob River below 60°20'N.
Parsed from above Lat=60.333333333333, Long=
Previously computed Lat=0, Long=0
Manually stored Lat=0, Long=0


Jools

This means I will work through the post of Oct 6th (Thanks Eric) and apply the co-ords manually and they will "stick". This is confirmed by the entry for which works as planned.

Jools

Hi Jools, I believe I've submitted now the lat, long updates for all the catfishes.

Jools wrote: 05 Oct 2020, 12:51May also add a notes field to assist.

One thing you mentioned before was a field for correction comments in order to include explanation/documentation for readers going forward that these corrections are just that - corrections of ambiguous data. I think it's a really valuable feature and a note of integrity that we display the fact that some type localities are not necessarily correct but are best efforts to interpret ambiguous data. Given how the "General remarks" field is used in so many other species, it's my feeling that this data correction should not go in that field. I suppose it can go in the "Occurrences" field, unless that field is also autopopulated by external database info (I think it is). How do you wish to handle this?

Cheers, Eric

I am not a fan of notes fields, but you're right, so much of this good work will be forgotten or go unexplained if we don't do something. How about a Type Locality notes field?


Jools

Yes that works. Or perhaps more generically an "occurrence notes" field, since often occurrences get reported here or in literature without being part of the official occurrence data. That would allow us to comment on type locality and also things like "also collected in rio xyz". Thanks.

Working on adding those new fields now, one other question - I'm looking at "Rio Madeira, about 200 miles east of 62°20'W, Amazonas State, Brazil." for . Do you think that's 200 miles downriver (northeast) or the point the river cross 200 miles east line of latitude?

Jools

Jools wrote: 21 Nov 2020, 13:30 Working on adding those new fields now, one other question - I'm looking at "Rio Madeira, about 200 miles east of 62°20'W, Amazonas State, Brazil." for

Farlowella smithi

. Do you think that's 200 miles downriver (northeast) or the point the river cross 200 miles east line of latitude?

Jools

I tried to take it literally. As you could tell by my narrative, it didn't make sense.

Cheers, Eric

It doesn't. That is unless you take "east" to mean "downriver", then it does work and Nova Olinda do Norte is the locality? Think it would be OK to do that once I add the explanation field.

Jools

Exactly, you can get there using the description, but as I mentioned above, that is inconsistent with the paratypes. But that's okay, I'd prefer to stay as true to the original paper as possible. I agree with your plan.

Cheers, Eric

Good stuff, I have added the type locality notes feature. Would you like to "guinea pig it" via the usual data submission process? I've tested it, but good to know I've not missed something.

Jools

Okay, will do.

Cheers, Eric