如何获取地图中显示的包裹或邮政编码边界？ [英] How to get parcel or zipcode boundaries for display in map?

问题描述

我想为指定的地块添加边界，以便在地图上以彩色边框/边框突出显示。在谷歌地图中，​​如果您知道围绕地块输入的坐标路径，则可以使用多边形功能完成此操作。但是，我没有多边形路径信息，但是我确实有位置的地理编码坐标以及包裹的评估者地块编号（APN）。

我发现这个其他SO贴子，它谈论了如何使用免费的人口普查局数据和一些开源软件来获取邮编多边形，但它涉及到很多（因为您必须下载和托管数据）以及我不确定它甚至会将精确度降至包裹边界。如果它支持包裹，这绝对是一种选择，但它看起来非常费时，尽管免费。

我还发现了一个名为 ParcelStream ，但认为它很贵，可能只是在其他SO帖子中使用上述解决方案。这也是一个选择，如果它是一个小的一次性费用，但不是如果它是昂贵的或订阅费。​​

我知道你可以在地图上手动创建叠加层，保存，然后分享它们，但我正在寻找一种自动化/程序化解决方案。

：//www.digmap.com/products/ParcelBoundaries.htmlrel =nofollow noreferrer>来自Digital Map Products的ParcelStream 不是一种选择，大约每月10K。他们建议订阅服务的目的是覆盖全国（不是本地），Google也是他们的客户。

更新＃2：使用美国上文提到的人口普查局数据解决方案（加上其他开源软件）似乎并没有在浏览其可用功能后向包裹提供边界数据 TIGERweb2010 site。

解决方案

经过一个多星期的研究和尝试出于不同的选择，有一些取决于你的预算以及你希望数据的一贯准确性。我从这个 stackExchange帖子得到了一些提示，但是做了一吨研究和增加更多。

总之，边界数据很难得到，价格昂贵，而且根据您的来源不同而有所不同。 邮政编码制表区（ZCTA's）不是很准确（像maponics说），可以通过检查此ZCTA网站为zip 92064.然后查看zillow上的zip文件并注意其差异。 ZCTA数据并不总是准确的（在这个邮政编码的情况下），但根据您的来源可以是免费的。

总之，我的选项按照优先顺序排列（因为我的预算较小，需要准确的数据）：

1. 仅限于包裹边界， 全部报告 非常价格合理，并为我的全县提供250美元的包裹边界。 以下是可供购买的县份列表（包裹）。 下面是Excel，Shapefile或KML格式的县级示例下载，尽管Excel文件似乎缺少多边形坐标（duh）。 KML格式有多边形，但看起来不错。 这里有一个定价细目链接，它基本上超越了你购买的更多商品。 li>
   
2. 仅限邮政编码边界，​​ Maponics 是相当定价IMO。基本上，这是一年一次的下载，每年只有200美元（仅限邮编边界），您可以在一年中使用这些下载并每年回购更新。它每月提供数千次宗地边界与销售代表（叹气）交谈后。不过，尽管如此，对于邮政编码界限仍然是一个很好的解决方案。


3. 只有邮编边界，您也可以使用 zip-codes.com ，这对我的县来说大约是50美元。不错。 仅限邮政编码边界，​​ 拉链边界。 仅限邮编界限，您可以从此FTP服务器由美国人口普查局提供，并将其转换为您的需要。免费，但漫长的过程需要其他工具和技巧（PostGreSQL，PostGIS），但它确实可以为您提供准确的badary数据，可用于邮政编码制表区（ZCTA's）。请阅读此其他SO帖子


4. 对于邻里边界，您可以使用 Zillow的免费邻域边界形状文件 。它是免费的，但它们在使用时确实需要徽标并链接到他们的网站。在下载我的州并查看我的城市之后，我注意到它并不完整，并且在阴影街区中存在许多空白，所以有点不起眼。
geocommunicator.gov/GeoComm/services.htm#Maprel =nofollow noreferrer> GeoCommunicator （由美国内政部 - 土地管理局 ）。 GeoCommunicator不适用于APN（评估者的地块号码），只能与（地块）地块一起使用，您还需要其他几条信息才能获得边界。在乡镇地理编码器服务上的 GetTRS API 需要一个经纬度，但未能解决一些坐标（针对住宅物业），我输入并返回了找不到LD功能。我也不确定哪个边界级别从该API返回（很多或更大）。另一个乡镇地理编码器服务的GetLatLng API 似乎更好解决方案，但这是除了（土地）批号之外还需要所有其他参数的解决方案。 文档表示它需要：用逗号分隔的一串乡镇描述单个PLSS勘测区域的范围属性，即使我可以获得（陆地）批号，也包含所有这些数据片段。

5. UrbanMapping的Mapfluence javascript API 有几种不同类型的边界数据，包括 =nofollow noreferrer>地块和邻里边界数据。花了几天的邮编，邻里和包裹边界请求后，返回的ZCTA边界与上面提到的一些邮编（92064）有很大不同，这正是ZCTA的本质。邻里边界非常稀疏（仅覆盖搜索区域的5％左右），在我测试的大多数情况下，它与建筑物一样小。此外，除了需要更多信息的文档外，由于指定的包裹边界表（umi.us_parcel.geometry）被API拒绝为几何表umi.us_parcel.geometry不存在，因此它们也不准确。所有与此相关的内容都没有社区文档，没有提交任何支持问题的在线答复，也没有电话支持从六个语音邮件中删除，并且没有返回的电子邮件。根据我对此的经验，尽管最初在粗糙的地方看到了钻石，但我会通过寻找包裹和邮政编码数据的替代路线。

