Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  1. Fotoware Alto
    • Release Notes
    • End-User Manual
    • Solutions
    • Terminology
    • User Guides
    • API Changelog
  2. Fotoware Veloz
    • Fotoware Veloz releases
    • Managing users and groups
    • Configuring archives
    • Configuring workflows
    • Configuring site behavior
    • Navigating and searching to find your assets
    • Working with your assets
    • Editing asset metadata
    • Uploading files
    • Version Control in Fotoware
    • Albums - Creating and sharing collections
    • Placing assets in a Content Management System (CMS)
    • Working with the Fotoware Pro interface
    • Using the Fotoware plugins
    • Consent management
    • User guide to FotoWeb for iPad (Legacy)
    • Picture conferencing with FotoWeb Screens (Legacy)
    • What's what in Fotoware
    • GDPR
    • Activity Exports
    • Example workflows
  3. Fotostation
    • Getting started with Fotostation
    • Viewing, selecting and sorting files
    • Managing your assets with archives
    • Adding metadata to assets in Fotostation
    • Searching for assets
    • Working with your assets
    • Version Control in Fotostation
    • Automating tasks with Actions
    • Configuring metadata fields and editors
    • Configuring Fotostation
    • Configuring Fotostation for multi-user environments
    • Troubleshooting Fotostation
  4. Fotoware Flow
    • About Flow
    • Getting started
    • Flow dictionary
  5. Fotoware On-premises
    • Fotoware On-premises releases
    • Getting started
    • Index Manager
    • FotoWeb
    • Color Factory
    • Connect
    • Operations Center Guide
  6. Integrations and APIs
    • Fotoware Alto API
    • Fotoware Veloz and On-premises API
  7. Fotoware Mobile
    • User guide for Fotoware Mobile for iPhone and Android
    • User guide to FotoWeb for iPad (Legacy)
    • User guide to FotoWeb for iPhone and Android (Legacy)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

Support

Table of Contents

Geo Point overview Geo Point value handling Geo Point field settings
  • Home
  • Fotoware Alto
  • End-User Manual
  • Schemas
  • Fields

Geo Point

19. May 2026

Elaine Foley

Table of Contents

Geo Point overview Geo Point value handling Geo Point field settings

The Geo Point Field has two number fields for adding longitude and latitude values. Applications like Google Maps use this kind of geo-information about a location. In Fotoware Alto, you can only use Geo Point values in Query Filters. 

Geo Point overview 

Icon
Behavior

VIDEO: How Geo Point behaves

Your browser does not support HTML5 video.

The behavior is similar to a single fieldset. 

Limitations Geo points are not accessible from the search. 
Special

The Geo Point consists of two fields: 

  • Latitude (lat)
  • Longitude (lon) 

The underlying schema that groups the two number fields is a system schema called GpsCoordinate. 

Usage in layers

Entering the details on the content after applying the layer that has the relevant Geo Point field created:

 

View in Edit mode of the clickable link:

Fotoware Alto creates this link: https://www.google.com/maps/@47.3938863,8.0433279,17z 
17z is the zoom factor. 

Examples
  • Address
  • GPS
  • Geomarketing

Geo Point value handling

Setup Example Layer: Corporate Information (ID: CorporateInformation) 

Field: Headquarter Location (ID: headquarterLocation)
Fieldpath corporateInformation.headquarterLocation.lon
corporateInformation.headquarterLocation.latthe 
Advanced search for the field or the field value Search: Find Items with Geo values not possible (Solutions)
Use in Display Pattern Display Pattern: Geo Point (Solutions)
Use in the business rule as path & field id

Path: corporateInformation.headquarterLocation.lon
Path: corporateInformation.headquarterLocation.lat

Field: headquarterLocation.lon
Field: headquarterLocation.lat

Returned field value 12.356 
The field itself does not return the combined value. You must get longitude and latitude.

Geo Point field settings

Name

The Name setting is available for various items, for example, fields, schemas, and business rules. This value defines what appears in the interface. You can change the name at any time and translate it into any configured metadata language. To add a translation for the name, select Add.

  • IDs and Names need to be the same or at least have the same meaning.
  • Sentence-style capitalization, for example, Media type and not Media Type.
  • Schema names in plural, for example, products, events, persons, or lists.
  • No numbers at the beginning of the ID (mediaType2 is correct, but not 2MediaType)
 
ID

The ID field is the ID of your field, which is used to link to this field. The field ID is always lowercase. The field's ID is set when creating a new field using camel casing. You need the field ID to configure filters or display patterns. 

The ID is automatically created from the name you insert: 

  • Example: You insert the field name "My NeW fielDs #1 Purpose?
  • Automatic ID: myNeWFielDs1Purpose

You can open the Display Pattern Editor to see the JSON of a Content Item. 

 
Required

The Required field setting determines whether or not an editor must provide a field value before being able to save the Content Item. If a field is required and the user has not provided a value or deleted an existing value,  the item cannot be saved. This value can be changed at any time. You cannot set a field required on a Layer with XMP mappings defined for any field. The Required field setting is unavailable for checkboxes, trigger fields, or dynamic view fields.

Attention: even if the field itself is not required when adding Geo Points, both the longitude and latitude values are required.

UI required The UI required field setting determines whether or not an editor must provide a field value to save the Content Item in the UI. If a field is UI required, and the user has not provided a value or deleted the existing value, the item cannot be saved in the UI. This value can be changed at any time.
The UI required field setting is unavailable for checkboxes, trigger fields, or dynamic view fields.
Include in filters

The Include in filters field setting adds the field as a filter for content (see Channels Configuration), and allows the field values to be edited in the Batch Editor (indexed fields). Fotoware Alto checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit and by testing your common search scenarios - too many values will not automatically result in better search results.

Geo Points work in channel filters, but you should show them as regions or areas. Users may find individual Geo Points in filters to be unhelpful. 

coordinate location

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Display Pattern: Geo Point
  • Display Pattern: Number
  • Display Pattern: Relationship
  • Fieldset
eco-lighthouse-miljøfyrtårn

Company

  • About us
  • Resellers
  • Careers
  • Contact us

Help & support

  • Support center
  • Consultancy
  • Tech partners
  • Fotostation
  • System status

Trust Center

  • Legal
  • Security
  • Sustainability & ESG

Locations

Fotoware AS (HQ)
Tollbugata 35
0157 OSLO
Norway
Fotoware Switzerland AG
Brown Boveri Str.7
5400 Baden
Switzerland

Copyright 2026 Fotoware All rights reserved.

  • Terms of service
  • Privacy policy
  • Cookie policy

Knowledge Base Software powered by Helpjuice

Expand