Fix privacy setting value mismatch preventing sighting creation

[Copilot]

The create sighting form was sending privacy values that failed backend validation, preventing any sightings from being created. No sightings meant no location data in the feed, resulting in blank maps in post detail views.

Changes

Form values corrected (siteapps/templates/sightings/create_sighting.html):

• "approximate" → "obscured"
• "hidden" → "private"

Default fallback updated (siteapps/sightings/views.py):

• Changed default from "approximate" to "obscured"

Backend expectations

Valid privacy settings defined in config/settings/base.py:

• PRIVACY_SETTING_PUBLIC = "public" - exact location shown
• PRIVACY_SETTING_OBSCURED = "obscured" - obfuscation box shown
• PRIVACY_SETTING_PRIVATE = "private" - no location shown

Status

• ✅ Public privacy: sightings create successfully, maps display
• ✅ Private privacy: sightings create successfully, no location shown
• ⚠️ Obscured privacy: requires additional work to calculate obfuscation box corners (frontend currently only sends radius, not computed corner coordinates)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>map in sighting detail is blank</issue_title>
<issue_description>does the feed sightings response include lat/lon data

if it does, why is the map display not working</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes map in sighting detail is blank #39

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[oldtopos]

@copilot is this pr still relevant

[Copilot]

@copilot is this pr still relevant

Yes, this PR is still relevant. The main branch still has the incorrect privacy setting values ("approximate" and "hidden") that cause sighting creation to fail backend validation. These need to be changed to "obscured" and "private" to match the backend's expectations defined in config/settings/base.py.

Without this fix, users cannot successfully create sightings with the default privacy setting, which prevents location data from being stored and causes blank maps in the post detail view.