An official website of the United States government
Here's how you know
A .mil website belongs to an official U.S. Department of Defense organization in the United States.
A lock (lock ) or https:// means you’ve safely connected to the .mil website. Share sensitive information only on official, secure websites.

Check this box if you want old 'non-friendly' URLs to be redirected to the new URLs.
Check this box to enable character replacement. This automatically replaces all spaces in page names.
Select the replacement character to use.
When the characters in this list appear in a page name, will be replaced with the value specified as the ‘replacement’ character (- or _). To replace any other character, append it to the end of the list. To stop any character from being replaced, remove it from the list.



[NOTE: The list shown in the ‘replace characters with supplied characters’ is actually the default for this one]
To replace a character in a URL with another character, use a comma delimited pair of characters where the first value in the pair is the ‘find’, and the second is the ‘replace’. f,r will find any ‘f’ in a URL and replace it with ‘r’. This can be used for replacing æ with ‘ae’ and similar. This only applies to Page and User Profile URLs and any URLs controlled through URL providers. You can only replace single characters - the 'find' character can only be a single value, while the 'replace' can be a string of one or more characters.
Check to hide the page extensions. This can be useful for SEO and also for masking the underlying technology to make it more difficult for hackers.
Specify the extension to use on the end of every page URL. The default value is .aspx. Note: using a custom page extension also requires configuring IIS to handle the custom extension. If you don't know what this means, leave it alone.
Select the behavior that should occur when a user browses to a deleted, expired or disabled page.
When checked, any URL generated by dNN will be converted to all lowercase. ie. Menus, breadcrumbs, module controls, etc.
When checked, any URL that is not in lower case will be redirected to the lower case version of that URL.
This character is used to replace any spaces in a generalized URL path where parameters with spaces have been supplied.
When checked, any accented (diacritic) characters such as å and è will be converted to their plain-ascii equivalent. Example : å -> a and è -> e.
When checked, the Custom URL Provider functionality of this site is enabled. When unchecked, no custom URL providers will be loaded.
When checked, any duplicate URLs found in this site will be reported in the event log. The system will choose which of the duplicate URLs to show.
The Ignore URL Regex pattern is used to stop processing of URLs by the URL Rewriting module. This should be used when the URL in question doesn’t need to be rewritten, redirected or otherwise processed through the URL Rewriter. Examples include images, css files, pdf files, service requests and requests for resources not associated with DotNetNuke.
The Do Not Rewrite URL regular expression stops URL Rewriting from occurring on any URL that matches. Use this value when a URL is being interpreted as a DotNetNuke page, but should not be.
The Site URLs Only regular expression pattern changes the processing order for matching URLs. When matched, the URLs are evaluated against any of the regular expressions in the siteURLs.config file, without first being checked against the list of friendly URLs for the site. Use this pattern to force processing through the siteURLs.config file for an explicit URL Rewrite or Redirect located within that file.
The Do Not Redirect URL regular expression pattern prevents matching URLs from being redirected in all cases. Use this pattern when a URL is being redirected incorrectly.
The Do Not Redirect https URL regular expression is used to stop unwanted redirects between http and https URLs. It prevents the redirect for any matching URLs, and works both for http->https and https->http redirects.
The Prevent Lowercase URL regular expression stops the automatic conversion to lower case for any matching URLs. Use this pattern to prevent the lowercase conversion of any URLs which need to remain in mixed/upper case. This is frequently used to stop the conversion of URLs where the contents of the URL contain an encoded character or case-sensitive value.
The Do Not Use Friendly URLs regular expression pattern is used to force certain DotNetNuke pages into using a longer URL for the page. This is normally used to generate behaviour for backwards compatibility.
The Keep in Querystring regular expression allows the matching of part of the friendly URL Path and ensuring that it stays in the querystring. When a DotNetNuke URL of /pagename/key/value is generated, a ‘Keep in Querystring Regular Expression’ pattern of /key/value will match that part of the path and leave it as part of the querystring for the generated URL; e.g. /pagename?key=value.
The URLs with no Extension regular expression pattern is used to validate URLs that do not refer to a resource on the server, are not DotNetNuke pages, but can be requested with no URL extension. URLs matching this regular expression will not be treated as a 404 when a matching DotNetNuke page can not be found for the URL.
This pattern is used to determine whether the characters that make up a page name or URL segment are valid for forming a friendly URL path. Characters that match the pattern will be removed from page names
 

