Skip to content

Commit

Permalink
Grab some copy from the old website to get something up.
Browse files Browse the repository at this point in the history
  • Loading branch information
tclarke committed Sep 9, 2023
1 parent 2f2e69b commit c978535
Show file tree
Hide file tree
Showing 11 changed files with 129 additions and 23 deletions.
13 changes: 13 additions & 0 deletions 404.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
title: "404"
excerpt: "Page Not Found"
permalink: 404.html
indexing: false
sitemap: false
---

Sorry, but the page could not be found.

Are you looking for:

{% include nav-default.html %}
36 changes: 14 additions & 22 deletions _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -89,12 +89,12 @@ remote_theme: daviddarnes/alembic@main
encoding: utf-8 # Make sure the encoding is right
lang: en-US # Set the site language
title: "Opticks" # Site name or title, also used in jekyll-seo-tag
logo: "/assets/logos/logo.svg" # Site logo, also used in jekyll-seo-tag
logo: "/assets/logos/logo@64px.png" # Site logo, also used in jekyll-seo-tag
description: "Opticks is a multi-platform electronic light table (ELT)" # Site description and default description, also used in jekyll-seo-tag
url: "https://www.opticks.org" # Site url, also used in jekyll-seo-tag
baseurl: ""
repo: "https://github.com/opticks-org/www"
email: "opticks-users@opticks.org"
email: "opticks-users@lists.sourceforge.net"
# disqus: "alembic-1" # Blog post comments, uncomment the option and set the site ID from your Disqus account
# date_format: "%-d %B %Y" # Blog post date formatting using placeholder formatting
# google_analytics: ""
Expand All @@ -107,37 +107,29 @@ css_inline: true # Will insert all styles into a single <style> block in the <he
favicons: # Favicons are also used in the manifest file. Syntax is 'size: path'
16: '/assets/logos/[email protected]'
32: '/assets/logos/[email protected]'
32: '/assets/logos/[email protected]'
96: '/assets/logos/[email protected]'
120: '/assets/logos/[email protected]'
144: '/assets/logos/[email protected]'
180: '/assets/logos/[email protected]'
512: '/assets/logos/[email protected]'
1024: '/assets/logos/[email protected]'

# 9. Site navigation
navigation_header:
- title: Home
url: /
- title: Elements
url: /elements/
- title: Blog
url: /blog/
- title: Categories
url: /categories/
- title: Search
url: /search/
- title: Fork Alembic
url: https://github.com/daviddarnes/alembic
- title: Get Opticks
url: /get-opticks/
- title: Community
url: /community/
-

navigation_footer:
- title: Created by David Darnes
url: https://darn.es
- title: Created by the Opticks Team
url: https://www.opticks.org

social_links: # Appears in sidebar. Set the urls then uncomment and comment out as desired
Twitter: https://twitter.com/DavidDarnes
LinkedIn: https://www.linkedin.com/in/daviddarnes
GitHub: https://github.com/daviddarnes
link: https://darn.es
GitHub: https://github.com/opticks-org
Twitter: https://twitter.com/opticksProject
Facebook: https://www.facebook.com/opticksproject/
link: https://www.opticks.org
RSS: /feed.xml

sharing_links: # Appear at the bottom of single blog posts, add as desired. The value can be 'true' or the desired button colour
Expand Down
Binary file added assets/Opticks3ScreenShot.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
66 changes: 66 additions & 0 deletions community.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
---
title: 'Opticks Community'
feature_text: |
## Why Should I Get Involved?
Opticks is an free and open source application. The best part of any open source project is the community, so why not join in? There are a variety of ways to get involved.
---

## I'm a Scientist/Analyst/End-user, How Can I Get Involved?
### Step 1: Connect
First, you have to connect to the Opticks community and here's how:

* Download the software, that's a good start.

* Have a question?

- Use our [e-mail list](/Mailing-Lists) to ask

- Jump into our real-time chat and ask

* Report any bugs you run across

* Is Opticks missing something? Tell us about it and put in a new feature request.

* Follow the latest developments

- Subscribe to the latest announcements using any RSS or Feed Reader, here is our Feed

- Or have the latest announcements e-mailed to you

- Come back and check out the Roadmap to see the future direction of Opticks.

* Follow the rest of the community

- Subscribe to the latest Opticks related blogs using any RSS or Feed Reader, here is our Feed

- Or have the latest blog postings e-mailed to you

### Step 2: Collaborate
Now that you've connected, you can help grow and support the opticks community, here's how:

