- Home
- Getting Started
- Documentation
- Proxy/Firewall
- Tour the Interface
- Tour the Layers
- JMARS Video Tutorials
- Lat/Lon Grid Layer
- Map Scalebar
- Nomenclature
- Crater Counting
- 3D
- Shape Layer
- Mosaics
- Map
- Advanced/Custom Maps
- Graphic/Numeric Maps
- Custom Map Sharing
- Stamp
- THEMIS
- MOC
- Viking
- CTX
- HiRise
- HiRISE Anaglyph
- HiRISE DTM
- HRSC
- CRISM Stamp Layer
- OMEGA
- Region of Interest
- TES
- THEMIS Planning
- Investigate Layer
- Landing Site Layer
- Tutorials
- Video Tutorials
- Displaying the Main View in 3D
- Finding THEMIS Observation Opportunities
- Submitting a THEMIS Region of Interest
- Loading a Custom Map
- Viewing TES Data in JMARS
- Using the Shape Layer
- Shape Layer: Intersect, Merge, and Subtract polygons from each other
- Shape Layer: Ellipse Drawing
- Shape Layer: Selecting a non-default column for circle-radius
- Shape Layer: Selecting a non-default column for fill-color
- Shape Layer: Add a Map Sampling Column
- Shape Layer: Adding a new color column based on the values of a radius column
- Shape Layer: Using Expressions
- Using JMARS for MSIP
- Introduction to SHARAD Radargrams
- Creating Numeric Maps
- JMARS Shortcut Keys
- JMARS Data Submission
- FAQ
- Open Source
- References
- Social Media
- Podcasts/Demos
- Download JMARS
JMARS ›
Small bug fix, Update!
High Resolution Export feature fix: Version 3.4.0 included a fix to preserve the relative size of text labels when exporting high resolution export but introduced an issue with exporting shapefiles.
JMARS 3.4.0 to JMARS 3.4.1 addressed an issue with the High Resolution Export feature and shapefiles. Version 3.4 included a fix to preserve the relative size of text labels when exporting at higher resolutions, but inadvertently introduced an issue that could cause shapes to export at the wrong position if the screen dimensions were changed as part of the export process.
If you haven't been making use of the High Resolution Export feature, don't change screen dimensions while exporting, weren't exporting shapefiles, or were using a version prior to JMARS 3.4, this bug wouldn't have affected you, and there's no need to rush to the 3.4.1 update.