Frequently Asked QuestionS

Q. Why is the Navy building a new Recreational Vehicle (RV) park?

A. Morale, Welfare, and Recreation (MWR) has identified a need to construct a new RV Park at Naval Support Activity (NSA) Annapolis. The existing RV Park at NSA Annapolis does not meet the requirements of modern RVs, does not meet Architectural Barriers Act (ABA) requirements, is not large enough to meet the demand for RV/camping facilities in the region, and does not have sufficient space to accommodate additional RV pads. The new facility would allow MWR to meet the important mission of serving our military families at NSA Annapolis.


Q. What level of National Environmental Policy Act (NEPA) analysis is being completed for this Proposed Action?

A. The Navy is preparing an Environmental Assessment (EA) in accordance with the NEPA, as implemented by the Council on Environmental Quality (CEQ) Regulations and Navy regulations for implementing the NEPA. The EA will analyze the potential environmental impacts of constructing and operating a new RV Park at NSA Annapolis to support the MWR mission.


Q. What is the Proposed Action?

A. The MWR program proposes to construct a new RV Park at NSA Annapolis. The RV Park would include the following:

  • Approximately 35-50 new concrete RV pads that would be approximately 40 feet by 20 feet with an adjacent car pad

  • At least four RV sites would meet the ABA-compliance guidelines

  • Electrical service and freeze-proof hose water and sewer connections

  • An ABA-accessible Comfort Station with a laundry facility and family style unisex cabana-style rooms that each hold a shower, sink, and toilet; vending machines; Wi-Fi; and an enclosed dumpster and recycling pad

  • Water and sewer infrastructure and other utilities would be provided to the site as necessary

  • Natural surroundings, such as trees and shrubs, would be preserved to the maximum extent possible and additional trees would be planted


Q. How large is the RV Park?

A. Approximately 35-50 new concrete RV pads that would be approximately 40 feet by 20 feet with an adjacent car pad. The RV Park would be approximately 3-4.5 acres.


Q. How many alternatives are being analyzed in the Environmental Assessment (EA) and where are they located?

A. Two action alternatives and the No Action Alternative are being analyzed in the EA. The two action alternatives are located at: Alternative 1 - Greenbury Point at Possum Point and Alternative 2 - North Severn Complex at Beach Road. The Proposed Action would not be implemented via the No Action Alternative. The No Action Alternative would not meet the purpose of and need for the Proposed Action; however, the No Action Alternative is carried forward for analysis in the EA to establish a comparative baseline for analysis.


Q. Did the Navy consider any other areas to build?

A. Four other alternatives were considered but will not be carried forward for analysis in the EA. These alternatives are listed below:
1. Expanding the Existing Navy Getaways Campground
2. Construction of a New RV Park at Gage Road
3. Construct New RV Park adjacent to the Nature Center on Greenbury Point
4. Construct New RV Park on the Upper or Lower Yards


Q. What Agency consultation is required for cultural resources?

A. The Navy completes Section 106 consultations with the Maryland Historical Trust (MHT) in accordance with the National Historic Preservation Act (NHPA) and its implementing regulations at 36 CFR Part 800. In 2020, the Navy completed Section 106 consultation with the SHPO for the construction of an RV Park at Possum Point. Concurrence from SHPO for no adverse effect to historic properties was received. Continued consultation with the SHPO for the Proposed Action will be completed.


Q. What is the Architectural Barriers Act (ABA) The ABA is the first federal law to address access to the built environment.

A. Passed by Congress in 1968, it ensures access to many federally funded facilities to this day. The ABA greatly informed the Americans with Disabilities Act (ADA) of 1990 and its requirements for access to facilities in the private and state and local government sectors.


