title: What is the practice in REST to name getting a resource by another resource ID
body: <p>I'm creating a RESTful weather by cities service, i.e. a client knows a city ID and wants to receive a weather report in JSON from this city. For example:</p>
  
  <pre><code>{temperature:xxx, humidity:xxx, pressure:xxx}
  </code></pre>
  
  <p>Two issues:</p>
  
  <ol>
  <li>What should  the Get URL be? (My first idea: <code>api/v1/WeatherByCityId/{cityid</code>) but it looks raw and untidy... or is it OK?</li>
  <li>Do I need to create two entities: <code>City (table="cities")</code> and <code>Weather (table="weathers")</code> and create a relationship? OR better create one entity <code>WeathersCities(table="weathers_cities")</code> (or whatever...)?</li>
  </ol>
  
  <p>(I'm not gonna use 3rd party weather services, please don't suggest RestTemplate, WebClient, FeignClient, etc. Yes, I will fill the weather data  by myself every hour.</p>