Showing posts with label GIS. Show all posts
Showing posts with label GIS. Show all posts

Wednesday, July 6, 2011

We are now mobile & spatially enabled!

What are two things that you think of when someone says mobile GIS? To me, it is pretty obvious... mobile, and spatial. Well guess what, our Mobile GIS blog is now both mobile and spatial. Hooray!

Take a look at out blog from your mobile device. Very pretty!

I have also started defining the location of the blogs. What this means, I don't really know, but I have done it anyway :)

Thursday, December 23, 2010

Height Enabling ArcPad

Height enabling features (i.e. collecting 3D x,y,z positions) in ArcPad is simple. You just need to make sure that you have (1) your data set up correctly; and (2) correctly configure your hardware.

Configuring your data
When creating a shapefile or feature class, you must specify that you want to z enable it. From within ArcGIS, this is simply a matter of selecting the "Coordinates include Z values. Used to store 3D data" option on the first page of the "Create new feature class" dialog.
In ArcPad, when creating a new shapefile, you should select the feature type as "PointZ".

Unfortunately, there is no way of z enabling a pre-existing, non z enabled feature class. You must create a new one, import the fields from your previous feature class, then import all of the features across. In this case, any features already captured will not have valid z values. You will need to update these.

Any features from these datasets that are collected within ArcPad will automatically be assigned a z height value at the time of creation. If you digitise a point, a z height of 0 will be assigned. You can easily change this value manually via the geometry page of the edit form if required. If you capture the features using a GPS or laser rangefinder, then provided they are configured correctly to output height coordinates, then these will automatically be assigned to the feature.

Configuring your hardware
This part will probably either be very easy, or a little bit tricky. Basically what you want to do is to make sure that whatever hardware you are using (GPS, laser rangefinder) is outputing data that includes height information. Most GPS units will do this by default. So unless you have gone in to your GPS and altered the messages that are being sent from it, you should be pretty right. If you have played around with the GPS, you will need to dig out your manual and make sure that the height information is being exported correctly.

With laser rangefinders, it should be as simple as making sure that some form of height measurement is being read and exported to ArcPad. For example, you should read the slope distance and inclination to the target. If you export only the bearing and the horizontal distance, then ArcPad has no way of knowing what the change in height from your position to the target actually is.

Accessing the height information
Accessing the height of your points from within ArcPad is also simple. When you create or edit a point, you can switch to the Geography page, which will show the coordinates of the point (including the z height). If you have a line or a polygon layer, it will list all of the coordinates of all of the vertices of that feature.
You can do the same when identifying a feature.

From within ArcGIS, it is not quite so simple. You must add the feature class to ArcMap, start an edit session, use the Edit Tool from the Editor toolbar (the black arrow), double click the point, then open the "Edit Sketch Properties" window. This will list the X, Y, Z coordinates of the selected point (or vertices of a line or polygon).

Another way of viewing this information is to add a float (or double) field to the feature class, then use the "Calculate Geometry" tool in the table view in ArcMap, to calculate the z coordinates of each feature and store that to a field.

Friday, February 27, 2009

ArcPad 8 is on its way!


ESRI has announced that ArcPad 8 will be released in the first quater of 2009. The new version will see an entirely revamped user interface, featureing an Office 2007 type feel with ribbons and quick launch toolbars. As a bonus, ArcPad Application Builder, the development framework for ArcPad, will be included with every ArcPad 8 license.

Other highlights of the new release include:
  • An ArcGIS Server Extension to allow direct synchronisation to ArcGIS Server from ArcPad
  • An improved, more intuitive GPS interface that takes up less screen real estate
  • An enhanced ArcPad Data Manager Extension, which will simplify the process of checking data out and in of the Geodatabase.
If you have any questions at all about the new release, training (for both ArcPad and Application Builder), give us a call on 03 6223 4919.




Stay tuned for further updates regarding the release date and pricing structure.

Tuesday, January 6, 2009

Rugged and Non-Rugged Field Units

Due to the nature of fieldwork, Mobile GIS hardware is often subject to harsh treatment from the elements and accidental knocks by users. For this reason ruggedized mobile devices are becoming an increasingly popular choice amongst Mobile GIS users.

There are a variety of mobile devices that come in a rugged format, which are classified with an International Protection code for enclosures (IP Rating). An explanation of the IP Rating classification system can be found at the Wikipedia webpage: http://en.wikipedia.org/wiki/IP_Code

Examples of rugged units include:
- Rugged Field PDA Units: TDS Nomad Series
- Rugged UMPC/Tablet Units: Getac E100, Xplore series
- Rugged Laptop Units: Panasonic Toughbook
- Rugged Digital Cameras: RICOH Caplio 500SE

An additional option available to users is to purchase a non-rugged unit and then a separate enclosure/case that will ruggedize your device for fieldwork. Cases produced by manufacturers such as Otterbox can transform standard mobile devices to droppable, dustproof, waterproof units at a fraction of the cost of purchasing a fully ruggedized unit.

Please contact RIA Mobile GIS for further information on the purchase and optimisation of your Mobile GIS System.