Q. How long has the Navy been planning the RV Park?

A. The proposed RV Park and associated facilities were outlined in the 2018 NSA Annapolis Installation Development Plan and associated Greenbury Point Area Development Plan. The RV Park assists in the goal of increasing the availability of morale, welfare, and recreational opportunities in the area.


Q. Who can reserve a space at the RV Park?

A. The RV Park serves authorized patrons including active duty service members, DoD civilians, dependents, and retirees.


Q. What would happen to the existing RV park?

A. The existing RV Park would continue to be used for RVs that do not require the larger pads and modernized facility features, and for visitors who do not require ABA accessibility. Q. What are the operating hours of the RV Park? A. RV Parks are utilized 24/7. Normal check-in would be with Recreation Lodging between 8:00 a.m. and 5:00 p.m. Late check-ins are accommodated and coordinated prior to arrival.


Q. Would an RV Park meet the goals identified in the Integrated Natural Resources Management Plan (INRMP)?

A. NSA Annapolis has developed and implemented an INRMP. One of the stated goals of the INRMP is to provide outdoor recreational opportunities for station personnel, their dependents and guests within the constraints of the installation mission and capability of the natural resources. The INRMP further defines recreational opportunities to be consumptive or non-consumptive outdoor recreation. Non-consumptive outdoor recreation includes but is not limited to primitive and RV camping. An example of camping facilities located at NSA Annapolis includes primitive and RV campsites.


Q. When will the RV park construction begin?

A. Project was approved by Congress in December of 2023. Request for Proposals (RFPs) will go out upon the completion of the EA, approximately in January of 2025 with project awarded no later than December of 2025. The project is a Design/Build, so plans are not required prior to the RFP. An actual construction start date is unknown at this time.


Q. Will the construction of an RV Park impact the Greenbury Point trails?

A. No, the RV Park would not impact the existing nature trails or the Tower Access Roads.


Q. Will appropriated funds (taxpayer dollars) be used to construct and operate the RV Park?

A. No


Q. Where will the proceeds go?

A. Profits from the RV Park would remain in the MWR fund to support our sailors locally and contribute to future re-capitalization projects.


Q. Will the EA assess cumulative impacts associated with other future projects (i.e. a golf course) on Greenbury Point?

A. The EA will include an analysis of the cumulative impacts associated with other officially proposed projects. However, a proposal for a new golf course on Greenbury Point is not under consideration by NSA Annapolis. Any proposed future action(s) on Greenbury Point, not included in the analysis for the RV Park EA, will undergo review in compliance with all applicable environmental laws, including the National Environmental Policy Act. 

Page Title

TEST SAMPLELorem ipsum dolor sit amet, consectetur adipiscing elit. Nam mollis ligula ac pharetra finibus. Aliquam erat volutpat. Aliquam id ultrices nunc, id tempor orci. Donec hendrerit enim eget neque scelerisque, nec sodales nisl sodales. Quisque placerat ultrices quam. Vivamus vehicula, felis at scelerisque ultricies, lectus est porttitor urna, nec dignissim diam neque in urna. Vivamus luctus augue eros, ac fringilla augue euismod et. Suspendisse accumsan nibh id ipsum rutrum, convallis luctus orci efficitur. Suspendisse sodales neque et risus fringilla suscipit. Etiam varius enim tortor, fringilla gravida arcu pulvinar ullamcorper. Nam sit amet mattis velit. Phasellus placerat placerat orci, ac pulvinar justo varius et. In lectus massa, ornare maximus massa non, commodo pulvinar magna. Quisque lectus nisl, varius feugiat nulla a, accumsan tristique est.

