Proceed to GeoCommunity Home Page


SpatialNewsGIS Data DepotGeoImaging ChannelGIS and MappingSoftwareGIS JobsGeoBids-RFPsGeoCommunity MarketplaceGIS Event Listings
HomeLoginAccountsAboutContactAdvertiseSearchFAQsForumsCartFree Newsletter

Sponsored by:


TOPICS
Today's News

Submit News

Feature Articles

Product Reviews

Education

News Affiliates

Discussions

Newsletters

Email Lists

Polls

Editor's Corner


SpatialNews Daily Newswire!
Subscribe now!

Latest Industry Headlines
SiteVision GIS Partnership With City of Roanoke VA Goes Live
Garmin® Introduces Delta™ Upland Remote Trainer with Beeper
Caliper Offers Updated Chile Data for Use with Maptitude 2013
Southampton’s Go! Rhinos Trail Mapped by Ordnance Survey
New Approach to Measuring Coral Growth Offers Valuable Tool for Reef Managers
Topo ly - Tailor-Fit for Companies' Online Mapping Needs

Latest GeoBids-RFPs
Nautical Charts*Poland
Software & Telemetry GPS
Spatial Data Management-DC
Geospatial and Mapping-DC
Next-Gen 911-MO

Recent Job Opportunities
Planner/GIS Specialist
Team Leader- Grape Supply Systems
Geospatial Developer

Recent Discussions
Raster images
cartographic symbology
Telephone Exchange areas in Europe
Problem showcasing Vector map on Windows CE device
Base map

GeoCommunity Mailing List
 
Mailing List Archives

Subject: GISList: Conflation Confusion Conclusions...
Date:  01/29/2003 08:48:08 AM
From:  Lega, Robert




Hi all.... I received many response to my question about conflating point =
attributes to polygon features. Mostly these came in the form of essential=
ly rebuilding the poly coverage using the point cover. This would have bee=
n the best way to proceed if, however all my points landed inside its own c=
orresponding poly. But, as you all know, things just are not that easy, mo=
st of my points were outside polys, many polys contained multiple points, a=
nd other scenarios that you can imagine.=20=20

I'd like to thank Jeff Hankley who suggested:
"In ArcEdit, try making your polygon coverage the edit coverage and your e=
ditfeature label, delete the existing labels (if there are any) and do a "g=
et" on labels from your point coverage. Quitsave, and build polys."

Also Chris Markel deserves my thanks for this response:
"I would think the Identity overlay function in Arc Workstation would allow
you to do this. I think it would work whether you have one point per
polygon, or several points per polygon - I think Identity will output points
with the polygon attributes of the polygon they fall in. Transferring the
attributes of several points to one polygon presents you with the
many-to-one problem, however."

Jason MacEachern, thanks for your suggestion:
"If you are sure that each point will fall within one polygon (i.e. 1-to-1 =
relationship) you could use the IDENTIFY command possibly.=20

IDENTIFY my_pt_cov my_poly_cov my_new_poly_cov POLY # JOIN

will create a new polygon coverage with all the attributes from the input c=
overage joined to the output coverage where they overlap."

And lastly James Graham, thanks for your response as well.


And as you can see each of the above responses required that all of my poin=
ts land inside a polygon, which is not the case. So what I ended up doing =
was using the GNIS Point conflation procedures from NHDinARC, with a slight=
modification, which allowed a radiated perimeter around each point at succ=
essive intervals. It worked great, and even created a Q that allowed me to=
verify each of the multiple radiated points to multiple polys.

Good luck...and thanks again
RSL



To unsubscribe, write to gislist-unsubscribe@geocomm.com
________________________________________________________________________
GeoCommunity GeoBids - less than $1 per day!
Get Access to the latest GIS & Geospatial Industry RFPs and bids
http://www.geobids.com

Setup a GeoCommunity Account and have access to
the GISDataDepot DRG & DOQQ Catalog
http://www.geocomm.com/login.php


Sponsored by:

For information
regarding
advertising rates
Click Here!

Copyright© 1995-2012 MindSites Group / Privacy Policy

GeoCommunity™, Wireless Developer Network™, GIS Data Depot®, and Spatial News™
including all logos and other service marks
are registered trademarks and trade communities of
MindSites Group