Pelias,Reverse-Geocoding tools

Pelias是一款基于ElasticSearch构建的模块化开源地理编码器,能够将地址转换为地球表面的位置,并支持反向地理编码。其核心特性包括完全开源、可根据需求本地安装和修改,具备快速自动补全等功能。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

Pelias is a modular, open-source geocoder built on top of ElasticSearch for fast geocoding.

Pelias is the project used to power Mapzen Search

What's a geocoder do anyway?

Geocoding is the process of transforming input text, such as an address, or a name of a place—to a location on the earth's surface.

geocode

... and a reverse geocoder, what's that?

Reverse geocoding is the opposite, it transforms your current geographic location in to a list of places nearby.

What makes Pelias different from other geocoders?

  • It's completely open-source and MIT licensed

  • It's based on open-data, so you can run it yourself

  • You can install it locally and modify to suit your needs

  • It has an impressive list of features, such as fast autocomplete

  • It's modular, so you don't need to be an expert to make changes

  • It's easy to install and requires no external dependencies

  • We run a continuous deployment cycle with a new version shipping weekly

What are the main goals of the Pelias project?

  • Provide accurate search results

  • Give users query suggestions (typeahead in the search box)

  • Account for location bias (places nearer to you appear higher in the results)

  • Support multiple data sources (Defaults include OpenStreetMap, OpenAddresses, geonames, quattroshapes etc)

  • Flexible software architecture

  • Easy to contribute software patches and features to

  • Easy to set-up and configure your own instance

  • No external dependencies (such as postgres)

  • Reliable, configurable & fast import process

  • Work equally well for a small city and the entire planet

Developer Documentation & API Access

Sure! Our API lives at search.mapzen.com, and is usable with a free API key (register here) and generous rate-limits. The endpoints are documented here; happy geocoding!

This documentation also applies to standalone versions of Pelias, leaving aside API keys, privacy flags, and data sources which may be configured differently for other installations.

$ curl -s "search.mapzen.com/v1/reverse?size=1&point.lat=40.74358294846026&point.lon=-73.99047374725342&api_key={YOUR_API_KEY}" | json
{  "geocoding": {    "version": "0.1",    "attribution": "http://search.mapzen.com/v1/attribution",    "query": {      "size": 1,      "private": false,      "point.lat": 40.74358294846026,      "point.lon": -73.99047374725342,      "boundary.circle.lat": 40.74358294846026,      "boundary.circle.lon": -73.99047374725342,      "boundary.circle.radius": 50
    },    "engine": {      "name": "Pelias",      "author": "Mapzen",      "version": "1.0"
    },    "timestamp": 1443189055394
  },  "type": "FeatureCollection",  "features": [
    {      "type": "Feature",      "properties": {        "id": "9851011",        "gid": "gn:venue:9851011",        "layer": "venue",        "source": "gn",        "name": "Arlington",        "country_a": "USA",        "country": "United States",        "region": "New York",        "region_a": "NY",        "county": "New York County",        "localadmin": "Manhattan",        "locality": "New York",        "neighbourhood": "Flatiron District",        "confidence": 0.9,        "distance": 0.004,        "label": "Arlington, Manhattan, NY"
      },      "geometry": {        "type": "Point",        "coordinates": [          -73.99051,          40.74361
        ]
      }
    }
  ],  "bbox": [    -73.99051,    40.74361,    -73.99051,    40.74361
  ]
}

How can I install my own instance of Pelias?

Check out our vagrant development environment.

How does it work?

Magic! Well, like any geocoder, Pelias essentially just executes search queries against an enormous amount of geographic data that maps longitude/latitude coordinates on the Earth to searchable names (eg Empire State Buildingor 28 Elm Street).  We run entirely on open datasets, like OpenStreetMap,GeoNames, and OpenAddresses.

The underlying architecture has three components:

  • import pipelines: the pipelines used to filter, normalize, and ingest geographic datasets into the Pelias database.

  • database: the underlying datastore that does all of the query heavy-lifting and powers our search results. We useElasticSearch.

  • API: the thing that users interact with. A thin layer sitting on top of the datastore that implements additional logic and features.

Here's how they interact:

A diagram of the Pelias architecture.

What's it built with?

Pelias itself (the import pipelines and API) is written in Node, which makes it highly accessible for other developers and performant under heavy I/O. It aims to be modular and is distributed across a number of Node packages, each with its own repository under the Pelias GitHub organization. ElasticSearch is our unconventional datastore of choice because of its unparalleled text functionality, which makes text search just work right out of the box, and sufficiently robust geospatial support.

Contributing

We built Pelias as an open source project not just because we believe that users should be able to view and play with the source code of tools they use, but to get the community involved in the project itself.

Anything that we can do to make contributing easier, we want to know about.  Feel free to reach out to us via Github,Gitter, email, or Twitter We'd love to help people get started working on Pelias, especially if you're new to open source or programming in general. Both this meta-repoand the API repo are good places to get started looking for tasks to tackle. You can also look across all of our issues on our meta-issue tracker, Waffle. We also welcome reporting issues or suggesting improvements to our documentation.

The current Pelias team can be found on Github as dianashk,missinglink, orangejulius,riordan, and stephenkhess.

Members emeritus include: randyme, seejohnrun, sevko, and hkrishna.


转载于:https://my.oschina.net/u/2306127/blog/600296

内容概要:该PPT详细介绍了企业架构设计的方法论,涵盖业务架构、数据架构、应用架构和技术架构四大核心模块。首先分析了企业架构现状,包括业务、数据、应用和技术四大架构的内容和关系,明确了企业架构设计的重要性。接着,阐述了新版企业架构总体框架(CSG-EAF 2.0)的形成过程,强调其融合了传统架构设计(TOGAF)和领域驱动设计(DDD)的优势,以适应数字化转型需求。业务架构部分通过梳理企业级和专业级价值流,细化业务能力、流程和对象,确保业务战略的有效落地。数据架构部分则遵循五大原则,确保数据的准确、一致和高效使用。应用架构方面,提出了分层解耦和服务化的设计原则,以提高灵活性和响应速度。最后,技术架构部分围绕技术框架、组件、平台和部署节点进行了详细设计,确保技术架构的稳定性和扩展性。 适合人群:适用于具有一定企业架构设计经验的IT架构师、项目经理和业务分析师,特别是那些希望深入了解如何将企业架构设计与数字化转型相结合的专业人士。 使用场景及目标:①帮助企业和组织梳理业务流程,优化业务能力,实现战略目标;②指导数据管理和应用开发,确保数据的一致性和应用的高效性;③为技术选型和系统部署提供科学依据,确保技术架构的稳定性和扩展性。 阅读建议:此资源内容详尽,涵盖企业架构设计的各个方面。建议读者在学习过程中,结合实际案例进行理解和实践,重点关注各架构模块之间的关联和协同,以便更好地应用于实际工作中。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值