IMPORT POINT ADDRESSES statement

Print this page
Learn more about Verizon Connect GeoBase.
Get information about the latest release

IMPORT POINT ADDRESSES Statement

This statement converts GIS-formatted point address data to GBFS data. This statement is used when importing a shapefile with multipoints where Point[0] is a Point location in the street.

Note
When importing a shapefile with PointAddress data, all of the columns described below are required.

Syntax

Alchemy

Copy

IMPORT POINT_ADDRESSES [
ID = %link_id,
PT_ADDR_ID = %pt_addr_id,
SIDE = %side,
ADDRESS = %address,
DISP_LON = %disp_lon == "" ? -180.0 : %disp_lon,
DISP_LAT = %disp_lat == "" ? -180.0 : %disp_lat,
AR_LINK_ID = %ar_link_id,
AR_SIDE = %ar_side
] FROM "dbf://" + $path + "\" + $dca + "\PointAddress" IF EXISTS;

Nomenclature

ID	The LinkID of the Link from which the Point will get its name.
PT_ADDR_ID	The Point Address ID. This is a unique ID for each Point Address.
SIDE	The side of the road of the Point Address (based on the orientation of the link from which it will get its name).
ADDRESS	The number of the Address (both numeric and non-numeric values are supported).
DISP_LON	The Longitude of the point where the Point Address will be displayed.
DISP_LAT	The Latitude of the point where the Point Address will be displayed.
AR_LINK_ID	The LinkId of the Link where the Point Address physically connects (in the vast majority of cases, this will be the same as ID).
AR_SIDE	The side of the road of the Point Address (considering the orientation of the link to which it physically connects).

IMPORT POINT ADDRESSES From CSV Files

To import Point Addresses from CSV format text files, use the following format.

Alchemy

Copy

IMPORT POINT ADDRESSES [name = %name, geom = wkt(%point)] FROM "csv://src_file";

Nomenclature

name	An expression referencing one or more column in the CSV source file.
geom	A column of Point Address data stored as well known text (WKT) in the CSV source file.

Example

CSV

Copy

link_id,pt_addr_id,side,address,disp_lon, disp_lat,ar_link_id,ar_side,point_location
1234,5678,left,15,-118.265676,34.046188,1234,left,POINT(-118.265676 34.046188)

Note
Note the formatting of our point. For Well Known Text, the location should be formatted as 'Longitude Latitude', reversing the conventional GeoBase standard of 'Latitude Longitude'. Note also the use of a space as a separator rather than a comma.

The IMPORT POINT ADDRESSES statement required to import data from the example CSV file shown above is:

Alchemy

Copy

IMPORT POINT ADDRESSES [
ID = %link_id,
PT_ADDR_ID = %pt_addr_id,
SIDE = %side,
ADDRESS = %address,
DISP_LON = %disp_lon,
DISP_LAT = %disp_lat,
AR_LINK_ID = %ar_link_id,
AR_SIDE = %ar_side,
GEOM = wkt(%point_location)
] FROM "csv://src_file";

The following table shows what each column name in this example provides.

link_id	The ID of the Link from which the Point will get its name.
pt_addr_id	The unique ID for this Point Address.
side	The side of the road of the Point Address (based on the orientation of the link from which it will get its name).
address	The number of the Address (both numeric and non-numeric values are supported).
disp_lon	The Longitude of the point where the Point Address will be displayed.
disp_lat	The Latitude of the point where the Point Address will be displayed.
ar_link_id	The LinkId of the Link where the Point Address physically connects (in the vast majority of cases, this will be the same as 'link_id').
ar_side	The side of the road of the Point Address (considering the orientation of the link to which it physically connects).
point_location	The Point Address location stored as WKT.