ogr2ogr Warning 502: Field name 'yyy xx' contains invalid characters. 'yyy_xx' will be used insteadESRI...
How to disable or uninstall iTunes under High Sierra without disabling SIP
How does insurance birth control work?
When to use mean vs median
Levi-Civita symbol: 3D matrix
Would the melodic leap of the opening phrase of Mozart's K545 be considered dissonant?
When was drinking water recognized as crucial in marathon running?
Giving a talk in my old university, how prominently should I tell students my salary?
Book about a time-travel war fought by computers
Transparent Materials for Creating Martian Dome Ceilings
How can I handle a player who pre-plans arguments about my rulings on RAW?
Why won't the strings command stop?
Create chunks from an array
PTIJ: Is all laundering forbidden during the 9 days?
How can I highlight parts in a screenshot
Split a number into equal parts given the number of parts
Can the Shape Water Cantrip be used to manipulate blood?
How do you say “my friend is throwing a party, do you wanna come?” in german
Why is it "take a leak?"
Canadian citizen, on US no-fly list. What can I do in order to be allowed on flights which go through US airspace?
GDAL GetGeoTransform Documentation -- Is there an oversight, or what am I misunderstanding?
is 'sed' thread safe
Should I use HTTPS on a domain that will only be used for redirection?
Why would the IRS ask for birth certificates or even audit a small tax return?
Rationale to prefer local variables over instance variables?
ogr2ogr Warning 502: Field name 'yyy xx' contains invalid characters. 'yyy_xx' will be used instead
ESRI Shapefile not loading into SQL ServerSpecify geom field name with ogr2ogr: gdb to PostgreSQLogr2ogr sql: what is the name of the geometry field?
On MSSQL tables/views that have field names with spaces or starting with a number we get the warning 502 re: replacing invalid characters with a _
As we re-injest some of these files into MSSQL and use them in other software we would like to keep the (poorly formatted) field names as otherwise we have to change every reference to the replaced fields. It could also affect AUTHORITY and Confirm etc that's used for asset management.
Is there a switch that allows us to do this?
Here's what I use
ogr2ogr -skipfailures -f "MapInfo File" -lco overwrite=yes -lco launder=no -lco relaxedFieldNameMatch=yes -lco unsetDefault=yes "D:QGvw_CONFIRM_PavementCondition.tab" "MSSQL:Server=xxxx;Database=GIS_Test;Trusted_Connection=True" -sql "SELECT * FROM dbo.vw_CONFIRM_PavementCondition" -a_srs EPSG:28354 -t_srs EPSG:28354 -s_srs EPSG:28354
Warning 6: dataset
D:QGvw_CONFIRM_PavementCondition.tab does not support layer
creation option launder Warning 502: Field name 'Road Pavement
Maintenance Grade' contains invalid characters.
'Road_Pavement_Maintenance_Grade' will be used instead. Warning 502:
Field name 'Road Pavement Roughness' contains invalid characters.
'Road_Pavement_Roughness' will be used instead. Warning 502: Field
name 'Road Pavement Profile' contains invalid characters.
'Road_Pavement_Profile' will be used instead. Warning 502: Field name
'Road Pavement Rutting' contains invalid characters.
'Road_Pavement_Rutting' will be used instead. Warning 502: Field name
'Road Pavement Overall Condition' contains invalid characters.
'Road_Pavement_Overall_Condition' will be used instead.
Does ogr2ogr.main used within python have some additional functionality not available in the .exe? if so a solution in this would be fine as well.
sql-server ogr2ogr
add a comment |
On MSSQL tables/views that have field names with spaces or starting with a number we get the warning 502 re: replacing invalid characters with a _
As we re-injest some of these files into MSSQL and use them in other software we would like to keep the (poorly formatted) field names as otherwise we have to change every reference to the replaced fields. It could also affect AUTHORITY and Confirm etc that's used for asset management.
Is there a switch that allows us to do this?
Here's what I use
ogr2ogr -skipfailures -f "MapInfo File" -lco overwrite=yes -lco launder=no -lco relaxedFieldNameMatch=yes -lco unsetDefault=yes "D:QGvw_CONFIRM_PavementCondition.tab" "MSSQL:Server=xxxx;Database=GIS_Test;Trusted_Connection=True" -sql "SELECT * FROM dbo.vw_CONFIRM_PavementCondition" -a_srs EPSG:28354 -t_srs EPSG:28354 -s_srs EPSG:28354
Warning 6: dataset
D:QGvw_CONFIRM_PavementCondition.tab does not support layer
creation option launder Warning 502: Field name 'Road Pavement
Maintenance Grade' contains invalid characters.
'Road_Pavement_Maintenance_Grade' will be used instead. Warning 502:
Field name 'Road Pavement Roughness' contains invalid characters.
'Road_Pavement_Roughness' will be used instead. Warning 502: Field
name 'Road Pavement Profile' contains invalid characters.
'Road_Pavement_Profile' will be used instead. Warning 502: Field name
'Road Pavement Rutting' contains invalid characters.
'Road_Pavement_Rutting' will be used instead. Warning 502: Field name
'Road Pavement Overall Condition' contains invalid characters.
'Road_Pavement_Overall_Condition' will be used instead.
Does ogr2ogr.main used within python have some additional functionality not available in the .exe? if so a solution in this would be fine as well.
sql-server ogr2ogr
add a comment |
On MSSQL tables/views that have field names with spaces or starting with a number we get the warning 502 re: replacing invalid characters with a _
As we re-injest some of these files into MSSQL and use them in other software we would like to keep the (poorly formatted) field names as otherwise we have to change every reference to the replaced fields. It could also affect AUTHORITY and Confirm etc that's used for asset management.
Is there a switch that allows us to do this?
Here's what I use
ogr2ogr -skipfailures -f "MapInfo File" -lco overwrite=yes -lco launder=no -lco relaxedFieldNameMatch=yes -lco unsetDefault=yes "D:QGvw_CONFIRM_PavementCondition.tab" "MSSQL:Server=xxxx;Database=GIS_Test;Trusted_Connection=True" -sql "SELECT * FROM dbo.vw_CONFIRM_PavementCondition" -a_srs EPSG:28354 -t_srs EPSG:28354 -s_srs EPSG:28354
Warning 6: dataset
D:QGvw_CONFIRM_PavementCondition.tab does not support layer
creation option launder Warning 502: Field name 'Road Pavement
Maintenance Grade' contains invalid characters.
'Road_Pavement_Maintenance_Grade' will be used instead. Warning 502:
Field name 'Road Pavement Roughness' contains invalid characters.
'Road_Pavement_Roughness' will be used instead. Warning 502: Field
name 'Road Pavement Profile' contains invalid characters.
'Road_Pavement_Profile' will be used instead. Warning 502: Field name
'Road Pavement Rutting' contains invalid characters.
'Road_Pavement_Rutting' will be used instead. Warning 502: Field name
'Road Pavement Overall Condition' contains invalid characters.
'Road_Pavement_Overall_Condition' will be used instead.
Does ogr2ogr.main used within python have some additional functionality not available in the .exe? if so a solution in this would be fine as well.
sql-server ogr2ogr
On MSSQL tables/views that have field names with spaces or starting with a number we get the warning 502 re: replacing invalid characters with a _
As we re-injest some of these files into MSSQL and use them in other software we would like to keep the (poorly formatted) field names as otherwise we have to change every reference to the replaced fields. It could also affect AUTHORITY and Confirm etc that's used for asset management.
Is there a switch that allows us to do this?
Here's what I use
ogr2ogr -skipfailures -f "MapInfo File" -lco overwrite=yes -lco launder=no -lco relaxedFieldNameMatch=yes -lco unsetDefault=yes "D:QGvw_CONFIRM_PavementCondition.tab" "MSSQL:Server=xxxx;Database=GIS_Test;Trusted_Connection=True" -sql "SELECT * FROM dbo.vw_CONFIRM_PavementCondition" -a_srs EPSG:28354 -t_srs EPSG:28354 -s_srs EPSG:28354
Warning 6: dataset
D:QGvw_CONFIRM_PavementCondition.tab does not support layer
creation option launder Warning 502: Field name 'Road Pavement
Maintenance Grade' contains invalid characters.
'Road_Pavement_Maintenance_Grade' will be used instead. Warning 502:
Field name 'Road Pavement Roughness' contains invalid characters.
'Road_Pavement_Roughness' will be used instead. Warning 502: Field
name 'Road Pavement Profile' contains invalid characters.
'Road_Pavement_Profile' will be used instead. Warning 502: Field name
'Road Pavement Rutting' contains invalid characters.
'Road_Pavement_Rutting' will be used instead. Warning 502: Field name
'Road Pavement Overall Condition' contains invalid characters.
'Road_Pavement_Overall_Condition' will be used instead.
Does ogr2ogr.main used within python have some additional functionality not available in the .exe? if so a solution in this would be fine as well.
sql-server ogr2ogr
sql-server ogr2ogr
asked 3 mins ago
GeorgeCGeorgeC
2,88132980
2,88132980
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f314671%2fogr2ogr-warning-502-field-name-yyy-xx-contains-invalid-characters-yyy-xx-w%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f314671%2fogr2ogr-warning-502-field-name-yyy-xx-contains-invalid-characters-yyy-xx-w%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown