postgis/PostGIS Manual — Korean @ OSGeo Weblate: The code is built into a single PostgreSQL extension library …

Translation

English

Tag: para

The code is built into a single PostgreSQL extension library called <code>address_standardizer</code> which can be installed with <code>CREATE EXTENSION address_standardizer;</code>. In addition to the address_standardizer extension, a sample data extension called <code>address_standardizer_data_us</code> extensions is built, which contains gaz, lex, and rules tables for US data. This extensions can be installed via: <code>CREATE EXTENSION address_standardizer_data_us;</code>

Korean

Needs editing

Skip

	English	Korean	Actions
	If you have lots of RAM and few developers:
	<link xlink:href="http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAINTENANCE-WORK-MEM">maintenance_work_mem</link> - the memory size used for VACUUM, CREATE INDEX, etc.
	Default: 16-64MB
	Generally too low - ties up I/O, locks objects while swapping memory
	Recommend 32MB to 1GB on production servers w/lots of RAM, but depends on the # of concurrent users. If you have lots of RAM and few developers:
	max_parallel_workers_per_gather
	This setting is only available for PostgreSQL 9.6+ and will only affect PostGIS 2.3+, since only PostGIS 2.3+ supports parallel queries. If set to higher than 0, then some queries such as those involving relation functions like <code>ST_Intersects</code> can use multiple processes and can run more than twice as fast when doing so. If you have a lot of processors to spare, you should change the value of this to as many processors as you have. Also make sure to bump up <code>max_worker_processes</code> to at least as high as this number.
	Default: 0
	Sets the maximum number of workers that can be started by a single <varname>Gather</varname> node. Parallel workers are taken from the pool of processes established by <varname>max_worker_processes</varname>. Note that the requested number of workers may not actually be available at run time. If this occurs, the plan will run with fewer workers than expected, which may be inefficient. Setting this value to 0, which is the default, disables parallel query execution.
	PostGIS Extras
	This chapter documents features found in the extras folder of the PostGIS source tarballs and source repository. These are not always packaged with PostGIS binary releases, but are usually PL/pgSQL based or standard shell scripts that can be run as is.
	&extras_address_standardizer; &extras_tigergeocoder;
	Address Standardizer	주소 표준화 도구
	This is a fork of the <link xlink:href="http://www.pagcgeo.org/docs/html/pagc-11.html">PAGC standardizer</link> (original code for this portion was <link xlink:href="http://sourceforge.net/p/pagc/code/360/tree/branches/sew-refactor/postgresql">PAGC PostgreSQL Address Standardizer</link>).	이 도구는 <link xlink:href="http://www.pagcgeo.org/docs/html/pagc-11.html">PAGC standardizer</link> 의 한 갈래(fork)입니다(이 갈래의 원본 코드는 <link xlink:href="http://sourceforge.net/p/pagc/code/360/tree/branches/sew-refactor/postgresql">PAGC PostgreSQL 주소 표준화 도구</link> 였습니다).
	The address standardizer is a single line address parser that takes an input address and normalizes it based on a set of rules stored in a table and helper lex and gaz tables.	주소 표준화 도구는 단일 라인 주소 파싱 도구로, 주소를 입력받아 테이블에 저장된 일련의 규칙 및 도우미 <link xlink:href="http://postgis.net/docs/lextab.html">어휘 목록(lexicon; lex) 테이블</link> 과 <link xlink:href="http://postgis.net/docs/gaztab.html">지명 색인(gazetteer; gaz) 테이블</link> 에 기반해서 정규화합니다.
	The code is built into a single PostgreSQL extension library called <code>address_standardizer</code> which can be installed with <code>CREATE EXTENSION address_standardizer;</code>. In addition to the address_standardizer extension, a sample data extension called <code>address_standardizer_data_us</code> extensions is built, which contains gaz, lex, and rules tables for US data. This extensions can be installed via: <code>CREATE EXTENSION address_standardizer_data_us;</code>	<code>CREATE EXTENSION address_standardizer;</code> 명령으로 설치할 수 있는 <code>address_standardizer</code> 라는 단일 PostgreSQL 확장 프로그램 라이브러리로 코드를 빌드합니다. <code>address_standardizer</code> 확장 프로그램에 더해, <code>address_standardizer_data_us</code> 라는 샘플 데이터 확장 프로그램도 빌드하는데, 미국 데이터에 대한 지명 색인, 어휘 목록, 규칙 테이블을 담고 있습니다. <code>CREATE EXTENSION address_standardizer_data_us;</code> 명령으로 이 확장 프로그램을 설치할 수 있습니다.
	The code for this extension can be found in the PostGIS <filename>extensions/address_standardizer</filename> and is currently self-contained.	PostGIS <filename>extensions/address_standardizer</filename> 에서 이 확장 프로그램을 위한 코드를 찾을 수 있으며, 현재 독립적으로 돼 있습니다.
	For installation instructions refer to: <xref linkend="installing_pagc_address_standardizer"/>.	설치에 대한 지침을 보고 싶다면 <xref linkend="installing_pagc_address_standardizer"/> 를 참조하십시오.
	How the Parser Works	파싱 도구의 작동 방식
	The parser works from right to left looking first at the macro elements for postcode, state/province, city, and then looks micro elements to determine if we are dealing with a house number street or intersection or landmark. It currently does not look for a country code or name, but that could be introduced in the future.	파싱 도구는 오른쪽에서 왼쪽 방향으로 먼저 우편번호, 주/도, 시군구에 해당하는 거시적(macro) 요소를 탐색한 다음, 가구의 번지수 또는 교차점 또는 랜드마크 가운데 어떤 것을 처리하고 있는지 결정하기 위한 미시적(micro) 요소를 탐색합니다. 현재 국가 코드 또는 국가명을 탐색하지는 않지만, 향후 추가될 수도 있습니다.
	Country code	국가 코드
	Assumed to be US or CA based on: postcode as US or Canada state/province as US or Canada else US	미국 또는 캐나다의 주/도, 미국 또는 캐나다의 우편번호를 바탕으로 미국 또는 캐나다로 가정합니다.
	Postcode/zipcode	우편번호/집코드(zip code)
	These are recognized using Perl compatible regular expressions. These regexs are currently in the parseaddress-api.c and are relatively simple to make changes to if needed.	펄(Perl) 호환 정규 표현식을 이용해서 우편번호를 인식합니다. 이 정규 표현식은 현재 parseaddress-api.c 파일에 담겨 있고, 필요한 경우 상대적으로 쉽게 변경할 수 있습니다.
	State/province	주/도
	These are recognized using Perl compatible regular expressions. These regexs are currently in the parseaddress-api.c but could get moved into includes in the future for easier maintenance.	펄(Perl) 호환 정규 표현식을 이용해서 우편번호를 인식합니다. 이 정규 표현식은 현재 parseaddress-api.c 파일에 담겨 있는데, 향후 유지보수를 더 쉽게 하기 위해 "includes"로 이동할 수도 있습니다.
	Address Standardizer Types	주소 표준화 도구 유형
	This section lists the PostgreSQL data types installed by Address Standardizer extension. Note we describe the casting behavior of these which is very important especially when designing your own functions.	이 단원에서 주소 표준화 도구 확장 프로그램이 설치한 PostgreSQL 데이터 유형을 소개합니다. 사용자 자신의 함수를 설계할 때 특히 중요한 이 유형들의 형변환 습성(cast behavior)을 설명한다는 점에 주의하십시오.
	A composite type that consists of the elements of an address. This is the return type for <varname>standardize_address</varname> function.	주소의 요소들로 이루어진 합성 유형입니다. <varname>standardize_address</varname> 함수가 이 유형을 반환합니다.
	Description	설명
	A composite type that consists of elements of an address. This is the return type for <xref linkend="standardize_address"/> function. Some descriptions for elements are borrowed from <link xlink:href="http://www.pagcgeo.org/docs/html/pagc-12.html#ss12.1">PAGC Postal Attributes</link>.	주소의 요소들로 이루어진 합성 유형입니다. <xref linkend="standardize_address"/> 함수가 이 유형을 반환합니다. <link xlink:href="http://www.pagcgeo.org/docs/html/pagc-12.html#ss12.1">PAGC Postal Attributes</link> 에서 요소들에 대한 몇몇 설명을 빌려왔습니다.

Loading…

None

String updated in the repository

English

Korean 387 characters edited Current translation Needs editing

<code>CREATE EXTENSION address_standardizer;</code> 명령으로 설치할 수 있는 <code>address_standardizer</code> 라는 단일 PostgreSQL 확장 프로그램 라이브러리로 코드를 빌드합니다. <code>address_standardizer</code> 확장 프로그램에 더해, <code>address_standardizer_data_us</code> 라는 샘플 데이터 확장 프로그램도 빌드하는데, 미국 데이터에 대한 지명 색인, 어휘 목록, 규칙 테이블을 담고 있습니다. <code>CREATE EXTENSION address_standardizer_data_us;</code> 명령으로 이 확장 프로그램을 설치할 수 있습니다.

8 months ago

Browse all string changes

Things to check

Mismatched full stop

Source and translation do not both end with a full stop

Reset

XML markup Enforced

XML tags in translation do not match source

Glossary

English	Korean
No related strings found in the glossary.

String information

Source string description

Tag: para

Flags

no-c-format

String age

8 months ago

Last updated

8 months ago

Source string age

8 months ago

Translation file

doc/po/ko_KR/postgis-manual.po, string 107