Atlas File Viewer

[Mariam Obregon]

Homer3 is the latest installment in the HOMER software series. It builds upon Homer2 by enabling custom processing scripts at subject and group levels. This will enable more powerful statistical analyses of these results results. Homer3 also implements the Shared NIR Data Format (SNIRF) that has been developed and adopted by a broad consortium of software and hardware developers. Please subscribe to the Homer3 community forum here on openfnirs.org! We are grateful to all of the Developers who have contributed to Homer and AtlasViewer over the years.

Please see the wikis for Homer3 and AtlasViewer to find documentation to guide you in using each software package. Training courses and webinars are available with data sets and exercises to help you better learn Homer3 and Atlasviewer.

After 10 years of developing the Homer2 and AtlasViewer toolboxes (2009 to 2019), Homer2 is now being replaced by Homer3. AtlasViewer will continue to evolve along with Homer3. Homer2 will remain available online. It is unlikely that any more revisions will be made to Homer2.

NOAA's Sea Level Rise map viewer gives users a way to visualize community-level impacts from coastal flooding or sea level rise (up to 10 feet above average high tides). Photo simulations of how future flooding might impact local landmarks are also provided, as well as data related to water depth, connectivity, flood frequency, socio-economic vulnerability, wetland loss and migration, and mapping confidence. The viewer shows areas along the contiguous United States coast, except for the Great Lakes.

The Sea Level Rise Viewer is created and maintained through NOAA's Office for Coastal Management Digital Coast. The maps are produced using detailed elevation maps with local and regional tidal variability. You can find additional information about the tool - including videos, tutorials, FAQs, and mapping methods - on its landing page. If you have further questions or comments about the Sea Level Rise Viewer, you can reach out through the Digital Coast contact form.

The updated viewer can be used in any browser and has more functionality. This viewer allows users to view multiple layers of geographic information to search and display along with access to advanced tools.

The 311 Community Contact Center is a centralized call center for the City of Albuquerque. The 311 service is a single telephone number for all non-emergency City of Albuquerque inquiries and services.

This link will take you to a site over which the City of Albuquerque has no control. The City assumes no responsibility for the content of the material contained at that site or for the accuracy of any information that is found there. The contents of any site or link not maintained by the City does not necessarily reflect the opinions, standards or policies of the City of Albuquerque, its officials, agents or employees.

The following training videos provide step-by-step instruction for new features of the Public GIS Viewer. The videos will open in a separate window, allowing you to toggle between the video and viewer.

The Public GIS Viewer contains the combined functionality of the Legacy GIS Viewer and the newer appearance of the Enhanced GIS Viewer. In addition, the viewer has been improved with the addition of the following features and is updated nightly.

The Public GIS Map Viewers use pop-up windows to display details on mapped wells and pipelines. Disable pop-up blocking software while using this viewer. If you are not sure if pop-up blocking is enabled on your computer, try our Pop-up Blocker Test.

The Railroad Commission of Texas (Commission) is committed to making its website accessible to all users. However, the inherent graphical nature of the Public GIS Viewers and the volumes of data represented make accessibility more difficult. The Public GIS Viewers use software written by ESRI, which currently does not meet the accessibility requirements outlined in Texas Government Code 2054, Subchapter M, and Texas Administrative Code, Chapter 206. ESRI has stated its commitment to meet accessibility requirements and continues to test its products for compliance. The Commission will continue to monitor the accessibility of GIS and the activity of GIS product vendors to improve compliance with state and federal accessibility requirements.

The Commission specifically disclaims any and all warranties, representations, or endorsements, express or implied, with regard to these data sets, including, but not limited to, the warranties of merchantability, fitness for a particular purpose, or non-infringement of privately owned rights.

Note: GIS maps may not be used for pipeline location purposes in lieu of calling an official notification center prior to excavating. It is a violation of Texas law to fail to make the required 8-1-1 calls.

