1 / 4

Location Formats: Civic vs. Geo - Understanding Use Cases and Transformations

Explore the comparison between Civic and Geo location formats in telecom systems, focusing on static vs. mobile use cases and transformation processes. Learn about addressing issues, GIS rendering, and practical applications.

fritz-oconnor
Download Presentation

Location Formats: Civic vs. Geo - Understanding Use Cases and Transformations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ESW07Location Formats:Convergence Now or Not at all? Roger Marshall TeleCommunication Systems, Inc. (TCS) ESW07 4/10-12/2007

  2. Location Formats – Civic vs. Geo, which is used for what? • Location type can be either civic or geodetic (“geo”) • Call modes are either Static or Mobile • View Nomadic as either Static:(Re-provisioned), or Mobile:(Seldom updated) • Civic is fully compatible with Static use cases •  Mobile might use Civic for “rough” routing (when available) •  Mobile uses Geo for dispatch, and for precise routing (if avail. in time) •  Geo association with Static is becoming more prominent • Examples: Picocells, GPS-enabled APs, VoIP terminals w/built in LDT

  3. Location Formats: Civic & Geo – How they describe Static vs. Mobile • 3GPP/3GPP2 is focused solely on Mobile – is Geo all they want/need? • Is the IETF focused on Static vs. Mobile rather than Civic vs. Geo? • Review of Civic Location Characteristics/Issues • Civic is geared for urban/suburban applications – Lacks global scalability • Doesn’t fit rural areas (examples include rural route, PO Box #) • Not a candidate for direct automatic location generation • Review of Geo Location Characteristics/Issues • Has to be “rendered” by GIS to become useful, though most PSAPs do this today • Reverse geo-coding result may not always be correct • May not be determinable indoors (use cases better served by Civic form) • Goal of Civic vs. Geo comparison • Focus on use case Static vs. Mobile, and appropriate location follows

  4. Location Formats – Civic and Geo, Basis and Transformation • Location is determined as either Given, Measured, or Derived • Given - applied to a location that is stated, provisioned • Civic Addresses (typical) – these are entered into “Wiremap Databases” • Seldom is a Geo location “given” • Measured – applied to a location that is calculated • Geodetic (typical) • Impossible to “measure” or “calculate” a Civic location • Derived – applies to either Civic or Geo, the basis of GIS systems • Obtained as a result of a transformation using the other form as input • Examples include: Geo-coding and Reverse Geo-coding • Basis of existing (Pre-i2) VoIP routing today • Many issues and some opportunities around derived locations • Requires consistent National/International PSAP boundary layer (GIS shape file) • Some PSAPs implement reverse-parcel-based-mapping: • input a lat/lon and get a civic location + polygon • Consider extensions to existing GIS systems, such as Reference Point mapping: • Input in a civic location + key_indicator, • Output: Lat/Lon of street centerline + offset or front door or (2d) structure centroid, etc.

More Related