Option to return only identifiers or different realizations of a catchment.

[dblodgett-usgs]

Would like to get back the json data without the geo part. Not sure what the API should look like for this, but seems like a simple thing to offer.

[dblodgett-usgs]

Currently, a featureSource just returns its key information and a link to its navigation end point.

We should also list endpoints for:

• .../{featureID}/ids return a list of all associated feature API URLs from all feature source tables.
• .../{featureID}/local exists as the local catchment characteristics
• .../{featureID}/tot exists as the total catchment characteristics
• .../{featureID}/div exists as the divergence routed catchment characteristics
• .../{featureID}/basin exists as the basin endpoint
• .../{featureID}/flowline would return the flowline for just the current feature
• .../{featureID}/catchment would return the catchment polygon for the current feature
• .../{featureID}/navigation/comid would return a list of comids without any additional data

e.g.

{
	"type": "FeatureCollection",
	"features": [
		{
			"type": "Feature",
			"geometry": {
				"type": "Point",
				"coordinates": [
					-89.2203937,
					42.9197239
				]
			},
			"properties": {
				"type": "hydrolocation",
				"source": "nwissite",
				"sourceName": "NWIS Surface Water Sites",
				"identifier": "USGS-05429700",
				"name": "YAHARA RIVER @ FORTON STREET BRIDGE @ STOUGHTON,WI",
				"uri": "https://waterdata.usgs.gov/monitoring-location/05429700",
				"comid": "13297194",
				"reachcode": "07090002007368",
				"measure": "76.9593300000",
				"navigation": "https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-05429700/navigation",
				"linked_ids": "https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-05429700/ids",
				"local_attributes": "https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-05429700/local",
				"total_attributes": "https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-05429700/tot",
				"divergence_attributes": "https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-05429700/div",
				"basin": "https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-05429700/basin",
				"flowline": "https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-05429700/flowline",
				"catchment": "https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-05429700/catchment"
			}
		}
	]
}

[EthanGrahn]

If we want to match the OGC API specification, it looks like these links would go into a links JSON array at the top level of the feature. http://opengeospatial.github.io/e-learning/ogcapi-features/text/operations.html#feature