When i open my shapefile with TatukGis Viewer i can see it perfectly. But
when i load it into GeoServer (add a new FeatureStores and then new
FeatureType) and try to display it in uDig (using wfs import from my local
GeoServer) i can not see a thing. uDig puts exclamation sign infront of the
imported shapefile. Am i doing something wrong? I set Feature Type to 4326.
I checked other FeatureTypes and they worked. Is it normal that Min Long,
Min Lat... are huge numbers, like: 5012202.219176441?
It looks like the shapefile you are trying to use are in a projected
coordinate system. If there is a prj file I would open that up to
determine what system the file is actually in and then use the relevant
EPSG code in the FeatureType ... using 4326 is definitely wrong
Chris
-----Original Message-----
From: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net] On Behalf Of
GeoUser
Sent: Monday, 3 July 2006 4:46 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Shapefile problem
When i open my shapefile with TatukGis Viewer i can see it perfectly.
But
when i load it into GeoServer (add a new FeatureStores and then new
FeatureType) and try to display it in uDig (using wfs import from my
local
GeoServer) i can not see a thing. uDig puts exclamation sign infront of
the
imported shapefile. Am i doing something wrong? I set Feature Type to
4326.
I checked other FeatureTypes and they worked. Is it normal that Min
Long,
Min Lat... are huge numbers, like: 5012202.219176441?
This e-mail and any files transmitted with it are intended only for the use of the addressee(s). It may contain information that is confidential and privileged. If you are not an intended recipient, any use, interference with, disclosure, distribution or copying of this material is unauthorised and prohibited. If you receive this in error, please notify the author by Return email to the sender. Information in this message not relating to the official business of DLI shall be understood as neither given nor endorsed by it. While every care is taken, it is recommended that you scan any attachments for viruses. DLI liability is limited to re-supplying affected attachments.
**********************
PLEASE NOTE: All dola.wa.gov.au and vgo.wa.gov.au email addresses have been decommissioned. These have been replaced by dli.wa.gov.au addresses. Please ensure that your records are updated to reflect this change. Further information can be obtained by contacting our service desk on 92737533 or emailing Servicedesk@anonymised.com
It is just a bounding box filter, which comes back to the unknown SRS value. UDig isn't broken here, it is relying on your specified SRS value .
Your .prj file says that the projection is a UTM zone, so not lat/lon. You just need to look for the SRS value corresponding to UTM zone 33N.
Brent Owens
(The Open Planning Project)
GeoUser wrote:
now i know what's wrong. uDig generates this xml file:
