Geodata Pixel User Manual¶
Introduction¶
Geodata Pixel is a solution for efficient image management. With Geodata Pixel, you get a common place to upload, store and structure image data, making it easy to find images based on time and place. The solution consists of an upload client, an upload API and a feature service.
The solution offers sharing mechanisms based on ArcGIS and provides opportunities for both internal and external sharing when needed. Safe storage of photos is secured and anonymization to sensitive data is included.
Access to the solution¶
The solution is web-based with the following structure: https://geodatapixel.no/{tenant}.
Where {tenant} is your organization's tenant ID. Contact your administrator for your specific tenant URL.
Access to the solution is user controlled with e-mail as username and a personal password.
User interface¶
When you log in to the solution, you will be taken to a landing page with an overview of your own projects and projects that have been shared with you. An overview of the projects can be found in the right-hand menu in the project list. In the left menu, you will see details of the project or data collection that is selected. You can also filter content by using search or based on image type. The map view in the middle shows you an overview of all projects, or the polygon of the selected project or data collection.
Projects¶
The data model in Pixel uses project as the main element. New projects are set up by entering a name and description, as well as proving a polygon for the project. This polygon will be the project's outer frame and will be part of the validation when uploading new elements to the project. If you are not interested in validating the location of the uploaded elements, you can choose to draw a polygon covering the entire country.
Project list¶
In the left menu, you will find an overview of available projects that you have created yourself or that have been shared with you. Each project has a name and a number for how many projects and data collections they hold.
Tap the name of a project to select it and see its sub-project or data collections.
Create new project¶
To create a project, select the Create new project button in the bottom of the project list
You will now see a dialog to fill in the following information about the project:
- Project Name
- Project description
Press the button draw project area to define the polygon of the project. You can use the mouse wheel to zoom or click and hold the left mouse button to pan the map. Click the left mouse button once to draw a break point to the polygon. Exit by closing the polygon in the first point or double click with the left mouse button.
Figure 1: Drawing of polygon for project area. The image on the left shows the stage when the penultimate breaking point is in place. The image on the right shows how the polygon can be completed by hovering the mouse cursor over the first breaking point. The orange symbol shows that the polygon is complete.
You now get a polygon for your project. You can drag the orange boxes to adjust the polygon.
Once you are satisfied with the information and polygon for your project, click the Save button. A new project is now created in the project list.
All projects can have two types of sub-elements: Sub-project and data collections. The number of sub-items is shown in parentheses to the right of the project name.
Subproject¶
To further divide a project, you can create one or more subprojects. A subproject is created by giving it a name and description, as well as defining a polygon that shows the extent of the subproject. Just like the main project, the subproject must be validated based on a polygon. Subprojects can be nested three levels deep
To create a new sub-project, follow these steps:
- Click on the three dots next to the project to display the menu options.
- Select Create Subproject.
- Fill in the necessary information about the subproject such as name and description.
- Draw a polygon to define the area of the subproject.
You now have a subproject in the project list.
Metadata for a project¶
Details of a project will be visible in the details field on the left side of the solution when a project is selected in the project list.
If you select a data collection from the project list, you will see the details for the selected data collection in the details box.
Open a data collection¶
To open a data collection, you must first select a data collection from the project list. Next, press the open button from the dialog box in the left menu. You will now see the overview page for the data collection.
Edit details for a project or data collection¶
Tap the pencil icon to edit the details of a project or data collection. You can now change the following:
- Name of the project or data collection
- Description
- Tags
Tags are used, among other things, to search for content. Add relevant tags that describe the project, area or content.
Remember to press the save button when you're done.
Delete a project or data collection¶
To delete a project or data collection, you must first select the one to be deleted from the project list. You can then open edit mode for your project or data collection by clicking the pencil icon. Then click the delete button.
Data collection¶
A data collection is a collection of uploaded photos. These can be created directly below the project level, in a sub-project, or both. Data collection are flexible and can be adapted as needed.
It is possible to upload multiple images to an existing data collection at any time. To create a new data collection, follow these steps:
- Click on the three dots next to the current project or sub-project to display the menu options.
- Select Create data collection.
- Fill in the necessary information about the data collection, such as the name and description.
- Select the data type from the drop-down menu. The following data types are supported
- Image (image), normal image data, jpeg, png etc.
- Raster (raster), raster data such as GeoTIFF, JPEG2000, etc.
- RGB (raster), raster data with three or four bands, uint8.
- DTM (raster), Digital Terrain Model data, single band, float32/float64.
- DSM (raster), Digital Surface Model data, single band, float32/float64.
- Tap the Save button when you're ready.
Data type seperation
A data collection can only hold images of a single data type.
Creating a raster data collection¶
When you choose a raster data collection (Raster, RGB, DTM or DSM), you will be asked to select or define some additional settings or rules for the raster data collection. These rules exists to ensure some consistency in the raster data that is uploaded to the data collection. The rules are as follows:
- Spatial reference ID (SRID)
- This is the expected spatial reference ID for the uploaded raster data. Also known as EPSG code, this is a unique identifier for the coordinate system.
- This is optional for all raster data collection types.
- If specified, all the rasters uploaded to the data collection must have the same SRID.
- Data type
- This is the expected data type for the uploaded raster data. The data type is the type of data stored in the raster, such as integer, float, etc.
- Available data types are:
- uint8 (unsigned 8-bit integer)
- int16 (signed 16-bit integer)
- float32 (32-bit floating point)
- float64 (64-bit floating point)
- uint16 (unsigned 16-bit integer)
- uint32 (unsigned 32-bit integer)
- uint64 (unsigned 64-bit integer)
- int32 (signed 32-bit integer)
- int64 (signed 64-bit integer)
- int8 (signed 8-bit integer)
- This is optional for the Raster data collection type.
- If specified, all the rasters uploaded to the data collection must have the same data type.
- Must be uint8 for RGB
- Must be float32 or float64 for DTM/DSM
- Cell size
- This is the expected cell size for the uploaded raster data. The cell size is the size of each pixel in the raster data, measured in the units of the coordinate system.
- This is optional for all raster data collection types.
- If specified, all the rasters uploaded to the data collection must have the same cell size.
- Format
- This is the expected format for the uploaded raster data. The format is the file format of the raster data, such as GeoTIFF, JPEG2000, etc.
- Available formats are:
- GTiff (GeoTIFF)
- PNG
- JPEG
- MRF
- PDF (Geospatial PDF)
- This is optional for the Raster data collection type.
- If specified, all the rasters uploaded to the data collection must have the same format.
- Must be GTiff for DTM/DSM
- Must be GTiff or JPEG for RGB
- Band count/Number of bands
- This is the expected number of bands for the uploaded raster data. The band count is the number of separate data layers in the raster data, such as red, green, blue, and alpha channels.
- This is optional for the Raster data collection type.
- If specified, all the rasters uploaded to the data collection must have the same band count.
- Must be 1 for DTM/DSM
- Must be 3 or 4 for RGB
Technical details
For a more technical detail see the Python Pixel Client Documentation
| Raster Otions | RGB Options | DTM/DSM Options |
|---|---|---|
![]() |
![]() |
![]() |
Uploading data to a data collection¶
While there are more than two data collection types, the two main types are images and raster data.
The main difference is that image data is points on a map with an image attached, while raster data is a raster image that covers an area on the map.
There are differences to the restrictions for the two data types, so it is important to select the correct type when creating a data collection.
Adding photos to an Image data collection¶
To upload photos to a data collection you have created you must first select the data collection in the project list. You will then see details related to the data collection in the left menu.
In the details dialog box you will find metadata for the data collection and information on how many photos have been uploaded. After first creation, this will be zero.
Tap the upload button to upload photos. You will now be directed to an upload page for selecting files. Drag and drop the files into the white box on the screen or click on the text "click here to choose files" to select files from the file explorer.
Here you can specify the type of images you will be uploading. The available types are:
- Generic Image (default) - This is the default type for images that do not fit into any of the other categories.
- 360 Image - Images taken using specialized cameras that provide 360-degree spherical surround views.
- Horizontal Image - Images where the exposure is approximately parallel to the ground and pointed to the horizon.
- Oblique Image - Images where the exposure is at an angle (at about 45 degrees) to the ground so the sides of objects can be seen.
- Nadir Image - Images where the exposure is nearly perpendicular to the ground and looking straight down. Only the top of objects can be seen.
- Inspection Image - Close-up images of assets (less than 5 meters from the camera).
You can upload multiple files at once.
Once you've loaded all the files click the confirm button to continue.
You will now see a display page for publishing the images. In the left menu, you get an overview of all the photos that have been uploaded. If you desired, you can overwrite the location of the images by clicking on the edit location button indicated by a mapmarker with a pencil. This will enable you to place a new location for the image on the map in the right menu. In the middle you get a view of the selected image. You can change which image is selected from the list in the left menu.
On the right side of the application, you can view metadata for the selected image. You can expand the overview by pressing the Show EXIF button. On the right side you will also find a dropdown menu for updating the image type for the selected image. At the bottom of the right menu, you will first see an overview map for all the images that have been uploaded. When you select an image from the left menu, you will see the location and orientation of the selected image.
Add more or delete images¶
At the bottom of the left menu, you can choose to delete individual images or add more using the buttons delete selected and add more files.
Images that aren't validated¶
If any of the images were not validated, you will receive a warning for those images. These may be images that are missing metadata for the location of where the photo was taken. This can be corrected by the Location button, and you can manually set the location using the map down in the right corner.
Manage metadata¶
In the left menu you can select multiple images and click the "Bulk override image metadata" button to change the metadata for all selected images at once. Here you can select map exif fields to Geodata Pixel metadata fields or add you own additional metadata fields. This is useful if you want to add override certain metadata for multiple images or add additional metadata to the images.
On the right side you can update the metadata for single images as well. When updating metadata for a single image, you will see the actual exif metadata available for the image.
Upload data collection¶
Tap the Upload button to upload all the images to save them in the selected data collection.
At the top of the application, you'll see a status for uploading process. Once all the photos are uploaded and processed, tap the button Open data collection to move on.
Upload rasters to a Raster data collection¶
If you have created a raster data collection (Raster, RGB, DTM or DSM), you can upload raster data to the data collection. For this example we've created a RGB data collection with these rules:
- Format: GTiff
- Data Type: uint8
- Number of Bands: 4
When selecting files for upload, select all the files that are part of a single raster dataset. This can be a single GeoTIFF file or multiple files that together form a raster dataset. We call these extra files support files. The support files can be any of the following:
- *.tfw (GeoTIFF World File)
- *.pgw (PNG World File)
- *.jgw (JPEG World File)
- *.prj (Projection file)
- *.aux.xml (Auxiliary XML file)
- *.ovr (Overviews file)
- *.xml (XML metadata file)
- *.idx, *.pjg, (MRF index and data files)
In the sample below, the support files are recognized to be a part of the raster dataset and will be uploaded together with the main raster file. The raster upload page displays the extent of the raster dataset on the map. It will not display the data due to the complexity of raster data formats. Press the Upload button to upload the raster dataset to the data collection.
Open Image data collection¶
Once the images are saved, you get an overview page where you can review the content of the data collection. In the left menu, you will see metadata for the data collection and a map with an overview of all the images, or the location of a selected image. In the image data dialog box, you can add tags to make the image more searchable in the application.
It is also possible to update the image type for the images in the data collection. This can be done by selecting the image type from the dropdown menu in the left menu.
A list of image metadata is also shown on the left side.
In the right menu, you have an overview of all the photos that have been saved. You can use the buttons at the top of the menu to change the content of the list.
Bulk edit images¶
At the bottom of the right menu there is a button that allows for bulk editing selected images. For now this is limited to changing the image type for all selected images as well as adding tags to all selected images.
Processed image type¶
Select whether original or processed images will be shown
In the top of the list of uploaded files, there is a dropdown menu where you can select which type of images you want to see. For now, you can choose between Original and Blurred images.
If there are images that have sensitive information such as license plates or people, the application will create a censored version of the image. These appear in the list of processed images. Tap an image with '
Filter by map extent¶
If you are interested in viewing images within a specific area, you can use the Filter by Map Extent button.
Zoom and pan to the desired area in the map section in the bottom left menu.
The list in the right menu will then be filtered to only show the images that are located within the selected map view.
Open Raster data collection¶
Once the rasters are saved, you get an overview page where you can review the content of the data collection. In the left menu, you will see metadata for the data collection and the information about selected raster. On the right menu, you will see an overview of all the rasters that have been saved in the data collection.
The raster can be visualized in the webapplication if the uploaded imagery is a COG Cloud Optimized GeoTIFF or if its optimized which is possible if you click the Optimize rasters button in the bottom right corner.
Optimize rasters¶
Optimization of rasters requires optimized_raster plugin
See note about plugins in Pixel for more information.
When you have uploaded rasters to a raster data collection, you can optimize the rasters if you want the imagery to be published in an image service or download the optimized version for your own use. The optimization will create a Cloud Optimized GeoTIFF (COG) from the uploaded raster data. This is a requirement for publishing the raster data in an ArcGIS Image Service.
To optimize all the rasters in the data collection click the Optimize all rasters button. Then the optimized rasters will be created as pending tasks. To run the optimization, you must click the Run all pending button. This will start the optimization process for all rasters in the data collection. The status of each optimized rasters will be shown in the list of optimized rasters. Valid statuses are:
- Submitted - The optimization task has been submitted and is waiting to be processed.
- In Progress - The optimization task is currently being processed.
- Completed - The optimization task has been completed successfully.
- Failed - The optimization task has failed.
Press the Refresh button to update the status of the optimization tasks. When the job is completed, a Download button will appear for each optimized raster. You can click this button to download the optimized raster as a Cloud Optimized GeoTIFF (COG). If you go back to the data collection overview page, you will se that it's now possible to view the raster in the web map.
Apply Nearblack¶
If the rasters in the data collection is compressed (usually JPEG) and has 3 bands its very likely that the raster will have artifacts in the background/border of the image. Optimization of rasters has an option to apply a Nearblack algorithm to the rasters. This will remove the artifacts in the background and make the border and edges of the raster more visually appealing. You can choose the colour (black or white) depending on the pixel values in the background of the raster (white is 255, black is 0). The nearblack algorithm will attempt to fill out the pixels in the "near(white/black)" areas with the selected colour.
Code samples for optimizing rasters
Code samples for optimizing rasters can be found in the Python Client Documentation.
Tags¶
Geodata Pixel has a data model that eases the storage of metadata on all elements. We call these tags. Through the application, this can be added and searched for. The element tags are also available on all the API services, so they can be used further in other solutions.
Automatic tagging¶
When images are uploaded to an image collection, a resizing and blurring of the images is conducted. At the same time, an automatic tagging is also done based on machine learning. This is a parent tagging that finds objects such as cars and boats, which is added to the images. When uploading through the API, you can also automatically tag images with the tags you want.
Manual tagging¶
All elements of the solution can be manually tagged. Projects and subprojects are tagged by editing the respective item in the edit menu on the main page. Images can be tagged by accessing the respective images in the image collection.
Attachments¶
Geodata Pixel allows you to attach arbitrary files to projects and data collections. This allows you to store additional information related to the project or data collection, such as reports, documents, or other relevant files.
The attachment interface is accessible from the project or data collection details window of the main page.
From the attachments interface, you can upload by clicking the "Upload"/"Upload more" button. This will open a dialog where you can drop files or click to select files from your file system. You can upload multiple files at once.
You can remove files with the X button next to each file in the list or empty the list by clicking the "Empty list" button.
To finalize the upload, click the "Upload files" button. This will upload all the files in the list to the project or data collection.
After uploading one or more files, you will see them listed in the attachments interface. You can click on the file name to edit name and/or add a description of the attached file. On the right side you can download the file or click the trash can icon to delete the file from the project or data collection.
Administration¶
From the header you can access the administration interface by clicking the "Admin" button. This will take you to the administration interface where you can manage users, published services, project access and data harvesting.
Data harvesting¶
Geodata Pixel allows you to configure automatic harvesting of images from your own ArcGIS Feature Services.
To begin you must first select a data collection to harvest into. This is done by selecting the data collection from the list to the right of the navigation menu.
The data collections are listed under their respective projects. For nested projects, project names are joined with an arrow (->) to indicate the hierarchy.
Once you have selected a data collection, you can create a new harvester by clicking the "Create new harvester" button.
Create a new harvester¶
When you create a new harvester, you will be presented with a multistep form where you can configure the harvester.
- Name and description: Provide a name and description for the harvester.