Field order is being sorted alphabetically in the popup configuration when a feature service is added to the New Map Viewer. Is there a way to make the map viewer honor the original field ordering as shown in the feature table?

Resorting the original order is problematic as field order is set to facilitate ease of data viewing or entry. Unfortunately, the caveat on the popup configuration mentions "Popups offered in map viewer are not compatible with all apps." This appears to be the same issue that @MarkEastwood experienced with his collector post. We are working on a configurable editing app which apparently does not honor new map viewer popup configurations. I tried using Experience Builder, assuming that the problem may be due to the underlying javascript api 3x/4x compatibility, but EB does not yet have an editing widget. It does not appear the popup reorder is honored in Field Maps either. Given this we are spending time to redo our work to use the Map Viewer Classic unless Esri has recommendations on using the new map viewer for editing wit original field order.

I did a bit of looking for an solution and checked out @KellyGerrow posts as she does such a great job with AGOL articles. For some reason it didn't show up on the community pages when searching, but @TonyViveiros2 asked the same question.

I'm running into the same thing involving inability to reorder fields in the New Map Viewer and have the desired order appear in Field Maps and/or Collector. Fortunately, I realized this early on so I did my field arrangements in Map Viewer Classic then saved over the map using the New Map Viewer and did the rest of my work using the New Viewer. This is definitely a big pain!

Thanks for confirming that my tests replicated the behavior you're seeing. We also had several other tests run, both in ArcGIS Online and in Portal. In each test, we were consistently seeing that New Map Viewer arranges fields alphabetically, in the pop up.

I've since learned this is the intended behavior for pop ups in New Map Viewer.

The Map Viewer offers a lot of new capabilities but there are some differences between the two. For instance the analysis tab is not available in new Map Viewer but it is in old. Another example is the "save layer" button used to be just for the old map viewer but now it is also offered in the new. In some cases, the new map viewer is still catching up to the old map viewer, in terms of capabilities and functionality.

As a workaround, you may decide to stay with Map Viewer Classic, particularly when configuring pop ups and working with forms (e.g., for use in Field Maps, etc.).

Let me know if you have additional questions or if we should explore other workarounds while New Map Viewer plays "catch up," in this instance.

Thanks for the follow up and also for providing feedback on the New Map Viewer and our latest release. Our release team has been hard at work, addressing potential issues that are arising during this early stage following the release. I'll provide your feedback to the development team, so that we can keep aligned with customer concerns and needs going forward. Development is a continuous process, and we're constantly adapting and changing to flow with the needs of the customer, as closely as possible.

To that end, I would also encourage your participation in the Ideas forum within Esri Community. You may already be participating, in which case, thank you very much for taking the time to contribute to the conversation. Ideas submitted there are monitored, voted on by other community members, and many are implemented by development for future releases across all Esri products and solutions.

I don't understand why it's the intended behaviour. Surely most people have their fields set up in a certain order for a reason? It would make more sense for the original field order to be used and allow people to change it to alphabetical if they really want to.

My workaround has been to convert the pop-up value type to String. Use arcade for this e.g. Text($feature.FID). I recommend creating them in the order you want them to display (this isn't confirmed to make a difference). Do this for all the values you'd like included in the pop up. Then select (add) the expression fields in the order you want them to appear (do NOT rearrange them after the selection).

I have a hard time understanding why this is considered the "Intended Behavior". The workaround that I have found works best is manually reordering the fields in the web maps JSON using the ArcGIS Online Assistant tool. This works but adds a lot of time to our web map development so our organization hasn't switched over to the "New" map viewer for most projects.

The Map Viewers, developed using the ESRI ArcGIS for Server technology, allow users to display, find, identify, and print map features located in Montgomery County, Maryland. The Montgomery County Government believes that the data presented in these Map Services are accurate. However, the Montgomery County Government and its data suppliers do not guarantee and make no warranties for the accuracy of the data presented in these map viewers. Please read the Internet Map Server Disclaimer carefully prior to selecting an Internet Map Service, or a map viewer .

c80f0f1006