I want to add a boundary to a specified parcel of land so that it stands out in the map with a colored outline/border. In google maps, this is done using the polygon functionality if you know that path of coordinates to enter to surround the land parcel. However, I do not have the polygon path info, but I do have the both the geocode coordinates for the location and also the Assessor's Parcel Number (APN) for the parcel as well.

I found this other SO post that talks a little about how to get the polygon for zipcodes using the free Census Bureau data coupled with some open source software, but it's quite involved (as you have to download and host the data) and I'm not sure it even does percision down to parcel boundaries. It's definitely an option if it supports parcels, but it looks to be very time consuming albeit free.

I also found a paid solution (price not displayed) called ParcelStream, but thinking it's expensive and probably just using the above solution in the other SO post. This is also an option if it's a small one time fee, but not if it's expensive or a subscription fee.

I am aware you can manually create overlays on maps, save, and then share them, but I'm looking for an automated/programatic solution.

UPDATE: okay, ParcelStream from Digital Map Products, is not an option and around 10k/month. They advised the subscription service is intended for national coverage (not local) and Google is among their clients.

UPDATE #2: Using the US Census Bureau data solution mentioned above (coupled with other open source software) doesn't seem to provide boundary data down the parcel after browsing the features available on it's TIGERweb2010 site.

解决方案

Okay after over a week of researching and trying out different options, there are a few depending on your budget and how consistently accurate you want the data to be. I got a few tips form this stackExchange post, but did a ton reserach and added more.

In short, boundary data is hard to get your hands on, expensive, and varies in quality depending on your source. Zip Code Tabulation Areas (ZCTA's) are not very accurate (like maponics says) and can be seen by checking this ZCTA site for zip 92064. Then look at that zip on zillow and notice the difference. ZCTA data is not always accurate (in the case of this zipcode), but can be free depending on your source.

In summary, here's my options in order of preference (given my smaller budget and need for accurate data):

1. For Parcel boundaries only, Report All is very reasonably priced and has parcel boundaries for my entire county for $250. Here's a list of available counties available for purchase (for parcels). Here's a sample download of a county in Excel, Shapefile, or KML format although the Excel file seems to be missing the polygon coordinates (duh). KML format has polygon and looks good though. Here's a link to the pricing breakdown which basically gets supercheap with the more listings you buy.
2. For zipcode boundaries only, Maponics is fairly priced IMO. Basically, it's a one time annual download that's $200 per county (zipcode boundaries only) that you'd use throughout the year and repurchase annually for updates. It offers parcel boundaries for several thousand per month after talking to the sales rep (sigh). However, still a good solution for zipcode boundaries though.
3. For zipcode boundaries only, you can also use zip-codes.com which is about $50 for my county. Not bad.
4. For zipcode boundaries only, zipboundary.com - pricing is by subscription.
5. For zipcode boundaries only, you can download the free raw data from this FTP server provided by the US Census Bureau and transform it to your needs. Free, but long lengthy process requiring other tools and skills (PostGreSQL, PostGIS), but it does give you accurate boudary data in terms of a polygon for Zip Code Tabulation Areas (ZCTA's). Read about it in this other SO post.
6. For neighborhood boundaries, you can use Zillow's free neighborhood boundary shape files. It's free, but they do require a logo and link to their site when used. After downloading my state and looking at my city, I noticed it was incomplete and somewhat innacurate as there were many gaps in the shaded neighborhoods.
7. GeoCommunicator (run by US Dept of Interior - Bureau of Land Management). GeoCommunicator doesn't work with APNs (Assessor's Parcel Number) and only works with (land) lots for which you would also need several other pieces of information to get a boundary for. The GetTRS API on the Township Geocoder Service takes a lat & lng, but failed to resolve some of the coordinates (for residential properties) I put in and returned "No LD Features found". I'm also not sure what boundary level is returned (lot or bigger) from that API. The other GetLatLng API on the Township Geocoder Service seems to be the better solution, but that's the one that needs all those other params in addition to the (land) lot number. The docs for it say it needs: "A comma-separated String of Township Range properties describing a single PLSS survey area" which consists of the all these pieces of data I wouldn't have even if I could obtain the (land) lot number.
8. UrbanMapping's Mapfluence javascript API has a several different types of boundary data including Parcel and neighborhood boundary data. After spending a few days working with the zipcode, neighborhood, and parcel boundary requests, the ZCTA boundaries returned are very different for some zipcodes (92064) as mentioned above which is just the nature of ZCTA's. The neighborhood boundaries are very sparse (only covered about 5% of the searched area) and are as small as buildings in the majority of the cases I tested. Plus, in addition to the docs needing more info, they are also inaccurate as the parcel boundary table specified (umi.us_parcel.geometry) gets rejected from the API as "Geometry table umi.us_parcel.geometry does not exist". All that combined with there is no community documentation, no online response from support issues submitted, no phone support from leaving half dozen voicemails, and no returned emails. Based on my experience with this, I'll pass and seek alternative routes for parcel and zipcode boudary data despite this initially looking a diamond in the rough.

这篇关于如何获取地图中显示的包裹或邮政编码边界？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！