- Authentication: When setting up the harvester, you need to provide authentication details for the ArcGIS Feature Service. This includes the URL of the service and either credentials (username and password) required to access it or an API key.
When using credentials, you must also supply the url to the endpoint where a token can be generated.
When using an API key, you can optionally provide a portal item ID associated with the API key. This allows us to get the API key expiration information. - Harvest filter: If you want to limit the images that are harvested, you can specify an SQL where clause to filter which images to harvest. You have to test and validate the SQL query before you can proceed. The SQL query must be valid for the ArcGIS Feature Service you are harvesting from.

- Harvest metadata: In this step, you can map the fields from the configured ArcGIS Feature Service to the metadata fields in Geodata Pixel. This allows you to ensure that the harvested images have the correct metadata associated with them.

- Extra fields: In the last step, you can configure a field that Pixel will write to on the Feature Service when the images are harvested.
You can also add additional metadata that does not fit the standard metadata fields. Fields can be added by selecting them from the "Extra fields" dropdown menu.
Manage harvesters¶
After you have created a harvester, it will be listed in the administration interface. A table will show you a quick overview of the harvesters with some basic information such as the name, description, and status of the harvester.
You can start and stop the harvester by clicking the "Start" or "Stop" buttons in the table.
For more indept management of the harvester, you can click the "Manage" button indicated by a pencil icon.
The details page for the harvester will show you the current harvester configuration, including:
- Authentication details.
- Harvest filter.
- Metadata mapping.
- Running, completed and failed tasks
From this page, you can edit most of the configuration of the harvester.
Pointing to another service
Since the ArcGIS Feature Service is a major part of the harvester this cannot be changed. If you need to change the ArcGIS Feature Service, you will have to create a new harvester.
Deleting the service
Pixel uses a a task log with the external and internal ids of each feature to keep track of harvested features. The task log is connected to the harvest service and will be deleted with it, so deleting and recreating a harvest service will re-harvest the features.
ArcGIS Services¶
All images and associated data uploaded to Geodata Pixel can be made available through ArcGIS services (Feature and Image). This is done by clicking on the Published Services button in the top menu of the application.
Superuser Privileges Required
Only superusers can create and manage ArcGIS services. See the User Management section for more information on user roles and permissions.
Overview of published services¶
When you select "Published services", you get an overview of existing Feature and Image services.
Switch between the service types using the tabs at the top of the overview table.
Which services are displayed depends on the user's access level. The user can only see services that contain data collections they have at least view-access to.
Information about the Services:
- Service name and description: This is information associated with each service.
- Data Collections: This column shows the number of data collections included in the service.
- Status: This column shows the current status of the service
- new - The service has been created but not yet started.
- running - The service is currently running and available for use.
- stopped - The service has been stopped and is not currently available for use.
- failed - The service has encountered an error during startup, update or stopping.
- out_of_sync - The service has been updated, but not refreshed to reflect the changes.
- updating - The service is currently being updated, usually starting, stopping or refreshing the service.
In the top right corner of the page, there are options to create new and delete existing services. In addition, each service has a choice for management.
Accessing Secured Services¶
Access to a secure service
If the service is configured with GDO user access control, you can generate tokens for accessing the service through
Geodata Online token service. You can use this token either through the token query parameter, Authorization or X-Esri-Authorization header.
Examples with cURL:
// With X-Esri-Authorization header
curl -X GET "<SERVICE_URL>" -H "X-Esri-Authorization: Bearer <YOUR_ACCESS_TOKEN>"
// With query parameter
curl -X GET "<SERVICE_URL>?token=<YOUR_ACCESS_TOKEN>"
// With Authorization header
curl -X GET "<SERVICE_URL> -H "Authorization: Bearer <YOUR_ACCESS_TOKEN>
Feature Services¶
Feature services in Pixel are used to expose images as point features through a known ArcGIS Feature Service. Each image is represented as a point feature with associated metadata. This allows for easy integration with other GIS applications and services.
Create new feature service¶
To create a new feature service, press the button.
Fill in the required information for the service:
- Service name: name of the service.
- Service description: description of what the service holds or similar.
- Access: Manage users who have access to the service. You can choose whether the service should be open to everyone or protected with access control. If the service is protected, you must select a Geodata Online user (GDO) from your organization to have access. In ArcGIS Online or ArcGIS Portal, this user must be provided to refer to the service in the solution. To add new GDO users as an option, you must contact Geodata.
- Choose whether to include a project layer in the service. if included, it will expose the parent projects of any image exposed by the service.
- Choose whether to enable oriented imagery capability for the image layer in the service.
- Select data collections to include in the service. All processed images in included data collections are exposed.
- Select the image version to include in the service. You can choose between original images or blurred images.
- There is an option to select which fields to include on the Image layer and if enabled, the projects layer. Available fields are listed in the dropdown menu. You can select a subset of these or check the "Include all" checkbox to include all the fields.
- If selecting a subset make note of the required fields that must be included. An updated list of required fields will be shown above the dropdown menu.
Required fields
There are different required fields for layers depending on whether the layer has enabled oriented imagery or not. These are listed on the publishing page. Attempting to publish a service where one or more layers are missing required fields will fail.
About Oriented Imagery
Oriented imagery funtionality has some limitations as of now. - Missing viewcones for standard images. - Ureliable map-image location tool (click in image and getting correlationg point in map, the reverse) This is expected to improve in the future
Oriented Imagery publishing
When publishing an oriented imagery enabled feature service, it's recommended to not include the project-layer. Otherwise, when adding this to ArcGIS Online/Portal for arcgis as an item, the oriented imagery capability of the image layer will not be recognized.
Service administration¶
To manage a feature service, press the manage button for the desired service.
In the Geodata Pixel service management interface, there are several options based on the status of the service. You can start or stop the service using the relevant buttons. The service address is displayed in the URL field, and you have the choice to copy this address. The table shows which data collections are included in the service. To make further changes, click the edit button in the top right corner.
Editing services¶
When you're in edit mode, you can make the following changes:
- Change service name and description: Update the information associated with the service.
- Include project layers: Specify whether the project layer should be part of the service by selecting a checkbox.
- GDO users: Manage users who have access to the service. You can choose whether the service should be open to everyone or protected with access control. If the service is protected, you must select a Geodata Online user (GDO) from your organization to have access. In ArcGIS Online or ArcGIS Portal, this user must be provided to refer to the service in the solution. To add new GDO users as an option, you must contact Geodata.
- Change the image version: Choose between original images or blurred images.
- Manage collections: Remove existing collections or add new ones as needed.
- Update the fields included in the service, both for the Image layer and the Project layer.
Image Services¶
Image services in Pixel are used to expose raster (RGB, DTM and DSM data collections) data through a ArcGIS Image Service. This allows for easy integration with other GIS applications and services that support ArcGIS Image Services. Pixel also supports enabling WMS capabilities through the ArcGIS Image Service.
Image service requires image_service plugin
The image service plugin is required to create and manage image services.
The plugin also needs the optimized_raster plugin to be able to optimize rasters for publishing.
See note about plugins in Pixel for more information.
Create new image service¶
Options for image services are
- Service name: name of the service.
- Service description: description of what the service holds or similar.
- Data collections: Select data collections to include in the service. All optimized rasters in included data collections are exposed.
- RGB data collections will be exposed as RGB imagery.
- DTM and DSM data collections will be exposed as Elevation imagery.
- Can only include data collections of the same type in the same service.
- Default service srid: Select the image services default spatial reference ID (SRID). It's a good idea to select a spatial reference that is close to the area of interest for the data collections in the service. This will improve performance when accessing the service.
- Enable WMS Service: Check this box to enable WMS capabilities for the image service.
- WMS Title: Title for the WMS service.
- WMS Abstract: Abstract/description for the WMS service.
- Supported WMS Srids: Select which spatial reference IDs (SRIDs) the WMS service should support. You can select multiple SRIDs if needed. Default will be WGS 84 (EPSG:4326) and the default service SRID.
- GDO Users: Manage users who have access to the service. You can choose whether the service should be open to everyone or protected with access control. If the service is protected, you must select a Geodata Online user (GDO) from your organization to have access. In ArcGIS Online or ArcGIS Portal, this user must be provided to refer to the service in the solution. To add new GDO users as an option, you must contact Geodata.
Optimize rasters
image services requires all the rasters in the data collections to be optimized see Optimize rasters for more information.
Image service administration¶
To manage an image service, press the manage button for the desired service. This page shows an overview of the service configuration and status. You can start, stop, delete or edit the service using the relevant buttons. The service address is displayed in the URL field. The table shows which data collections are included in the service.
- Edit: Click this button to make changes to the service configuration.
- Stop service: Click this button to stop the service if it is currently running.
-
Refresh service: Click this button to refresh the service to update the data it exposes.
Data in the service
The data in the services are static at the time of creation or last refresh. If data is added to a data collection that is part of the service, the service must be refreshed to include the new data. This happens also automatically every 24 hours.
-
Start service: Click this button to start the service if it is currently stopped or new.
- Delete service: Click this button to delete the service. Only stopped services can be deleted.
The page also includes information about the size of the service. These cannot be changed. If you need to scale the service up for better performance, please contact Geodata.
- Number of replicas: The number of machines the service is running on (horizontally scaled)
- Server size: The size of the machines the service is running on (vertically scaled)
- Valid values are
small,medium,largeandextra_large
- Valid values are
Image Service best practices and how tos¶
Image services in Pixel are built on top of ArcGIS Image Services. There are some reccomendations for using and managing these services.
Image Service Types¶
Pixel will automatically create the appropriate Image Service based on the data collection type.
- RGB data collections will be published as a Processed image service which will just be a simple image service with a single layer.
- DTM and DSM data collections will be published as an Elevation with available raster functions or WMS layers.
- Hillshade, Slope, Aspect, MultidirectionalHillshace, MultiShadeRelief, ShadeRelief (see illustration below)
Collect similar data into the same service¶
When creating image services, it is a good idea to group similar data collections into the same service. Avoid creating multiple image services for data collections with similar characteristics.
For example if you're flying several missions with a drone and collecting RGB imagery over time and area. Split the missions into different RGB data collections, but group all the RGB data collections into the same image service. The image service has capabilities to filter the data based on data collection names, project names and tags. The same is true for DTM and DSM data collections.
Supported image service clients¶
Pixel image services are supported by ArcGIS online and ArcGIS Enterprise. Can be used through web maps, ArcGIS javaScript API.
Image server can be added to ArcGIS Pro through the "Add Data" button in the Map ribbon, selecting "Data from Path" and entering the service URL.
If you enable WMS capabilities for the image service, it can be used in any client that supports WMS. This includes QGIS and other open source GIS clients.
How to filter data in the image service¶
When adding the image service to a web map or other client, you can filter the data based on data collection names, project names and tags. This allows you to only show the data that is relevant for your use case.
The WMS only shows a single layer with all the data in the service. To filter the data you can use the QUERY or IMAGES parameter in the WMS request. For more information see Filtering images in WMS requests.
User management¶
From the administration interface, you can manage users in your organization. This includes adding new users, editing existing users, and deactivating users.
Permissions to manage users
Only superusers can manage other users.
Add new user¶
To add a new user, click on the "Add user" button in the user management interface. Fill in the required information for the new user, including their email address, first name and surname, password user type and if it is active. Once you have entered all the necessary information, click the "Save" button to create the new user.
User types are defined as follows:
- Viewer - Read only access to the application, can view projects and data collections but cannot create or edit them.
- Editor - Access to create and edit projects and data collections, can also view them.
- Superuser - Full access to the application, can manage users and settings.
User types and permissions
User types are application-level permissions. users with the viewer user type cannot do create, update and delete operations even if they are granted Admin role on projects Superusers have full edit capabilities on all projects, regardless of what role, if any, they have on the project.
Edit existing user¶
To edit an existing user, click on the "Edit" button indicated by a person with a pencil icon on the right side of the users table in the user management interface. You can change the user's email address, first name, surname, user type and if it is active. Once you have made the necessary changes, click the "Save" button to update the user's information.
Project access management¶
Users and roles¶
Access control internally in your own organization is done on the project level. When creating a project, only the user who creates the project will have access initially. If you want to change this, click on "Access" in the navigation menu on the left side of the administration interface.
| User type | Description |
|---|---|
| Admin | Full access to the application, setup of services and administration of users |
| Editor | Access to create and edit projects and data in the application |
| Viewer | Read only access |
Share access to a project¶
As the owner or administrator of a project, you can grant access to the project to other users:
- Select the project to share from the project list.
- Click on the "Add user" button.
- Select a user from the drop-down list.
- Select the user type for the user.
- Click the save icon to save the edits.
Remove user from a project¶
As the owner or administrator of a project, you can remove access to the project for other users:
- Select the project to share from the project list.
- Find the user in the list of accesses that you want to remove.
- Tap the delete icon to delete access for the user.
Integration with Esri products¶
When you create services in Geodata Pixel, these are feature services. These services are primarily supported by Esri products. Whether or not images are supported depends on the specific solutions that you use.
The most common way to make the services available is through your own Portal. This applies to both ArcGIS Online and ArcGIS Enterprise. For more information on how to make services available, please refer to the resources in the table below.
| Resource | URL |
|---|---|
| Using services in ArcGIS Enterprise | Connect to secure services - Portal for ArcGIS | Documentation for ArcGIS Enterprise |
| Using services in web maps in ArcGIS Online | Add layers from a URL - ArcGIS Online Help | Documentation |
| Using services in ArcGIS Pro | Add a web feature layer for editing - ArcGIS Pro | Documentation |
Format requirements¶
Use of metadata in the solution (Exif information)¶
Geodata Pixel uses metadata from the images that are uploaded. Therefore, it is important that the images hold this metadata.
Challenges with metadata¶
Unfortunately, there is no standard for what metadata should look like, and different camera manufacturers have different formats. This can lead to challenges with metadata from your camera. The application supports most known variants, but there may be some formats that lack support.
What you can do¶
If you experience problems with metadata from your camera, you can send Geodata a sample image. Geodata will then quickly add support for this variant in updated version of the application.
API¶
Swagger documentation for the API can be found here: https://prod.api.geodatapixel.no/{customer}/docs where {customer} needs to be replaced with your own Tenant name. This is the same name that you find in the URL when accessing the applications upload client.






