Duis imperdiet, velit lobortis tempus commodo, eros magna laoreet tortor, nec feugiat nunc dui vitae tellus. Ut in neque mollis, viverra dolor at, convallis turpis. Nullam nisi magna, lobortis quis sapien et, scelerisque viverra justo. Suspendisse est erat, finibus ac gravida ac, blandit et diam. Curabitur maximus, dui vitae tincidunt pellentesque, ante neque dignissim metus, nec posuere odio odio ut tortor. Proin sollicitudin arcu vel fringilla rutrum. Proin in tincidunt purus, eget blandit erat. Vivamus dictum enim ac justo vestibulum lobortis. Donec lobortis orci mi. Quisque ut ultrices dolor. Interdum et malesuada fames ac ante ipsum primis in faucibus.

Cras et bibendum ipsum. In vitae lorem nec nisl interdum placerat. Curabitur imperdiet orci purus, non condimentum ante varius non. Sed nulla massa, condimentum a consectetur at, gravida ac augue. Aenean nisl dolor, elementum sit amet finibus congue, interdum id ipsum. Duis elementum nisl id leo commodo, non egestas dolor efficitur. Mauris mollis sapien nibh, at suscipit ipsum volutpat in. Proin faucibus tortor nulla, a consectetur nulla ultrices quis. Aenean at neque convallis, bibendum felis ac, elementum tellus.

Praesent feugiat nibh nec ante bibendum fermentum. Suspendisse porta condimentum eleifend. Donec ligula mi, lobortis quis porta sed, tincidunt nec felis. Suspendisse iaculis suscipit nisi quis suscipit. Sed consequat augue a arcu tincidunt tincidunt. Cras rutrum lacus a tortor aliquet, id varius ligula rutrum. Donec volutpat vestibulum tristique. In leo purus, venenatis vitae dolor molestie, porta ullamcorper leo. Etiam vehicula vitae ipsum quis dignissim. Suspendisse consectetur, quam non pellentesque dignissim, tortor justo volutpat ex, non efficitur metus nibh in orci. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Interdum et malesuada fames ac ante ipsum primis in faucibus. Etiam quis quam eget arcu consectetur aliquet.

Aliquam congue aliquet magna quis ultrices. Sed augue diam, varius tincidunt dui at, cursus condimentum sapien. Nam rutrum consectetur metus ac condimentum. Fusce semper odio sit amet laoreet fringilla. Mauris sagittis ligula arcu. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Vestibulum ut venenatis ante. Nunc molestie consequat consectetur. Sed vitae fringilla libero, eu laoreet felis. Vivamus ultricies dui malesuada orci porttitor placerat. Nunc enim erat, euismod a orci a, feugiat consequat dolor. Aenean laoreet ullamcorper lacus vitae laoreet.

 

Google Translation Disclaimer

  • Google Translate, a third party service provided by Google, performs all translations directly and dynamically.
  • Commander, Navy Region Southwest, cnrsw.cnic.navy.mil has no control over the features, functions, or performance of the Google Translate service.
  • The automated translations should not be considered exact and should be used only as an approximation of the original English language content.
  • This service is meant solely for the assistance of limited English-speaking users of the website.
  • Commander, Navy Region Southwest, cnrsw.cnic.navy.mil does not warrant the accuracy, reliability, or timeliness of any information translated.
  • Some items cannot be translated, including but not limited to image buttons, drop down menus, graphics, photos, or portable document formats (pdfs).
  • Commander, Navy Region Southwest, cnrsw.cnic.navy.mil does not directly endorse Google Translate or imply that it is the only language translation solution available to users.
  • All site visitors may choose to use similar tools for their translation needs. Any individuals or parties that use Commander, Navy Region Southwest, cnrsw.cnic.navy.mil content in translated form, whether by Google Translate or by any other translation services, do so at their own risk.
  • IE users: Please note that Google Translate may not render correctly when using Internet Explorer. Users are advised to use MS Edge, Safari, Chrome, or Firefox browser to take full advantage of the Google Translate feature.
  • The official text of content on this site is the English version found on this website. If any questions arise related to the accuracy of the information contained in translated text, refer to the English version on this website, it is the official version.

Naval District Washington   |   1411 Parsons Ave SE Suite 200   |   Washington DC, 20374-5001
Official U.S. Navy Website