[Talk-us] parcel data next steps

Ian Dees ian.dees at gmail.com
Fri Feb 22 17:07:35 UTC 2013


On Thu, Feb 21, 2013 at 6:27 PM, Brian Cavagnolo <bcavagnolo at gmail.com>wrote:

> Hey guys,
>
> In a previous thread on parcel data, some people expressed interest in
> participating in creating some sort of open repository for parcel
> data.  I was imagining a conference call or something to discuss next
> steps, but I think we can advance with email.  I'm imagining that it
> makes sense to separate the data gathering process from the data
> standardization/import process.
>
> Regarding the data gathering, the main objective is to gather recent
> raw data, licensing terms, and meta data from jurisdictions in
> whatever form they make it available, organize it in a dumb directory
> structure.  I was just going to set up an FTP (read-write)  and HTTP
> (read-only) server to get this going.  Are there any
> recommendations/opinions on a longer-term approach here?  Custom
> webapp?  Off-the-shelf webapp?  Somebody mentioned a git repository.
>

I think the easiest thing to do right now is to collect a list of URLs and
contact information for where this data might be. When it's easily
obtainable we should download it and collate it. I've got a directory on
the OSM US server with a few large chunks of data. I'm happy to give you an
account if you want to continue filling that up.

As far as metadata about this stuff I think a spreadsheet will have to do
for now until we figure out commonalities between the available metadata. I
suppose knowing the vintage, license, contact information, and location of
the file(s) containing parcel data is the most important part.


>
> Regarding standardization/import, I was planning on setting up an
> empty instance of the rails port as a test bed.  Then participating
> users could point JOSM and other tools at this alternative rails port
> to examine, edit, and import parcel data.  We could also provide
> planet-style dumps and mapnik tiles.  The idea is that we would have a
> safe place to screw up and learn.  Does this sound like a reasonable
> direction?


I don't think we should worry about importing or standardizing into
anything yet. That step should happen once we have a pretty good size
sample of the data so we can figure out what's available.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20130222/0483afcc/attachment.html>


More information about the Talk-us mailing list