Nordeste Sigla Em Ingles

Abbreviations and Acronyms for Brazil's Northeast Region

Working with geospatial data on Brazil's Northeast region requires knowing the standard abbreviations used in English-language publications, datasets, and government reports. The region is commonly referred to using a handful of established acronyms, and mixing them up will get your analysis rejected by peer reviewers or flagged by automated systems.

nordeste sigla em ingles

The most frequent abbreviation you will encounter is NEB, standing for Northeast Brazil. It appears in academic papers, World Bank reports, and climate modeling datasets. Another variant you may see is Northeast BR, though that is more of a shorthand convention than a true acronym. There are also regional institutional acronyms that show up in English texts. CODAE (Comissão de Desenvolvimento do Estado da Amazônia Oriental) sometimes gets referenced when discussing Northeast-adjacent infrastructure projects. BNDES is the Banco Nacional de Desenvolvimento Econômico e Social, and while it operates nationally, it frequently funds projects specifically targeting the Northeast. Reports from the bank always use the acronym BNDES regardless of the language.

For climate data, the INMET (Instituto Nacional de Meteorologia) station codes are used internationally. A station like SAL refers to Salvador, Bahia, and REC refers to Recife. These three-letter ICAO-style codes are what you need if you are pulling rainfall or temperature series for the Northeast from global databases like GHCN or ERA5. I spent about three weeks last year cleaning a dataset that was supposed to cover Northeast Brazil but had stations labeled with ambiguous codes. The problem was that several weather stations in the southern part of Minas Gerais were included because their latitude overlapped with the official Northeast boundary in one of the shapefiles I was using. The workaround was straightforward: I cross-referenced every station code against the INMET official municipality list and filtered out any that were not in the nine Northeastern states — Bahia, Alagoas, Ceará, Maranhão, Paraíba, Pernambuco, Piauí, Rio Grande do Norte, and Sergipe. That cut the dataset from roughly 840 stations down to about 620, and the remaining anomalies dropped significantly.

Another thing people usually miss is the difference between NE as a region code and NE as a state abbreviation. In Portuguese, NE does not abbreviate any single state, but in English-language datasets sourced from IBGE or ANATEL, NE will always mean the Northeast region. If you see MA, that is Maranhão. CE is Ceará. PE is Pernambuco. Confusing these two uses of NE has caused more than one analyst to misaggregate state-level data in published work. When you are searching for datasets, Google Scholar and Scopus will return results using both full names and acronyms. A search for "Northeast Brazil climate trends" will give you broader results than a search for "NEB precipitation." I usually run both and merge the results manually because many Brazilian researchers publish in English using the acronym while international authors use the full region name.

For satellite and remote sensing products, NEB is less common. NASA Earthdata and the European Space Agency tend to use bounding coordinates or reference the administrative regions by their state abbreviations. If you are working with MODIS or Sentinel-2 products, you will find better results searching by state code pairs — for example, BA-PE-AL for a subset covering Bahia, Pernambuco, and Alagoas. A practical tip: when exporting data from IBGE's SIDRA system, the region field uses the Portuguese abbreviation NE, but the English-language API returns Region: Northeast. The inconsistency trips up automated pipelines. I resolve this by writing a simple mapping function at the start of every script that normalizes region labels across all input sources.

If you need a reference document with all the standard abbreviations laid out, IBGE's own "Normas de Representação Cartográfica" PDF contains the official codes, though it is only available in Portuguese. The English summaries from the World Bank's Brazil country pages reference NEB and the state codes without listing every station identifier, which is why the INMET cross-reference step I described earlier is necessary. The most common pitfall I see is assuming that NE in any English text automatically means the Brazilian Northeast. In US geographic contexts, NE means Northeast, and in general academic writing, it can refer to any northeastern region depending on the paper's focus. Always check the methodology section or the data appendix for a region definition before including a dataset in your analysis.

Standard Acronym Reference Table

Below is a quick reference for the most useful abbreviations when working with Northeast Brazil data in English. NEB — Northeast Brazil. Used in most international climate and economic datasets.

NE — Northeast region code in IBGE systems. Not a state abbreviation. BNDES — National Bank for Economic and Social Development. Referenced in English-language project documentation.

INMET — National Institute of Meteorology. Station codes are internationally recognized. State codes — BA, AL, CE, MA, PB, PE, PI, RN, SE. These remain consistent across Portuguese and English sources and are the safest identifiers to use in any pipeline.

One more edge case worth noting: the state of Maranhão is sometimes classified under the North region (Norte) in older IBGE tables from before the 1970s regional reorganization. If you are working with historical data predating 1970, Maranhão may appear under N or Norte codes rather than NE. This has come up in several economic history papers I have reviewed, and it causes serious data integrity issues when modern researchers pull pre-1970 series without checking the regional classification scheme used in the original source. The workaround is to verify the year of each dataset against IBGE's regional boundaries at that time. IBGE publishes a history of regional divisions on its website, and cross-checking that timeline takes about ten minutes per dataset but prevents months of downstream corrections.