Texas Natural Resources Information System

The Texas Natural Resources Information System (TNRIS) is the principal state archive in Texas for natural resources data. TNRIS provides a central access point for Texas Natural Resources data, census data, digital and paper maps, and information about datasets collected by state agencies and other organizations. TNRIS is a division of the Texas Water Development Board (TWDB).

TNRIS
State Government
IndustryGeographic Information Systems (GIS)
FoundedAustin, Texas (1968)
HeadquartersAustin, Texas, United States
Key people
Richard Wade, Director
ProductsHistorical and Current Aerial Photography
Current and Historical USGS Printed Maps
GIS Education
Public Domain Data Warehouse
Number of employees
14
Websitetnris.org

About TNRIS

TNRIS was established by the Legislature in 1968 as the Texas Water-Oriented Data Bank. In 1972, after four years of growth and diversification, it was renamed the Texas Natural Resources Information System. The mission of TNRIS is to provide a "centralized information system incorporating all Texas natural resource data, socioeconomic data related to natural resources, and indexes related to that data that are collected by state agencies or other entities." (Texas Water Code, 16.021).

The TNRIS offices are located in the Stephen F. Austin Building, 1700 North Congress Avenue, in Austin, Texas.

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.
gollark: I think LetsEncrypt may not be very happy with that, though.
gollark: Yes, and you can just use a reverse proxy (with "vhosts" or whatever) for that, easy enough.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.