Matias Cardoso

Matias Cardoso is a municipality in the north of the state of Minas Gerais in Brazil.

Location of Matias Cardoso in the state of Minas Gerais

Location

Matias Cardoso is located on the right bank of the São Francisco River. It is 10 km. south of Manga and is 72 km. northwest of Jaíba. As of 2007 the population was 10,270 in an area of 1,938 km².

  • The elevation of the municipal seat is 472 meters.
  • It became a municipality in 1993
  • The postal code (CEP) is 39478-000
  • Statistical microregion: Januária

The municipality contains the 6,358 hectares (15,710 acres) Jaíba Biological Reserve, a fully protected conservation unit created in 1994.[1]

Economy

The economy is based on agriculture with emphasis on cattle raising. There were 46,000 head in 2006. The main agricultural crops were cotton, peanuts, corn, manioc, sorghum, sugarcane, and mamona—castor oil plant. The GDP was R$37,034,000 in 2005.

Health

This municipality is extremely isolated from major population centers and suffers from drought and poor soils. It is one of the poorest in the state and in the country.

  • Municipal Human Development Index: .602 (2000)
  • State ranking: 831 out of 853 municipalities as of 2000
  • National ranking: 4,618 out of 5,138 municipalities as of 2000

(For the complete list see Frigoletto)

  • Illiteracy rate: 32.51% (older than 16)--the rate for the state was 11.96% (2000)
  • Infant mortality rate: 12.20—the rate for the state was 17.40 (2000)
  • Urbanization rate: 43%--the rate for the state was 80% (2000)
  • Urban area connected to sewers: 2.4%--the state percentage was 81.39% (2000)
  • Urban area with garbage collection: 34.06%--the state percentage was 91.37 (2000)
  • Health clinics: 4
gollark: Well, what didn't work, then?
gollark: They aren't that hard. You just use `server_name` in the `server` block.
gollark: Not specifically wordpress, no.
gollark: I would probably use nginx, because I'm used to it and it has nicer configuration:```nginxhttp { # whatever important configuration you have for all HTTP servers, `nginx.conf` probably ships with some # fallback in case someone visits with an unrecognized Host header server { listen 80 default_server; listen [::]:80 default_server; return 301 http://somedomain$request_uri; } server { listen 80; # you may (probably do) want HTTPS instead, in which case this bit is somewhat different - you need to deal with certs and stuff, and use port 443 - also you should probably add HTTP/2 listen [::]:80; # IPv6 server_name domain1.com; location / { proxy_pass http://backend1:8080/; } } server { listen 80; listen [::]:80; server_name domain2.com; location / { proxy_pass http://backend2:8080/; } }}```
gollark: The reverse-proxy solution is in my opinion the best one, although it would require some config.

References
  1. Josefina Ivonete Fagundes (2005), Sistema de Áreas Protegidas - SAP (in Portuguese), IEF - Instituto Estadual de Florestal - MG, archived from the original on 2017-02-16, retrieved 2016-04-27

See also

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.