You may have noticed already that cApiTaliZAtioN isn't a big deal for search.
You can type **yankee stadium** or **Yankee Stadium** or even **YANKEE STADIUM** if you're really excited about finding it. See for yourself by comparing the results of the previous search to the following:
Now that you've seen some examples of search, let's examine the results closer.
When requesting search results you will always get back `GeoJSON` results, unless something goes terribly wrong, in which case you'll get a really helpful error.
@ -80,7 +66,7 @@ When requesting search results you will always get back `GeoJSON` results, unles
You will find the following top-level structure to every response:
```
```javascript
{
"geocoding":{...},
"type":"FeatureCollection",
@ -94,7 +80,7 @@ This is where you will find the list of results that best matched your input par
Each item in this list will contain all the information needed to identify it in human-readable format in the `properties` block, as well as computer friendly coordinates in the `geometry` property. Note the `label` property, which is a human-friendly representation of the place, ready to be displayed to an end-user.
```
```javascript
{
"type":"Feature",
"properties":{
@ -132,11 +118,12 @@ we had to split it out into its own section.
## Result count
You may have noticed that there were **10** places in the results for our **Stinky Beach** search.
You may have noticed that there were **10** places in the results for all the previous search examples.
That's the _default_ number of results the API will return, unless otherwise specified.
Below is the region that will be searched. Museums located outside of this highlighted region will **NOT** be included in the results. The museums returned will be sorted based on how well they matched the `text` parameter, in this case **museum**.