Counties cannot be added to Project or selected in Identify

Bug Reports
,
32

Another example is Lincoln Co., Colorado (place ID=249). It cannot be called up in Identify by typing it into the place box (not under Filters, either). It can be called up in Explore, though, as with the previous example. This is another county name that repeats itself over a dozen times in various U.S. states. Not sure whether that is a contributing factor that causes this bug to occur.

Workaround is editing the URL by inserting the place ID manually:
https://www.inaturalist.org/observations/identify?place_id=249

Nonetheless, it is clearly a bug that should be fixed. I am sure there are other examples.

33

(I merged this with an existing report that has the same root cause.)

There are about 160 counties with this same problem. Last I heard, the suggested solution from staff is to ask individually to have it fixed when you encounter one of the problem counties.

34

Email iNaturalist Help?

35

That should work, yes.

36

Thanks for your help with this issue!

1 Like
37

@tiwane do you think you would be able to do this with Jackson County, Ohio and Washington County, Wisconsin? Thanks!

Place not Showing up in Project
38

OK, done.

39

Thank you so much! Hate to bother you again, but could you please do the same for Montgomery, Morgan, and Jackson Counties, Kentucky? Sorry to pester you so much :sweat_smile:

40

OK, done.

41

Thanks again!

42

Hello! I am having this exact problem with Washington County, Missouri. I am trying to create a Project for aforementioned county, and it is not showing up whatever I do. Any help will be appreciated :)

Cannot Filter for Specific County when making a collection project
43

for folks who don’t want to wait for staff to do whatever they do to allow a particular place to show up, it’s possible to add places to a collection project via the API. this describes one workflow to add taxa to a collection project: https://forum.inaturalist.org/t/moving-a-list-to-a-project/64938/2. to add a place instead of taxa, just adapt step #4 to use an appropriate rule definition for your place.

start by finding the numeric ID of your place. one way to do this is to go to the place page in the iNat website, add .json to the URL, and then navigate to that. for example, if your place page is https://www.inaturalist.org/places/washington-county-mo-us, then you would look for the numeric value assigned to the id field in https://www.inaturalist.org/places/washington-county-mo-us.json.

then look to see if you have any places already defined in your project. if you don’t have any places already in your project, then you would use this rule definition in step #4, replacing 0 with whatever the numeric ID of your place is:

source_rules['place']['include']['ids'] = [0]

if you already have places defined in your project and wish to preserve them while adding your new place, then use this rule definition instead, replacing 0 with whatever the numeric ID of your place is:

source_rules['place']['include']['ids'] = await get_project_rules_operand_ids(project_id, operand_type=source_rules['place']['operand_type'], operator=source_rules['place']['include']['operator'])
source_rules['place']['include']['ids'].append(0)
1 Like