Remove navicaching (?)

[andrixnet]

According to MrYuck:

We both have links to nearby Navicaches, but that site is beyond dead.
Haven't published a cache since 2015.
As soon as the guy who own's it credit card expires, that site will be gone.

[andrixnet]

I know this is configurable for cache page, but there are additional links at the bottom, to search on other sites for nearby caches.

Plus, if the site is no longer available or the content not worthy, do we keep the code to handle it, do we remove it or disable it?

[following5]

Navicache still is dead. Agree that NC waypoints can be removed, completely.

What do you think of adding a field for Opencaching waypoints instead? For caches that are listed at multiple Opencaching sites.

[harrieklomp]

I started some years ago with links to QC (qualitycaching) but the owner has past away. This can also be removed.

Yes, why not involve other OC sites.

[deg-pl]

Good idea!

[harrieklomp]

How about a cache that is listed on 3 different OC sites?

• OCFFDB
• OP70E7
• OB1A6D

[deg-pl]

JSON?

[following5]

A quick and easy solution would be to allow just one OC waypoint.

That could be improved (later?) by making the input and database field longer and allow to enter multiple space-separated waypoints.

An even better - and even more expensive - solution IMHO would be a foreign_waypoints table, which can store an arbitrary number of any waypoint codes for a cache. They are distinguised by the first two letters. For input, use just one long text field for any type of waypoints, and parse that into the DB table (or an error message).