Was anyone ever able to address the problem that the forceSchemaCRS call sets
the schema to null? Is the fix just to comment out that line which nulls
the schema?
Thanks!
Ashley
jody.garnett wrote
> Hey Rodrigo:
>
> Rodrigo Paes wrote:
>> Hi Jody,
>> I tried your approach and here is what ha
Michael Bedward wrote:
> Interesting. But does it only occurs when there is a glitch in the
> transform calculation as with Rodrigo's case ?
>
> I routinely do the forceSchema thing but I just tested omitting it
> when creating new shapefiles and got valid prj files.
>
>
That is good that bug i
Hey Rodrigo:
Rodrigo Paes wrote:
> Hi Jody,
> I tried your approach and here is what happened:
>
> - When I call the createSchema, it creates the schema but the crs is null;
> - Then I call the forceSchemaCRS and it creates the .prj properly but
> the schema is set to null;
> - Then when I call t
Hi Jody,
I tried your approach and here is what happened:
- When I call the createSchema, it creates the schema but the crs is null;
- Then I call the forceSchemaCRS and it creates the .prj properly but the
schema is set to null;
- Then when I call the command: featureStore =
(FeatureStore) shapeF
Interesting. But does it only occurs when there is a glitch in the
transform calculation as with Rodrigo's case ?
I routinely do the forceSchema thing but I just tested omitting it
when creating new shapefiles and got valid prj files.
Michael
Hey.
The shapefile datastore does not seem to be writing out the prj very
well. I know a work around - but I think you are the first person to
look at why this problem is occurring.
After calling:
shapefileDataStore.createSchema(collection.getSchema());
You can force the prj file to be writte
Hello,
I'm trying to save a shapefile from a MemoryDataStore.
The shapefile seems to be ok, however it is not saving the .prj file
properly, when I open it, it is empty (0 bytes).
When I call the createSchema(), I'm getting the following warning: "PRJ file
not generated for null CoordinateRe