* Answer questions. It's one of the easiest ways to give back and one of the very best ways.

- You can answer questions on the e-mail list.

- Or the real-time chat

- Or Both.

* Tell your friends

- If you have a blog or start a blog, let us know and we can add your blog to the Opticks Spectrum, a collection of Opticks community blogs. If you want your blog added, please contact Thomas Fordon [email protected].

* Help anyway you can

- Have some sample data? Why not donate it to the community?

- Have some free time? Why not test the release candidates and let us know what problems you find?

- Know how to write documentation? Why not help improve the documentation and make it even better for the next new user?

## I'm a Programmer, How Can I Get Involved?
* First, check out the above section for ways to get involved. It's a great list of ways to get involved that applies to everyone.

* Write an extension. Check out the Opticks Extension Development for more details on writing an extension.

* Fix an open bug or implement a new feature request. Check out Opticks Development for more details.
8 changes: 8 additions & 0 deletions get-opticks.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
title: 'Get Opticks'
---
# Latest Release
You can download binaries and source code for the latest release and view the changelog at [GitHub Releases](https://github.com/opticks-org/opticks/releases)

# Building from source
Instructions for building from source are in the [Code/BUILDING.md](https://github.com/opticks-org/opticks/blob/master/Code/BUILDING.md) file in the source tree.
29 changes: 28 additions & 1 deletion index.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,5 +4,32 @@ feature_text: |
## Opticks
A multi-platform electronic light table (ELT)
---
{% include figure.html image="/assets/Opticks3ScreenShot.jpg" %}

# Welcome to Opticks

Opticks is an expandable remote sensing and imagery analysis software platform that is free and open source. If you are interested you can learn about the [history of Opticks](#history-of-opticks).

If you've used commercial tools like: ERDAS IMAGINE, RemoteView, ENVI, or SOCET GXP, then you need to give Opticks a try. Unlike other competing tools, you can add capability to Opticks by creating an extension. Opticks provides the most advanced extension capability of any other remote sensing tool on the market.

## Features
* Free and open source
* Supports the following file formats: NITF 2.0/2.1, GeoTIFF, ENVI, ASPAM/PAR, CGM, DTED, Generic RAW, ESRI Shapefile, HDF5, AVI, MPEG, JPEG, GIF, PNG, BMP
* Zoom, pan, rotate spatially large datasets
* Quickly layer GIS features, annotations, results, and other information over your data to provide context
* Many image display controls such as colormap, histogram, transparency, etc.
* Support for datasets larger than four gigabytes
* Analysts can quickly combine steps using graphical wizards
* Support for processing data in its native interleave of BIP, BSQ or BIL
* Get extensions to drop in new capability.

## History of Opticks

### Backstory
Opticks was originally developed by [Ball Aerospace](http://www.ballaerospace.com/) for the US Air Force, specifically the National Air and Space Intelligence Center (NASIC) starting in the Spring of 2000. It was originally created for hyperspectral analysis, but was designed to be easier to use than ENVI, the tool of choice for researchers at the time. Opticks is meant to be used for non-literal exploitation as opposed to geospatial imagery analysis performed by tools such as [GRASS](http://grass.osgeo.org/) and [QGIS](http://www.qgis.org/). Ball Aerospace and the Air Force started working jointly in 2006 to release the core application into the open source, excluding some of the processing algorithms. This was accomplished to [great fanfare](http://www.ballaerospace.com/page.jsp?page=30&id=279) in December 2007. Both Ball Aerospace and the Air Force continue to support this open-source effort.

Since the original open-source release of Opticks, Ball Aerospace and the Air Force have worked to release some previously closed-source Opticks extensions. Specifically, the IDL Scripting and Spectral Processing extension were transitioned from closed source extensions and brought out into the open source. In a demonstration of our commitment to open source, the Python Scripting extension was developed as open source from day one.

### Where did the name come from? Isn't it mis-spelled?
We were looking for a name that was unique and easy to remember. We also wanted it to have something to do with what the application does, meaning imagery analysis. Someone mentioned that [Isaac Newton's original book on optics and refraction of light](http://en.wikipedia.org/wiki/Opticks) was called [Opticks](http://en.wikipedia.org/wiki/Opticks). So, we decided that would be a pretty good name, because who doesn't like Isaac Newton. So, that's how we ended up with the name. And as you can now see, it is not mis-spelled.

Foo bar baz ack

0 comments on commit c978535

Please sign in to comment.