By Scott Mueller
On 17, Dec 2014 | In Mapping Solutions | By Scott Mueller
Recently, I was given the opportunity to travel to Wichita, Kansas and be interviewed for GIS Analyst position with Enertech. Enertech assists natural gas and oil distribution and transmission companies to build public awareness programs for their areas of operations. This small but growing company uses GIS and spatial analysis to build their programs and identify residents of the areas and to gather knowledge of the pipelines surrounding areas.
I flew out of Milwaukee, to Chicago, and onto Wichita on a Sunday. After landing, the President of Enertech, Mark Allen, picked me up at the airport and we sat down for dinner, talked football and the city of Wichita. It was a nice relaxing conversation that took my nerves off the big day ahead. After dinner, I was dropped off at the Hotel in downtown Wichita and relaxed and waited for tomorrow morning for the interview.
Monday morning, I was picked up from the hotel by the Vice President of Enertech, Lisa, and driven to the Enertech office. Here I got to meet all the people that make up the Enertech team and have a brief conversation with all of them before the real interview started. For the interview, Lisa, Mark, and the four GIS people of Enertech sat around a table and discussed my history and skills with GIS and how I could contribute to the team. I was asked questions about my problem solving abilities, data management skills, and spatial analysis background. The team seemed delighted to be able to browse through my portfolio and see a collection of my best works throughout my time at UW-Whitewater.
The interview ended with an hour long test of on a computer, using ArcGIS. Though I was nervous to start the test, my experience working with GIS here at UW-Whitewater had me more than prepared.
As my time and interview in Wichita came to a close, we took a short trip to the new Enertech office that was currently under construction. This new location will be a great place. with more room to move and breath, where the company can continue to expand and grow. We ended the day with dinner with the Mark, Lisa, and the GIS team and a quick tour around Wichita.
I am grateful to be given the chance to see and experience Wichita for a day, and to meet all the people that make up Enertech, a place that I hope I can help expand and grow. Enertech seems like a great company that would fit my personality and be a wonderful location to begin my GIS career and life outside of Whitewater.
We continue to hone our drone flying and mission skills. At our test/training site, we’ve successfully flown a mission with a complete set of imagery along with sufficient ground control to georeference and rectify the imagery. Thanks to Craig Schreiner, UWW campus photographer, for coming out for the afternoon and taking such great photos.
By Eric Compas
On 30, Jul 2014 | In Mapping Solutions | By Eric Compas
We’re proud to announce that Guy Hydrick, Pangea Studios new Program Manager, started his new position today. Guy’s coming to us from Pennsylvania with a masters degree in Environmental Sciences from the University of Manchester, a strong background in local government, and stellar GIS skills. We’re looking forward to integrating him into our operation and seeing what new directions his expertise takes us.
After days of installing and configuring software, we’ve gotten some of our first images and models (taken during our training in Akron, Ohio). Using our post-process imaging software, we stitched together over 200 photos and created a 3D point “cloud” from overlapping images (stereo pairs). As a result, we now have scaled 3D models of our survey and training area.
The photo above shows the stitched 2D image mosaic, and the videos below show the 3D reconstruction using a regular camera and a second with a camera modified to take infrared pictures. This can help us assess vegetation health as well as making 3D reconstructions.
We’re now in the air! As part of our drone project, we traveled to Akron, Ohio, to get flight training from Event38. Six students and Dr. John Frye joined us on the trip to learn the ropes. At the training, we learned how to assemble and do a pre-flight check on the plane, as well as how to launch (a hard hand toss), complete an aerial photography mission, and land the plane manually (it was easier than we thought! All eight of us successfully landed the plane).
Thanks to Joe from Event38 for the great day of training!
For our drone project, we’ve decided to purchase a fixed-wing aircraft, the E384, from Event38, a small company out of Akron, Ohio. Their system is built on top of open source and open hardware APM platform developed by 3DRobotics. The advantages include:
- longer flight times (~90 min) for aerial surveying (relative to quadcopter options)
- great open source mission planning software developed to work with the APM
- decreased hazards from spinning props (the plane is a “pusher” with the prop behind the wings)
- access to the open source community surrounding the APM
- a proven platform for acquiring usable imagery
- easy access to parts for any repairs that may be necessary
- potential for using aircraft as template for building our own from scratch
This spring we were recently awarded a NASA/Wisconsin Space Grant Consortium Research Infrastructure grant to explore the use of low-cost unmanned aerial vehicles (UAVs), or “drones,” for high temporal and spatial resolution imagery. Our plan is to purchase an off-the-shelf system and create imagery for several UW-Whitewater projects including: habitat mapping for an endangered turtle release site, post-storm event imagery, and seasonal changes in-stream debris.
Stay tuned to this channel as we carry out our plans this summer!
This tutorial does not discuss how to connect to a server. Please see our other content for that. Requirements for this are a ArcServer Connection and if you need to be able to edit your maps , all your data must be sourced in a SDE. Don’t forget to register your data store or you will copy all data to the server and waste space.
On 13, Jun 2013 | In Mapping Solutions | By ColonC20
1.) If you are using a print map, you will need to scan in to your compute and save it as a JPG. If you are using a PDF of a map you will need to save it as a JPG (you can simply screenshot or use the snipping tool and save it as a JPG).
2.) In ArcMap, make sure that the Georeferencing Toolbar is on. Customize>Toolbars> Georeferencing (Make sure that there is a check mark next to it).
3.) The Georeferencing Toolbar looks like this:
4.) Then, in ArcMap add the image that you want to georeference by clicking the Add Data button. After you select your image, click the Add button.
5.) Then, after you add your image, click the drop down arrow next to the Add Data button and click Add Basemap and choose one that will be most helpful to you.
6.) Then in the TOC, right click on the image you want to georeference and click Zoom To Layer.
7.) In the Georeferencing toolbar click the Add Control Points icon
8.) Then, find an intersection of roads on the image and click to place the Control Point there.
9.) Next, right click on the basemap in the TOC and click Zoom To Layer. Zoom to the location on the basemap where your image is actually located on the globe. Find the same intersection of roads that you added a control point on the image and add a control point to that same intersection on the basemap.
10.) The image will move to that location. Find two more intersections to add control points (spread them out across the image). If after having a total of 3 control points you feel your image still needs to be aligned, add more control points as necessary.
By Craig Nelson
On 05, Jun 2013 | In Mapping Solutions | By Craig Nelson
While deploying and configuring our newest geodatabase, I was tasked with setting up user login information for each employee on the PANGEA team, rather than simply sharing the superuser login. As someone who worked with creating users, setting up user groups, and granting access/edit/deletion privileges for databases in classes previously, I assumed the task would take a matter of minutes. I was wrong.
Initially, the project seemed to be running quite smoothly. By connecting to our database server via remote desktop, then running the PostgreSQL DBMS Admin client (pgAdmin III), I was able to quickly establish 3 separate user groups (User, Publisher, and Admin). From there, I simply created individual user logins, then added them to their respective groups. Through pgAdmin, I tested to make sure that all Admin users could create, edit, and delete new databases, that Publishers could create and edit, and that Users could only view, but not change, the database. So far, everything was working well.
The issues started once I began to work outside the database server. Through ArcMap, we needed to setup our new server with geodatabases, rather than normal, blank databases. To do so, the ArcMap client needed to access the database server, then upload several tables full of geographical referential data. However, each time we tried running the very simple tool within ArcMap, we’d end up with a connectivity error. After a few hours of troubleshooting these issues, including editing config files to enable ip access and tinkering with several server settings, we eventually discovered the problem through simple ping tests via the DOS command prompt. Our database server’s Windows Firewall hadn’t been configured to allow outside access. In just a few mouse clicks, we enabled access and were back on our way.
After successfully allowing access to our new database in ArcMap, we set up a new geodatabase to begin testing user privileges. However, it seemed that no matter how many privileges we granted both our groups and our users via pgAdmin, not a single account other than the original superuser was able to make any changes to the database due to ownership. We attempted to grant privileges on a group basis, a per-user basis, a per-database basis, and even a per-schema basis, and yet nothing seemed to make a difference within ArcMap. It wasn’t until we contacted the experts at ESRI that we found a solution to our issue.
Rather than granting privileges on a database level through the database server itself, we found that the key to setting up user privileges for ArcMap Geodatabases boiled down to two simple ideas: one, that each user needed their own version of the database schema and two, that privileges in ArcMap are granted on a per-dataset, rather than per-database basis. Now that we have this solution, we have been able to successfully build, deploy, and grant user privileges as planned to geodatabases on a new database server.
In short, the steps to granting dataset privileges for ArcMap geodatabases are as follows:
1) Create a new Login Role through your database server’s DBMS client
2) Grant basic database access privileges through DBMS client
3) Within your geodatabase, create a new schema with corresponding access privileges through DBMS client
4) In ArcMap, connect to your geodatabase via the your superuser (owner) account
5) Once connected, right-click on each dataset, navigate to manage, then privileges, where you can grant SELECT, ADD, EDIT, and/or DELETE privileges to each user.